The first thing every operator asks when they move from cards to crypto: what happens when a customer disputes a transaction? The short answer: it stays between you and the customer. The long answer is more useful.
What you lose
You lose the card network's dispute machinery. Visa, Mastercard, and the acquirer are no longer arbitrating between you and the cardholder. That is exactly the point — the same machinery that resolves disputes is the machinery that lets a customer reverse a legitimate transaction 120 days after the fact.
What you keep
You keep the customer relationship, which is where every dispute worth resolving lives anyway. The player who is genuinely unhappy — the wager didn't post, the balance didn't credit, the withdrawal is stuck — is not helped by a chargeback. They're helped by an operator who can look up the transaction on-chain and either fix the problem or explain, unambiguously, what happened.
The framework
Every operator we work with runs a version of this three-tier framework:
- 01Tier 1 — Automated lookup. The customer opens a dispute in-app. The system pulls the on-chain transaction, the internal ledger entry, and the balance credit event. If they all match, the customer sees the receipt with block confirmations. Most 'my payment didn't credit' tickets resolve at this tier without an agent.
- 02Tier 2 — Agent review. The disputes that survive Tier 1 are genuine edge cases: a transaction sent to a stale address, a wallet client that broadcast twice, a network fee misconfiguration. Agents have the ledger, the on-chain history, and the customer's session log in one console.
- 03Tier 3 — Refund. When the operator is at fault, the operator refunds. In stablecoin, on-chain, to an address the customer verifies. The refund is a transaction, not a request to a third party.
Why this converges better than card disputes
Card disputes are asymmetric. The cardholder files, the merchant defends, the network arbitrates on a schedule that has nothing to do with either party. Meanwhile the merchant's funds are frozen. Merchants lose 40–60% of chargebacks even when the transaction was legitimate — not because they were wrong, but because they couldn't produce the exact evidence in the exact format the network wanted, on the network's timeline.
Crypto disputes are symmetric. Both parties see the same chain, the same block, the same confirmations. Disagreement is possible but ambiguity isn't. When the merchant is wrong, they refund. When the customer is wrong, the evidence is a block explorer link.
This does not eliminate customer friction. It relocates it — from a card network's arbitration queue to the merchant's own support desk. If the merchant is not prepared to run a support desk, this is worse. If the merchant is prepared, it's dramatically better.