#morteza_webhooks

1 messages ¡ Page 1 of 1 (latest)

past moatBOT
#

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

📝 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.

shut storm
#

We have a food ordering platform, users go to checkout and start the payment process while it's being processed they go back and add remove items from the order, what's the best practice to handle this ? should we depend on stripe or handle on our backend ?

stuck granite
#

Hi! That's something you'd have to handle in your app - once a 'cart' is paid for it should no longer be able to be changed.

shut storm
#

but the problem is what if payment status takes time to be succesful

stuck granite
#

Once they click 'pay', make the cart unmodifiable, and there's no problem.

shut storm
#

and let me ask you something, we have use stripe-hosted payment page and we have specified payment_methods only for cards. w've defined success and cancel url and when we are redirected to success does it mean that payment was 100% successful ? I asked other colleagues of yours and they said since card payment method is synchronous so when you are redirected to success url it means that card payment was 100% successful and you can fulfill the order

stuck granite
#

With a CheckoutSession, a customer arriving at the success URL means the payment was successful. You would have also received a checkout_session.completed event as well.

#

But you can always retrieve the Checkout Session and confirm, which is never a bad idea.

shut storm
#

so you are saying that we should alwasy rely on webhooks ?

#

and never trust the success callbacks to fulfill the orders

stuck granite
#

I'm quite curious how you came to that conculsion based on what I said there.

#

But also, you are correct - it's always possible that a user may not return to the URL, so you should use BOTH the success URL and the webhook event to trigger next steps.

shut storm
#

I just wanna know if we can rely on that success urls as 100% success

#

or in sdk we get error, success variables and if payment mthod is sync then we can consider them as a success

stuck granite
#

Assuming you're including the Checkout Session ID in the URL, 100% of people who land there with a valid Checkout Session ID did successfully complete the Checkout Session.

#

That doesn't mean 100% of the people who completed a Checkout Session end up there though.

shut storm
#

one of my colleagues say that we have experienced a situation in which user has make a purchase at stripe-hosted page and got redirected to success url but we with webhook we realized that payment was not successful and money had been withdrawn to the user's card

#

is this even possible ?

#

since card payment is sync

stuck granite
#

What's the Checkout Session ID for that one?

stuck granite
#

Any luck finding it?