USDC checkout for merchants

Accept USDC payments through a hosted merchant checkout.

Payclave lets a business accept USDC online through a hosted checkout and receive USDC on Polygon directly in a wallet it controls. Your backend creates one checkout session per order. The customer pays from a connected wallet or with one-time Scan or copy instructions. Payclave verifies the payment onchain before the invoice is marked paid and your signed `invoice.paid` webhook fires. The fee is 0.7% per completed live payment; test mode is free.

Configured USDC settlement

Keep the settlement token explicit with a USDC wallet on Polygon linked to the invoice.

Hosted customer experience

Send customers to a Payclave-branded page instead of building wallet connection and payment status UI from scratch.

Operational evidence

Review payment outcomes, transaction details, webhook delivery status, and delivery attempts from the dashboard and API.

From order to payment record

A checkout flow with a verifiable outcome.

  1. 1

    Configure the merchant

    Add the USDC settlement wallet on Polygon and keep test and live credentials separate.

  2. 2

    Create the checkout session

    Your backend supplies the authoritative order amount and reference and receives the public checkout URL.

  3. 3

    Present the supported payment flow

    Payclave displays the connected-wallet or Scan or copy options available for that checkout without exposing merchant secrets.

  4. 4

    Act on verified payment

    The merchant verifies the signed webhook and fulfills only after the invoice has the appropriate paid status.

Add USDC without rebuilding the order system

Payclave checkout sessions fit alongside an existing cart, invoice, or order service. The merchant system remains responsible for price and inventory, then creates a checkout session with the trusted amount when the customer chooses stablecoin payment.

The returned checkout URL can be opened from a normal payment button. Status can be read through the API and received through signed webhooks, so the existing fulfillment workflow stays in control.

Separate customer payment choice from merchant reconciliation

The customer-facing flow may support different source tokens or networks. The merchant record still identifies USDC as the settlement token, the invoice amount, and the final settlement evidence used for reconciliation.

This keeps payment flexibility at checkout from creating ambiguous internal records for finance, support, or engineering teams.

Verify before the order changes state

Payclave does not trust a browser callback as payment proof. Verification checks the transaction hash, destination, token, chain, amount, timing, confirmation state, and duplicate transaction use before the invoice becomes paid.

Webhook attempt logs and replay controls help operators recover when the merchant endpoint is temporarily unavailable without losing the payment record.

Frequently asked questions

Accept USDC payments: common questions.

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.