#izag_webhooks
subtle spadeBOT
đ 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/1386695242023178320
đ 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.
- izag_api, 5 days ago, 5 messages
teal jetty
Hi, can you share the Payment Intent id where it took 3 mins to trigger that event after the confirm call?
pine basin
I apologize, I have now been informed that there was no delay. It was simply the time it took for the user to complete the 3ds.
However we would like to know what is the recommendation for updating our users after a successful payment. What is the max amount of time we would need to wait before assuming failure?
teal jetty
No worries, there is not a blanket timeline we can share. Here is our recommendation, https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=elements#web-submit-payment
You provide a return_url to this function to indicate where Stripe should redirect the user after they complete the payment. Then, after you get the events, you can start your order etc
pine basin
Great. Can I tell you the process we follow? And then maybe you could confirm if it up to the standards?
We have a react frontend that confirms the payment. The return url points to our loading ("payment processing") page. Out .net backend receives the webhook call with the payment confirmed/ failed. We then log the payment in our db and send the status to our frontend using SignalR to either allow the user to use the app, or provide the next steps in cases of failure.
teal jetty
What do you do with payment methods that do not get teh success of failure right away? Some payment methods require a few days for the bank to respond. What do you do in those cases?
pine basin
So for the moment we offer only cc and paypal. Which which payment methods should be aware of that? We are planning to implement more in the future
teal jetty
I highly recommend that you follow https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=elements#web-submit-payment
instead, and not wait for the event to show the success page.
pine basin
so we have a few processes that run on our database after a payment is confirmed and they would not be able to use any of the tools we offer before that, that is why we opted for the webhook approach. But we might be able to switch per your recommendation, if you think that this is the best apprach.
teal jetty
Yeah, what I shared is our recommended flow and especially if you plan on adding more payment methods it would be even more pertinent
pine basin
I understand. Thank you!