#wei_webhooks
candid walrusBOT
đ 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/1245427848450146372
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
light vigil
So it sounds like your system is using some amount of legacy tech, along with the more modern stuff. The source objects are legacy and were replaced by Payment Method objects
sacred moth
We checked 10k payment intents with script. A small part of payment intents (3%) have source field, but none of them have source and payment_method at the same time.
We don't know why there were some Payment Intent with source field & null payment_method.
light vigil
That makes sense. You would only ever use one or the other
sacred moth
Is it because these payment intents were created before a certain datetime?
light vigil
More likely that the Source objects were attached to a Customer before a certain time. Or there's part of your system that still creates Sources. You would need to spot check a few of those objects and/or loop through a list of them and retrieve (https://docs.stripe.com/api/sources/retrieve) each one to get their created attribute (https://docs.stripe.com/api/sources/object#source_object-created)to figure out why they exist
sacred moth
I understand. So, even if legacy sources still exist in our system, as long as we check both the payment_method and source fields, we can reliably infer the payment method. Is my understanding correct?