Network
AmexCode
P22Response window
20 calendar daysWin difficulty
HardDispute type
Processing ErrorAmex P22 — Non-Matching Card Number: What It Is and How to Respond
Urgent — 20-day response window: Amex gives merchants only 20 calendar days to respond to P22 disputes. Immediately contact your payment processor and gateway support to obtain the authorization and settlement records you need to investigate.
P22 is triggered when the card account number in the settlement record doesn't match the account number that was authorized. This is almost always a technical processing error — either in your system, your gateway, or in the transmission of data between systems. The cardholder whose card was actually charged may not have authorised the transaction, because the charge was applied to the wrong account.
Unlike most chargeback types, P22 is not about a disputed purchase — it is a signal that something went wrong in your payment processing pipeline. When you receive a P22, the right first step is to investigate the root cause with your gateway provider, not just respond to the dispute.
Common reasons you received this dispute
- 1Gateway misconfiguration causing the settlement record to reference a different card number than the authorization
- 2A data error in batch processing that corrupted or mismatched card numbers between authorization and settlement
- 3Card number corruption in transit between your system and your gateway or acquirer
- 4A manual entry error that affected the settlement record but not the original authorization
Can you win this dispute?
Fight this dispute if...
- ✓You can demonstrate that both the authorization and settlement records correctly reference the same card number, and the mismatch is a data display or parsing error on Amex's side
- ✓Your gateway provider confirms the data was transmitted correctly and the card numbers match in both records
Accept this chargeback if...
- ✗Investigation confirms a genuine mismatch between the authorized card number and the settlement record
- ✗Your gateway provider identifies a processing or configuration error that caused the mismatch
- ✗You cannot produce matching authorization and settlement records for the transaction
Investigate the root cause, not just the dispute
P22 disputes are a signal that something is wrong in your payment processing pipeline. Even if you accept the chargeback, work with your gateway provider to identify and fix the root cause before it recurs. Multiple P22 disputes can indicate a systemic configuration issue that will continue generating chargebacks until addressed.
How to prevent this chargeback
- 1
Use end-to-end tokenization: Tokenization replaces the actual card number with a stable token at the point of capture. That same token is used through authorization and settlement, eliminating the possibility of a card number mismatch between systems. If you are seeing recurring P22 disputes, implementing tokenization is the most effective prevention.
- 2
Implement transaction reconciliation that compares authorization and settlement card numbers: An automated reconciliation step that checks card identifiers between your authorization records and your settlement records can catch mismatches before they result in chargebacks.
- 3
Work with your gateway provider if you see recurring P22 disputes: A single P22 may be an isolated data error. Multiple P22 disputes indicate a systemic issue — likely a gateway misconfiguration or integration bug. Engage your gateway provider's technical support to audit your integration.
Key deadlines
Response window: 20 calendar days from the chargeback notification date.
Contact your gateway provider immediately — you will need their authorization and settlement records to investigate and respond within the 20-day window.
Frequently asked questions
What is an Amex P22 chargeback?
Amex P22 (Non-Matching Card Number) is filed when the card account number in the settlement record does not match the account number that was authorized. This is almost always a technical processing error — in your system, your gateway, or in the transmission of data between systems. The cardholder whose card was charged may not have authorised the transaction because it was applied to the wrong account.
Why do card number mismatches happen?
Card number mismatches in P22 disputes are typically caused by tokenization errors, data corruption during transmission between systems, gateway misconfiguration, or manual entry errors that affected the settlement record but not the original authorization. In rare cases, a batch processing error can cause settlement records to be matched to the wrong authorization.
Can I fight a P22 chargeback?
Fighting P22 is rarely successful because the dispute almost always reflects a genuine processing error on the merchant side. The only scenario where a contest is viable is if you can demonstrate that the authorization and settlement records correctly reference the same card number and the mismatch is a data display or parsing error on Amex's side — which requires detailed gateway and authorization logs. In most cases, P22 indicates a real error that should be investigated and fixed.
How does tokenization prevent P22 disputes?
End-to-end tokenization replaces the actual card number with a stable token at the point of capture, and that token is used consistently through authorization and settlement. Because the token never changes between systems, there is no opportunity for a card number mismatch to occur. If you are seeing recurring P22 disputes, switching to a tokenization solution or reviewing your gateway's token handling is the most effective long-term fix.
Related reason codes
Dealing with an Amex P22 chargeback?
Generate a winning dispute response in minutes, or let ChargeMate handle it for you.
3 free generations included · No credit card required