#darkstriker_code
wheat cobaltBOT
👋 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/1354189076194136077
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
formal slate
I'm not sure if the user is explaining the correct issue but I thought you might be helpful
random hedge
Hi, do you have the checkout session creation id so I can further look? What was the exact error? Did you attempt to go through the checkout again? Did it work? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
formal slate
no this is an odd scenario
i have had over 600 users work correctly but this one user had this issue
random hedge
It could be an internet connectivity issue but without a concrete example I will not be able to review further
formal slate
that's what i'm thinking but this is where i'm confused
The message said Error no Internet. Then the user refreshed and this screen appeared. Payment went through.
random hedge
So you do have the checkout session id. Can you share that with me so I can further look?
formal slate
i have emailed the person who manages the stripe account to provide me with more information
random hedge
Sounds good
formal slate
have you seen that message before though?
random hedge
Specifically, on the fulfillment part we discuss how you'd listen to events:
You can’t rely on triggering fulfilment only from your Checkout landing page, because your customers aren’t guaranteed to visit that page. For example, someone can pay successfully in Checkout and then lose their connection to the internet before your landing page loads.
Set up a webhook event handler so Stripe can send payment events directly to your server, bypassing the client entirely. Webhooks provide the most reliable way to confirm when you get paid. If webhook event delivery fails, Stripe retries multiple times.
formal slate
You can’t rely on triggering fulfilment only from your Checkout landing page, because your customers aren’t guaranteed to visit that page. For example, someone can pay successfully in Checkout and then lose their connection to the internet before your landing page loads.
that's probably what happened
random hedge
Likely
wheat cobaltBOT
random hedge
Given that they payment succeeded, it is likely the issue. I'd highly recommended implenting and listening to the events to fulfill your orders moving forward
random hedge
Hmm, that is not 'new' to Stripe.
We document how you can build this here: https://docs.stripe.com/webhooks/quickstart
formal slate
is there a way to force the payment to not succeed if a message code of some kind is received?
random hedge
No there is not
random hedge
Can you copy and paste the pi_ id for me?
formal slate
the payment id?
nevermind i see
i hate to ask the guy i work with to do that
i'll type it out for you
copper sable
Hi! I'm jumping in for my colleague here.
There isn't really anything for us to check here; there's no way for us to know what happened on your or your customer's side.
formal slate
pi_3R5qFOCJj8vWaDbW10sR2TF0
copper sable
Listening for relevant events is critical for any asynchronous payment methods (or anything else asynchronous).
formal slate
i understand
this is our first issue
and trying to understand this better
did stripe take a long time to respond
did the user not have internet after stripe confirmed
just trying to better understand this
copper sable
Almost certainly the latter.
formal slate
i'm sorry dont know what that means
copper sable
did the user not have internet after stripe confirmed
That is the latter of the two options - and the most likely cause.
copper sable
👍 Let me know if you have any questions.