#jkile9_api
lean nebulaBOT
đ 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/1282791940244635721
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
celest tapir
Hello, SetupIntents are reccommended if you are not charging the user up front. We have this doc that shows how to save a PM via a SetupIntent and charge it later
https://docs.stripe.com/payments/save-and-reuse
If you are taking a payment up front, we reccommend using a PaymentIntent instead. PaymentIntents have a property called setup_future_usage, if you set that property, Stripe will save the payment method for re-use while taking payment on the payment intnet. We have this doc that shows saving and re-using a PM here
https://docs.stripe.com/payments/save-during-payment?platform=web&ui=embedded-form
chilly jackal
So SetupIntent is in fact what I would want to be doing? I just wasn't sure if a SetupIntent was only valid for a single PaymentIntent
It seems like that was what I was looking for, but just wanted to make sure that once it's setup, they are able to use that card repeatedly to purchase credits without needing to add their payment method again
Another related question: if we already have customers onboarded using the Payment Source API, they shouldn't need to be migrated moving forward, would they? i.e. needing to add their payment method again?
celest tapir
It seems like that was what I was looking for, but just wanted to make sure that once it's setup, they are able to use that card repeatedly to purchase credits without needing to add their payment method again
Saved cards will be re-usable multiple times. PaymentMethods are only usable once if you don't save them to a Customer before they are used on their first payment, but both of the methods that I linked to will attach the PM to a customer, so the PM will be re-usable however many times.
Another related question: if we already have customers onboarded using the Payment Source API, they shouldn't need to be migrated moving forward, would they? i.e. needing to add their payment method again?
Correct. Our PaymentMethods API is backwards compatible with card sources. You can simply pass a source ID to any parameter that expects a payment method ID in our API and it will work.
chilly jackal
Amazing! Thank you so much for the assistance, I appreciate it! Have a great day!
celest tapir
Of course, happy I could help clarify