Hosted checkout

What you configure

Hosted checkout gives you a production-ready payment surface without building on-chain UX yourself. Most teams configure storefront/checkout via merchant endpoints, then create payment intents from backend order events.

• Allowed quote chains and fiat options.
• Available fiat currencies and corridors.
• Storefront presentation (logo, theme, return URLs).

Merchant checkout endpoints

The following are merchant-authenticated. Public payer-facing variants live under the same root but do not require credentials.

• POST/v1/merchant/checkout/storefrontsCreate storefront
• POST/v1/merchant/checkout/qrcodesCreate QR code
• GET/v1/merchant/checkout/quote-chain-optionsAllowed quote chains
• GET/v1/merchant/checkout/fiat-currency-optionsAvailable fiat currencies

Developer pattern

• Use merchant checkout quote-chain options before exposing checkout token selectors.
• Display the returned deposit address or hosted checkout URL to the payer.
• Use webhooks for state transitions, never poll the session every second.