Handling payment disputes: a guide for customer support. 8 chapters and a final quiz.

Chapter 1. Understanding a payment complaint.

Behind the words “I don’t recognize this payment” lie very different situations: a stolen card, a forgotten purchase, a misunderstood subscription, a child playing with a phone, a late delivery. Support has to diagnose quickly and accurately. Every day that passes brings the customer closer to the “dispute” button in their banking app. A dispute handled by the bank (the chargeback) always costs more than one resolved directly.

• Unrecognized charge: the customer does not recognize the line on their statement (real fraud, or an unclear descriptor).
• Non-delivery: the order was paid for, but the package never arrived or is late.
• Not as described: the product received is different or defective, or the service was not provided.
• Disputed subscription: a free trial that turned into a paid plan, an automatic renewal, a cancellation that was “impossible.”
• Processing error: a duplicate charge, the wrong amount, a promised refund that never arrived.

Chapter 2. Reading a dispute: fraud or consumer dispute?

Everything that follows depends on the initial diagnosis. In a fraud case, the cardholder did not authorize the payment. In a consumer dispute, they paid but contest the goods or service. The card networks themselves group chargeback reasons into separate families. The reason code tells you what the issuing bank will have to prove, and what you will have to produce in response.

Five questions that diagnose a case

• Do you have an account or an order with us? An active account with a purchase history points to an innocent failure to recognize the charge, or to friendly fraud.
• Do you still have your card? A lost or stolen card means fraud is likely: tell the customer to block the card immediately.
• Does the descriptor on your statement match our business name? An unclear descriptor explains a huge share of “I don’t recognize this” claims.
• Could someone in your household have placed this order? Children and partners are the leading source of “fraud” that isn’t fraud.
• What happened with the order itself? A delay, a disappointing product, a failed cancellation: the case becomes a consumer dispute, not fraud.

Chapter 3. Defusing disputes: when and how to refund proactively.

The math is cold. A lost chargeback costs the transaction amount + a €15 to €40 fee + handling time + a hit to your ratios monitored by Visa and Mastercard. A direct refund costs… the amount. Once the odds of losing the dispute are significant, refunding up front is the economically rational decision, and often the right one for the customer relationship too.

The card networks have industrialized this defusing step. Alerts (Ethoca for Mastercard, Verifi CDRN for Visa) notify the merchant that a dispute has just been filed, giving it 24 to 72 hours to refund and avoid the chargeback. RDR (Rapid Dispute Resolution, Visa) goes further and refunds automatically under rules you set (maximum amount, reason type). The escalation chapter covers this in more detail. For now, remember that an alert you pay for and then ignore is the worst possible investment.

Chapter 4. Using response scripts to calm customers without overcommitting.

With a worried or angry customer, the winning sequence has four steps: acknowledge the emotion, restate the facts, act (or say exactly what will happen and when), and confirm in writing. A payment dispute involves the customer’s money. Keep the tone calm and factual, never defensive. Above all, never make a promise the business won’t keep.

Customer: “There’s a €49.90 payment on my statement that I don’t recognize.”

1. Acknowledge and reassure:
“I completely understand your concern. Let’s look into it together right now.”

2. Diagnose (the 5 questions):
“May I ask for the date and the exact amount? Do you still have your card?
Does the descriptor match OUR-BUSINESS-NAME?”

3a. If you find the order:
“I see an order from July 3: a monthly subscription taken out with
the email address j.doe@example.com. I’m resending the confirmation. Would you
like to keep it, or shall I cancel it?”

3b. If no order matches and fraud is likely:
“I can’t find any order in your name, so your card may have been
used fraudulently. Please contact your bank right away to block
the card. On our side, I’m reporting the transaction
to our fraud team and requesting a refund.”

4. Confirm in writing within the hour, with a case number.

1. “Apologies for the wait. I’ll check the tracking right now.”

2. With the tracking in hand:
“The carrier shows delivery on July 8 at 2:32 p.m., signed for.
I’m sending you the proof of delivery. If that isn’t your signature,
let me know and I’ll open a claim with the carrier within 48 hours.”

3. Package actually lost, or later than the promised delivery date:
“The package is considered lost. You have two options:
priority reshipment starting tomorrow, or a full refund to your card within 3
business days. Which would you prefer?”

Don’t say: “It’s the carrier’s fault, take it up with them.”
(Your sales contract is with the customer: delivery is your responsibility.)

1. “I’m canceling your subscription right now. It’s done, and you’ll receive
the confirmation email in a few minutes.”

2. Handle the last payment:
“I see that the July 1 charge went through after your first
request on June 28, so I’m refunding it in full to your card.”

3. Close the loop:
“No further charges will be made. Case number: 2026-07-1234.
If anything else shows up on your statement, just reply
to the confirmation email.”

Chapter 5. Knowing the deadlines: the law and the card networks.

Two clocks run in parallel: the law (the French Monetary and Financial Code and Consumer Code) and the card networks (Visa, Mastercard, and CB rules). A good agent knows both. The first sets the customer’s rights, the second the timetable for the battle over evidence.

For support, these deadlines help calm customers down. Telling a fraud victim that “the law protects you, and your bank must refund you within one business day if the fraud is confirmed” shows reassuring expertise. That still leaves your side of the case: the internal report, and your own refund if the order was fraudulent.

Chapter 6. Escalating to the bank or PSP, and using deflection tools.

Support does not work alone, and the right contact depends on the type of case. Escalate too late and you lose time against the deadlines; escalate to the wrong place and you lose the customer. The division of roles fits in one line. Fraud goes to the customer’s bank, consumer disputes stay with you, and the dispute mechanics run through your PSP.

Deflection tools: resolving the dispute before it becomes a chargeback

• Ethoca Alerts (Mastercard) and Verifi CDRN (Visa): the issuing bank flags the dispute to the merchant in near real time, and the merchant has 24 to 72 hours to refund and avoid a formal chargeback.
• Verifi RDR (Rapid Dispute Resolution, Visa): an automatic refund under rules the merchant sets (amount cap, accepted reason codes). The dispute is resolved before it even exists.
• Order Insight (Visa) and Consumer Clarity (Mastercard): when the customer calls their bank, the bank sees the order details in real time (product, address, device) and can clear up an unrecognized charge without opening a dispute.

Chapter 7. Documenting for representment: building a winning case.

Once the chargeback arrives and the merchant decides to fight it, it “represents” the transaction: through its PSP, it sends back a package of evidence (compelling evidence) that rebuts the stated reason. The golden rule is short: you are not answering the customer, you are answering the reason code. You don’t win a fraud case with photos of a package, or a non-delivery case with login logs.

Compelling Evidence 3.0: Visa’s weapon against friendly fraud

Since April 2023, Visa’s CE 3.0 program has enabled a liability shift on card-not-present fraud disputes (10.4). The merchant must provide at least two earlier undisputed transactions by the same cardholder, made 120 to 365 days before the disputed transaction. These transactions must share matching data: the device fingerprint or IP address, plus a second element such as the customer account or delivery address. The dispute is then reclassified. A “stranger” who has paid three times from the same phone is unlikely to be a fraudster. That is why it pays to collect and retain the device ID, IP address, and account identifiers on every order.

The 3-D Secure liability shift is another shield. As a general rule, a transaction successfully authenticated with 3DS shifts fraud liability to the issuing bank, so a “fraud” chargeback on an authenticated 3DS transaction is normally invalid. It is a near-unbeatable representment argument, but it does not cover consumer disputes, which can still be raised in full.

• Meet the PSP’s deadline: a late submission isn’t even reviewed, and you lose by default.
• One structured document: a one-page summary (reason code, rebuttal, list of exhibits), followed by the evidence in order. Bank analysts handle huge volumes, and clarity wins cases.
• Stick to the facts: dates, amounts, references. No judgments about the customer, no storytelling.
• Learn from every case: each case won or lost feeds the knowledge base (what evidence was missing? what data field wasn’t being collected?).

Chapter 8. Measuring, improving, and avoiding costly mistakes.

What isn’t measured drifts. A support team that handles payment disputes well tracks a handful of metrics, and knows by heart the short list of mistakes that turn a €30 incident into a major loss.

Post-dispute NPS deserves special mention, because surveying only “happy” customers tells you nothing. Surveying every customer 7 days after a dispute closes shows how well the process really works. It also identifies the agents whose scripts turn a moment of tension into proof of reliability.

Eight costly mistakes

• Unreadable billing descriptor (legal entity name instead of the trading name): a factory for “I don’t recognize this” claims. Getting the PSP to fix it is often the highest-return anti-dispute measure.
• Refunding outside the original channel (bank transfer, untracked store credit): invisible to the bank, and worthless if a chargeback follows.
• Responding to the PSP late: an automatic loss, regardless of the merits.
• Representing every case without evidence that matches the reason code: fees pile up, the arbitration ratio worsens, and credibility with the PSP suffers.
• Promising without a record: a gesture promised verbally and never delivered is the fastest path to a bank dispute.
• Ignoring paid alerts (Ethoca/Verifi): you pay for the alert, then the chargeback, then the fees.
• Sending consumer disputes to the bank: support creates its own chargebacks.
• Siloing support from the fraud team: support holds signals (repeat offenders, recurring reasons, problem products) that fraud rules and the product team should be using every week.