What Amex Reason Code P22 Means
American Express reason code P22, titled Non-Matching Card Number, is filed when the card number submitted in the clearing/settlement file does not match the card number that was authorized. This indicates a discrepancy between the authorization and settlement records — two steps in the transaction process that must match for a valid, chargeback-resistant transaction.
P22 is related to but distinct from P01 (Unassigned Card Number). P01 involves a card number that doesn’t correspond to any Amex account. P22 involves a card number that exists but doesn’t match the card number used in the authorization. Both are technical processing compliance failures, but P22 specifically involves a mismatch between two transaction records rather than an entirely invalid card number.
P22 disputes require identifying exactly where in the authorization-to-settlement chain the card number diverged. This typically involves coordination with your payment gateway and acquiring bank to trace the card number through both the authorization and settlement records.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Amex | P22 | Non-Matching Card Number | This page; 20-day response window |
| Visa | 12.7 | Invalid Data | Visa data mismatch code |
| Mastercard | 4834 | Duplicate Processing | Mastercard processing compliance code |
| Discover | DP | Duplicate Processing | Discover processing error code |
Common Trigger Scenarios
- Tokenization mismatch. A payment token was mapped to the wrong card number in your tokenization vault, causing the authorization and settlement to reference different underlying card numbers.
- Batch processing data corruption. A data error in the settlement batch substituted a different card number in the clearing file compared to the original authorization.
- Manual keying error at settlement. In a manual processing environment, a different card number was entered at settlement than was used for the original authorization.
- System migration error. A payment system migration mapped authorization records to incorrect settlement card numbers, affecting transactions processed around the migration date.
Evidence You Will Need
- Authorization record showing the card number used for the original authorization, with the authorization code and timestamp
- Settlement record from your payment processor showing what card number was submitted for settlement
- Technical investigation documentation identifying where the card number discrepancy occurred in your processing chain
- Gateway or processor logs tracing the card number through both the authorization and settlement steps
Learn Exactly How to Package and Present This Evidence
The Processing Errors Defense Guide covers the exact evidence sequence for Amex P22 representments, formatting requirements, and how to structure your response for maximum impact.
Learn exactly how to package and present this evidence →How Merchants Lose This Dispute
- Cannot explain the discrepancy. Without a clear explanation of where and why the card numbers diverged, Amex has no basis to accept the transaction.
- Tokenization system errors. If your token vault maps to incorrect card numbers, you have a systemic data integrity problem that will generate ongoing P22 disputes.
- No matching authorization record. If you can’t produce an authorization that corresponds to the disputed settlement card number, there’s nothing to tie the transaction together.
- Missing the 20-day response window. Late responses are automatic losses.
Get the Step-by-Step Winning Strategy
Our Processing Errors Defense Guide includes copy-paste representment language for Amex P22, evidence checklist, and cross-network strategy for handling similar codes on Visa and Mastercard.
Get the step-by-step winning strategy →Response Framework Overview
- Obtain both the authorization and settlement records. Contact your payment gateway and acquiring bank to get both records and identify the specific card numbers in each.
- Document the technical cause. Identify the root cause of the mismatch — tokenization error, batch error, manual error — and explain it clearly in your representment.
- Provide the correct authorization matching the cardholder. If you can show that a valid authorization exists for the cardholder’s card number, even if the settlement record has a discrepancy, present this as evidence the transaction was legitimately authorized.
- Show the fix was implemented. Amex responds more favorably to representments that include a clear explanation of corrective action taken to prevent recurrence.
Prevention Tips
- Validate token-to-card-number mappings regularly. Periodically audit your tokenization vault to ensure tokens consistently resolve to the correct card numbers.
- Implement authorization-to-settlement matching checks. Build automated validation in your settlement process that flags any transaction where the settlement card number doesn’t match the authorization card number.
- Test payment system migrations thoroughly. Any migration of payment processing systems should include specific testing of authorization-to-settlement card number consistency.
- Avoid manual entry in settlement processes. Manual entry at any point in the settlement process introduces risk of P22 errors. Use automated batch submission wherever possible.
Frequently Asked Questions
How is P22 different from P01?
P01 involves a card number that doesn’t correspond to any active Amex account. P22 involves a card number that is valid and assigned to an Amex account, but doesn’t match the card number that was authorized. P01 is an invalid number; P22 is a real number that doesn’t match.
Can I win P22 if I have an authorization code?
An authorization code is necessary but may not be sufficient. You need to demonstrate that the authorization code corresponds to the cardholder’s card number and explain why the settlement file showed a different number. The explanation of the technical discrepancy is as important as the authorization record itself.
What should I do if I see multiple P22 disputes at once?
Multiple simultaneous P22 disputes strongly suggest a systemic error in your payment processing chain — likely a tokenization vault problem, batch processing bug, or the aftermath of a system migration. Immediately contact your payment processor and acquiring bank to identify and fix the root cause before attempting to respond to individual disputes.