#gaston-webhooks-3ds
1 messages · Page 1 of 1 (latest)
@pine acorn you should ~never use the source.* events, those are old/legacy and deprecated
Great to know that! How do we handle 3DS failure/ignore cases from webhooks?
You mostly don't, there's no "expiration" in that flow, the PAymentIntent just stays in requires_action
Great! Is it possible to decline a 3DS payment? If so, how can I capture that from a Stripe webhook? I am sorry if my questions sound weird, but it's the first time I'm dealing with 3DS/
Hello I'm part of Gaston's team and we mention the expired because in the documentation it says:
source.canceled A Source object expired and cannot be used to create a charge.
I know it exists but it's legacy, that API was deprecated over 3 years ago. It still works
Great, thanks. What do you recommend us to do in the case the user decides not to verify that payment? Is there a way to cancel that flow ? Since our flow is waiting for a verification
We don't have an "automatic expiry" so you would track this on your end. For example run a cron job daily to look in your database for PaymentIntents that were waiting on 3DS and either email the customer to get the back on session, or cancel the PaymentIntent for example
Great that's a good solution. Thank you very much for your time and help it's well appreciated 🙂