Chargeback dispute reason codes — all card networks
A chargeback reason code is the identifier a card network assigns to a dispute to explain why a transaction is being challenged — it determines the evidence you need and your deadline to respond. Use this free lookup to find what any Visa, Mastercard, American Express, Discover, or UnionPay dispute reason code means, which category it falls under, and how to prevent it. Search by code, keyword, or category to sharpen your chargeback prevention and dispute-response strategy.
Showing 47 of 47 reference codes.
Fraud — card-absent environment
The cardholder says they did not authorize a card-not-present transaction (online, phone, or mail order).
Prevent it: Use 3-D Secure 2, AVS and CVV on every keyed/online order, and keep clear delivery and access logs.
EMV liability shift counterfeit fraud
A counterfeit card was used at a terminal that could not read the chip.
Prevent it: Accept EMV chip and contactless at every terminal so liability stays with the issuer.
No authorization
The transaction was completed without a valid authorization approval.
Prevent it: Always obtain and keep an approval code; never force or re-attempt a declined auth.
Incorrect amount
The amount charged does not match what the cardholder agreed to.
Prevent it: Confirm the final amount at checkout and match the settled amount to the receipt.
Duplicate processing
The same transaction was submitted and settled more than once.
Prevent it: Void duplicates before batch and reconcile daily; disable double-submit on checkout.
Merchandise or services not received
The cardholder paid but says they never received the goods or services.
Prevent it: Keep tracking and delivery confirmation; provide clear fulfillment timelines.
Cancelled recurring transaction
A subscription or recurring charge continued after the cardholder cancelled.
Prevent it: Honor cancellations immediately and send confirmation; keep the cancellation record.
Not as described or defective
The goods or services were materially different from the description or arrived damaged.
Prevent it: Use accurate product descriptions and images; document condition at shipment.
Credit not processed
A promised refund or credit was not issued to the cardholder.
Prevent it: Process refunds promptly and keep the credit transaction reference.
Cancelled merchandise or services
The cardholder cancelled per your policy but was still charged.
Prevent it: Display return/cancellation policy at checkout and apply it consistently.
No cardholder authorization
The cardholder states they did not authorize or participate in the transaction.
Prevent it: Enable 3-D Secure/SecureCode, AVS and CVV; retain proof of cardholder involvement.
Fraudulent processing of transactions
Multiple transactions were processed without cardholder consent at one merchant.
Prevent it: Monitor for card testing and velocity spikes; use fraud screening rules.
Authorization-related chargeback
Required authorization was not obtained or was declined.
Prevent it: Obtain approval for every transaction and never bypass a decline.
Point-of-interaction error
A processing error such as a duplicate or incorrect amount occurred.
Prevent it: Reconcile batches daily and void duplicates before settlement.
Cardholder dispute (goods/services)
Goods or services were not as described, defective, not received, or a credit was not processed.
Prevent it: Accurate descriptions, delivery proof, and prompt refunds with references.
Goods or services not provided
The cardholder paid but did not receive the purchased goods or services.
Prevent it: Provide realistic delivery dates and keep fulfillment/tracking evidence.
Cancelled recurring transaction
A recurring or subscription payment continued after cancellation.
Prevent it: Stop billing on cancellation immediately and confirm in writing.
Late presentment
The transaction was submitted for settlement outside the allowed window.
Prevent it: Settle batches within card-network timeframes, typically within a few days.
Missing imprint
The card member denies participation and no valid card imprint or record of presence exists.
Prevent it: Capture EMV/chip or full electronic transaction records for every sale.
No card member authorization
The card member says they did not authorize or participate in the charge.
Prevent it: Use SafeKey (3-D Secure), AVS and CID/CVV; retain proof of cardholder involvement.
Card not present
A card-not-present charge the card member states they did not authorize.
Prevent it: Enable SafeKey and verify AVS/CID on keyed and online orders.
EMV counterfeit
Counterfeit chip card processed at a non-EMV terminal.
Prevent it: Accept EMV chip so counterfeit-fraud liability shifts to the issuer.
Authorization approval expired
The transaction was submitted after the authorization had expired.
Prevent it: Capture/settle within the authorization validity period; reauthorize if delayed.
No valid authorization
The charge was submitted without a valid approval.
Prevent it: Obtain and keep an approval code for every transaction.
Incorrect charge amount
The amount charged differs from the amount the card member agreed to.
Prevent it: Confirm the final amount at checkout and match settlement to the receipt.
Duplicate charge
The same transaction was billed more than once.
Prevent it: Void duplicates before batch and reconcile daily.
Goods / services not received
The card member paid but did not receive the goods or services.
Prevent it: Keep delivery/tracking proof and provide clear fulfillment timelines.
Goods / services not as described
What was received was materially different from the description.
Prevent it: Use accurate descriptions and document condition at shipment.
Cancelled recurring billing
A recurring charge continued after the card member cancelled.
Prevent it: Stop billing on cancellation immediately and confirm in writing.
Credit not processed
A promised refund or credit was never issued.
Prevent it: Process refunds promptly and keep the credit reference.
Fraud — card present
The cardholder denies a card-present transaction they say they did not authorize.
Prevent it: Accept EMV chip/contactless and retain the transaction record.
Fraud — card not present
The cardholder denies authorizing a keyed or online transaction.
Prevent it: Use ProtectBuy (3-D Secure), AVS and CID on all card-not-present orders.
Fraud — counterfeit chip
Counterfeit chip card processed without EMV.
Prevent it: Enable EMV acceptance to shift counterfeit liability to the issuer.
No authorization
The transaction lacked a required, valid authorization.
Prevent it: Authorize every transaction and never bypass a decline.
Expired authorization
Settlement occurred after the authorization expired.
Prevent it: Capture within the authorization window or reauthorize.
Duplicate processing
The transaction was processed and settled more than once.
Prevent it: Void duplicates before batch and reconcile daily.
Incorrect amount / late presentment
The amount is wrong or the transaction settled late.
Prevent it: Confirm amounts and settle batches within network timeframes.
Non-receipt of goods or services
The cardholder paid but did not receive the goods or services.
Prevent it: Keep delivery confirmation and communicate fulfillment timelines.
Quality of goods or services
Goods or services were defective or not as described.
Prevent it: Accurate descriptions, quality control, and clear return policy.
Recurring payments
A recurring charge continued after cancellation.
Prevent it: Honor cancellations immediately and confirm in writing.
Credit not processed
A promised credit or refund was not issued.
Prevent it: Process refunds promptly and retain the credit reference.
Cardholder does not recognize transaction
The cardholder does not recognize or denies authorizing the transaction.
Prevent it: Use 3-D Secure and retain authentication and delivery records.
Fraudulent transaction
The transaction is reported as fraudulent by the issuer or cardholder.
Prevent it: Screen high-risk orders and enable cardholder authentication.
No valid authorization
The transaction was processed without a valid approval.
Prevent it: Obtain and keep an approval for every transaction.
Duplicate / incorrect processing
The transaction was duplicated or processed incorrectly.
Prevent it: Void duplicates before settlement and reconcile daily.
Goods or services not provided
The cardholder did not receive the purchased goods or services.
Prevent it: Keep delivery evidence and clear fulfillment timelines.
Cancelled or credit not processed
A cancellation or promised refund was not honored.
Prevent it: Apply cancellation policy consistently and process refunds promptly.
Reference only. Each card network (Visa, Mastercard, American Express, Discover, and UnionPay) sets and periodically updates its reason codes, evidence requirements, and response windows — always confirm the current code and deadline in your processor’s dispute console.
Turn reason codes into won disputes
The reason code tells you exactly what evidence a dispute needs. Our chargeback defense team maps each code to a representment playbook, files inside the network deadline, and enrolls your account in Ethoca and Verifi pre-dispute alerts so many disputes can be refunded before they ever post against your chargeback ratio. Whether you run low-risk retail or one of 50+ high-risk merchant account categories, keeping disputes below the card-network monitoring thresholds protects your high-volume processing and your standing with the acquirer.
Reason code FAQ
What is a chargeback reason code?
A reason code is the short identifier the card network attaches to a dispute to explain why the cardholder or issuer is challenging a transaction — for example fraud, non-receipt, or a duplicate charge. The code determines what evidence you need to respond and how long you have to do it.
Are Visa and Mastercard reason codes the same?
No. Visa and Mastercard each maintain their own reason-code systems (Visa uses a category.subcategory format like 13.1; Mastercard uses four-digit codes like 4853). Both cover similar dispute types — fraud, authorization, processing errors, and consumer disputes — but the codes and response windows differ by network.
How do I respond to a dispute?
Match your evidence to the reason code: proof of delivery for non-receipt, 3-D Secure and AVS/CVV results for fraud, the signed authorization for recurring disputes, and so on. Respond inside the network deadline through your processor’s dispute console. Our chargeback defense team assembles and files representment evidence for you.
How do I keep my chargeback ratio down?
Prevent disputes before they post: clear billing descriptors, accurate product descriptions, fast refunds, and pre-dispute alerts (Ethoca and Verifi) that let you refund before a chargeback is filed. Use our chargeback ratio calculator to see where you stand against the card-network monitoring thresholds.
What chargeback ratio triggers a card-network monitoring program?
Each network runs its own dispute-monitoring program — Visa VAMP and the Mastercard Excessive Chargeback Program are the most common — and enrollment is driven by both your chargeback count and your dispute-to-transaction ratio. Once a merchant is flagged, fines and remediation requirements escalate, so the goal is to stay well under the threshold. Model your numbers with our VAMP and chargeback ratio calculators, and if your ratio is already elevated, a high-risk merchant account with active dispute management is the fastest path back to good standing.
Can Gray Merchants help if I was terminated or placed on a chargeback monitoring list?
Yes. Gray Merchants underwrites low-risk and high-risk businesses alike — including merchants who were declined or terminated elsewhere for excessive disputes. We combine a stable merchant account with representment, pre-dispute alerts, and reason-code-driven prevention so you can rebuild your processing history. Get approved to see your options.