Visa · Chargeback reason codes
Visa 12.7 chargeback: Invalid Data explained
Checked
Visa reason code 12.7, Invalid Data, means the authorization request contained invalid or incorrect data, for example a merchant category code at authorization that does not match the one used at settlement. The bank has 75 days from the processing date to file. Answer with proof the authorization data was valid and matched the settled transaction. Keeping authorization and settlement data identical prevents it.
- Category
- Processing error
- Time limit for the bank to file
- 75 days from the transaction processing date
- Time limit to respond
- Your processor's deadline (on Stripe usually 7–21 days); under Visa rules the acquirer files a Dispute Response within 30 days of the dispute processing date
- Typical evidence
- Proof the authorization data was valid and matches settlement
- Can it be prevented?
- Yes: keep authorization and settlement data identical
- Who usually wins
- The merchant when the data matches
What PlatformDTC does
PlatformDTC creates and captures each card payment on the same processor payment for the same store account, so the details authorized are the details settled. PlatformDTC answers this kind of dispute with its standard evidence pack built from the order: customer name, email, IP address, billing and shipping address, items bought, carrier, tracking and ship date, the refund policy, and any refund already issued. With "Answer a chargeback automatically" switched on, it sends the response to the bank for you before the deadline.
What it means
The issuer says it approved the transaction based on data that turned out to be invalid.
Why customers file it
Different merchant category codes or other fields between authorization and settlement.
Evidence that wins
Under Visa rules every response can also show that you already refunded and the bank ignored it, that the dispute is invalid, or that the cardholder withdrew it.
- Proof the authorization did not contain invalid data
- Matching merchant category code at authorization and settlement
How to prevent it
- Keep authorization data identical to settlement data
For developers
On Stripe the dispute object arrives with reason "general" and the card network's own code in payment_method_details.card.network_reason_code; listen for charge.dispute.created and read evidence_details.due_by for the deadline.
Processing Error (category 12) disputes have a Dispute Response stage: the acquirer answers within 30 days, then the issuer may pre-arbitrate within 30 days of that response.
Frequently asked questions
- How long does the bank have for 12.7?
- 75 days from the processing date, shorter than most processing error codes.
- What is a typical cause?
- A merchant category code at authorization that does not match the one at settlement.
Sources
Related
- 12.4 — The charge was posted to a card number that does not match the cardholder's account.
- 11.2 — The sale was completed even though the authorization was declined.
- 13.1 — The cardholder says the goods or services never arrived.
- 13.2 — The cardholder says a subscription billed them after they cancelled or withdrew permission.
- 13.3 — The cardholder says the goods or services were not as described or were defective.
- 13.4 — The goods were identified as counterfeit by the brand owner, customs or an expert.
- 13.5 — The cardholder says the terms of sale were misrepresented, including trials that turned into charges.
- 13.6 — The cardholder has a refund receipt, but the refund never reached their card.