Error codes
Hard decline
Stripe
incorrect_number
The card number is incorrect.
What does incorrect_number mean?
The incorrect_number decline code is returned when the card number itself fails validation by the card network. This is usually a data entry issue — a mistyped digit, transposed numbers, or a corrupted stored credential — rather than an issue with a real card account.
Is it a soft or hard decline?
incorrect_number is a hard decline. The specific number is not a valid card, so no retry with the same data can succeed. Recovery requires updating the card number to a correct value.
Common root causes
Customer mistyped the card number during checkout
OCR or scan errors when adding a card from a photo
Data migration issue that corrupted stored card numbers
Test card number accidentally used in live mode
Recommended recovery steps
Do not retry the same number. It will never succeed.
Route the customer to re-enter payment details with clear messaging that the number needs correction.
Use Stripe Elements or Checkout which validate card numbers in real time before submission.
Consider wallet payments (Apple Pay, Google Pay) which avoid manual number entry entirely.
How FlyCode handles incorrect_number
FlyCode minimizes incorrect_number errors by using network tokens wherever issuers support them — sidestepping raw card number handling entirely. For cards requiring re-entry, FlyCode routes customers to streamlined update flows with wallet payment options, reducing the chance of further data entry errors.
What does incorrect_number mean?
The incorrect_number decline code is returned when the card number itself fails validation by the card network. This is usually a data entry issue — a mistyped digit, transposed numbers, or a corrupted stored credential — rather than an issue with a real card account.
Is it a soft or hard decline?
incorrect_number is a hard decline. The specific number is not a valid card, so no retry with the same data can succeed. Recovery requires updating the card number to a correct value.
Common root causes
Customer mistyped the card number during checkout
OCR or scan errors when adding a card from a photo
Data migration issue that corrupted stored card numbers
Test card number accidentally used in live mode
Recommended recovery steps
Do not retry the same number. It will never succeed.
Route the customer to re-enter payment details with clear messaging that the number needs correction.
Use Stripe Elements or Checkout which validate card numbers in real time before submission.
Consider wallet payments (Apple Pay, Google Pay) which avoid manual number entry entirely.
How FlyCode handles incorrect_number
FlyCode minimizes incorrect_number errors by using network tokens wherever issuers support them — sidestepping raw card number handling entirely. For cards requiring re-entry, FlyCode routes customers to streamlined update flows with wallet payment options, reducing the chance of further data entry errors.
What does incorrect_number mean?
The incorrect_number decline code is returned when the card number itself fails validation by the card network. This is usually a data entry issue — a mistyped digit, transposed numbers, or a corrupted stored credential — rather than an issue with a real card account.
Is it a soft or hard decline?
incorrect_number is a hard decline. The specific number is not a valid card, so no retry with the same data can succeed. Recovery requires updating the card number to a correct value.
Common root causes
Customer mistyped the card number during checkout
OCR or scan errors when adding a card from a photo
Data migration issue that corrupted stored card numbers
Test card number accidentally used in live mode
Recommended recovery steps
Do not retry the same number. It will never succeed.
Route the customer to re-enter payment details with clear messaging that the number needs correction.
Use Stripe Elements or Checkout which validate card numbers in real time before submission.
Consider wallet payments (Apple Pay, Google Pay) which avoid manual number entry entirely.
How FlyCode handles incorrect_number
FlyCode minimizes incorrect_number errors by using network tokens wherever issuers support them — sidestepping raw card number handling entirely. For cards requiring re-entry, FlyCode routes customers to streamlined update flows with wallet payment options, reducing the chance of further data entry errors.
Understanding This Decline Code
Extended content body
Frequently Asked Questions
What does incorrect_number mean?
Can incorrect_number be recovered through retry?
No. The card number itself fails network validation, so retries will always fail. Recovery requires the customer to enter a correct card number or use an alternate payment method.
How does FlyCode handle incorrect_number?
FlyCode uses network tokens where available, which sidestep raw card number issues entirely. For cards without tokens, FlyCode routes customers to streamlined update flows that minimize the friction of re-entering card details.
