Decide who holds the funds
Some providers receive payments into an account they control and pay out later. Non-custodial options send settlement straight to a wallet you control.
Choosing a stablecoin payment setup
There are four common ways to accept stablecoins: publish a wallet address, install a store plugin, use a custodial payment processor, or use non-custodial hosted checkout. They differ in who holds the funds, how payments match orders, and how much your team builds and checks by hand.
Maintained by Payclave Product and Engineering. Updated .
Some providers receive payments into an account they control and pay out later. Non-custodial options send settlement straight to a wallet you control.
A shared wallet address leaves matching to you. Checkout sessions tie each payment to one order, amount, and expiry.
Reliable fulfillment needs verified, final payments and a signed event, not a screenshot or a browser redirect.
The simplest setup is to show customers a wallet address, the token, the network, and the amount. Funds go straight to your wallet and there is no provider fee. Everything else is manual: matching transfers to orders, checking the token contract and network, waiting for finality, and handling wrong amounts, late payments, and duplicates.
This works for rare, individually arranged payments where someone on your team checks each transfer. It breaks down once several customers pay the same address.
E-commerce platforms such as WooCommerce and Shopify have crypto payment extensions. A plugin is quick to add to an existing store, but it inherits the custody model, supported networks, and fees of the provider behind it. Read the provider's terms, not only the plugin listing, to learn where funds land and who controls them.
Custodial processors receive the customer's payment into an account they operate, then pay the merchant out in crypto or fiat. That can suit businesses that want automatic conversion to local currency. The trade-off is that the provider holds funds between payment and payout, which adds counterparty risk, account limits, and onboarding requirements.
Non-custodial hosted checkout gives each order its own checkout session while settlement goes directly to a wallet you control. Payclave works this way: your backend creates a checkout session, the customer pays from a connected wallet or one-time Scan or copy instructions, and USDC or USDT on Polygon reaches your settlement wallet. Payclave verifies the payment onchain and sends a signed webhook before you fulfill.
Because Payclave never holds the funds, it does not convert stablecoins to fiat. Businesses that need fiat settlement must handle conversion separately.
Use the same checklist for every option so the comparison stays about your requirements rather than marketing claims.
USDC and USDT are both dollar-pegged stablecoins issued by different companies. Customers often hold one but not the other, so accepting both, or accepting payment routes that convert between them, widens who can pay. For your own books, pick the settlement token your treasury and accounting already use. Payclave settles in either USDC or USDT on Polygon, chosen per settlement wallet.
For the complete request fields, response schemas, error codes, and event types, use the Payclave API reference.
Related guides
Compare hosted stablecoin checkout with manual wallet instructions across customer experience, order matching, verification, settlement, and fulfillment.
Read the guideCreate a Payclave stablecoin checkout session from your backend, use idempotency correctly, redirect to hosted checkout, and confirm payment safely.
Read the guideHow Payclave verifies stablecoin settlement: confirmation, recipient, token, amount, expiry, and duplicate transaction use before marking an invoice paid.
Read the guideTest the workflow
Use test keys and the API playground to verify checkout creation, payment status, and signed webhook handling.