Stablecoin payments for ecommerce

Vendor material on this subject is a monoculture: lower fees, no chargebacks, global reach, the future of commerce. Every claim is true and none of them tells you whether it applies to your store.

We maintain a directory of merchants that actually do this, verified from their own documentation. Here is what that data says, including the parts that argue against adopting it.

What the adopting categories have in common

Look at where stablecoin acceptance is concentrated in our directory — hosting, VPNs, domain registrars, gift cards, gaming credit — and a pattern is immediate. These are not “tech-forward” categories. They share four properties:

1. Digital or instantly-fulfilled goods. No shipping, so no delivery dispute.
2. Genuinely global customers. Buyers whose cards routinely fail cross-border.
3. A real fraud and chargeback problem. Digital goods are the classic chargeback-fraud target.
4. Enough order value that a flat network fee is negligible.

The full picture is on the Stablecoin Spend Index, and the category distribution chart is embeddable if you want to use it in a business case.

That fourth point is the one nobody mentions, and it is decisive. A network fee does not scale with the payment: sending $8 and sending $800 cost the same gas. So stablecoin payments get cheaper as a percentage the larger they get — the exact opposite of card processing, where the percentage is fixed and the flat component is small.

Which means the honest test is not “am I an innovative brand?” It is:

Do I sell something expensive, digital, internationally, to people who get defrauded or declined?

Four yeses and this is a serious operational improvement. Four noes and it is a press release.

The chargeback question, which is the real one

Fee comparisons dominate the marketing and are the smaller effect. The larger one is that a stablecoin payment cannot be reversed.

For a store with a 0.1% dispute rate, that is worth little. For a store selling digital goods into markets where friendly fraud is endemic, it can exceed the entire processing fee — and it removes the review overhead, the evidence submission, and the risk of breaching a card network’s dispute threshold.

Two things have to be said alongside that, because they are the cost of the benefit:

Your customer loses the same protection. They are paying an internet business irreversibly with no issuer behind them. That asymmetry is the whole product, and pretending otherwise is how a merchant ends up with angry customers rather than an efficient payment method.

Say it at checkout. Merchants who state their crypto refund position clearly do better than merchants who bury it. SEAGM states there are no refund options on cryptocurrency payments. PureVPN excludes crypto from its 31-day money-back guarantee. Both policies are unfavourable and both are honestly published, which is the reason neither generates surprise.

Choosing a coin, from the data

The Spend Index shows USDC accepted at more merchants in our directory than USDT, which inverts what you would predict from market size. The reason is regulatory rather than preferential: under MiCA, EU payment gateways withdrew USDT for EU-established merchants. Cherry Servers documented its own forced migration and set a hard cutover date of 1 April 2025.

The practical consequence for a store:

• Selling into the EU? You need USDC. Your gateway may not even offer USDT.
• Selling into Asia, LatAm, Turkey, Nigeria? USDT is what your customers hold, usually on Tron, usually cheaply. Not offering it means telling them to swap first, which is the most expensive step in the whole transaction — see stablecoin payment fees.
• Selling to both? Take both. Most crypto-native gateways carry both; Stripe and Shopify Payments carry only USDC.

Our USDC vs USDT comparison has the full argument.

Platform by platform

Full comparison in the gateway guide.

The five practical decisions

Networks. Enable Base, Solana and Polygon alongside Ethereum. Mainnet-only is the most common avoidable mistake: the flat gas cost can be a meaningful share of a small basket, your customer pays it, and some do not complete.

Settlement. Convert to fiat unless you have a named reason to hold the asset. “Dollar-denominated treasury without a US bank account” is a good reason. “Crypto is the future” is not a treasury policy.

Refunds. Write the policy before launch. A refund is a fresh outbound transfer to an address the customer gives you, on a chain they must specify correctly, and getting it wrong loses the money. See how stablecoin refunds work.

Presentation. Label the option properly. “Pay with USDC or USDT — on Base, Solana or Polygon” converts better than a bare crypto icon, because it tells a holder that their specific asset works.

Measurement. Set a threshold in advance — a share of orders, or a reduction in disputes — and review at ninety days. Payment methods accumulate; one nobody uses is still a line in your checkout and a page in your PCI scope.

When not to bother

Say it plainly, because nobody selling gateways will: if you sell moderately priced physical goods to domestic customers who pay by card without friction, stablecoin acceptance will produce a rounding error in your order volume and a real amount of operational work. There are stores in this position that have adopted it, and the honest description of what they got is a press release.

The case is strong when your customers are international, your goods are digital, your average order is large, or your chargeback rate is a line item somebody complains about. If none of those is true, the correct answer is not yet.

Already accepting? Get listed — it is free, we verify from your own documentation, and payment never affects a verification status.