How is P22 different from P01?

P01 involves a card number Amex never issued at all. P22 involves a real account being billed for a charge that does not match what that cardmember authorized, typically from data corruption between authorization and settlement.

Can I rebill the correct customer after a P22?

Yes. Identify the true account from your authorization and order records, then process a fresh, properly authorized charge, ideally after notifying the customer of the correction.

American Express · Processing Errors

Reason code P22: Non-Matching Card Number

With P22, the card number submitted in settlement does not match any charge the cardmember made, usually because the number was altered, truncated, or corrupted somewhere between authorization and clearing. The named cardmember is being billed for a transaction that does not belong to their account as processed.

Issuer filing window

typically 120 days from the charge date

Merchant response window

typically 20 days to respond

Why P22 chargebacks happen

A settlement file mangled the account number after a valid authorization.
Manual keying at settlement introduced digits different from the authorized card.
A gateway or middleware bug swapped card tokens between concurrent transactions.
Legacy batch formats truncated or padded the number field incorrectly.

How to fight a P22 chargeback

Retrieve the original authorization record and demonstrate the approved account number, then resubmit the charge correctly on that account.
Supply the order documentation connecting the true cardmember to the purchase, showing which account should have been billed.
If a token-swap bug is suspected, include the affected transaction pair to support correction of both.
Where the correct account cannot be established, accept the chargeback and trace the corruption point with your processor.

How to prevent P22 chargebacks

Process end-to-end on tokens from a single vault so the settled credential always equals the authorized credential.
Checksum-validate account fields at every hop between gateway, switch, and processor.
Retire batch integrations that reformat card data in transit.
Reconcile authorization-to-settlement matching daily and treat any mismatch as a sev-1 pipeline defect.

Frequently asked questions

How is P22 different from P01?: P01 involves a card number Amex never issued at all. P22 involves a real account being billed for a charge that does not match what that cardmember authorized, typically from data corruption between authorization and settlement.
Can I rebill the correct customer after a P22?: Yes. Identify the true account from your authorization and order records, then process a fresh, properly authorized charge, ideally after notifying the customer of the correction.

Related American Express codes