1.5% and No Chargebacks: What Stripe's Stablecoin Checkout Costs, and What It Cannot Do

Stripe charges 1.5% of the transaction for stablecoin payments and 2.9% plus 30 cents for a domestic card. On a $100 order that is $1.50 instead of $3.20, and because there is no fixed component, the stablecoin rate is lower at every order value. Price, then, is not the decision. Four documented limits are: a cap of 10,000 USD per transaction, refunds that return to the customer's wallet as stablecoins rather than to a card, no manual capture, and no dispute process. If one of those collides with how you sell, the cheaper rate is unusable no matter how good the arithmetic looks.

The fee arithmetic at five order values

Both columns come from Stripe's published US pricing page, read on 30 July 2026. The card column is 2.9% plus $0.30 for a domestic card. The stablecoin column is 1.5% with conversion, wallet screening and network fees included. The multiplication is ours.

That table understates the gap for anyone selling across borders. Stripe adds 1.5% for an international card and a further 1% when currency conversion is required, so a European customer paying a US business by card is on 5.4% plus 30 cents, against the same flat 1.5%. It also leaves out the $15 dispute fee that Stripe charges for each dispute received, refunded only if you win. We work through the rest of the per-rail comparison in the payment link tax.

The four limits, and the business each one rules out

The manual capture gap is the one that catches people out. If your checkout authorises a card at order time and captures when the item ships, that flow does not exist here. The customer pays once, immediately, and your only lever afterwards is a refund.

No chargebacks cuts in two directions

Stripe's documentation is direct about it: "you won't have disputes that turn into chargebacks, with funds withdrawn from your Stripe account." For a merchant who has been through a dispute cycle, that reads like the whole point. No $15 dispute fee, no evidence submission, no reserve pressure of the kind we described in why processors freeze your money, and no ratio creeping toward a network monitoring threshold.

The other side is that the card network was also doing something for your customer. Strip it out and your refund policy is the entire consumer protection layer on that order. A buyer who feels wronged has your support inbox and nothing else. That is survivable for repeat B2B customers who know you. It is a harder sell to a first-time buyer of a $400 consumer product, and it makes the terms you publish do real work rather than sit as boilerplate. Our piece on designing a returns policy is the right companion read before you offer this to consumers. The flip side of the same coin is worth stating plainly: the fraud you would previously have absorbed as a chargeback now stays absorbed by the customer, which is exactly why it should be reserved for orders where you have some relationship.

What settles, and where

You are not holding tokens. Payments settle into your Stripe balance in your local currency, converted automatically, so your bookkeeping looks the same as a card sale. Accepted tokens are USDC on Tempo, Ethereum, Solana, Polygon and Base, plus USDP on Ethereum and Solana and USDG on Ethereum, the last two US only. Payout timing varies by network.

Acceptance is generally available for US businesses. Hong Kong, Mexico, Switzerland and 29 European countries including Germany, France, Spain, Italy, the Netherlands, Ireland, Poland and the Nordics are listed as private preview, which means you ask rather than switch it on. Your customers can pay from anywhere outside sanctioned countries, which is the actual attraction: a buyer in a country where your card acceptance rate is poor gets a route that does not depend on their issuer.

Switching it on this afternoon

1. Open Dashboard, Settings, Payment methods and enable the crypto payment method.
2. Check your surface is covered. Stripe lists Checkout, Elements, Invoicing, Payment Links and Billing, so subscriptions and invoices both work.
3. If you run Connect, enable the method on each connected account. It is not inherited from the platform.
4. Run one test purchase yourself. The customer leaves your checkout for crypto.stripe.com, picks a currency and network, connects a wallet, and returns. Time that detour, because it is a real drop-off risk and the reason you leave cards enabled as the default.
5. Rewrite one line in your refund terms: refunds on this method return as stablecoins to the wallet used, not to a card or a bank account.
6. Set a maximum. If your average order is $200, there is no reason to expose the method on a $9,000 invoice where a single failed refund conversation costs more than the fee saved.

The rule we would apply

Enable it as a second option, never the default, when all three are true: your typical order sits between roughly $200 and $9,999, you capture funds at the moment of purchase rather than later, and your refund rate is low enough that returning tokens to a wallet is an edge case rather than a weekly conversation.

The saving is real at that shape. A consultancy sending twenty invoices a month at $3,000 pays $87.30 per invoice on cards and $45.00 on stablecoins, which is $846 a month, about $10,000 a year, for adding one payment method to an invoice template. A shop selling $45 consumer goods with a 12% return rate saves 65 cents an order and buys itself a refund process its customers did not ask for. Same rate, two completely different answers.