#tunnnna

1 messages · Page 1 of 1 (latest)

meager solarBOT
cunning plaza
#

Would be appreciated if you can provide a PaymentIntent ID so I can look closer

compact cobalt
#

Yes, I set up correctly. This has only happened once. The other correctly substitute {CHECKOUT_SESSION_ID} with a Checkout Session ID. I don't know the PaymentIntent ID but the IDs before and after this occurred are "pi_3M4D5hBhKZo8IQRf1KKFisAb", "pi_3M4CMXBhKZo8IQRf0xr472qD", "pi_3M4C0NBhKZo8IQRf01immHfQ", "pi_3M48GWBhKZo8IQRf0GjGVTTy".

cunning plaza
compact cobalt
#

The request ID is req_L5AosJm25BD3gF.

compact cobalt
#

I think it is possible that the url (/{success_url}?session_id=%7BCHECKOUT_SESSION_ID%7D) was typed directly into the browser if Stripe substitutes {CHECKOUT_SESSION_ID} with a Checkout Session ID without exception.

cunning plaza
#

That's only the Get request, We would like to know the request to create that Checkout Session Id

#

I am looking at POST requests around that time and see you are passing in

https://reel.lumiere.theater/seat_success?session_id={CHECKOUT_SESSION_ID}

which looks correct to me

#

Is it possible that Stripe does not substitute {CHECKOUT_SESSION_ID} with a Checkout Session ID after the customer is redirected to the success page.
I don't think this would happen, but if we can find the concrete Session Id, it would help investigate easier. Even better if you can reproduce consistently