Chargeback Reason Codes Overview
Chargeback Reason Codes Overview
The Reason Codes listed are based on Payment Card Company Rules and do not account for Cobranded or Private Label Relationships between the merchant and issuer.
Mastercard
Effective
Change Retrieval Bank Doc
Reason Code Description Date Time Frame Required Required
Effective
Change Retrieval Bank Doc
Reason Code Description Date Time Frame Required Required
120 days from one of the following - the central processing date of the the transaction or the last date that the cardholder
30 Services/Merchandise Not Rendered expected to recieve the services or merchandise, not to exceed 540 days. No Yes
41 Cancelled Recurring Transaction 120 Days from the central processing date of the transaction No No
120 Days from the central processing date of the transaction, expected receipt date or for delayed delivery it
would be 120 days from the receipt date or last expected date of delivery or 60 days after learning of the dispute
from the cardholder.
For merchandise or services purchased on or before the Transaction Processing Date, the date the Cardholder
received the merchandise or services
For merchandise or services provided after the Transaction Processing Date, the date the Cardholder received
the merchandise or services
Counterfeit- 120 calendar days from the date the Cardholder received the merchandise or the date on which the
Cardholder was notified that the merchandise was counterfeit, not to exceed 540 calendar days from the
Transaction Processing Date
Misrepresented terms- 120 calendar days from the last date that the Cardholder expected to receive the
merchandise or services or the date on which the Cardholder was first made aware that the merchandise or
53 Not As Described/Defective services would not be provided, not to exceed 540 calendar days from the Transaction Processing Date No Yes
57 Fraudulent Processing of Transactions 120 Days from the central processing date of the transaction No Yes
62 Counterfeit Transaction 120 Days from the central processing date of the transaction No Yes
70 Int'l only Card Recovery Bulletin or Exception File 75 Days from the central processing date of the transaction No No
71 Authorization Reqest Declined 75 Days from the central processing date of the transaction No No
72 No Authorization 75 Days from the central processing date of the transaction No No
73 Expired Card 75 Days from the central processing date of the transaction No No
120 Days from the central processing date of the transaction If ATM, Visa TravelMoney, or Online Check Card Transaction,
74 Late Presentment 20 calendar days from the central processing date of the adjustment No No
75 Cardholder Does Not Recognize 120 Days from the central processing date of the transaction No No
76 Incorrect Transaction Code(Credit Posted as a Purchase) 120 Days from the central processing date of the transaction No Sometimes
77 Non-Matching Account Number 75 Calender days from the Transaction Date No No
78 Int'l only Service Violation Code 75 Days from the central processing date of the transaction No No
80 Incorrect Transaction Amount Or Account number 120 Days from the central processing date of the transaction No Sometimes
81 Fraud- Card Present Environment 120 Days from the central processing date of the transaction Yes Sometimes
82 Duplicate Processing 120 Days from the central processing date of the transaction No No
83 Fraud- Card Not Present Environment 120 Days from the central processing date of the transaction No Yes
Effective
Change Retrieval Bank doc
Reason Code Description Date Time Frame Required required
120 calendar days from the central processing date of the transaction, However, the issuer can initiate Yes - unless
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer "No
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the Signature" or
4752 AA Does Not Recognize 120 calendar days, whichever is greater to initiate the dispute. "CAT" No
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4541 AP Recurring Payments 120 calendar days, whichever is greater to initiate the dispute. Sometimes Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4586 AW Altered Amount 120 calendar days, whichever is greater to initiate the dispute. Sometimes Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4550 CD Credit/Debit Posted Incorrectly 120 calendar days, whichever is greater to initiate the dispute. Sometimes Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4534 DP Duplicate Processing 120 calendar days, whichever is greater to initiate the dispute. Yes Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4864 NF Non-Receipt of Case from ATM 120 calendar days, whichever is greater to initiate the dispute. Sometimes Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4865 PM Paid by Other Means 120 calendar days, whichever is greater to initiate the dispute. Sometimes Yes
Up to 120 calendar days from the scheduled delivery date agreed upon between the cardholder and the
merchant but may not exceed 540 calendar days from the Processing Date. If a delivery date was not provided
or agreed upon, then the issuer may initiate the disptue from 15 to 120 calender days from the Processing Date.
4755 RG Non-Receipt of Goods or Services N/A Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
120 calendar days, whichever is greater to initiate the dispute.
Alleged Counterfeit Merchandise Up to 120 calendar days from the date that the cardholder receives notice of
Counterfeit Merchandise, not to exceed 540 days from the Processing Date.
Misrepresentation of terms of a puchase up to 120 days from the date scheduled for the last delivery of goods
4553 RM Cardholder Disputes Quality of Goods or Services or services to the cardholder, not to exceed 540 days from the Processing date. Sometimes Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
120 calendar days, whichever is greater to initiate the dispute.
Merchants in the direct marketing, food services, fast food, cruise line, transportation, lodging, and vehicle rental
industries. Issuers may initiate RN2 Disputes up to 120 calendar days from the scheduled event date, but not
more than 540 calendar days from the Processing Date. If the scheduled event date is not available to the
Issuer, then the Issuer may initiate a RN2 Dispute up to 120 calendar days from the Processing Date. The
Issuer must wait 15 calendar days from either: (i) the date of cancellation by the Cardholder of services or (ii) a
reservation or the date goods were returned, as applicable, before initiating an RN2 Dispute.
The initiation period begins on one of the following dates, as applicable: (a) the Processing Date; (b) the date of
the Credit Transaction Receipt; (c) the date of the return; (d) the date of the cancellation; or (e) the date of the
8002 RN2 Credit Not Processed reservation. RN2 Disputes may not be initiated more than 540 days from the dates indicated. Sometimes Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4863 AT Authorization NonCompliance 120 calendar days, whichever is greater to initiate the dispute. Sometimes No
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4753 IN Invalid Card Number 120 calendar days, whichever is greater to initiate the dispute. Sometimes Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4542 LP Late Presentation 120 calendar days, whichever is greater to initiate the dispute. Sometimes No
120 calendar days from the central processing date of the transaction or no later than 540 calendar days from
the Processing Date or Discover’s determination that such Card Transaction is not compliant with the Operating
4757 TF Violation of Operating Regulations Regulations, but in any event no later than 540 days of the Processing Date. Yes No
120 calendar days from the central processing date of the transaction, However, the issuer can initiate Yes - unless
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer "No
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the Signature" or
7010 UA01 Fraud - Card Present Transaction 120 calendar days, whichever is greater to initiate the dispute. "CAT" Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
7030 UA02 Fraud - Card Not Present Transaction 120 calendar days, whichever is greater to initiate the dispute. Sometimes Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4866 UA05 Fraud Chip Card Counterfeit Tranaction 120 calendar days, whichever is greater to initiate the dispute. Sometimes Yes
120 calendar days from the central processing date of the transaction, However, the issuer can initiate
chargebacks past the 120 day timeframe when a Ticket Retrieval Request has been received. If the issuer
processed a Ticket Retrieval Request they will have an additional 60 days from the close date of the TRR or the
4867 UA06 Fraud Chip and PIN Transaction 120 calendar days, whichever is greater to initiate the dispute. Sometimes Yes
4762 05 Good Faith Investigation To collect funds from the merchant when the merchant accepts the initial retrieval request for Good Faith Yes No
AMEX
Effective
Change Retrieval Bank doc
Reason Code Description Date Time Frame Required required
A01 No Valid Authorization/Excessive Amount 180 calendar days from the central processing date of the transaction No No
A02 No Authorization/Invalid Approval Code 180 calendar days from the central processing date of the transaction No No
A08 Authorization Approval Code Expired 180 calendar days from the central processing date of the transaction No No
C02 Credit Not Processed 180 calendar days from the central processing date of the transaction No Yes
180 calendar days from the central processing date of the transaction OR 180 days from the expected date of
C04 Credit Not Processed / Returned Merchandise delivery, or the date of cancellation/return No Yes
180 calendar days from the central processing date of the transaction OR 180 days from the expected date of
C05 Credit Not Processed / Cancelled Transaction delivery, or the date of cancellation/return No Yes
180 calendar days from the central processing date of the transaction OR 180 days from the date of delivery,
C08 Non Receipt of Merchandise / Service expected delivery date No Yes
C14 Paid By Other Means 180 calendar days from the central processing date of the transaction No No
C18 Cancelled Trans / No Show 180 calendar days from the central processing date of the transaction No Yes
C28 Cancelled Recurring 180 calendar days from the central processing date of the transaction No Yes
C31 Cardholder Dispute - Not As Described 180 calendar days from the central processing date of the transaction No Yes
C32 Cardholder Dispute - Defective 180 calendar days from the central processing date of the transaction No Yes
F10 No swipe - keyed transaction 180 calendar days from the central processing date of the transaction No No
F14 No Signature Obtained 180 calendar days from the central processing date of the transaction Yes No
F24 Fraud - No Cardholder Knowledge 180 calendar days from the central processing date of the transaction Yes No
F29 Fraudulent Transaction - Card Not Present 180 calendar days from the central processing date of the transaction No No
F30 EMV Counterfeit 180 calendar days from the central processing date of the transaction No No
F31 EMV Lost/Stolen/Non Received 4/16/2016 180 calendar days from the central processing date of the transaction No No
FR2 Fraud - Full Recourse Agreement 180 calendar days from the central processing date of the transaction No No
FR4 Immediate Chargeback Program 180 calendar days from the central processing date of the transaction No No
FR5 Immediate Chargeback Program 180 calendar days from the central processing date of the transaction No No
FR6 Immediate Chargeback Program 180 calendar days from the central processing date of the transaction No No
M01 Merchant Accepted Chargeback 180 calendar days from the central processing date of the transaction Yes No
M04 Merchant Accepted Chargeback 180 calendar days from the central processing date of the transaction Yes No
M10 Captial damages 180 calendar days from the central processing date of the transaction No Yes
M19 Offset adjustment
M23 Offset adjustment
M27 Offset adjustment
M29 Discount Fees
M36 Dispute Other 180 calendar days from the central processing date of the transaction No No
M43 Marketing Programs
M44 Marketing Programs
M45 Offset adjustment
M46 Offset adjustment
M49 Unauthorized Charge - Car Rental 180 calendar days from the central processing date of the transaction No No
P01 Non-Matching Account Number 180 calendar days from the central processing date of the transaction No No
P03 Credit Posted as a Card Sale 180 calendar days from the central processing date of the transaction No Yes
P04 Card Sale Posted as a Credit 180 calendar days from the central processing date of the transaction No Yes
P05 Transaction amount differs 180 calendar days from the central processing date of the transaction No Yes
P07 Late Presentment 180 calendar days from the central processing date of the transaction No No
P08 Duplicate Processing 180 calendar days from the central processing date of the transaction No Yes
P22 Card Number Does Not Match Original Charge 180 calendar days from the central processing date of the transaction No Yes
P23 Correct Transaction Currency Code Not Provided 180 calendar days from the central processing date of the transaction No No
R03 Insufficient Doc 180 calendar days from the central processing date of the transaction Yes No
R13 Retrieval Response Not Received 180 calendar days from the central processing date of the transaction Yes No
WEX
Effective
Change
Reason Code Report Description Date Long Description
Classification: C - Reject
1 FLEET INVALID Reject – Fleet Invalid
2 VEHICLE INVALID Reject – Vehicle Invalid
4 PRODUCT INVALID Reject – Product Invalid
5 TERMINATED VEHICLE Reject – Terminated Vehicle
6 SITE INVALID Reject – Site Invalid
7 PPG INVALID Reject – PPG Invalid
8 DOLLARS INVALID-MANUAL Reject – Dollars Invalid-Manual
9 GALLONS INVALID-MANUAL Reject – Gallons Invalid-Manual
10 DOLLARS INVALID-ELEC Reject – Dollars Invalid-Electronic
11 GALLONS INVALID-ELECT Reject – Gallons Invalid-Electronic
12 TERMINATED FLEET Reject – Terminated Fleet
13 VEHICLE EXPIRATION Reject – Vehicle Expiration Exception
14 FUEL DUPLICATE SALE Reject – Duplicate Transaction
17 UNREASONABLE DATE Reject – Unreasonable Date
19 TEST ACCOUNT Reject – Test Account
21 AGE OF TRANSACTION Reject – Age of Transaction (Sales exceeding 120 Days)
22 INVALID ITEMS Reject – Invalid Items (Service Industry Specific)
Classification: A - Adjustment
1 TICKET CPY NOT RCVD <60 Adjustment Entered – Ticket Copy Not Received
2 DUPLICATE SALE Adjustment Entered – Duplicate Sale
4 INV NOT SIGNED BY CUST Adjustment Entered – No Signature
5 INCORRECT SALE AMOUNT Adjustment Entered – Incorrect Sale Amount
6 UNAUTHORIZED USE/FRAUD Adjustment Entered – Unauthorized Use/Fraud
7 TRANSACTION CORRECTION Adjustment Entered – Transaction Correction
8 SALE AFTER SUSPENSION Adjustment Entered – Sale After Suspension
9 NO AUTHORIZATION CODE Adjustment Entered – No Authorization Code
10 UNAUTHORIZED/UNCOLLECT Adjustment Entered – Unauthorized/Uncollect
17 KEYED SALE NO IMPRINT Adjustment Entered – Keyed Sale, No imprint
18 NON-FUEL ON FUEL-ONLY Adjustment Entered – Non-Fuel on Fuel-only
19 TICKET CPY NOT LEGIBLE Adjustment Entered – Ticket Copy Not Legible
20 AUTH NOT VALID Adjustment Entered – Authentication Not Valid
21 AGE OF TRANSACTION Adjustment Entered – Age of Transaction
22 PURCH INFO NOT CAPTURED Adjustment Entered – Purchase info not captured
23 CARD NOT PRESENT Adjustment Entered – Card not present
24 COLLUSION Adjustment Entered – Collusion
25 HANDWRITTEN TICKET Adjustment Entered – Handwritten Ticket
26 SALE EXCEEDS PURCH LMT Adjustment Entered – Sale exceeds purchase limit
27 UNAUTHORIZED MERCH Adjustment Entered – Unauthorized Merchandise
A1 RE-ADD TO FLEET ACCOUNT Adjustment Entered – Re-Add to Fleet Account
E1 CHARGE REFUTED SEE FILE Adjustment Entered – Fleet Refuses Charge
Classification: R - Correct Reject
15 CORRECTED FUEL DUP SALE Corrected Reject – Corrected Fuel Duplicate Sale
16 CORRECTED ERROR Corrected Reject – Corrected Error
Classification: M - Manual Entry
1 POSTED WRONG VEHICLE # Manually Entered - Posted Wrong Vehicle #
2 POSTED TO WRONG ACCT # Manually Entered - Posted to wrong account #
3 CORRECT TAX AMOUNT Manually Entered - New Account
4 WRONG PROD CODE Manually Entered - Wrong Product Code
5 CORRECT TAX AMOUNT Manually Entered - Correct Tax Amount
6 INVALID DUPE REJECT Manually Entered - Invalid Duplicate Reject
7 INVALID GAL/PPG AMT Manually Entered - Invalid Gal/PPG sale amount
8 AGED SALES TRANS Manually Entered - Aged Sales Transaction
9 TICKET SENT FOR KEYING Manually Entered - Ticket sent for keying
10 INVALID DATE SET Manually Entered - Invalid Date Set
11 TO WRONG MERCH ID Manually Entered - To wrong Merchant Id
Voyager
Reason Effective
Code Change Date Description
05 Cardholder Does Not Agree with the Amount Billed
21 Cardholder Does Not Recognize Transaction
22 Transaction Certification (ICC Transaction)
23 Transaction Information Document (TID) needed for cardholder's personal records expense report
41 Fraud Investigation
42 Potential Chargeback or Compliance Documentation.
43 Health Care Request
Reason Effective
Code Change Date Description
27 HealthCare IIAS Auto-sub Data Retrieval Request
28 Cardholder Requests with Signature
30 Cardholder request due to dispute
33 Fraud Analysis request
34 Legal Process request
Discover
Issuer may initiate a Ticket Retrival Request within 18 months of the Processing Date of the transaction
Reason Effective
Code Change Date Description
Ticket Retrieval Request
01 Transaction Documentation Request
03 Transaction Documentation Request Due to Cardholder Dispute
04 Transaction Documentation Request for Fraud Analysis
05 Good Faith Investigation
AMEX
Reason Effective
Code Change Date Description
127 Cardholder Does Not Recognize
147 No Cardholder Authorization
154 Cardholder Cancelled
155 Non Receipt of Merchandise
158 Request for Credit
169 Correct Transaction Currency Code Not Provided
170 Cardholder Cancelled
173 Duplicate Billing
175 Request for Credit
176 Cardholder Does Not Recognize
177 No Cardholder Authorization
193 Fraud Investigation
680 Cardholder Does Not Agree with Amount Billed
684 Paid by Other Means
691 Request for Copy
693 No Cardholder Authorization
004 Non-Receipt of Goods or Services
021 Cancelled Recurring Transaction
024 Cardholder Disptue Defective/Not as Described
059 Cardholder Disptue Defective/Not as Described
061 Debit Posted as Credit
062 Credit Posted as Debit
063 Quality of Goods or Services
WEX
Reason Effective
Code Change Date Description
40 Duplicate Transaction
43 Need Signed Copy
60 Dispute Transaction
1B Possible Fraud
LP Loss Prevention
Voyager
Reason Effective
Code Change Date Description
0 Need Invoice
1 Need Signed Invoice
180 calendar days from the central processing date of the transaction and 100 calendar days for Prepaid Card
Transactions Not to exceed two years from the processing date of the tranaction.