greggles_best-practices

[merry drum]

👋 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/1215788054917288046

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[quaint mango]

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• greggles_unexpected, 1 hour ago, 18 messages

[half swan]

@pastel brook I'm sorry I don't really understand this sentence

Create a setupintent first or collect payment method first then create the setupintent as needed?

[pastel brook]

https://docs.stripe.com/payments/save-and-reuse
This documentation outlines the process of setting up the setupintent which returns the client secret necessary to create the payment element which collects the payment method.

https://docs.stripe.com/payments/accept-a-payment-deferred?type=setup
This one outlines how to create the payment element first then
https://docs.stripe.com/payments/accept-a-payment-deferred?platform=web&type=setup#create-intent
create the setupintent after.

It seems to make little sense to create a setupintent everytime someone visits an account page if they would want to update their payment method a very small percentage of those times

[half swan]

I mean SetupIntents cost you nothing so it's not really an issue. But sure some developers don't like that and that's why we built that "deferred" flow

so yes it's totally fine to collect payment method details first and then create+confirm a SetupIntent server-side if they want to attach a new PaymentMethod

[pastel brook]

Fair point.

Thank you, I'll give it more thought.

[half swan]

let me know if you have any questions about it, happy to chat more!

[pastel brook]

Thank you, I appreciate your help.