Configured USDC settlement
Keep the settlement token explicit with a USDC wallet on Polygon linked to the invoice.
USDC checkout for merchants
Turn an order amount into a Payclave checkout session, direct the customer through a supported payment route, and receive USDC in your Polygon settlement wallet.
Keep the settlement token explicit with a USDC wallet on Polygon linked to the invoice.
Send customers to a Payclave-branded page instead of building wallet connection and payment status UI from scratch.
Review payment outcomes, transaction details, webhook delivery status, and delivery attempts from the dashboard and API.
From order to payment record
Add the USDC settlement wallet on Polygon and keep test and live credentials separate.
Your backend supplies the authoritative order amount and reference and receives the public checkout URL.
Payclave displays the connected-wallet or Scan or copy options available for that checkout without exposing merchant secrets.
The merchant verifies the signed webhook and fulfills only after the invoice has the appropriate paid status.
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.
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.
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
Create the Payclave checkout session from your backend after the order amount is finalized, then redirect the customer to the returned checkout URL and process the signed payment webhook on your server.
No. Payclave does not provide fiat settlement or exchange services. The merchant receives the configured stablecoin settlement in its own wallet.
Yes. Test mode has separate keys and records so a team can validate session creation, the hosted flow, status handling, and webhook verification before live activation.
No successful verification should reuse the same chain and transaction hash for another invoice. Duplicate-use checks are part of the payment verification process.
Explore Payclave
Accept stablecoin payments with Payclave-hosted checkout sessions, direct-to-wallet settlement, independent onchain verification, and signed webhooks.
Learn moreIntegrate stablecoin checkout with Payclave APIs and SDKs for checkout sessions, invoices, verified payment status, and signed webhook delivery.
Learn moreAccept USDT payments with Payclave-hosted checkout, USDT settlement on Polygon, independent onchain verification, and signed webhooks.
Learn moreTest the flow
Use test keys, the API playground, and signed webhook examples to validate the complete order-to-payment flow.