API and SDK
The planned developer interface and the payment concepts you can prepare for today.
Planned capability. Availability and final details will depend on the release.
Reway's planned API and SDK would let applications create and track cross-chain payments using the same underlying payment model as the app.
This page introduces the planned capabilities. Endpoint references, SDK packages, authentication details, and webhook contracts will need to accompany the public release.
The intended developer workflow
An application would describe a payment: who should receive it, how much, and the preferred settlement asset and network. The payer's supported asset would fund a route that satisfies those receiving preferences.
The integration would then present the quote, handle the required user authorization, and track the final payment status.
Planned capabilities
| Capability | Intended use |
|---|---|
| Create payments and links | Start a payment flow from your application. |
| Request a route | Obtain the supported route and payment quote. |
| Configure settlement preferences | Define the receiving asset and network. |
| Retrieve status and transactions | Track the result and inspect transaction references. |
| Receive webhooks | Notify your system about payment updates. |
| Embed checkout | Keep the payment experience close to your product. |
| Manage API access and logs | Support operating and reviewing an integration. |
What you can prepare now
Decide where your product needs a payment, how you will associate it with an order or customer, and what the recipient wants to receive. Plan how your interface will distinguish a payment being prepared, being processed, and being confirmed.
These are design questions you can work through before an API contract is published. They are not API field names or a confirmed event schema.
Read how Reway works for the payment model, business payments for settlement needs, and dashboard and activity for the information a payment record should explain.
Integration details to wait for
A production integration needs published details for endpoints, credentials, supported networks, request validation, error behavior, idempotency, webhook verification, and final payment states.
For a shareable flow using the app, start with payment links.