Visa 12.7 - Invalid Data
TL;DR
- The transaction record had missing fields, bad formatting, a wrong MCC or a bad terminal ID
- Dispute window is 120 days from the transaction date
- You win by producing a complete, correctly formatted transaction record
- This is an integration defect. Your developer fixes it, not your support team
Transaction contains invalid or improperly formatted data that caused processing issues.
Overview
Invalid data disputes occur when transaction records contain errors, missing fields, or formatting issues that prevent proper processing or create discrepancies.
When This Code Applies
- Missing required transaction fields
- Improperly formatted data
- Invalid merchant category code
- Incorrect terminal identifier
- Data integrity failures
Conditions for Valid Dispute
Issuer Must Verify
- Transaction data is invalid or missing
- Data issue caused incorrect processing
- Cardholder was impacted
Common Data Issues
| Field | Issue |
|---|---|
| MCC | Wrong or invalid code |
| Terminal ID | Mismatched or missing |
| Transaction date | Wrong format or value |
| Amount | Invalid format |
| Card number | Formatting errors |
Time Frames
| Scenario | Dispute Window |
|---|---|
| Standard | 120 days from transaction date |
Representment Options
1. Data Was Valid
Evidence required:
- Complete transaction record
- All required fields present
- Proper formatting
- Processor confirmation
2. Data Issue Did Not Impact Cardholder
Evidence required:
- Transaction processed correctly
- No financial harm
- Cardholder received goods/services
- Issue was technical only
3. Data Corrected
Evidence required:
- Original submission
- Corrected resubmission
- Processor acceptance
- No duplicate processing
Why This Happens
Common Causes
- API integration errors - Missing or malformed fields
- System migrations - Data mapping issues
- Manual entry - Incomplete information
- Terminal issues - Hardware/software problems
- Third-party errors - Gateway or processor issues
Required Transaction Data
Standard Required Fields
| Field | Requirement |
|---|---|
| Card number | Valid, complete |
| Expiration | MM/YY format |
| Amount | Correct format, currency |
| Date/time | Valid timestamp |
| MCC | Valid 4-digit code |
| Terminal ID | Assigned identifier |
| Authorization code | From issuer approval |
CNP-Specific Fields
| Field | Requirement |
|---|---|
| CVV2 | If collected |
| AVS | Address data |
| 3DS | Authentication data |
| IP address | Customer location |
Prevention Strategies
Technical Controls
- Validation before submission - Check all fields
- Schema enforcement - Reject malformed data
- Integration testing - Verify data flows correctly
- Error handling - Don't submit incomplete records
System Configuration
- Correct MCC - Verify with acquirer
- Valid terminal IDs - Properly configured
- Date/time sync - Accurate timestamps
- Currency codes - ISO 4217 format
Monitoring
- Rejection tracking - Know when data fails
- Field validation - Pre-submit checks
- Error alerting - Quick notification
- Regular audits - Review data quality
Win Rate Expectations
| Defense Type | Expected Win Rate |
|---|---|
| Valid data proven | 85-95% |
| No cardholder impact | 70-80% |
| Data was indeed invalid | Under 15% |
Common Mistakes
- No pre-submission validation - Bad data gets through
- Wrong MCC code - Impacts interchange and rules
- Missing required fields - Causes rejections
- Timezone issues - Date/time discrepancies
Related Codes
- 12.2 - Incorrect Transaction Code
- 12.4 - Incorrect Account Number
- 12.5 - Incorrect Amount