Conditions
The cardholder contacted the issuer claiming that the cardholder did not authorize the transaction.
Dependencies
- A cardholder letter, email, message, or completed Dispute Resolution Form describing the cardholder’s complaint in sufficient detail to enable all parties to understand the dispute.
- Account Block and Reissue MUST be completed
- Fraud Reporting MUST be completed
- Exception File Listing MUST be completed
First Chargeback Validations
| Validation | Value | Logic | Associated Rule(s) |
|---|---|---|---|
| Face-to-face card-read transactions. A face-to-face transaction at an attended terminal with card-read (not key-entered) account information. | False | (A AND B AND C) OR (D AND E AND F)
| IsFacetoFaceTransaction_MC |
| Consumer-Presented QR transaction that was properly identified in the Authorization Request/0100 message or Financial Transaction Request/0200 message. | False |
| IsMCQRTransaction_MC |
| Authorization Approval after the FNS Date. The issuer approved the transaction after submitting two or more chargebacks involving the same Mastercard card account (for this purpose, “account” means primary account number [PAN] and expiration date) for any of the following message reason codes: 4837, 4840, 4870, or 4871. Message reason code 4863 first chargebacks will be included in the FNS count once the FNS fraud chargeback count is two or greater. | False | 2 or more previous disputes with reason code 4837, 4840, 4870, or 4871 on the same card number | IsApprovedAfterFNS_MC |
| FNS Counter Exceeds 15 Fraud-Related Chargebacks. The issuer submitted more than 15 chargebacks in aggregate involving the same account for message reason codes 4837, 4840, 4870, or 4871. | False | 15 or more previous disputes with reason code 4837, 4840, 4870, or 4871 on the same card number | IsFNSCountReached_MC |
| Emergency cash disbursements or emergency travelers check refunds. | False | processingCode = "12" | IsEmergencyCash_MC |
| ATM Transaction | False | cardAcceptorBusinessCode = 6011 | IsATMMCC_MC |
| Transactions that occurred at a cardholder-activated terminal (CAT) that were properly identified in the authorization messages and clearing records as CAT Level 1 (where a PIN is required) or when properly identified in the clearing records as CAT Level 3. | False | cardholderActivatedTerminalLevel in (1,3) | IsCATIneligible_MC |
| Counterfeit card transactions that occurred at a CAT Level 2 where the acquirer transmitted the full unedited card-read data in the Authorization Request/0100 message and obtained an authorization approval or valid transaction certificate. | False |
| IsCounterfeitCATIneligible_MC |
| Transactions resulting from an account takeover and subsequently reported to SAFE as such. An account takeover occurs when the transaction posts to an account that was fraudulently taken over from the authorized cardholder that opened the account. | False | Claim Reason equals "ATO" | IsATO |
| Mastercard Commercial Payments Account. The transaction was a Mastercard Commercial Payments Account transaction. A Mastercard Commercial Payments Account transaction occurs when PDS 0002 (GCMS Product Identifier) was MAP (Mastercard Commercial Payments Account) in the First Presentment/1240 message. | False | gcmsProductIndentifier = "MAP" | IsMCCommercialPayment_MC |
| Digital Goods. An e-commerce transaction that was less than or equal to USD 25 (or the local currency equivalent) for the purchase of digital goods resulted because the merchant did not offer purchasing control settings to the cardholder when the cardholder created an account with the merchant. Digital goods are goods that are stored, delivered, and used in electronic format, such as, by way of example but not limitation, books, newspapers, magazines, music, games, game pieces, and software (excludes gift cards). | False |
| IsDigitialGoodsUnderLimit_MC |
Properly identified Mastercard SecureCode, Masterpass by Mastercard, and Digital Secure Remote Payment (DSRP) transactions (including any subsequent transaction related to the original DSRP transaction, such as a partial shipment or recurring payment) identified in authorization (DE 48, subelement 42 [Electronic Commerce Indicators], subfield, 1 (Electronic Commerce Security Level Indicator and UCAF Collection Indicator), positions 1, 2, and 3) with the values of 211, 212, 215, 217, 221, 222, 225, 241, 242, or 245. 21.2 Mandate Added 217 and removed 911, 912 and 915. | False | electronicCommerceSecurityLevelIndicatorAndUcafCollectionIndicat in (211, 212, 215, 217, 221, 222, 225, 241, 242, 245) | IsSecureCodeMPassDSRP |
Automated Fuel Dispenser (MCC 5542). An automated fuel dispenser transaction alleged to be lost/stolen/never received issue (NRI) fraud that was identified with MCC 5542 and CAT 2 and occurred at a hybrid (EMV contactless and/or contact chip-enabled) terminal. 21.1 Mandate Added | False |
| IsAutomatedFuelDispCATEligble_MC |
Pre-Arbitration Notes
When submitting a pre-arbitration case for recurring, e-commerce, or MO/TO transactions, the user must specify, in the answer to the "Why are you initiating pre-arbitration?" question, or as Supporting Documentation, that the information (meaning cardholder name, billing address, or both) provided in the second presentment did not match the information on file with the issuer at the time of the disputed transaction (or equivalent wording).
Pre-arbitration case filing is not available when the acquirer provided compelling evidence documenting authentication of the cardholder using SecureCode at the start of a recurring transaction arrangement. In this case, the issuer may consider disputing the transaction as a Cardholder Dispute.