USDT receiving asset
Configure a USDT receiving wallet on Polygon so checkout sessions target the asset used by your merchant operation.
USDT checkout for merchants
Create a hosted checkout for each order, let the customer complete a supported wallet or scan/copy payment flow, and receive a verified invoice status when USDT settlement reaches the wallet you configured.
Configure a USDT receiving wallet on Polygon so checkout sessions target the asset used by your merchant operation.
Keep the amount, merchant reference, payment attempt, and final status connected instead of reconciling a shared address manually.
Use authenticated webhook events and API reads to update the order only after Payclave verifies settlement.
From order to payment record
Configure the Polygon wallet that should receive merchant USDT settlement and complete the required merchant setup.
Send the trusted amount, reference, and idempotency key from your backend and receive a hosted checkout URL.
The customer connects a supported wallet or follows the one-time scan/copy instructions shown for the checkout.
Payclave records the settlement evidence, updates the invoice outcome, and delivers the signed event to your endpoint.
A transaction hash by itself does not identify which order should be fulfilled. Payclave creates a checkout session and invoice around the merchant's trusted amount and reference so the payment record can be reconciled with the correct customer order.
Expiry and amount outcomes are explicit. A payment received after the allowed window or for the wrong amount is recorded for review instead of silently becoming a successful order.
Payclave does not collect USDT into a pooled merchant account or require a later Payclave payout. The configured receiving wallet is the merchant's destination for USDT settlement on Polygon.
Because the merchant controls that wallet, the merchant also remains responsible for wallet security, access recovery, and any refund sent after a completed payment.
The API exposes checkout-session, invoice, and payment status. Signed webhook deliveries notify the merchant backend, with attempt records and retry state available for operations and troubleshooting.
The recommended integration verifies the webhook signature and uses the event or invoice identifier as an idempotency boundary before changing an order to paid.
Frequently asked questions
Yes. Your backend can create a Payclave checkout session and redirect the customer to its hosted URL. JavaScript and React button integrations are also available for supported use cases.
The current merchant receiving setup supports USDT on Polygon. Customers may be shown other supported payment routes, but the merchant invoice keeps its configured receiving asset explicit.
No merchant account is required for the customer. The customer opens the hosted checkout and completes the supported wallet or scan/copy payment flow.
Payclave records underpaid or overpaid outcomes separately from a correctly paid invoice so the merchant can review the payment without treating it as an automatic success.
Explore Payclave
Accept stablecoin payments with Payclave hosted checkout sessions, direct wallet settlement, independent onchain verification, and signed webhooks.
Learn moreUse a non-custodial crypto checkout where stablecoin settlement goes to the merchant's configured wallet and payment status is verified independently.
Learn morePayclave pricing: test mode is free, with a flat 0.7% fee per live stablecoin payment and no monthly or setup fee.
Learn moreTest the flow
Use test keys, the API playground, and signed webhook examples to validate the complete order-to-payment flow.