P2P chargeback: when the buyer reverses a bank transfer

What a chargeback is and why crypto is defenseless here

A chargeback is a forced return of funds initiated not by the recipient but by the payer's bank or payment system at the payer's own request. The mechanism was originally devised as consumer protection: if a card paid for goods that were not delivered or were charged twice, the cardholder disputes the operation through their bank, and the money is returned. Related concepts: a dispute (a card dispute), a reversal under 161-FZ (in Russia — contesting a transfer made without the client's consent), a recall (the reversal of a bank transfer), and a cancellation of an SBP (Faster Payments) payment on a fraud complaint.

The key asymmetry for a P2P crypto seller looks like this:

It is in this gap that fraud lives: the buyer pays you with "real" money, you release the crypto, and then they go to their bank and claim that "the transfer was made without their consent" or "the goods were not received." The bank returns the fiat to them. The crypto is already with them. The seller is left without both the money and the asset at once — this is the double loss.

Typical scenarios of how a seller is left with nothing

• "Payment without consent." The buyer pays from a card/account, receives the crypto, then writes to the bank that the operation was not made by them or was made under duress. In Russia, under 161-FZ and anti-fraud practice, banks not infrequently return the disputed amount, especially if the account is a "mule's."
• Payment from a stolen/someone else's card. The money arrives, you release the asset, the real cardholder disputes the charge — the refund goes to them, not the fraudster, but it is debited from you.
• "Goods not received." In channels where P2P is disguised as payment for a service/goods, the buyer disputes on the classic consumer basis.
• Mismatched payment details. The payment came from a name/account other than the one specified in the order (payment by a third party) — later it is easier to reverse, and you have also broken the platform's rules.
• Interbank transfer recall. The sender's bank initiates the return of an "erroneous" payment; the funds are debited from your account.

The link with AML: why this is not only "about money"

Chargeback risk and AML risk are intertwined. A reversed payment often means that dirty money came to you: the funds are stolen (carding), or it is a "spin" through mules for laundering. Even if you physically lost only the fiat, your crypto address has now received a counter-movement tied to a fraudulent operation and may be flagged by the platform or by blockchain analytics. So protection against chargebacks is at the same time KYC/AML hygiene: you verify that the money and the counterparty are clean, not merely that "the transfer arrived."

Protection: the layers that actually work

No single technique gives a hundred-percent guarantee, but assembled into a system they remove most attacks. We work in layers.

1. Wait for the actual credit, not a "notification." Do not release crypto on a "sent" screenshot or a push notification. Open your banking app yourself and check that the money is on the balance and available. Remember: "credited" ≠ "irreversible" — but it is the minimum threshold.
2. The payer's name must match the counterparty on the order. Payment must arrive from the same person named in the deal. Payment by a third party — decline and return, recording the reason.
3. Check the payment reference. Require an empty reference or a neutral "transfer between individuals." Comments like "payment for goods," "for a service," "debt repayment" raise the chance of a successful dispute and drag you into a consumer dispute.
4. Hold limits for a new/unverified counterparty. Small first deals, raising the limit only after a history. A large sum from a new person — stop.
5. Verify the source and reputation. The account's age on the platform, the number of deals, reviews, KYC status. Run the associated crypto address through AML scoring (for example, AMLConsensus) before releasing the asset.
6. Record the evidence. Screenshots of the order, the chat, the payment details, the fact of the credit with date/time and balance. This is your evidence base at the bank and on the platform.
7. Do not go into "direct" deals bypassing escrow. The platform's escrow is your insurance. A request to "let's do it directly, no fee" is almost always preparation for a scam.

A mini-diagram: how the attack unfolds and where to break it

The breaking point is stages 2–3: it is there that checks, limits, and a refusal to rush save the deal. After stage 3 there is nothing left to recover.

A template checklist before releasing the asset

Print it out or keep it in a note. Release crypto only when every item is "yes."

• ☐ I see the money on the balance in my own banking app (not from a screenshot).
• ☐ The payer's name = the counterparty's name on the order.
• ☐ The payment reference is neutral/empty, without "for goods/service."
• ☐ The amount is within the limit for this level of trust in the counterparty.
• ☐ The buyer's account: age, deals, reviews, KYC — all in order.
• ☐ The associated crypto address was run through AML scoring, risk acceptable.
• ☐ The deal goes through the platform's escrow, not "directly."
• ☐ Screenshots saved: order, chat, credit with date and time.

What to do if a chargeback has already happened

1. Immediately gather all evidence of good faith: correspondence, payment details, the fact of the credit, the address scoring.
2. Open a dispute on the P2P platform — escrow and moderation are often on the side of whoever has more documents.
3. Contact your bank with an explanation of the nature of the operation; be prepared for the bank to possibly qualify the incoming payment as disputed.
4. Do not try to "win back" the loss with a new risky deal — that is how people lose a second time.
5. Add the counterparty and their details to your personal blacklist; if there are signs of a fraudulent scheme — document them for a possible report.