Discover · Authorization
Reason code EX: Expired Card
The merchant completed a transaction on a card that was past its expiration date. Discover holds the merchant responsible for accepting a card that was no longer valid at the time of sale, typically because the expiry was keyed manually, ignored, or bypassed. The underlying purchase may be genuine, but the acceptance was non-compliant.
Issuer filing window
typically 120 days from the processing date
Merchant response window
typically 30 days to respond
Why EX chargebacks happen
- A card-on-file transaction ran against stored credentials that expired before the billing date.
- Staff manually keyed a transaction and entered or overrode the expiration date incorrectly.
- A forced or offline authorization bypassed the expiry check the network would have applied.
- A recurring billing engine kept charging stale card data instead of using an account updater.
- The expiration date was misread from a damaged card in a card-present fallback scenario.
How to fight a EX chargeback
- Check the authorization record first; if Discover approved the authorization with the expiry submitted, provide that approval code and argue the transaction was validly authorized.
- Show that updated card credentials were obtained through an account updater service before the charge, if applicable.
- Provide evidence the card was within its validity period on the transaction date if the dispute stems from a date discrepancy.
- If the card genuinely was expired and no valid authorization exists, accept the chargeback and pursue the customer for payment directly through normal collection channels.
- Include the full authorization request and response data so Discover's analyst can see exactly what was submitted and approved.
How to prevent EX chargebacks
- Validate expiration dates on every transaction, including manually keyed and MOTO orders, with no override path for staff.
- Enroll stored credentials in an account updater so recurring charges pick up reissued card details automatically.
- Prompt subscription customers to update payment details ahead of expiry with automated dunning emails.
- Never force-authorize a declined transaction to salvage a sale; a forced approval on an expired card converts a decline into a guaranteed chargeback.
- Purge or refresh vaulted cards past their expiry rather than attempting charges on them.
Frequently asked questions
- Can I fight an EX chargeback if Discover approved the authorization?
- Yes, and it is your strongest angle. If the authorization request included the card data you had and Discover returned an approval code, submit that record. An issuer that approved the authorization has a weak basis for charging back on expiry grounds.
- Why did my recurring billing trigger an expired card chargeback instead of a decline?
- Some processing paths, especially forced or offline authorizations and certain stored-credential flows, complete without a fresh expiry check. The charge settles, the cardholder or Discover flags the invalid card later, and it comes back as EX. Real-time validation and an account updater close this gap.
- Does an EX chargeback mean the customer keeps the goods for free?
- The network debt is settled by the chargeback, but the customer's underlying obligation to pay you still exists. You can pursue payment directly with a fresh valid card or an invoice, though as a practical matter recovery on small amounts rarely pays for the effort.
Related Discover codes