Create a payment request
Availability and preparation
Merchant routes for creating, retrieving, listing and closing Checkouts are confirmed; actual access depends on your account and environment. No-code dashboard tools and reusable payment links remain unconfirmed. Confirm payments through server-side queries without depending on Webhooks.
Prepare a business order ID, trusted amount, pricing currency, available payment method and server credentials. If you operate the business rather than its integration, give this guide to your technical owner. Never put an API Key in a web page, chat or customer form.
Create and share the payment entry
- Save the order, expected amount and currency in your own system. Derive prices from trusted server records; the customer's browser must not override them.
- Retrieve the payment methods available to the account. Use only complete method, asset and network combinations actually returned. IPP and direct ERC-20 transfers are different methods.
- Before creating Checkout, persist the payment attempt, request parameters and idempotency key. This key identifies the same operation across retries; use a new key only for a new business operation.
- Save the returned Checkout ID, real URL and order association. One business order can have multiple Checkouts; an order ID alone does not deduplicate creation.
- Share that URL with the intended payer. Authenticate access to your merchant order page before showing its payment status. Do not construct a Checkout URL yourself.
- Query the saved Checkout from your server. Verify order association, amount, currency, main status and funds exceptions, then arrange one fulfillment using the order guide.
Your technical owner should verify request formats in the developer center's commercial payments quickstart. This page does not supply unconfirmed endpoints or parameters.
Recover after an interruption
| Situation | Next action |
|---|---|
| Creation times out before an ID is received | Find the saved operation and recover with the original key and parameters under the applicable idempotency rules; do not immediately create another attempt |
| Checkout ID exists but retrieval fails | Keep the result unresolved and resume querying; do not label it unpaid |
| Customer clicks pay repeatedly | Query the original session; show a waiting message for processing instead of requesting another transfer |
Customer returns to an open Checkout | Query its latest state and resume the original entry while valid |
| Session has failed or closed | Check the reason and possible late funds before deciding whether to create a new session |
| No methods or insufficient access | Check environment, credentials and account availability; do not improvise another network or asset |
Keep a payment record
Keep the order's association with every attempt, expected values, latest query time, exception outcome and unique fulfillment record. return_url is the destination of the return-to-merchant button, not proof of receipt or a promise of automatic redirection. Read payment exceptions before delivery and Checkout and payment links for dashboard tools.