nicelydone_api | Stripe Developers | Page 1

teal spruceBOT Apr 23, 2025, 5:47 PM

#

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

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

#

warm cloud Apr 23, 2025, 5:47 PM

#

Hi, what do you mean by 'future-proof' here?

ripe skiff Apr 23, 2025, 5:48 PM

#

I remember last time I had troubles support strongly recommended some method, but I forgot which

#

I guess I was marketed to do intent. As checkout was old or unsecure

warm cloud Apr 23, 2025, 5:51 PM

#

Hmm, CheckoutSessions is secure. I'm unsure what the discuss was around, can you add more details?

Depending on your developer skills, and business use case, https://docs.stripe.com/payments/online-payments#payment-uis we do recommend multiple flows. Checkout is still one of the recommended approaches.

ripe skiff Apr 23, 2025, 5:51 PM

#

ok thanks

warm cloud Apr 23, 2025, 5:52 PM

#

Sure

ripe skiff Apr 23, 2025, 5:58 PM

#

sorry are you still here?

it was discussion Charge API vs Intent (session) API

Is charge ok to use in 2025?

warm cloud Apr 23, 2025, 6:01 PM

#

Ahh, I see

#

In that case, you'd wand to use PaymentIntents API, https://docs.stripe.com/payments/payment-intents/migration/charges

#

Charges is our legacy product

#nicelydone_api