Stripe webhook event
customer.source.expiring
A card on file is expiring at the end of the month.
Quick answer
Near the end of the month a saved card is set to expire.
| Event type | customer.source.expiring |
|---|---|
| Category | Customers & payment methods |
| When it fires | Near the end of the month a saved card is set to expire. |
| Recovery-relevant? | Yes, used in failed-payment recovery |
When it fires
Near the end of the month a saved card is set to expire.
What to do with it
Send a pre-dunning expiry reminder so the customer updates the card before the next charge fails.
This is a payment-recovery event
customer.source.expiring is part of the failed-payment lifecycle. Handling it well, with retries, branded emails, a card update page, and stop-on-success, is what recovers the ~9% of MRR most SaaS lose to failed payments. See how to recover failed Stripe payments or skip the build with SubRevival.
Stop building webhook handlers
SubRevival consumes the failed-payment events for you and runs the full recovery stack, no endpoint to build, secure, or maintain. 5-minute Stripe OAuth, $19/mo flat.
Start Recovering RevenueFAQ
What does the Stripe customer.source.expiring webhook event mean?
A card on file is expiring at the end of the month.
When does customer.source.expiring fire?
Near the end of the month a saved card is set to expire.
What should I do when I receive a customer.source.expiring event?
Send a pre-dunning expiry reminder so the customer updates the card before the next charge fails.
Related events
Source: official Stripe events documentation.