Network
VisaCode
12.7Response window
30 calendar daysWin difficulty
HardDispute type
Processing ErrorVisa 12.7 — Invalid Data: What It Is and How to Respond
Note: Visa 12.7 is almost entirely a technical issue. In most cases, the right response is to accept the chargeback and work with your payment processor to fix the underlying data problem — not to contest it. Multiple 12.7 disputes for the same data field indicate a systemic configuration issue.
Visa 12.7 is a technical dispute filed when the transaction data submitted to Visa's network doesn't meet its required data standards — missing fields, malformed data, incorrect merchant category codes, or data that violates Visa's transaction format requirements. This is almost entirely a merchant-side or processor-side technical issue.
Unlike consumer or fraud disputes, 12.7 is not about the cardholder's experience — it's about whether the data your systems sent to Visa complied with network rules. The most productive response is to identify the specific field or format issue and resolve it at the source.
Common reasons you received this dispute
- 1Transaction was submitted without required data fields (e.g. missing AVS data or authorisation code)
- 2Merchant Category Code (MCC) doesn't match the type of transaction processed
- 3Transaction data format doesn't conform to Visa's specifications
- 4Auth code was missing or invalid at settlement
- 5Terminal ID, merchant ID, or other technical fields contained invalid values
Can you win this dispute?
Fight this dispute if...
- ✓You can demonstrate the data was valid and the error was on the network or processor side — this is rare but possible
- ✓Your processor confirms the data submitted was fully compliant and the dispute was raised in error
Accept this chargeback if...
- ✗Your records confirm the submitted data was malformed or incomplete — fix the technical issue and prevent recurrence rather than contesting
- ✗Your processor confirms the data did not meet Visa's requirements
Evidence checklist
- ✅ Required
Original transaction record showing the data as submitted: The raw transaction data your system sent to Visa, showing all fields and their values at the time of submission.
- ✅ Required
Processor confirmation of the issue: Written confirmation from your payment processor identifying which data field failed and why, and any corrected transaction submitted subsequently.
- ⭐ Strongly recommended
Payment gateway transaction log showing field values submitted: The gateway-level log confirming exactly what was sent, which helps attribute the error to the correct party (merchant vs. processor).
How to write your response
For 12.7, your response should identify the specific data issue, confirm whether it has been corrected, and provide evidence of the corrected transaction if one was submitted. If contesting (rare), you must show the data was in fact valid and the dispute was raised in error.
In most cases, contact your processor before drafting your response — they will be able to identify the specific field that failed compliance and confirm the remediation steps taken.
“We respond to chargeback [reference] under Visa 12.7. We have worked with our payment processor to identify the data issue. Exhibit A shows the original transaction record. Exhibit B is confirmation from our processor identifying the specific field that did not meet Visa requirements and confirmation that this has been corrected in our integration. We have taken steps to prevent recurrence. [If contesting:] Exhibit C shows that the data submitted was valid — we request reversal of this chargeback.”
Key deadlines
Response window: 30 calendar days from the notification date.
Contact your payment processor immediately — they need to identify the root cause and ideally provide written confirmation before you submit your response.
How to prevent this chargeback
- 1
Work with your payment processor to ensure Visa compliance: Have them audit your transaction data fields annually. A full compliance review is especially important after any integration changes or processor migrations.
- 2
Ensure your MCC is correct for your business type: An incorrect Merchant Category Code is a common source of 12.7 disputes. Verify your MCC matches your actual business activity — contact your acquirer if you need it updated.
- 3
Test your integration in Visa's sandbox before going live: When adding new payment features, test thoroughly for data format compliance before launching. A failed test in sandbox is far cheaper than a batch of 12.7 disputes in production.
- 4
Monitor for 12.7 patterns: Multiple disputes citing the same data field point to a systemic configuration issue. Set up alerts for 12.7 disputes so you can identify and fix recurring problems quickly.
Frequently asked questions
What is Visa 12.7?
A technical dispute where transaction data submitted to Visa's network didn't meet its required standards — missing fields, malformed data, incorrect merchant category codes, or data that violates Visa's transaction format requirements.
Is this my fault or my payment processor's?
Often the payment processor's responsibility to ensure correct data formatting and Visa compliance — contact them first. However, if you've configured an incorrect MCC or merchant ID, that's your side to fix.
What should I do after receiving a 12.7?
Accept the chargeback, but more importantly, identify and fix the underlying data issue with your processor. Multiple 12.7 disputes for the same field point to a systemic configuration issue that needs to be addressed before it generates further chargebacks.
How long do I have to respond to a Visa 12.7 chargeback?
30 calendar days from the chargeback notification date. In most cases, the priority is fixing the technical root cause — contact your payment processor while preparing your response.
Related reason codes
Dealing with a Visa 12.7 chargeback?
Generate a winning dispute response in minutes, or let ChargeMate handle it for you.
3 free generations included · No credit card required