Network
AmexCode
P01Response window
20 calendar daysWin difficulty
HardDispute type
Processing ErrorAmex P01 — Unassigned Card Number: What It Is and How to Respond
20-day deadline: Amex gives merchants only 20 calendar days to respond to P-code disputes. Act immediately — gather your authorization records and gateway logs as soon as you receive this notification.
P01 is triggered when a transaction was processed using an account number that doesn't exist in American Express's records — the card number has no assigned account. This is almost always a processing or data entry error. In rare cases, it indicates attempted fraud using a fabricated card number that passed basic Luhn algorithm checks but doesn't correspond to a real account.
Because the card number is unrecognised at the network level, American Express cannot post the transaction to any account, and the dispute is raised as a processing error. The merchant is expected to investigate how an invalid number was submitted and provide evidence of where the error occurred.
Common reasons you received this dispute
- 1Manual card entry with a transposition error — a single digit wrong produces an account number that doesn't exist
- 2A system bug in your payment gateway or integration that corrupted the card number during processing
- 3An expired or cancelled card number retained in your system that no longer maps to any active account
- 4A fraudster using a synthetically generated card number that passes Luhn checks but has no real account behind it
Can you win this dispute?
Fight this dispute if...
- ✓You can show the transaction was processed using a valid, properly obtained authorisation and that the error is in how the number reached Amex — a data routing discrepancy
- ✓Your gateway logs show a valid card number was submitted and the number Amex received differs from what you sent
- ✓You have an authorisation record showing the correct account number as captured at point of sale
Accept this chargeback if...
- ✗The account number was genuinely invalid and you cannot show a valid authorisation was obtained
- ✗The error occurred in your systems — a retained old number, a keyed entry mistake, or a known integration bug
- ✗You have no documentation of what number was submitted or how it was captured
Evidence checklist
- ✅ Required
Authorisation record showing the full card number as captured: The authorisation your system requested, showing the complete account number as it was captured at the point of sale or in your checkout. This establishes what you submitted.
- ✅ Required
Terminal or gateway logs showing the exact number submitted: The raw transaction log from your payment gateway or POS terminal confirming what was transmitted for this specific transaction.
- ⭐ Strongly recommended
Proof the number was provided by the cardholder in this form (if applicable): If the card number was presented by the cardholder (e.g. written on an order form, entered in a checkout), documentation showing the number as they provided it — demonstrating the error originated with the cardholder.
How to prevent this chargeback
- 1
Enable real-time card validation in your payment gateway: A properly configured gateway will reject an invalid card number before a transaction is attempted, preventing P01 at the source.
- 2
Use tokenization rather than storing raw card numbers: Tokenization eliminates the risk of number corruption in your systems. Stored raw card data can degrade or become mismatched over time — tokens do not.
- 3
Audit your card data entry processes for manual input errors: If any part of your flow involves manual card entry, implement digit confirmation steps and consider requiring card-present entry methods wherever possible.
Frequently asked questions
What is Amex P01?
Amex P01 is filed when a transaction was processed using an account number that doesn't exist in American Express's records. The card number has no assigned account, making the charge impossible to post. It's almost always the result of a processing or data entry error rather than fraud.
When would a transaction be processed on an unassigned card number?
The most common causes are a manual card entry with a transposition error, a system or gateway bug that corrupted the card number during transmission, or a retained expired/cancelled card number. In rare cases a fraudster may use a synthetically generated card number that passes Luhn algorithm checks but has no real account behind it.
Can I fight a P01 dispute?
Yes — if you can demonstrate the error was on Amex's side or in transmission rather than in how you captured the card number. Present your authorization record and gateway logs showing the exact number you submitted. If those logs show a valid number that differs from what Amex received, you have strong grounds to contest the dispute as a data routing error.
How do I prevent P01 disputes?
Enable real-time card validation in your payment gateway so invalid numbers are rejected at the point of entry before a transaction is attempted. Use tokenization rather than storing raw card numbers, which eliminates the risk of number corruption in your systems. Audit any manual card entry processes for transposition errors — even a single digit wrong will produce a P01.
Related reason codes
Dealing with an Amex P01 chargeback?
Generate a winning dispute response in minutes, or let ChargeMate handle it for you.
3 free generations included · No credit card required