Invalid Expiry Month

Why it happens

Most subscription businesses collect card details once at signup and again whenever a customer updates payment info. `invalid_expiry_month` tends to show up right after one of those update moments: a customer retypes their card into an update-payment form and mistypes the month field, transposes month and year, or a checkout integration passes the expiration data in the wrong format to Stripe. Because the value never reaches the issuing bank for a real authorization check, this decline happens on Stripe's own validation before the transaction gets that far.

How to fix it

Retrying the exact same submitted month will fail the exact same way every time, since the problem is the value itself, not network congestion or a temporary bank hold. That said, this is fundamentally a correctable data-entry issue: once the customer or the checkout form supplies a real, correctly formatted month, the charge can succeed immediately. The fix is correction, not persistence. Treat this as a form problem first. Check whether your checkout or payment-update flow is passing expiration data in the format Stripe's API expects, and whether client-side validation catches an out-of-range month before submission. On the customer-facing side, ask them to re-enter their card details rather than assuming the card is expired or invalid. Because this is squarely a data problem, a fast, specific nudge to fix the input gets more of these resolved than a generic "payment failed" message.

Questions

• Does `invalid_expiry_month` mean the card itself is expired?+

  Not necessarily. It usually means the month value submitted with the charge is not a valid month, often a typo or formatting issue from a checkout or update-payment form, rather than proof the physical card has expired.

• Can this decline resolve itself if Foxhound just keeps retrying?+

  No. The same invalid month value produces the same rejection on every attempt. The value has to be corrected before the charge can go through.

• What's the fastest way to fix `invalid_expiry_month` for a customer?+

  Have them re-enter their card details through your payment-update page, since a fresh, correctly validated submission usually clears the problem immediately.

• Should merchants suspect a checkout bug when this code appears often?+

  If it shows up at unusual volume, it can be worth checking whether the checkout or update form is sending expiration data in the format Stripe's API expects, since a form bug can generate `invalid_expiry_month` across many customers at once.

• How is `invalid_expiry_month` different from `expired_card`?+

  `expired_card` means the stored expiration date is real but has passed. `invalid_expiry_month` means the month value itself doesn't parse as a valid month at all, which points more toward a data-entry or format problem than an actually expired card.