Expired card: how to recover the payment
Quick answer
`expired_card` means the card number is recognised but its expiry date has passed, so the issuer will reject every charge until the customer supplies updated card details.
Worth retrying? No — the credential or customer action must change first.
Why this decline happens
- The card reached its printed expiry date and the customer has not updated the stored details.
- A replacement card was issued with a new expiry date, and sometimes a new number.
- The card was re-issued after loss, theft, or a card-network reissue programme.
Retry strategy that fits this code
- Retrying the same credentials cannot succeed. Treat this as a credential-update task, not a retry task.
- Check whether your processor's account-updater or network-token service can refresh the expiry automatically before you contact the customer.
- Only after an automated update lands should you re-attempt the charge.
- If no updated credential arrives, escalate to the customer with a direct update link.
What to tell the customer
- Say plainly that the card on file has expired — this is a low-embarrassment, high-response reason.
- Link straight to a hosted card-update page; do not ask for card details by email or chat.
- Show the last four digits and brand so the customer knows which card you mean.
- Remind them the subscription continues uninterrupted once the new card is saved.
Frequently asked
- Can an expired card ever be recovered without customer action?
- Sometimes. Card-network account updater services and network tokens can refresh the expiry date automatically when the issuer participates. Coverage is partial, so a customer-facing fallback is still required.
- Why do expired-card declines cluster at month end?
- Cards expire at the end of their printed month, so a batch of subscribers on the same expiry month fail together as that month closes.
Handling this at scale, not one invoice at a time
A single decline code is easy to handle manually. A steady stream of them across different customers, invoice values, and failure reasons is a workflow problem. RRLabs classifies each failure, scores the recovery opportunity, and recommends the next best action — then attributes recovered revenue only once your billing provider confirms the payment succeeded.