Input error · recoverable

incorrect_number

Card number is invalid (wrong digits or fails Luhn check).

What just happened

Customer fat-fingered the card number, or the card was deactivated and the number isn't recognized anymore.

Retry strategy

Don't retry. Customer must enter a different/correct number.

What to tell the customer

Your card number didn't validate. Please double-check the digits or use a different card.

Recommended action

Surface the error immediately, prompt for re-entry. No automatic retries.

Want to see what this looks like on your Stripe?

See how often "incorrect_number" hits your Stripe account in the last 30 days — and how much MRR is at risk because of it.

Run free audit

Related codes

Frequently asked questions

Is "incorrect_number" a soft or hard decline?+
It's classified as a input error: Wrong number, expiry, or CVC. Customer needs to re-enter card details.
Should I retry a "incorrect_number" decline?+
Don't retry. Customer must enter a different/correct number.
What should I tell my customer when this happens?+
Your card number didn't validate. Please double-check the digits or use a different card.
How do I prevent this decline going forward?+
Surface the error immediately, prompt for re-entry. No automatic retries.
Does Rechurn handle this decline code automatically?+
Yes. Rechurn classifies "incorrect_number" and runs the optimal retry cadence with a personalized email sequence. Run a free audit to see how many of your failed charges are this code.