Hosted stablecoin checkout

Accept stablecoin payments with a checkout built for merchant operations.

Payclave gives merchants a hosted checkout, invoice records, payment verification, and webhook delivery while stablecoins settle to the receiving wallet the merchant configures. Customers get a focused payment experience; merchants get a reliable record before fulfillment.

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 receiving wallet instead of requiring 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. 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. 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. 3

    Verify the settlement

    Transaction, recipient, token, chain, amount, expiry, confirmation, and duplicate-use checks determine the payment outcome.

  4. 4

    Fulfill from a signed event

    Your backend verifies the Payclave webhook signature, handles the event idempotently, and fulfills the matching order.

A checkout flow instead of manual wallet instructions

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.

A narrow receiving setup with flexible customer payment

Merchants configure a USDC or USDT receiving wallet on Polygon. Customers can use supported source tokens through wallet checkout or generate one-time scan/copy instructions for supported deposit networks, while the merchant-facing invoice keeps one receiving asset and amount.

That separation keeps the customer payment choice inside checkout without turning Payclave into a merchant wallet or exchange. Payclave orchestrates the experience and verifies the resulting settlement record.

Payment operations your backend can trust

Checkout sessions, invoices, payment records, webhook deliveries, retry attempts, and audit events 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

Questions about stablecoin checkout.

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 merchant or customer funds?

No. Payclave is non-custodial and does not hold funds or manage private keys. Settlement is sent to the receiving wallet configured by the merchant.

Which stablecoins can a merchant receive?

The current receiving-wallet setup supports USDC or USDT on Polygon. Supported customer payment sources can 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.

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.