Invoices and checkout
The planned tools for billing customers and bringing Reway into a checkout.
Planned capability. Availability and final details will depend on the release.
Invoices and checkout are planned ways to connect Reway payments with a business's existing customer workflow. They build on the same receiving preference: the business selects a supported output asset and network.
Smart invoices
The invoice generator is intended to produce a professional invoice linked to a payment. Proposed fields include an invoice ID, business and customer information, amount, description, issue date, due date, and payment link.
After payment is detected, the intended flow can update the invoice's status and provide a receipt or payment record. The final field set and automation will depend on the release.
| Invoice information | Purpose |
|---|---|
| Invoice ID and dates | Identifies the invoice and when payment is due. |
| Business and customer | Records who is billing whom. |
| Amount and description | Explains the goods or services being paid for. |
| Payment link | Connects the invoice to the payment flow. |
| Status and transaction reference | Connects billing records to the payment outcome. |
These are proposed invoice capabilities. They do not establish support for country-specific invoice or tax requirements.
Reway Checkout
Checkout is the intended purchase flow for merchants. A business could price a service and choose USDC on Base as its supported settlement preference. A customer could fund that payment using a different supported asset, with the route determined by the quote.
Possible integration forms include a hosted checkout, payment button, embedded widget, JavaScript or React integration, and API access. These are product directions rather than released integration instructions.
White-label checkout
White-label Checkout would let a business adapt the presentation with its logo, brand name, colors, and labels, while retaining Reway's payment infrastructure.
Brand customization would not remove the need to show clear payment amounts, receiving details, costs, and authorization requests.
What you can use as a starting point
Use the available payment link flow for a shareable payment experience. For embedded integrations, consult the API and SDK overview. No checkout embed snippet or production API contract is defined in this guide.