#varsh59_webhooks
trail pewterBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1382386709869887658
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
rapid spruce
Hi there
next flame
Hello!
rapid spruce
So payment_method.automatically_updated would be sent when a card's details are updated through the automatic card update process and payment_method.updated would be sent for other updates that happen on the Payment Method.
Likely, you would want to listen to both event types
next flame
Got it!
Another question is that, will these payment_method events be able to capture the customer.source.updated changes as well.
Asking this, because, some of the customers are using source. If we completely stop listening to customer.source.updated event, it'll be a problem
rapid spruce
I suppose my question would be, why stop listening to that event when you have Customers that still have a Source that is in use?
next flame
The whole plan is to deprecate the source event listener and migrate to payment method related events, but only if payment method can capture source related events as well.
If not, we'll fallback to the source event only for now probably.
rapid spruce
Those are different things though. I expect that payment_method.updated and payment_method.automatically_updated events are delivered for objects of type pm_abc123 and customer.source.updated events are sent for objects of type src_abc123 and card_abc123