What is a stablecoin checkout?

A stablecoin checkout is a customer-facing payment flow that attaches a stablecoin payment to an order or invoice. Payclave adds the hosted page, payment instructions, verification, status records, and webhook delivery needed to operate that flow.

Does Payclave hold customer payments or merchant settlement?

No. Payclave is non-custodial and does not hold customer payments or merchant settlement. It never receives, stores, or has access to private keys. Settlement reaches the wallet configured by the merchant.

Which stablecoins can a merchant receive?

Merchant settlement currently supports USDC or USDT on Polygon. Customer payment options vary by the checkout route and connected wallet.

How should a merchant know when to fulfill?

The merchant backend should verify a signed payment webhook, handle the event idempotently, and confirm the matching invoice status through the API when appropriate. A browser redirect alone is not proof of payment.

Hosted stablecoin checkout

Accept stablecoin payments with a checkout built for merchant operations.

A stablecoin checkout is a payment page that ties one stablecoin payment to one order: a fixed amount, a merchant reference, an expiry, and a verified final status. With Payclave, customers pay with supported tokens they already hold, and the merchant receives USDC or USDT on Polygon in its own settlement wallet. Payclave never holds the funds.

Start in test mode Read API docs

Hosted checkout

Create a checkout session and send the customer to a Payclave-branded payment page with an amount, reference, and expiry.

Direct settlement

Payments settle to the configured settlement wallet without a later Payclave payout step.

Verified status

Payclave checks settlement independently before an invoice becomes paid and a fulfillment webhook is delivered.

From order to payment record

A checkout flow with a verifiable outcome.

1
Create a checkout session
Your server sends the trusted order amount and reference with a secret API key, or a limited browser integration uses a publishable key.
2
Let the customer choose how to pay
The hosted page supports a connected-wallet flow or scan/copy payment instructions for supported networks.
3
Verify the settlement
Transaction, recipient, token, chain, amount, expiry, confirmation, and duplicate-use checks determine the payment outcome.
4
Fulfill from a signed event
Your backend verifies the Payclave webhook signature, handles the event idempotently, and fulfills the matching order.

Why not just share a wallet address?

A reusable wallet address in an order confirmation leaves the merchant to reconcile amounts, networks, transaction hashes, and late payments by hand. A Payclave checkout session keeps those details attached to a single order and gives the customer one canonical payment URL.

The invoice remains pending while payment is in progress. It moves to a paid, underpaid, overpaid, expired, failed, or cancelled outcome based on evidence recorded for that checkout, not on a browser success screen alone.

What does the merchant receive?

Merchants receive exactly one settlement token per wallet: USDC or USDT on Polygon. Customers may pay from other supported tokens or networks; the invoice still records a single settlement token and amount. Customers can use supported source tokens through wallet checkout or generate one-time Scan or copy instructions for supported deposit networks.

That separation keeps the customer's payment choice inside checkout without turning Payclave into a custodial wallet or exchange service. Payclave coordinates the experience and verifies the resulting settlement record.

What records does each payment create?

Checkout sessions, invoices, payment records, webhook delivery status, and latest attempt details remain available in the merchant dashboard and API. Idempotency keys protect session creation, while signed webhooks let the merchant authenticate status changes.

Test mode is separated from live mode so teams can exercise checkout creation, webhook handling, and fulfillment logic before accepting a live stablecoin payment.

Frequently asked questions

Stablecoin checkout: common questions.

Explore Payclave

Test the flow

Create a checkout session before you change your production stack.

Use test keys, the API playground, and signed webhook examples to validate the complete order-to-payment flow.

Open API playground Start merchant setup

Accept stablecoin payments with a checkout built for merchant operations.

Hosted checkout

Direct settlement

Verified status

A checkout flow with a verifiable outcome.

Create a checkout session

Let the customer choose how to pay

Verify the settlement

Fulfill from a signed event

Why not just share a wallet address?

What does the merchant receive?

What records does each payment create?

Stablecoin checkout: common questions.

Continue planning your integration.

Accept USDT payments

Accept USDC payments

Stablecoin payment API

Create a checkout session

Checkout vs wallet transfers

Create a checkout session before you change your production stack.