#shuffo_best-practices

1 messages ¡ Page 1 of 1 (latest)

shadow flowerBOT
#

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

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

prisma geode
#

As for whether you adopt Elements with Checkout Sessions now, that is entirely up to the requirements of your project

empty lynx
#

Wow, I've been searching through your docs for a very long time and couldn't find this page, thanks!

Yes, checkout sessions seem to be marked as "public preview" so perhaps we wait... although it would be interesting to know, have you seen an up tick in people moving to that recently? And I'm guessing it is going to be the main way to setup things going forward?

prisma geode
#

Yes generally that is a going to become the 'recommended' path for users in time

#

(I can't really say much beyond that, but can help with any techical Qs you have about those APIs)

empty lynx
#

If we use Stripe server/client code that is fixed to a beta release, such as mentioned here: https://docs.stripe.com/checkout/custom/quickstart#set-up-server

I assume any breaking changes only come into play when we upgrade to a newer version?

I can see you have a changelog - https://docs.stripe.com/checkout/elements-with-checkout-sessions-api/changelog

Keep track of changes to the Elements with Checkout Sessions API integration.

Use Elements and the Checkout Sessions API to build a checkout page.

prisma geode
#

Yes, exactly

#

We keep any breaking changes during the preview period behind version increments (similar to our main API versioning really)