Payments Academy
Chargeback: starting point for whole PAYMENT OPERATIONS STARTED LIVE 01 Chargeback - Every chargeback carries a reason code ACTIVE 02 Chargeback - code QUEUED 03 Consumer dispute codes - not received QUEUED 04 Strong evidence submitted on time - can reverse the chargeback and return QUEUED 05 Merchant representment window - much shorter, typically a few weeks from QUEUED 06 Analyse chargeback data - product that generates many not as described QUEUED Every chargeback carries a reason code, and the code is the starting point for the whole dispute. Step 1 of 6 Chargeback: starting point for whole STARTED Chargeback Every chargeback carries a reason code ACTIVE Chargeback code QUEUED Consumer dispute codes not received QUEUED Strong evidence submitted on time can reverse the chargeback and return QUEUED Merchant representment window much shorter, typically a few weeks from QUEUED Analyse chargeback data product that generates many not as QUEUED Every chargeback carries a reason code, and the code is the starting point for the whole dispute.
Chargeback arrives with the reason PAYMENT OPERATIONS IN PROGRESS LIVE 01 Chargeback - Every chargeback carries a reason code DONE 02 Chargeback - code ACTIVE 03 Consumer dispute codes - not received QUEUED 04 Strong evidence submitted on time - can reverse the chargeback and return QUEUED 05 Merchant representment window - much shorter, typically a few weeks from QUEUED 06 Analyse chargeback data - product that generates many not as described QUEUED The chargeback arrives with the reason code Step 2 of 6 Chargeback arrives with the reason IN PROGRESS Chargeback Every chargeback carries a reason code DONE Chargeback code ACTIVE Consumer dispute codes not received QUEUED Strong evidence submitted on time can reverse the chargeback and return QUEUED Merchant representment window much shorter, typically a few weeks from QUEUED Analyse chargeback data product that generates many not as QUEUED The chargeback arrives with the reason code
Consumer dispute codes cover goods PAYMENT OPERATIONS IN PROGRESS LIVE 01 Chargeback - Every chargeback carries a reason code DONE 02 Chargeback - code DONE 03 Consumer dispute codes - not received ACTIVE 04 Strong evidence submitted on time - can reverse the chargeback and return QUEUED 05 Merchant representment window - much shorter, typically a few weeks from QUEUED 06 Analyse chargeback data - product that generates many not as described QUEUED Consumer dispute codes cover goods not received Step 3 of 6 Consumer dispute codes cover goods IN PROGRESS Chargeback Every chargeback carries a reason code DONE Chargeback code DONE Consumer dispute codes not received ACTIVE Strong evidence submitted on time can reverse the chargeback and return QUEUED Merchant representment window much shorter, typically a few weeks from QUEUED Analyse chargeback data product that generates many not as QUEUED Consumer dispute codes cover goods not received
Strong evidence submitted on time PAYMENT OPERATIONS IN PROGRESS LIVE 01 Chargeback - Every chargeback carries a reason code DONE 02 Chargeback - code DONE 03 Consumer dispute codes - not received DONE 04 Strong evidence submitted on time - can reverse the chargeback and return ACTIVE 05 Merchant representment window - much shorter, typically a few weeks from QUEUED 06 Analyse chargeback data - product that generates many not as described QUEUED Strong evidence submitted on time can reverse the chargeback and return the funds. Step 4 of 6 Strong evidence submitted on time IN PROGRESS Chargeback Every chargeback carries a reason code DONE Chargeback code DONE Consumer dispute codes not received DONE Strong evidence submitted on time can reverse the chargeback and return ACTIVE Merchant representment window much shorter, typically a few weeks from QUEUED Analyse chargeback data product that generates many not as QUEUED Strong evidence submitted on time can reverse the chargeback and return the funds.
Merchant representment window PAYMENT OPERATIONS IN PROGRESS LIVE 01 Chargeback - Every chargeback carries a reason code DONE 02 Chargeback - code DONE 03 Consumer dispute codes - not received DONE 04 Strong evidence submitted on time - can reverse the chargeback and return DONE 05 Merchant representment window - much shorter, typically a few weeks from ACTIVE 06 Analyse chargeback data - product that generates many not as described QUEUED The merchant representment window is much shorter, typically a few weeks from the chargeback date, and the exact number of days is set by the scheme and shown on the chargeback notice. Step 5 of 6 Merchant representment window IN PROGRESS Chargeback Every chargeback carries a reason code DONE Chargeback code DONE Consumer dispute codes not received DONE Strong evidence submitted on time can reverse the chargeback and return DONE Merchant representment window much shorter, typically a few weeks from ACTIVE Analyse chargeback data product that generates many not as QUEUED The merchant representment window is much shorter, typically a few weeks from the chargeback date, and the exact number of days is set by the scheme and shown on the chargeback notice.
Analyse chargeback data for patterns PAYMENT OPERATIONS COMPLETE LIVE 01 Chargeback - Every chargeback carries a reason code DONE 02 Chargeback - code DONE 03 Consumer dispute codes - not received DONE 04 Strong evidence submitted on time - can reverse the chargeback and return DONE 05 Merchant representment window - much shorter, typically a few weeks from DONE 06 Analyse chargeback data - product that generates many not as described ACTIVE Analyse chargeback data for patterns: a product that generates many not as described claims, a channel that attracts fraud, or a descriptor that confuses cardholders. Step 6 of 6 Analyse chargeback data for patterns COMPLETE Chargeback Every chargeback carries a reason code DONE Chargeback code DONE Consumer dispute codes not received DONE Strong evidence submitted on time can reverse the chargeback and return DONE Merchant representment window much shorter, typically a few weeks from DONE Analyse chargeback data product that generates many not as ACTIVE Analyse chargeback data for patterns: a product that generates many not as described claims, a channel that attracts fraud, or a descriptor that confuses cardholders.

Key points of this lesson, in order.

0:00 / 4:21 Step 1 of 6

Reason Codes and Dispute Handling

3D Secure, Tokenization and Chargebacks, Lesson 7 of 7, Narration 4:21, D08 Cards and alternative payments

PresentmentChargeback3D Secure

What you will learn

Your objective. By the end of this lesson, you will be able to explain reason codes and dispute handling. Every chargeback carries a reason code, and the code is the starting point for the whole dispute.

Why it matters. The analyst must map each code to its evidence and its workflow.

Chapter objective: Learner explains 3D Secure authentication, tokenization, chargeback reason codes, and dispute handling, and decides the correct chargeback response for a given dispute scenario. Learner applies this skill in realistic banking scenarios, with clear examples and correct terminology throughout.

Key learning points

  • Chargeback: starting point for whole
  • Chargeback arrives with the reason
  • Consumer dispute codes cover goods
  • Strong evidence submitted on time
  • Merchant representment window
  • Analyse chargeback data for patterns

Key terms

Presentment: The submission of a card transaction by the acquirer to the scheme for clearing after authorisation and capture.

Chargeback: A dispute raised by a cardholder through the issuer to reverse a card payment, for example for fraud, non delivery or a duplicate charge.

3D Secure: A security protocol that adds an authentication step to online card payments, usually by asking the cardholder to confirm the payment with their bank.

Payment flow diagram showing Reason Codes and Dispute Handling.

Practise this lesson

Exercise

Handle the exception described in this lesson the way the lesson prescribes.

Use the exception type, the reason code and the recovery path in this lesson.

  1. What to do. State what happened, what the correct action is, what must not be done, and what the post-incident review should capture.

Correct result. The correct action is the one the lesson prescribes for this exception type, with the right reason code and the right message. The payment must not be resent without checking whether it already settled, because that creates a duplicate.

Why. An exception handled wrongly is worse than the exception itself. A duplicate payment is a loss, and an unlearned exception will happen again.

Check your understanding

Practice question

Which of the following best describes reason codes and dispute handling?

Takeaway and next step

What to remember

Consumer dispute codes cover goods not received, Visa 13.1 and Mastercard 4855, goods not as described, Visa 13.3, and a credit not processed, Mastercard 4860, where a refund was promised but never given.

Follow a payment through every stage, from instruction to beneficiary credit, and note where it can stop.

Open the Payment Lifecycle Simulator →

Builds on "The Chargeback Lifecycle".

Transcript and full text

Show transcript

Every chargeback carries a reason code, and the code is the starting point for the whole dispute. A reason code is a standard code defined by the card scheme that explains why the cardholder is disputing the transaction. The code determines what evidence the merchant must provide, how long the merchant has to respond, and whether the dispute can be won at all. The analyst must map each code to its evidence and its workflow. Step one is the cardholder raising the dispute with the issuer. The cardholder contacts the issuer, by phone, app or branch, and says they do not recognise a transaction, did not receive the goods, were charged the wrong amount, or were charged twice. The issuer checks the transaction, and if the claim fits a scheme reason code, it raises a chargeback and debits the acquirer, which debits the merchant. The chargeback arrives with the reason code, the transaction details, and a deadline for the merchant response, typically measured in days under scheme rules, with the cardholder generally able to dispute within up to 120 days of the transaction. Step two is the reason code itself, and the main categories are the same across Visa and Mastercard, even though the codes differ. Fraud codes cover a transaction the cardholder says they did not make, for example Visa 10.4 for card absent fraud and Mastercard 4808 for cardholder fraud. Processing error codes cover duplicate processing, Visa 11.1 and Mastercard 4834, a wrong amount, Visa 12.2 and Mastercard 4846, and late presentment, Visa 12.1 and Mastercard 4842, where the merchant presented the transaction after the scheme time limit. Consumer dispute codes cover goods not received, Visa 13.1 and Mastercard 4855, goods not as described, Visa 13.3, and a credit not processed, Mastercard 4860, where a refund was promised but never given. Step three is representment, where the merchant defends the charge. The acquirer passes the chargeback to the merchant with the reason code and the deadline. The merchant gathers the evidence that fits that code: for a fraud chargeback, proof that 3D Secure authentication was completed, or that the delivery address matched the cardholder address; for a not received claim, a tracking record showing delivery, ideally with a signature The merchant submits the evidence through the acquirer to the issuer, and this submission is called representment. Strong evidence submitted on time can reverse the chargeback and return the funds. Step four is pre-arbitration and arbitration, where the dispute escalates. If the issuer rejects the representment, it may raise a second chargeback, called pre-arbitration, and the merchant must decide whether to accept it or to escalate further. If the merchant escalates, the case goes to arbitration, where the scheme decides, and the losing side pays the amount plus an arbitration fee. Arbitration is expensive, so a good dispute team only escalates cases with strong evidence and a value that justifies the fee. Step five is the timeline, and missing a deadline loses the case automatically. The cardholder dispute window is commonly up to 120 days from the transaction, depending on the reason code and the scheme. The merchant representment window is much shorter, typically a few weeks from the chargeback date, and the exact number of days is set by the scheme and shown on the chargeback notice. Pre-arbitration and arbitration have their own windows, also set by the scheme. A dispute system that does not track these deadlines, with alerts before each one expires, will lose winnable cases on timing alone. The analyst should verify that every chargeback carries its deadline in the system, and that ageing reports show what is due this week. For the analyst, dispute handling is a system of maps, triage and feedback. Map every reason code to the evidence required, the team that collects it, and the workflow that submits it. Triage incoming chargebacks by value and by winnability, so the team spends its time on cases that can be won and on the largest amounts. Analyse chargeback data for patterns: a product that generates many not as described claims, a channel that attracts fraud, or a descriptor that confuses cardholders. Feed that analysis back into product, pricing and fraud prevention, so disputes become a source of insight, not just a cost.

Every chargeback carries a reason code, and the code is the starting point for the whole dispute. A reason code is a standard code defined by the card scheme that explains why the cardholder is disputing the transaction. The code determines what evidence the merchant must provide, how long the merchant has to respond, and whether the dispute can be won at all. The analyst must map each code to its evidence and its workflow.

Step one is the cardholder raising the dispute with the issuer. The cardholder contacts the issuer, by phone, app or branch, and says they do not recognise a transaction, did not receive the goods, were charged the wrong amount, or were charged twice. The issuer checks the transaction, and if the claim fits a scheme reason code, it raises a chargeback and debits the acquirer, which debits the merchant. The chargeback arrives with the reason code, the transaction details, and a deadline for the merchant response, typically measured in days under scheme rules, with the cardholder generally able to dispute within up to 120 days of the transaction.

Step two is the reason code itself, and the main categories are the same across Visa and Mastercard, even though the codes differ. Fraud codes cover a transaction the cardholder says they did not make, for example Visa 10.4 for card absent fraud and Mastercard 4808 for cardholder fraud. Processing error codes cover duplicate processing, Visa 11.1 and Mastercard 4834, a wrong amount, Visa 12.2 and Mastercard 4846, and late presentment, Visa 12.1 and Mastercard 4842, where the merchant presented the transaction after the scheme time limit. Consumer dispute codes cover goods not received, Visa 13.1 and Mastercard 4855, goods not as described, Visa 13.3, and a credit not processed, Mastercard 4860, where a refund was promised but never given.

Step three is representment, where the merchant defends the charge. The acquirer passes the chargeback to the merchant with the reason code and the deadline. The merchant gathers the evidence that fits that code: for a fraud chargeback, proof that 3D Secure authentication was completed, or that the delivery address matched the cardholder address; for a not received claim, a tracking record showing delivery, ideally with a signature The merchant submits the evidence through the acquirer to the issuer, and this submission is called representment. Strong evidence submitted on time can reverse the chargeback and return the funds.

Step four is pre-arbitration and arbitration, where the dispute escalates. If the issuer rejects the representment, it may raise a second chargeback, called pre-arbitration, and the merchant must decide whether to accept it or to escalate further. If the merchant escalates, the case goes to arbitration, where the scheme decides, and the losing side pays the amount plus an arbitration fee. Arbitration is expensive, so a good dispute team only escalates cases with strong evidence and a value that justifies the fee.

Step five is the timeline, and missing a deadline loses the case automatically. The cardholder dispute window is commonly up to 120 days from the transaction, depending on the reason code and the scheme. The merchant representment window is much shorter, typically a few weeks from the chargeback date, and the exact number of days is set by the scheme and shown on the chargeback notice. Pre-arbitration and arbitration have their own windows, also set by the scheme. A dispute system that does not track these deadlines, with alerts before each one expires, will lose winnable cases on timing alone. The analyst should verify that every chargeback carries its deadline in the system, and that ageing reports show what is due this week.

For the analyst, dispute handling is a system of maps, triage and feedback. Map every reason code to the evidence required, the team that collects it, and the workflow that submits it. Triage incoming chargebacks by value and by winnability, so the team spends its time on cases that can be won and on the largest amounts. Analyse chargeback data for patterns: a product that generates many not as described claims, a channel that attracts fraud, or a descriptor that confuses cardholders. Feed that analysis back into product, pricing and fraud prevention, so disputes become a source of insight, not just a cost.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.