Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.stablepayfi.ai/llms.txt

Use this file to discover all available pages before exploring further.

Stablecoin Checkout is StablePay’s hosted checkout product for one-time stablecoin payments. It gives merchants a payer-facing checkout experience for USDT and USDC without requiring the merchant to build wallet connection, chain selection, transaction monitoring, QR/address payment logic, or exception handling from scratch. Merchants create a checkout session from their backend, redirect the payer to a StablePay-hosted checkout page, and receive payment status updates through the dashboard and webhooks. StablePay handles the checkout UX, wallet and transfer instructions, on-chain monitoring, payment status detection, and exception visibility.

When to use it

Use Stablecoin Checkout when a customer is paying once for a defined purchase or balance update. Common fit examples include:
  • Ecommerce orders from a website or custom storefront.
  • App or game top-ups where the payer needs a clear hosted payment page.
  • Digital goods, content, services, bookings, and one-time account credits.
  • Custom commerce flows where your backend owns order creation and fulfillment.
  • Merchant systems that need stablecoin payment acceptance without building wallet infrastructure.

Try the demo

You can try a demo checkout mall here:

Checkout demo mall

Open the demo mall to see a one-time StablePay Checkout flow from a payer’s perspective.
For recurring billing, use Stablecoin Subscriptions. For a bill addressed to a specific customer, use Invoicing. For a reusable public payment page, use Payment Links.

How it works

  1. Your backend creates a checkout session with amount, currency, order context, and redirect URLs.
  2. StablePay returns a hosted checkout URL.
  3. The payer opens checkout and selects a supported payment method, such as wallet connection or transfer / QR-style payment.
  4. StablePay presents payer-facing instructions and monitors the on-chain payment.
  5. StablePay updates the session status and sends webhook events so your system can fulfill the order.
The merchant experience is intentionally simple: create a session, redirect the payer, listen for payment status, and fulfill after confirmation.

Key capabilities

CapabilityDescription
Hosted checkoutStablePay hosts the payer-facing payment page and payment instructions.
One integration for multiple payment methodsA single checkout integration can present supported wallet and transfer-style payment options.
Wallet pay and QR paymentPayers can connect supported wallets or pay by scanning/copying the displayed payment details.
Chain and payment monitoringStablePay monitors the relevant on-chain payment and updates the session lifecycle.
Exception visibilitySessions can surface states such as paid, underpaid, overpaid, expired, and canceled.
WebhooksMerchants can synchronize fulfillment, receipts, and internal order status.
Refund supportEligible completed payments can be refunded through the payment refund workflow.

Payment status and exceptions

Stablecoin Checkout is built for the realities of on-chain payments. Payers may send too little, send too much, pay after a session expires, or cancel before paying. StablePay detects and exposes these outcomes so merchants can avoid treating every chain transaction as a simple success or failure. Use webhook events and dashboard status together to decide when to fulfill, when to contact the customer, and when a manual review is needed.

Important notes

  • Stablecoin Checkout is for one-time payments only. It does not create subscriptions or future automatic charges.
  • Payers do not need to create a StablePay account to complete payment.
  • Blockchain payments are final once confirmed. StablePay can provide transaction records and event logs for merchant-customer communication.
  • StablePay Checkout wallet and transfer payment coverage is maintained in Supported Wallets.
  • Detailed network, currency, and regional coverage is maintained in Reference pages instead of repeated here.
Last modified on April 23, 2026