Decline Code 14: Invalid Card Number
Decline code 14 indicates that the card number provided does not correspond to any valid account in the card network. The number itself fails basic validation — it may have been mistyped, truncated, or completely fabricated. This is a hard decline because retrying the same invalid number will always produce the same result. Recovery requires the customer to provide a correct card number.
Affected Percentage
~5% of all declines
Recovery Rate
30-40% with customer outreach
Recommended Action
Do not retry
Common Causes
Data entry error
The most common cause — the customer mistyped one or more digits when entering their card number. A single transposed digit will make the entire number invalid.
Stale card data from a migration
If you migrated customer payment data between processors or systems, card numbers may have been truncated, corrupted, or improperly mapped during the transfer.
Test card number used in production
Developers sometimes accidentally leave test card numbers (like Stripe's 4242 4242 4242 4242) in production code or database seeds.
Card number changed after reissue
Some banks issue replacement cards with completely new numbers. If a stored card number is from a reissued card, the old number becomes invalid.
Recommended Retry Strategy
Timing
Do not retry. The card number is invalid and will never succeed. Contact the customer immediately to collect correct card details.
Max Retries
0 — retrying is pointless
Reasoning
An invalid card number is a data problem, not a timing problem. No amount of retries will make an incorrect number correct. The only recovery path is to get the correct card number from the customer.
Best Practices
- 1
Implement Luhn algorithm validation on the client side to catch most typos before the transaction is even submitted.
- 2
Show the card type icon (Visa, Mastercard, etc.) as the customer types, so they can visually confirm they're entering the right card.
- 3
If this code appears on a previously-working card, check whether a data migration or system update may have corrupted stored card numbers.
- 4
Send the customer an email within hours explaining that their card number appears to be incorrect and providing a direct, pre-authenticated link to update it.
How Rezoki Handles This Automatically
Rezoki immediately identifies invalid card number declines as non-retryable and skips the retry queue entirely, saving time and avoiding wasted processing fees. Instead, Rezoki triggers an instant email to the customer with clear, simple instructions to update their card. The email includes a pre-authenticated one-click link to the payment update page, minimizing friction. If the customer doesn't respond within 48 hours, Rezoki follows up with a second email and, for high-value accounts, an AI voice call to walk the customer through the update process.