Analyze my chargebacks

Visa reason code 12.7: what it means and how to respond

Visa reason code 12.7 covers invalid authorization data. Learn who files it, how to prove the data was correct, and which deadlines apply.

What Visa code 12.7 means and when it applies

Visa code 12.7, “Invalid Data,” is filed when a transaction was authorized using data that could have changed the issuer’s decision. For the case to qualify, at least one of these two triggers must have occurred:

  1. The authorization used invalid or incorrect data. The error appeared in the authorization requestThe electronic message sent at the time of purchase to ask whether the transaction can be approved. It records data such as the transaction date, amount, and merchant category., in a required field. Visa lists the Transaction Date, MCCMCC stands for Merchant Category Code. It identifies the merchant’s primary business activity for payment processing., merchant or transaction type indicator, country code, state code, special condition indicator, or another required field.
  2. The MCC does not match between authorization and first presentment. The MCC in the authorization request does not match the MCC in the Clearing RecordThe record sent after the purchase to present the transaction and calculate settlement among participants. For 12.7, it lets the parties compare the first-presentment MCC with the authorization MCC. for the first presentment of the same transaction.

Under either trigger, the dispute covers the full transaction amount.

Source for both triggers, the fields, and the full transaction amount: Visa Core Rules §11.9.6.1, Table 11-83 (ID# 0030308), and §11.9.6.2, Table 11-84 (ID# 0030309).

A trigger alone is not enough. In addition, all of the requirements below must be met:

  1. The error would change the decision. The issuer certifies that it would have declined the request if valid data had been provided.
  2. The issuer explains why. The certification must include an explanation of why the valid data would have caused a decline. Both elements are required.
  3. The dispute was filed on time. The issuer has 75 calendar days from the Transaction Processing Date.
  4. The transaction is not excluded. 12.7 does not apply to a Mobile Push Payment TransactionA Visa transaction initiated by the cardholder on a phone or other mobile device to pay for goods or services or move money. or an ATM Cash Disbursement.

Source for the validity requirements: Visa Core Rules §11.9.6.3 through §11.9.6.5, Tables 11-85 through 11-87 (ID# 0030629, 0030310, and 0030311).

Visa applies the same certification requirement to both triggers and does not describe a separate test for the MCC mismatch. An error that would not have changed the authorization decision does not support a 12.7 dispute. If the actual issue is the transaction type, currency, account number, amount, or duplicate processing, see codes 12.2, 12.3, 12.4, 12.5, and 12.6, respectively.

Deadlines for each party under Visa 12.7

1 block represents 5 calendar days.

  1. IssuerFile the 12.7 disputeThe clock starts when the transaction is processed by Visa.
    Up to 75 calendar days
  2. AcquirerSubmit a Visa-permitted defense pathThe clock starts when the dispute is processed by Visa.
    Up to 30 calendar days
  3. IssuerEscalate the case to pre-arbitrationThe clock starts when the acquirer’s defense is processed by Visa.
    Up to 30 calendar days
  4. AcquirerRespond to the issuer’s pre-arbitration attemptThe clock starts when the issuer’s pre-arbitration attempt is processed by Visa.
    Up to 30 calendar days
  5. IssuerAsk Visa to decide the caseThe clock starts when the acquirer’s pre-arbitration response is processed by Visa.
    Up to 10 calendar days
These are the time limits set by Visa.Your deadline to submit documents may be shorter; confirm it with your acquirer.Source:Visa Core Rules, Tabelas 11-86 (ID# 0030310) e 11-2 (ID# 0030213)

Who files the dispute and what happens next

The issuer, the bank that issued the card, files the 12.7 dispute. It does not need to provide a cardholder letter. It must provide Visa with certification that it would have declined the authorization if valid data had been provided and an explanation of why.

The case proceeds through VROLVisa Resolve Online is the system where the issuer files the dispute and the acquirer submits the response and case documents.. The merchant does not respond directly to Visa. It gathers the records and gives them to the acquirer, the institution that represents the merchant in the Visa card scheme.

12.7 uses the CollaborationThe process for Categories 12 and 13 in which the issuer and acquirer exchange documents before Visa may need to decide the case. flow. The acquirer may submit a Dispute ResponseThe formal response the acquirer sends through VROL to challenge the dispute with one of the evidence types Visa permits. within 30 calendar days of the Dispute Processing Date. The issuer may then begin pre-arbitrationThe stage where the issuer asks the acquirer to review its response before taking the case to Visa for a decision.. If the parties do not resolve the case, the issuer may request Visa arbitration.

Source for filing and process: Visa Core Rules §11.9.6.5, Table 11-87 (ID# 0030311), §11.2.3, Table 11-2 (ID# 0030213), and §11.3.1.

Before building a defense, check whether this dispute is invalidProving any one condition is enough to challenge the dispute's validity.
  • The transaction is a Mobile Push Payment Transaction or an ATM Cash Disbursement — the two express exclusions from the condition.
  • The authorization actually carried valid data: the field identified by the issuer was correct in the request.
  • The issuer cannot certify that the authorization would have been declined with valid data — in other words, it would have been approved anyway.
  • The dispute was filed more than 75 calendar days after the Transaction Processing Date.
  • A full credit or Reversal had already resolved the transaction before the dispute, and the issuer did not account for it.

Source:Visa Core Rules §11.9.6 — Tabela 11-85 (ID# 0030629), com as Tabelas 11-86 e 11-87

How to reduce the risk of this code

Visa’s guidance is to process every transaction with correct data and keep the merchant account configured with the proper information. In practice, focus the review on these points:

  1. Check required fields before submission. Validate the Transaction Date, MCC, merchant or transaction type indicators, country and state codes, and special condition indicator.
  2. Keep the same MCC through first presentment. The authorization and Clearing Record must identify the same business activity.
  3. Retain transaction-level records. Keep the authorization request with the exact value of each field and, when applicable, the matching Clearing Record. The approval code alone does not show which data was transmitted.
  4. Document credits and Reversals. Record the amount, processing date, and ARNARN stands for Acquirer Reference Number. It helps locate a credit or transaction in the card scheme and link both records to the same payment. used to link the credit to the original transaction.

Source for prevention: Visa Dispute Management Guidelines for Visa Merchants, Condition 12.7, p. 36. Source for the fields and MCC comparison: Visa Core Rules §11.9.6.1 and §11.9.6.2, Tables 11-83 and 11-84 (ID# 0030308 and 0030309).

Evidence the merchant needs to gather

Validate my authorization

The merchant gives the documents to the acquirer, which submits the Dispute Response through VROL. The response must provide evidence of exactly one of these four options:

  1. The issuer did not address a credit or Reversal already issued. Gather the credit or Reversal record with the amount and processing date. Include the ARN and original transaction details to show the connection between the two records.
  2. The dispute is invalid. Provide the record that shows why the condition fails. For either of the two express exclusions, it is enough to prove that the transaction was a Mobile Push Payment Transaction or an ATM Cash Disbursement. The calculation between the Transaction Processing Date and the filing of the dispute also shows whether the issuer exceeded the 75-day limit.
  3. The cardholder no longer disputes the transaction. Provide the cardholder’s own letter or email, including the date, sender identification, and information linking the statement to the disputed transaction.
  4. The authorization did not contain invalid data. Provide the authorization request record showing the exact value in the field identified by the issuer, together with the transaction identifiers, date, time, and amount. Only when the issuer alleges an MCC mismatch, add the Clearing Record for the first presentment to show that the two MCCs match.

Each option has its own document set. Do not mix evidence from two paths to try to create a fifth defense. First choose the statement the records support; then confirm that every document required for that path is present.

If the authorization did use invalid data and none of the four options applies, Visa’s guidance is to accept the dispute. In that situation, adding documents unrelated to one of the options does not correct the issue that caused the 12.7 dispute.

Source for the four options: Visa Core Rules §11.9.6.6, Table 11-88 (ID# 0030312). Source for the documents and guidance to accept the case when the data was invalid: Visa Dispute Management Guidelines for Visa Merchants, Condition 12.7, p. 36.

Frequently asked questions

When does Visa reason code 12.7 apply to a transaction?

12.7 is Visa’s “Invalid Data” dispute condition. It applies when authorization was obtained using invalid or incorrect data in a required field. It also applies when the MCC in the authorization request does not match the MCC in the clearing record for the first presentment of the same transaction. The dispute covers the full transaction amount.

Can any incorrect data support a 12.7 dispute?

No. The issuer must certify that the authorization request would have been declined if valid data had been provided. It must also explain why. Both elements are required. A data error that would not have changed the authorization decision does not support a 12.7 dispute.

Which fields can lead to a 12.7 chargeback?

The rule lists the Transaction Date, MCC, merchant or transaction type indicator, country code, state code, and special condition indicator. It also covers any other required field.

How long does the issuer have to file a 12.7 dispute?

The issuer has 75 calendar days from the Transaction Processing Date. This window is shorter than the 120-day period for the other Category 12 codes, 12.2 through 12.6.

What must the merchant provide to respond to a 12.7 dispute?

The acquirer submits a Dispute Response through VROL within 30 calendar days of the Dispute Processing Date. The response must provide evidence of exactly one of four options: the authorization did not contain invalid data; a credit or Reversal was not addressed by the issuer; the dispute is invalid; or the cardholder no longer disputes the transaction.

For which transactions is a 12.7 dispute invalid?

A 12.7 dispute is invalid for a Mobile Push Payment Transaction and for an ATM Cash Disbursement. These are the two express exclusions in the rule.

View all Visa chargeback reason codes or return to Knowledge.

First step

Start with your chargeback history.

Sparsu uses the data you already have to size the opportunity, recognize patterns and identify which data can improve the next decisions.