#eckhartpark_code
dawn vortexBOT
đ 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/1358947752763195424
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
agile rapids
hello! for something like this we strongly recommend webhooks
https://docs.stripe.com/payments/payment-intents/verifying-status#webhooks
the page i linked to includes other solutions for handling this client-side, but client-side flows are always far more brittle
agile rapids
yeah not really, most of the client side implementations are more useful for displaying data to the customer right away
for server side / database related actions, webhooks are far more reliable
for example, after redirecting the user you can use retrievePaymentIntent to verify if they've paid and show them something or not show them something or give them a confirmation etc
but relying on client side code means you're adding a dependency on whatever is happening in their browser to send the data back to your server
gentle seal
I see, should I still use confirmpayment to do the redirecting since that works?
cuz it successfully redirects
agile rapids
yep! confirmPayment is still an important part of the flow
gentle seal
ahhh ok
agile rapids
if you never call that, then the payment will never confirm