A card chargeback is a reversal you don't control. A stablecoin payment is final the moment it confirms. That single difference rewrites the spreadsheet.
Most stores don't lose money on fraud. They lose it on friendly fraud — the customer who got the goods, then told their bank they didn't. The bank sides with the cardholder, claws the money back, and adds a fee on top. You're out the product, the shipping, and the dispute charge, all at once.
A stablecoin checkout doesn't have that lever. When a USDT or USDC payment confirms on-chain, it's settled. No issuer sits behind the customer to reverse it sixty days later. That changes the math, and it changes how you have to think about disputes and refunds. This is the version of that conversation we'd give a store before they flip the rail on.
What a card rail actually costs you
The headline cost of a card chargeback is the disputed amount. The real cost is the stack underneath it:
- The disputed transaction — clawed back in full.
- The dispute fee — charged whether you win or lose.
- The goods — already shipped, rarely returned.
- The chargeback ratio — too many and your processor raises rates or drops you.
That fourth one is the quiet killer. A store can be profitable on a per-order basis and still get terminated because its dispute ratio crossed a threshold it never watched. The reversal isn't an event; it's a standing liability on every card order for months after the sale.
What confirmation finality removes
On-chain settlement deletes items 1 and 2 outright. There is no issuer to reverse the payment and no per-dispute fee, because there is no dispute mechanism baked into the rail. When a payment to your e-commerce checkout confirms, the funds are yours.
That's not a loophole. It's the property the rail was built on. A confirmed BTC, ETH, or stablecoin transfer is irreversible by design — reorg-aware confirmation thresholds exist precisely so that "confirmed" means "settled," and we hold the invoice in a pending state until the chain agrees. Once it clears those confirmations, no third party can pull it back.
So the friendly-fraud playbook — buy, receive, charge back — has nowhere to plug in. The customer who wants their money back has to ask you, on your terms, through your refund flow.
The trade you're actually making
Removing chargebacks doesn't remove disputes. It moves them off the card network and onto you.
On a card rail, the bank arbitrates and you react. On a stablecoin rail, you are the arbiter. A customer who's unhappy emails support instead of calling Visa. That's better — you control the outcome, the timing, and the record — but only if you've built the refund path before you need it.
On cards, the dispute process is imposed on you. On-chain, you have to design it. The store that skips that design step trades chargeback losses for support chaos.
Two things change in your operations:
- No automatic reversals. Nobody is going to refund the customer for you. If a refund is warranted, you issue it.
- Refunds are sends, not reversals. You're not "voiding" a card auth — you're sending crypto back to an address. That's a deliberate, signed action, which means it needs the same care as a payout.
This is why we built refunds as a first-class flow rather than a checkbox. A refund references the original invoice, so you always know what you're returning against, and it goes out as a real on-chain send you authorize — not a silent reversal you can't see.
The cross-border part nobody prices in
Here's the line item that doesn't show up on the chargeback spreadsheet at all: the orders you never got.
Card rails are regional. A customer in a country your processor doesn't serve well — or whose bank routinely declines cross-border merchants — simply fails at checkout. You don't see a chargeback. You see an abandoned cart, and you assume it was price or shipping.
Stablecoins don't have that border. USDT and USDC settle the same way for a payer in São Paulo as one in Jakarta, because the rail is the chain, not a correspondent banking relationship. We expose USDT on Tron, Ethereum, and Solana, and USDC on Ethereum, Base, and Solana — so a customer reaches for the wallet and network they already hold, and the payment clears at the same finality wherever they are. If you want the regional breakdown of which rail wins where, we wrote that up in USDT on TRC-20 vs ERC-20.
The chargeback math, then, isn't just "fewer reversals." It's "fewer reversals plus the orders a card rail was quietly losing for you."
How to model it before you switch
Don't flip the rail on a vibe. Put real numbers next to each other:
The honest caveat: a confirmed stablecoin payment is final, which cuts both ways. If you ship the wrong thing, you own the refund — there's no chargeback safety net that quietly makes a bad order disappear. That's a feature for an honest store and a discipline for a sloppy one. Build the refund flow, write the policy, and the irreversibility works for you instead of against you.
Operating rule
Card chargebacks are a tax you pay for someone else arbitrating your disputes. A stablecoin checkout removes the tax and hands you the arbitration. Take the deal — but only after you've stood up a real refund path through hosted checkout, because finality with no refund plan is just a different way to make customers angry. The plumbing is the easy part. We built it. The policy is yours.