#kryze_unexpected
warped waspBOT
👋 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/1297961593518424167
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
stable crest
Hi 👋
Can you share the Checkout Session ID?
obsidian charm
Yes but is the conversation private ?
stable crest
Yes and the Checkout ID is useless to anyone not a Stripe Admin or your account admin
obsidian charm
pi_3QBasTEuhOHWb2vb111B9Sx7 and pi_3QBavFEuhOHWb2vb00RHNzhM
stable crest
Taking a look
So which one represents the checkout session that did not redirect?
These are two entirely separate checkout sessions
warped waspBOT
obsidian charm
Yes but I'm not exactly sure I can only tell you what the client tell me because it's the second time we are contacted about that
Let me rewrite his message here
sly raven
👋
Stepping in
Just to be clear, this is a public server so this chat is not private
But the object IDs are safe to share here
obsidian charm
The client told me : She got through the checkout and filled her information, she then click to pay, and got nothing, she thought the payement didnt went through so she clicked again but she got charged two times
The strange part I saw is that there is a payement at 13:34 that end also at 13:34, but the other one start at 13:31 and end at 13:37
sly raven
Yeah as my colleague noted these are two different Checkout Sessions. We don't prevent multiple Checkout Sessions from being created if a customer goes through the checkout flow multiple times.
obsidian charm
She didn't went through two times (as she said) but rather clicked two times on pay
That's why I'm wondering what happened
sly raven
Yeah that doesn't really make sense here... these are two different hosted checkout sessions.
Meaning the customer was redirected twice to a hosted Checkout page
It is impossible to have multiple successful payments for the same Checkout Session
And that did not happen here.
obsidian charm
I'm agreeing with you because I didn't saw anything strange on my logs, looked like she went two times on the checkout flow
Also, she should have gotten the Validation page displayed two times since its logged two times at the right hours on my logs
And Stripe showed me she got the emails after the payment
sly raven
Yeah so if you want to prevent something like this you could check if there are any open Checkout Sessions after your customer successfully completes one, and then you could expire any open Sessions for that same Customer (based on the Customer ID for instance) using https://docs.stripe.com/api/checkout/sessions/expire.
But you would have to implement this logic yourself -- it isn't something provided out of the box