splitrox_checkout-redirect

[icy dock]

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

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

[sour moss]

Hi there 👋 it's hard to say without more details on what your customers are seeing. Are they encountering network issues when being redirected to your success URL?

@cloud mango just wanted to check and see if you were around to tell me a bit more about what your customers are seeing?

[cloud mango]

Hi, yes I'm still here, well my customer don't have that much information at this moment as it is already over. This is what I was able to get from him:

The purchase is over so right now is little bit difficult, also I'm not sure if they are encountering network issues but I'll ask

[sour moss]

Hm, that isn't much to go on. I'll look to see if we've gotten similar reports of this behavior when using PayPal, but offhand it's not something I recall hearing about recently.

[cloud mango]

I wouldnt say is only PayPal, being honest, most of the payments i had issues with are with iDeal, i opened a ticket with one of your work colleages and they said that was not an issue but by that time I didn't had logging on my side but right now i can confirm that indeed i'm not getting the call for some reason

[sour moss]

Let's take a step back. Do you have business logic relying on the page at your success URL being loaded? Like do you have order fulfillment or access control that is triggered by that page?

Or is the customer experience the only concern here, rather than downstream processes not triggering?

[cloud mango]

Indeed business logic relying on the page

Thats my main concern

Only if there is a safer way?

[sour moss]

Gotcha! That was my thinking, and this is actually why we don't recommend relying on logic on the success page. Intermittent network issues, like your customer losing connectivity unexpectedly after completing payment, can disrupt the redirect and rendering of your page.

Instead we recommend setting up a webhook endpiont to listen for Events that we emit. Those use direct communication between our servers and yours, so no client network connectivity to worry about, and have built in retry behavior in case there is a communication issue.
https://docs.stripe.com/webhooks

And this guide goes into more detail about our suggestion for order fulfillment that specifically pertains to using Checkout Sessions:
https://docs.stripe.com/checkout/fulfillment

[slate inlet]

splitrox_checkout-redirect

[final knot]

hi, I am not from the stripe team

This is a bad approach, if the payment has not been completed users can still be redirected to success URL

you should set up webhooks and listen for payment_intent.succeeded

[slate inlet]

That's definitely incorrect to recommend this

checkout.session.completed + success_url are definitely the right approach and what we document. For "synchronous" payment methods such as card payments or Link payments, when the end customer hits success_url they have already paid.
Some payment methods are incorrect such as bank debits in which case there are additional Events to listen for.
You should not listen to payment_intent.succeeded Events when using Checkout

[final knot]

Yes, but for bank transfer , sepa , etc. payment can fail even after the checkout.session.completed

payment_intent.succeeded makes sure the payment has sucessfully processed.

I was told this by your support team.

Please tell users all possible cases.