#pistonmaster_error
1 messages Β· Page 1 of 1 (latest)
π 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/1375366547933233194
π Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- pistonmaster_unexpected, 3 days ago, 61 messages
With checkout value = 0β¬
With a checkout value >0β¬
The error message is from: https://api.stripe.com/v1/elements/sessions?deferred_intent[mode]=setup&deferred_intent[currency]=eur&deferred_intent[payment_method_types][0]=card&deferred_intent[payment_method_types][1]=paypal&deferred_intent[payment_method_types][2]=amazon_pay&deferred_intent[setup_future_usage]=off_session&deferred_intent[capture_method]=automatic_async¤cy=eur&key=<my public key>&_stripe_version=2025-03-31.basil&type=deferred_intent&locale=de&referrer_host=<my domain>&elements_init_source=custom_checkout&stripe_js_id=<my stripe js id>&checkout_session_id=cs_live_a1Z5LGCCV2EvHswaDVfJSaudav0TyoAIG13Nf2HrCrPISj2q96wNCshyRh
Stripped out a few secret values.
The request is made by web elements in checkout session mode (ui_mode: custom)
I can send full URLs where the error can be seen privately.
hello! Gimme a while to take a look
can you share the request id from that above request ^. It should be in the headers section of the network request, and have the prefix req_. If you ended up needing to create a new Checkout Session id, that's fine too, I just want to take a look at the request for that error
Sure! request-id req_wZw3HQqyUYmNVR
great! π at it now
All other requests from the web elements in checkout session mode got a 200 response, so it must be this one that's the problem. Perhaps something wasn't properly coded to support 0β¬ checkouts in live mode.
Also tried hiding the PaymentElement now if value = 0β¬, but it still fails
e.g. here it still hides the address elements even if the PaymentElement is removed
hmmmmm, how odd, I think this is going to take us a while to look into, it'd be best if you wrote in with your test site, login details (if required) and steps to navigate to the page where we can reproduce the issue.
I'm going to DM you a link where you can write in
Hello @opal haven, we have sent you a direct message, please check it at https://discord.com/channels/@me/1375376786619371571
- πThe message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
π will do