12.7
What Visa Reason Code 12.7 Invalid Data Means
A 12.7 dispute says your authorization used bad data. Here is what that means and how to answer it.
- Network
- Visa
- Published
A 12.7 dispute says the authorization for a sale used invalid or incorrect data. Visa calls this condition Invalid Data. It sits in the 12 group, Processing Errors. If you got a notice with this code, the card issuer thinks the sale should never have gone through.
What is Visa reason code 12.7 (Invalid Data)?
A Visa dispute is how a card issuer sends a contested transaction back. Under 12.7, the authorization was obtained using invalid or incorrect data. In plain terms, the request that approved the sale carried wrong or broken information, and the issuer says a correct request would have failed.
This is not a fraud claim. The cardholder is not saying someone stole the card. The claim is about a technical error in how the sale was approved.
Common examples of invalid data in an authorization request
The claim usually points at data that does not match the card or the cardholder. A few common cases:
- The wrong expiration date was sent, and the approval went through anyway.
- The card number was keyed in with a typo that still matched a live account.
- Required fields were left blank or filled with placeholder values.
- The terminal sent data in a format the network does not accept.
If your terminal or software is old or misconfigured, this kind of error can happen without anyone noticing. That is why the code exists. It catches approvals that should have been declines.
What the issuer must prove to file a 12.7 dispute
The issuer cannot just assert that the data was bad. For 12.7, the issuer must certify the authorization would have been declined if the data had been valid. That is a real bar to clear. The issuer has to show the bad data mattered, and that a clean request would have failed.
If the issuer cannot show that, the dispute is weak. A merchant can accept a Visa dispute, or reject it by sending supporting documents to its card processor. Rejecting is often the right call here, because the issuer's own burden is strict.
How to defend against a 12.7 chargeback
To answer a 12.7 dispute, a merchant can show the authorization did not contain invalid data. That is the whole defense in one line. You are proving the approval was clean.
Pull the full authorization record for the sale. Show every field your system sent. If the data matches the card and the request was well formed, say so plainly and attach the record.
Do this fast. Each step of a Visa dispute has a set time limit, so a late answer can lose the case. Also keep your papers clear. Visa dispute evidence must be easy to read and in English, or come with an English translation.
Evidence checklist for a 12.7 response
Gather these before you write your reply:
- The authorization request and response, with all fields shown.
- The approval code and the exact approval message from the network.
- Terminal logs or gateway logs for that sale.
- Proof the card data matched, such as an AVS or CVV result that passed.
- Any order record that ties the sale to the approval.
Lead with the authorization record. It is the one document that speaks directly to the claim.
One more thing to know. An acquirer may respond only once to the original Visa dispute. You get one shot at this round, so make it complete. If the case moves on, the issuer must deal with the evidence in the Dispute Response. It may switch dispute conditions only if the first condition was valid.
How 12.7 differs from other processing-error codes
Codes in the 12 group all claim a processing mistake, but each points at a different mistake. A 12.6 claim says the same charge was paid twice or paid by other means. You can read about that one in Visa reason code 12.6, duplicate processing.
Older codes made similar claims about approvals. The old 7.2 no authorization code covered sales that were never approved at all. The old 7.1 declined authorization code covered sales that were approved after a decline. A 12.7 claim is different. The sale was approved, and the fight is over whether the approval used good data.
If the notice you got is unclear, start with how to read a chargeback notice. If you have already sent your reply, see what happens after you answer a chargeback for the rounds that can follow.