How to accept USDC on your website

Search results for this question are mostly gateway advertisements. The genuinely useful framing is different, and it comes down to one question you should answer before comparing any providers:

Do you want to end up holding USDC, or holding dollars?

Everything else — which provider, which integration, how much work — follows from that.

• Dollars. You want lower processing fees and no chargebacks, and you want the money in your bank account like every other sale. Use a gateway that converts on receipt. This is most businesses.
• USDC. You want a dollar-denominated balance you control, possibly because banking in your jurisdiction is slow or expensive, or because you pay suppliers in stablecoins. This needs a self-custody or crypto-settling gateway and a real answer about key management.

Answer that, then pick from the four integration shapes below.

The four ways

1. Hosted gateway checkout — the default

You create a payment through the provider’s API, redirect the customer to a page the provider hosts, and receive a webhook when the payment confirms. The provider handles wallets, network selection, exchange rates, expiry and underpayment.

Effort: an afternoon. Fee: the provider’s rate, broadly 0.5%–1.5%. You never touch a private key.

This is what almost every merchant in our directory does, and it is the right answer unless you have a specific reason to do otherwise. Compare providers in our gateway guide and the payment provider directory.

The one implementation detail that matters: verify the webhook signature and treat the webhook, not the redirect, as the source of truth. A customer closing the tab after paying must still get their order. A customer replaying your success URL must not.

2. Your existing processor — the least work of all

If you already run Stripe, stablecoins are a dashboard toggle rather than an integration. The money lands in your existing balance, in fiat, and reconciles with everything else.

The constraints are real and worth reading before you plan around it: USDC but no USDT, a $10,000 per-transaction customer limit, fiat settlement only, and accepting is generally available only in the US. We cover all of it in how to accept stablecoins with Stripe.

On Shopify, Shopify Payments offers USDC natively — see Shopify stablecoin payments.

3. A plugin, if you are on WooCommerce or similar

Most gateways publish plugins for the common ecommerce platforms. Effort drops to configuration. The trade is that you inherit the plugin’s update cadence and its assumptions, and payment plugins are a place where an unmaintained one becomes a liability rather than merely stale. Check the last release date before installing, and check it again in six months.

4. Direct wallet payment — more work than it looks

You publish an address, watch the chain, and credit the order when funds arrive. No gateway, no fee, full custody.

It sounds simple and is not. You are now responsible for generating a unique address per order (reusing one makes reconciliation guesswork), handling underpayment and overpayment, deciding confirmation depth, pricing the invoice against a moving quote, and — the part people underestimate — securing keys for an account that receives money continuously.

Several hosting providers in our directory do run something like this successfully. It suits businesses where crypto revenue is a large share of total revenue and the engineering is justified. For a shop adding a payment option, it rarely is.

Which networks to enable

Enable several. There is very little cost to you and a large cost to your customer if you do not.

Accepting only Ethereum mainnet is the most common avoidable mistake. The fee is flat per transaction, so on a $20 order it can be a meaningful fraction of the purchase — see stablecoin payment fees. Your customer pays it, notices, and sometimes does not complete.

What to decide before you launch

The refund policy, in writing. This is the one most merchants postpone and it is the one that generates complaints. A stablecoin payment is irreversible, so a refund is a new outbound transfer to an address the customer supplies — and if they supply an address on the wrong chain, the money is gone. Decide whether you refund in stablecoin, in fiat, or in store credit, and publish it.

Merchants who state an unfavourable policy clearly do better than merchants who leave it implicit. SEAGM says outright that there are no refund options on cryptocurrency payments. It is a worse policy than most, honestly disclosed, and that disclosure is a point in their favour.

What you tell the customer at checkout. They are giving up their chargeback. Saying so costs you nothing and buys trust; letting them discover it during a dispute costs you the customer.

The compliance position. Receiving crypto has obligations that vary a great deal by jurisdiction, and accounting treatment differs from a card sale even when you convert immediately. This is a question for your accountant and, depending on where you are, your lawyer — not for a guide on a directory site, and we are not going to pretend otherwise.

What you actually gain. Lower fees than cards, no chargebacks, instant settlement, and customers who could not pay you before. Our stablecoin payments vs credit cards comparison puts numbers on it.

The short version

Most businesses should enable a hosted gateway that converts to fiat, turn on Base, Solana and Polygon alongside Ethereum, verify the webhook rather than the redirect, publish a refund policy before launch, and say plainly at checkout that the payment is final.

That is a day of work and it is genuinely most of the value. The elaborate versions — self-custody, direct wallet integration, holding a stablecoin treasury — are worth doing when you have a reason you can name, and are overhead until then.

Ready to be listed once you are live? Submit your business — it is free, and we verify from your own documentation.