Stripe decline code
incorrect_numberThe card number is not valid. It likely failed the Luhn checksum or does not exist.
Type
Recoverable
Frequency
Uncommonincorrect_number is almost always a customer data entry error during the original card collection. Because the number itself is invalid, retrying is impossible. The customer must re-enter their card details. If you see this code on a card that was previously working, the card number on file was corrupted or the issuer rotated the card without updating Account Updater.
Do not retry. The card number is invalid and every retry will fail. Send the customer directly to a card update page.
Ask the customer to re-enter their card details. Do not imply they entered it incorrectly intentionally; a common cause is autofill errors or paste issues.
Permanent issue. The card cannot be charged. Customer must provide a new payment method.
The Luhn algorithm is a simple checksum formula used to validate credit card numbers. Every real card number passes Luhn. If Stripe returns incorrect_number, the provided number failed this check.
How Rebounce handles incorrect_number
Rebounce classifies every failed payment by its Stripe decline code and applies the optimal recovery strategy automatically. For incorrect_number, that means a limited retry window combined with customer outreach. Multi-channel follow-up through email, SMS, WhatsApp, and in-app banners ensures the customer actually sees the message.
invalid_numberHard declineThe card number is not a valid card number according to the issuer.
incorrect_cvcHard declineThe card verification code (CVC) provided does not match what the bank has on file.
expired_cardHard declineThe card has passed its expiration date. This is a hard decline: retrying will never succeed until the card is replaced.