#dragan_best-practices
pure heronBOT
👋 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/1240231195388678184
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
ruby berry
👋 happy to help
if you want to integrate with subscriptions we don't recommend using SetupIntents
so neither of these resources is the way to go
soft atlas
Hey, @ruby berry. Thank you for the feedback.
What would be the approach then?
ruby berry
soft atlas
Just to give some more context.
Users will login. They can be either members or admins that can create resources. Resources have to be paid.
The idea is to have a separate section in the Users settings page which will allow them to add a payment method (card) that will be used later in the app.
They will have a section to choose the subscription plan (atm we’ll have only one). When creating a subscription plan the already added payment method will be attached.
Then they can go to our dashboard and create resources. Before we create the resources for them in backend we need to bill them via already added card and selected subscription plan.
soft atlas
https://docs.stripe.com/billing/subscriptions/build-subscriptions?platform=web&u...
I'm looking at the docs now.
ruby berry
you can use SetupIntents if you want and then update the customer's invoice_settings.default_payment_method
but you might face another 3DS authentication after adding the subscription
soft atlas
but you might face another 3DS authentication after adding the subscription
Exactly, I've read that info somewhere that another 3DS will occur on the first recurring payment.
Another important aspect is that we want to allow customer later to have multiple payment methods.
ruby berry
yes sure
but this is why we don't recommend it in the case of subscriptions
but there are use-cases where you don't have other choices than to use SetupIntents
soft atlas
https://docs.stripe.com/billing/subscriptions/build-subscriptions?platform=web&u...
Aha, understood.
I guess for the beginning where the majority will use only one payment method we can go with this approach.
And later on, when we allow them multiple payment methods we would need to rely on SetupIntents, right?
ruby berry
yes that's correct
soft atlas
Sounds good. Thank you for the clarification and the speed of light help!
pure heronBOT