#anton-webhooks-paymentmethod
1 messages · Page 1 of 1 (latest)
Hi there 👋 taking a look at that.
Do you happen to have the ID of the card or Payment Method that was set to expire that I could take a closer look at?
Yes Here is the informations :
Customer ID: cus_OX9gWEND85BdLj
Payement method id : pm_1Nk5PPJkqIos8jtJwOfuAl0R (expires 12/23)
Subscription ID : sub_1Nk5R2JkqIos8jtJ35ggz0KT
Thank you for that! Hm, yeah, I'm not spotting any of those Events being generated, let me see if I can spot why, will likely be several minutes though.
Ok Thanks
Sorry about the delay there, had to double check some things with some teammates.
So the short answer of why you aren't seeing those Events, is that you're using our newer flows which create Payment Methods instead of Sources. Which isn't necessarily a bad thing.
Payment Methods support Card Account Updater (which is also more widely adopted than it was when customer.source.expiring was introduced)
https://stripe.com/docs/billing/revenue-recovery/smarter-saved-cards
This helps to mitigate the impact of expiring cards, by having issuers notify us when they issue a new card for the customer.
There's also a setting that you can enable here:
https://dashboard.stripe.com/settings/billing/automatic
In the Prevent failed payments -> Custmer emails section that allows you to enable emails to be sent for expiring cards. We focus more on the API in this forum, so I'm admittedly not too familiar with the inner workings of that prebuilt email flow.
Another option that you can do, is you can store the details (particularly the expiration date) of the Payment Methods that get created by your flow on your end. That would allow you to check them periodically to see if there are any that seem like they'll expire soon.
OK thank you I thinsk i choose option number 2
If you're going to do that, I would also recommend subscribing to payment_method.automatically_updated Events, so you're made aware if we update the expiration details of a payment method.