A chargeback reverses a card payment; it cannot reverse a crypto transfer. If the problem is with the card payment — someone used your card without permission, or you paid and nothing was delivered — a chargeback has something to work with. If the problem is with the crypto after delivery — you were tricked into sending it to a scammer, or a hacker drained your wallet — there is no card payment to reverse, and a chargeback will almost certainly be denied. Everything in this guide follows from that split. If you want the verdict for your exact situation first, run it through the Crypto-Purchase Chargeback Reality Checker.
Why post-delivery chargebacks fail
Call it the delivery-is-the-event principle. The chargeback system judges the card transaction, and it judges it against a closed list of reasons: unauthorized use, non-delivery, not as described, cancelled-but-charged, promised-refund-missing, billing error. Now apply that list to the most common crypto-scam story: you authorized a card payment, the exchange delivered the crypto, and then you sent that crypto to a scammer. Which reason fits? Not unauthorized use — you authorized the payment. Not non-delivery — the crypto arrived. Not a billing error — the amount and merchant are correct. The merchant's representment evidence is devastatingly simple: a payment you authorized plus a delivery record. Banks deny these disputes not out of indifference but because, on the evidence the system is built to weigh, the merchant is right about the card transaction. The fraud happened one step later, in a transfer the card system never touched — and confirmed blockchain transfers cannot be undone by any bank or exchange, so there is nothing for the issuer to pull back even if it wanted to.
The same logic kills the other post-delivery filings people try. Disputing a card purchase because the crypto's price crashed is buyer's remorse with a crypto wrapper. Disputing because you sent coins to the wrong address is a user error in a transfer, not a card dispute. And disputing a P2P payment after you released the crypto is, from the bank's side, a completed purchase of an asset you received — the fact that the counterparty lied to you does not change what the card transaction was.
The unauthorized-only path that works
There is exactly one crypto situation where a chargeback is the right tool: the card charge itself was unauthorized. Someone else used your card to buy crypto. A hacker used your saved card after breaking into your exchange account. A thief used a stolen card number on an exchange. In all three, the card transaction fails the authorization test, and the law is built for it: the Fair Credit Billing Act (15 U.S.C. 1666) treats unauthorized use as a billing error on credit cards, with written notice due within 60 days of the statement and liability capped at $50; Regulation E (12 CFR 1005.6 and 1005.11) does the same work for debit cards and electronic transfers, with its own 60-day statement-notice rule. At the networks the family is fraud — Visa 10.4, Mastercard 4837, Amex F24 — and it is the strongest family in the system because the issuer's question is simple: did you authorize this charge?
Three things make this path work in practice. First, speed: report within 60 days of the statement to keep the strongest protections, and cancel and reissue the card immediately — an open card is an invitation to repeat the purchase. Second, a clean statement: you did not make, authorize, or benefit from the purchase, and you did not touch, move, or spend any crypto that landed from it — using it turns a fraud claim into a dispute about benefit. Third, honesty about the boundary: if the unauthorized purchase was made by someone in your household, say so; a household purchase filed as stranger fraud is first-party misuse, and the exchange's device and account records will expose it. The non-delivery family is the second working path, and it is narrower: you paid by card, the charge posted, and the exchange never delivered the crypto. That is Visa 13.1 / Mastercard 4853 / Amex C08 — the merchant must produce a delivery record, and if it cannot, issuers side with the cardholder. Contact the exchange in writing first, then file.
P2P escrow and release: the mechanics that decide everything
Peer-to-peer trading has its own physics, and most P2P losses come from misunderstanding it. When you place a P2P order, the crypto is escrowed — held by the platform — and it is released only when the seller confirms receipt of fiat. That escrow is the only moment in crypto trading when a transaction can still be stopped. The Appeal button exists for exactly that moment: it locks the escrowed crypto while support mediates, and it must be pressed before release, not after. Two warnings from the platforms' own safety guidance matter more than any other advice in this guide. First, never release on the strength of a screenshot, an SMS notification, or a PDF receipt — all three are trivially faked, and the only proof that counts is a cleared balance inside your own banking app. Second, the appeal is a mediation channel, not a promise: the platform is not a party to your trade, and its terms say so plainly. An appeal can save escrowed crypto; it cannot recover released crypto.
Release is the point of no return, and scammers know it — which is why P2P fraud scripts are all pressure scripts: urgency ("release now or the order cancels"), fake proof (an edited bank screenshot), fake authority ("support" contacting you on a chat app to demand release), and off-platform detours ("let's finish this on WhatsApp, faster"). Every one of those is a reason to appeal instead of releasing. And one more mechanical fact: exchanges publish their own appeal windows and support procedures, and they change them — so if you are mid-trade, check the exchange's own terms inside the app right now rather than trusting any article's day count, including this one. We deliberately give no day count here, because a wrong count is worse than none.
What to do instead — the route that actually helps
When a chargeback is the wrong tool, this is the route that replaces it, in order. First, the exchange. If a trade is still in escrow, appeal inside the official app immediately and do not release. If the crypto is gone, report the counterparty to the exchange fraud team anyway, with the transaction hash and wallet addresses — exchanges can flag and sometimes freeze a scammer's account, but only when it is reported. Second, law enforcement. File with the FBI Internet Crime Complaint Center (IC3) and save the confirmation number; file with the FTC at ReportFraud.ftc.gov; file a local police report. None of these recovers funds by itself — reports support investigation, pattern tracking, and, when funds are still sitting in an exchange account, freeze requests — but every later route asks for these report numbers, so file them early. Third, the bank — but only about the bank. If your issuer mishandled a genuine dispute — ignored your evidence, missed its own deadlines, closed the case without explanation — complain to the CFPB about the handling. A CFPB complaint is not a second attempt at the same chargeback; it is a complaint about process, and it produces a response from the bank, not a reversal. Fourth, secure everything. Change the exchange and email passwords, enable authenticator-app two-factor authentication, revoke API keys and connected apps, and remove any remote-access software the scammer asked you to install — email access is how most account takeovers continue.
One thing to refuse, absolutely: anyone who offers to recover your crypto for an upfront fee. Recovery scams are a second scam built on the first — they target people who have already lost money, they charge upfront, and no legitimate service can "hack back" confirmed blockchain transfers. If someone promises recovery, that promise is itself the warning sign.
Scam warning signs
The patterns repeat so reliably that you can learn them like a checklist. Pig-butchering / fake investment platforms: a new romantic or friendly contact steers you to a trading platform, early "profits" appear and small withdrawals work, then larger deposits are demanded and withdrawals suddenly need "taxes" or "fees" to unlock — the platform was fake from the start. P2P pressure scripts: urgency to release, fake payment screenshots, fake support accounts on chat apps, and any push to move the trade off-platform. Impersonation: anyone claiming to be exchange support, a bank fraud team, or law enforcement who contacts you first on social media or chat and asks for codes, passwords, or a release — real support works only inside the official app. Recovery offers: upfront-fee recovery services, as above. Too-good math: promised outsized returns, doubling schemes, and "celebrity-endorsed" crypto giveaways that ask you to send coins first to "verify" your wallet. The common thread: every one of these ends with you authorizing a transfer yourself — which is precisely why the chargeback system cannot undo it, and why prevention, not dispute, is the only reliable defence.
Quick map
Situation
Chargeback?
The route that works
Someone used my card without permission to buy crypto
Yes — fraud family
Visa 10.4 / Mastercard 4837 / Amex F24; cancel the card; file within 60 days of the statement
Hacker bought crypto with my saved card
Yes — fraud family
Secure the account first, then file as unauthorized use; report to the exchange and IC3
Paid by card, exchange never delivered the crypto
Yes — non-delivery
Exchange support in writing first, then Visa 13.1 / Mastercard 4853 / Amex C08
Only the card transaction, never the crypto itself. An unauthorized card purchase can be disputed under the fraud reason codes. A card payment you authorized, where the crypto was delivered, will almost certainly be denied — the card transaction did what you told it to do, and the merchant delivered what was paid for.
No. Filing an authorized payment as unauthorized is first-party misuse: the exchange's records will show you authorized the payment and received the crypto, the claim will be denied on that evidence, and the consequences can include a closed card account and, in serious cases, exposure to bank-fraud allegations.
If a P2P trade is still in escrow, appeal inside the exchange app before releasing anything. Otherwise report to the exchange fraud team, file with the FBI Internet Crime Complaint Center (IC3) and the FTC, and file a local police report — with the transaction hash and wallet addresses. If your bank mishandled a genuine dispute, complain to the CFPB about the handling.
Once crypto is released, the appeal window for that trade has closed: release is the point of no return for P2P trades, and confirmed blockchain transfers cannot be reversed by any exchange or bank. The appeal mechanism exists to lock escrowed crypto while a trade is still open — it is a mediation channel, not a recovery tool for completed trades.
Sources (verified October 24, 2026): Regulation E, 12 CFR 1005.6 and 1005.11 (CFPB — unauthorized-transfer liability tiers and the 60-day statement-notice rule); Fair Credit Billing Act, 15 U.S.C. 1666 (billing error includes unauthorized use; 60-day written notice; $50 liability cap); Visa Core Rules / Mastercard Chargeback Guide / Amex dispute codes via the site's reason-code dataset (fraud family 10.4 / 4837 / F24; non-delivery family 13.1 / 4853 / C08); Binance P2P terms and safety guidance (escrow on order placement, Appeal button locks escrowed crypto, appeal is a mediation channel and the platform is not a party to the trade); FBI IC3 and FTC consumer reporting guidance (reporting routes for crypto fraud). Exchange appeal windows and support procedures are deliberately not stated in days: exchanges publish their own windows and change them, so readers should check the exchange's own terms inside the app. No single-press P2P case report is relied on here.
General information only — not legal advice. If you have already filed a claim you now believe was inaccurate, contact your issuer promptly to correct the record.
Chargeback Clock