Amex Reason Code P22: Non-Matching Card Number

What Amex reason code P22 means

P22 is a card-number mismatch. The number on the charge you submitted doesn’t match the number on the authorization, or doesn’t match the account American Express has on file. In practice it usually means the card data changed somewhere between authorization and settlement, or the charge was submitted without a proper authorization for that card.

It’s close to P01 Unassigned Card Number, but P01 is about a number that isn’t valid at all. P22 is about a number that doesn’t match.

Like P01, P22 is uncommon for stores that tokenize cards and settle automatically through a modern gateway. It shows up mostly where card numbers are re-keyed or copied between systems.

Common causes

• Card numbers keyed differently at authorization and at submission
• Offline transactions submitted without an online authorization
• Data corruption or truncation in batch files
• Stored-card migrations that mapped tokens to the wrong cards
• Custom integrations that build settlement records separately from authorizations

Evidence that wins a P22 dispute

1. Authorization record with approval code and the (masked) card number.
2. Settlement record showing the same card number submitted with that approval.
3. Processor confirmation if the mismatch was introduced on their side.

Where mismatches creep in

Most P22s come from systems that store card data in more than one place. Examples: a phone-order team that keys the number again at month-end, or a custom integration that builds settlement files from a separate database rather than from the authorization response. Settling against the token or authorization reference removes the second copy that can drift.

How to prevent P22 disputes

• Settle charges against the authorization or token itself, never against re-entered card data.
• Avoid offline processing for keyed transactions.
• Validate token-to-card mappings after any migration.
• Reconcile authorizations to settlements daily.

Should you fight or accept?

Fight if your records show matching numbers on both the authorization and the submitted charge. Otherwise accept, re-collect payment from the customer with a fresh authorization, and fix the data flow.