#aquas-confirm-reload
1 messages · Page 1 of 1 (latest)
@random heart not really. The whole point of this is to handle any payment method, some will go to a partner first and then back to your return_url. So you have to be resilient to that, and there's no reason to "wait for the webhook" in that case
@random heart does that make sense?
yeah that makes sense
You can technically disable the redirect for card payments though
https://stripe.com/docs/js/payment_intents/confirm_payment#confirm_payment_intent-options-redirect it's discouraged but it works
i see, so if I included
redirect: 'if_required',
Then for non-redirect payments, I could await {paymentIntent} from stripe.confirmPayment and it won't refresh page, and then for redirect payments it will force refresh page as default
yes
discouraged as in it's out of the ordinary or potential security issue?
Hi @random heart I'm taking over this thread
hi jack! sounds good