sayori_best-practices

[bronze hinge]

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.

• sayori_code, 6 hours ago, 15 messages

[clear arrow]

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

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

[patent fiber]

an example of the existing stripe elements flow:

[waxen sail]

Yes your intuition is correct. PaymentElement does require some separated call to the Tax Calculation API. But it's the balance, as Elements has some fundamatall differences with Checkout that sometime it's not easy to just switch

With that being said, no objective if you could just move everything to Checkout and happily continue

One of the key differences is Checkout is Stripe hosted, where Payment Elements are embeded into your website

[patent fiber]

thanks - wanted to make sure i wasn't overlooking something obvious that would have been simpler

we've been happy with Stripe Checkout in our second subscription system but haven't really put much thought into whether we should migrate the old system. are you aware of any particular difficulties/pain points when transitioning an existing Elements implementation into a Checkout system?

thinking solely on subscription access, ease of customer renewal, etc... frontend changes can be dealt with

[waxen sail]

It' hard to tell, because they are kinda completely different experiences. There are many things to compare, but in general PaymentElements is more flexible/customizable, and Checkout is doing a lot more for you. That you will have things you can't control anymore

I would suggest test out both flow in Test mode and run an thoroughly analysis on both of them