#eli_paymentintent-webhook

1 messages ¡ Page 1 of 1 (latest)

ivory sigilBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1253803472747499611

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

lusty finch
#

Yeah you should never rely on the customer reaching the return_url. Anything could happen (browser crash, network issue, etc). You should instead rely on webhooks: https://docs.stripe.com/webhooks. And use your database/caching to prevent duplicate event processing

icy whale
#

any way to take action client side? All my conversion code is client side and i need to clean up the cart from localstorage as well. This will be a bigger migration from confirmcardpayment otherwise

lusty finch
#

I mean return_url is the alternative

#

But it's discouraged due to issues I mentioned above

#

We never recommend doing that

#

Webhooks is the right way to implement order fulfillment/payment success logic

icy whale
#

Okay, thank you

ivory sigilBOT