#iammaxim_unexpected
clever viperBOT
đ Welcome to your new thread!
âąď¸ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!
đ 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/1212208431071764521
đ Have more to share? You can add more detail below, including code, screenshots, videos, etc.
â˛ď¸ 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. Thank you for your patience!
snow dragon
I'd like to add that I am unfamiliar with what an object=source even is.
honest aspen
hello! taking a look and will get back to you in a bit!
to simplify, Sources are legacy API objects that predate PaymentMethods. You can read more about Sources here if you're interested https://docs.stripe.com/sources. In any case, our APIs are backwards compatible and you can use Sources with PaymentIntents
To answer the question of how it got created, did you perform some kind of migration on the 21 Feb?
snow dragon
No, we did not
I am completely perplexed how, even in the dashboard, there is a object=source for this cus
Oh, I think I understand now.
It looks like the user added a different payment method through
Origin: https://invoice.stripe.com/
And not our systems
honest aspen
ah, great that you managed to figure that out!
snow dragon
So if that happens, it creates a object=source and not object=card. Is that correct?
honest aspen
yep
but depending on the situation, a PaymentMethod might be created instead from an Invoice. A PaymentMethod would not be returned from the sources or default source parameter though
you can find the default PaymentMethod on a customer in https://docs.stripe.com/api/customers/object#customer_object-invoice_settings-default_payment_method