5 - Exception Processing
5.1 - Copy Requests
File name = YMMDD + File ID + .crf - e.g. “40320001.crf”
5.1.1 - File Header & Trailer
Cf. Chapter 3.3.1 (File Type: crf = Copy Requests file) and Chapter 3.3.2
5.1.2 - Copy Request
| Field Name | Length | Comment |
|---|---|---|
| Transaction Code | 2 | 52 = Copy Request |
| Card Type | 1 | V = Visa, M = MasterCard |
| Card Number | 19 | right filled with spaces |
| Transaction Amount | 12 | left zero filled, 2 decimals implied |
| Transaction Currency | 3 | ISO numeric code (e.g. 840 = US dollar) |
| Transaction Date | 10 | YYYY-MM-DD |
| Transaction ID | 12 | |
| Merchant ID | 6 | |
| Terminal ID | 8 | |
| Original Batch ID | 10 | Original Batch ID as assigned by Merchant or Processor |
| Reason Code | 2 | 2 digit code |
| Transaction LCID | 15 | LifeCycle ID, cf. Chapter 4.1.4 |
5.2 - Fraud Reports
File name = YMMDD + File ID + .frf - e.g. “40320001.frf”
5.2.1 - File Header & Trailer
Cf. Chapter 3.3.1 (File Type: frf = Fraud Reports file) and Chapter 3.3.2
5.2.2 - Fraud Report
| Field Name | Length | Comment |
|---|---|---|
| Transaction Code | 2 | 40 = Fraud Report |
| Card Type | 1 | V = Visa, M = MasterCard |
| Card Number | 19 | Right filled with spaces |
| Transaction Amount | 12 | Left zero filled, 2 decimals implied |
| Transaction Currency | 3 | ISO numeric code (e.g. 840 = US dollar) |
| Transaction Date | 10 | YYYY-MM-DD (original transaction local date) |
| Transaction ID | 12 | |
| Merchant ID | 6 | |
| Terminal ID | 8 | |
| Original Batch ID | 10 | Original Batch ID as assigned by Merchant or Processor |
| Fraud Type | 2 | Visa: (n1+space) cf. 5.2.3 / MasterCard: cf. 5.2.4 |
| Notification Code | 1 | Visa:1 = Addition2 = Addition of subsequent duplicate transaction3 = Change4 = Delete5 = Reactivate |
| Issuer Generated Authorization | 1 | Visa: OptionalY = Issuer authorized transactionX = Transaction authorized but not by issuerN = Transaction not authorized |
| Account Sequence Number | 4 | Visa: identifies a transaction within the account number. A maximum of 1000 transactions on a specific account may be added to the Visa fraud master file. The member may also pre-assign a sequence number within the 4000–4999 range. |
| Fraud Investigative Status | 2 | Visa: Optional, member-assigned. Alpha-numerical, including spaces. |
| Transaction LCID | 15 | LifeCycle ID, cf. Chapter 4.1.4 |
5.2.3 - Fraud Types - Visa
| Fraud Type Code | Description |
|---|---|
| 0 | Lost — Issuer confirms a transaction is fraudulent on a Visa account as a result of a claim by the cardholder that the card was lost. |
| 1 | Stolen — Issuer confirms a transaction is fraudulent on a Visa account as a result of a claim by the cardholder that the card was stolen. |
| 2 | Card not received as issued (NRI) — Issuer confirms a transaction is fraudulent on a Visa account as a result of a claim that the cardholder did not receive the issued card, although the issuer confirms it was sent to the cardholder (through any delivery method). |
| 3 | Fraudulent application — Issuer confirms a transaction is fraudulent on a Visa account as a result of a claim that the cardholder never applied for the card OR the issuer confirms that information given on the application was falsified. |
| 4 | Issuer-reported counterfeit - Issuer confirms a transaction is fraudulent on a Visa account as a result of a claim that the cardholder did not knowingly participate in a transaction OR the issuer confirms that such an account was never issued (in the absence of a cardholder) and the issuer confirms that the card or magnetic stripe used in a Card Present environment has been unlawfully altered or duplicated. |
| 5 | Miscellaneous/Account takeover — Issuer confirms a transaction is fraudulent on a Visa account as a result of a claim that a transaction was not authorized by the cardholder but cannot be categorized under another Fraud Type category, such as but not limited to:Multiple draft imprints obtained unlawfully from a legitimate card.Unauthorized alterations to a sales draft. U.S. only: Account takeover—Issuer confirms a transaction is fraudulent on a Visa account as a result of a claim that a transaction was not authorized by the cardholder and the issuer confirms that another party has unlawfully represented itself as the cardholder. |
| 6 | Fraudulent use of account number — Issuer confirms a transaction is fraudulent on a Visa account as a result of a claim that a transaction was not authorized by the cardholder OR the issuer confirms that such an account was never issued (in the absence of a cardholder) and the account number has been fraudulently used in a Card Not Present environment (for example, for MOTO or Internet transactions). |
| 7 | (U.S. only) used by the Issuers' Clearinghouse Service (ICS) |
| 8 | (U.S. only) used by ICS |
| 9 | Acquirer-reported counterfeit — Acquirer confirms that the transaction involved has an unissued or invalid BIN. |
| A | Incorrect Processing - Fraudulent transaction was made possible due to incorrect processing. This type identifies situations in which lack of validating a security element was the factor that enabled fraud to occur. For example: Fraudulent EMV transaction resulting from lack of cryptogram validation. Vulnerabilities in the implementation of EMV may allow fraudsters to use a chip cards with fake cryptograms.Fraudulent transaction on a magnetic stripe transaction resulting from lack of Card Verification Value (CVV) validation |
| B | Account or Credential takeover - Fraud resulted from fraudsters taking over an account or credentials from a legitimate client. Examples may include:Use of personally identifiable information (PII) to circumvent the issuer's authentication process or cardholder's stolen credentials for requesting a new bank-issued card for fraudulent use. Fraudulent use of card data and PII to circumvent the issuer's authentication process and enable provisioning of the payment card onto a mobile device / digital wallet, which is subsequently used for fraudulent purchases.Fraudulent use of the cardholder's digital wallet via stolen user credentials (i.e., mobile passcode, wallet login information). |
5.2.4 - Fraud Type Codes - MasterCard
| Fraud Type Code | Description |
|---|---|
| 00 | Lost Fraud — A fraudulent transaction that occurs with the use of a lost credit or debit card (or other device accessing a credit or debit card account—for example, convenience checks) without the actual, implied, or apparent authority of the cardholder. |
| 01 | Stolen Fraud — A fraudulent transaction that occurs with the use of a stolen credit or debit card (or other device accessing a credit or debit card account—for example, convenience checks) without the actual, implied, or apparent authority of the cardholder. |
| 02 | Never Received Issue — The interception and use of a credit or debit card (or other device accessing credit or debit card account, for example, convenience checks) before receipt by the cardholder by a person without the actual, implied, or apparent authority of the cardholder. |
| 03 | Fraudulent Application - A fraudulent transaction that occurs with the use of a credit or debit card that was obtained with an application using a false name or other false identification information. |
| 04 | Counterfeit Card Fraud - The use of altered or illegally reproduced credit or debit card (or other physical device accessing a credit or debit card account, for example, convenience checks) including the replication or alteration of the magnetic stripe or embossing. |
| 05 | Account Takeover Fraud - an existing credit or debit account is used without the actual, implied, or apparent authority of the cardholder, by a person who gains access to and use of the account through an unauthorized means, such as a change of address or request for re-issuance of credit or debit cards (or other device for accessing a credit or debit account—for example, convenience checks) but not lost or stolen cards. |
| 06 | Card Not Present Fraud - A fraudulent transaction that occurs with the use of credit or debit account information including pseudo-account information without the physical card or other device being involved, via the phone, mail, Internet, or other electronic means without the actual, implied, or apparent authority of the cardholder. |
| 07 | Multiple Imprint Fraud - A fraudulent transaction that occurs with a credit or debit card where the merchant using paper forms instead of a point-of interaction (POI) device to conduct a transaction makes several imprints of a card during an otherwise normal sale to the cardholder. |
| 51 | Bust-out Collusive Merchant — A collusive cardholder engaging in transactions with a collusive merchant as defined in the Cardholder-Merchant Collusion Program. |
5.3 - Chargebacks
File name = YMMDD + File ID + .cbf - e.g. “40320001.cbf”
5.3.1 - File Header & Trailer
Cf. Chapter 3.3.1 (File Type: cbf = Charge-Backs file) and Chapter 3.3.2
5.3.2 - Chargeback Transaction
| Field Name | Length | Comment |
|---|---|---|
| Transaction Code | 2 | 15 = Sales draft chargeback16 = Credit voucher chargeback35 = Sales draft chargeback reversal36 = Credit voucher chargeback reversal |
| Card Type | 1 | V = Visa, M = MasterCard |
| Card Number | 19 | Right filled with spaces |
| Transaction Amount | 12 | This is the amount charged back by the Issuer. left zero filled, 2 decimal places implied |
| Original Transaction Amount | 12 | Usually the same as Transaction Amount, but can be different in case of Partial Chargeback |
| Transaction Currency | 3 | ISO numeric code (e.g. 840 = US dollar) |
| Transaction Date | 10 | YYYY-MM-DD (original transaction local date) |
| Transaction ID | 12 | |
| Merchant ID | 6 | |
| Terminal ID | 8 | |
| Original Batch ID | 10 | Original Batch ID as assigned by Merchant or Processor |
| Reason Code | 2-8 | Between 2 and 8 digit code for chargeback assigned by the Card Issuer (MasterCard reason codes are defined as 4-digit, the first two being ‘48’ for all cases relevant to us, hence we only transmit the latter two digits). For customers using the new Visa Reason Codes this field is eight characters. |
| Documentation Indicator | 1 | Space = No support documentation required0 = No support documentation provided1 = Support documentation to follow |
| Message Text | 50 | Provided by Card Issuer (optional) |
| Processing Date | 10 | ‘VICB’ + YYMMDD – the date when the chargeback was processed at Visa Europe or MasterCard centre |
| Transaction LCID | 15 | LifeCycle ID, cf. Chapter 4.1.4 |
5.4 - Representments
File name = YMMDD + File ID + .rpf” - e.g. “40320001.rpf”
5.4.1 - File Header & Trailer
Cf. Chapter 3.3.1 (File Type = rpf = Re-Presentments file) and Chapter 3.3.2
5.4.2 - Representment Transaction
| Field Name | Length | Comment |
|---|---|---|
| Transaction Code | 2 | 65 = Sales draft Representment66 = Credit voucher Representment |
| Card Type | 1 | V = Visa, M = MasterCard |
| Card Number | 19 | Right filled with spaces |
| Transaction Amount | 12 | This is the new amount for the representment. Left zero filled, 2 decimals implied |
| Original Transaction Amount | 12 | |
| Transaction Currency | 3 | ISO numeric code (e.g. 840 = US dollar) |
| Transaction Date | 10 | YYYY-MM-DD (original transaction local date) |
| Authorization Code | 6 | |
| Transaction ID | 12 | The same as the original Transaction ID |
| Merchant ID | 6 | |
| Terminal ID | 8 | |
| Original Batch ID | 10 | Original Batch ID as assigned by Merchant or Processor |
| Message Text | 50 | Provided by Rapyd |
| Processing Date | 10 | ‘VIRP’ + YYMMDD – the date when the representment was sent to Visa Europe or MasterCard centre |
| Transaction LCID | 15 | LifeCycle ID, cf. Chapter 4.1.4 |