#zenoitulos
1 messages · Page 1 of 1 (latest)
- This depends on the authentication method but I think the intent falls back to
requires_payment_methodafter 24 hours
- You should notify the customer that they did not complete their payment and they need to come back on-session to complete it
ok, so for #1, you are saying that after sometime the intent status changes but there are no timeouts or time limits between stripe and the bank UI where the customer would complete the auth?
No that is not what I said
The Payment Intent does not fail, it transitions back to a state of requires_payment_method. This means it requires your customer to come back on-session and provide new payment method details
sure, i get that. I think what I am asking more of is what is the customer experience if they were to take a "long time" completing the 3DS auth? and is there any timeout.
like what if we get the redrect_url back from stripe and the customer is forwarded there and they sit on their banks page for 2 hrs. Would it still work?
like is Stripe expecting some result in some amount of time?
As I said, it depends on the bank and their authentication method. Some authentication can take multiple days
got it, so that "max" if any is bank specific
so sounds like stripe does not care. however long the bank auth process takes, when that is submitted back to Stripe, the process will continue. correct?
Yes thats right -- or it might result in a failure if the bank times out and notifies stripe as a failure/abandonment
ok, and for #2, outside of customer notification... no other impact. In that state, there should be no authorization/funds held on the card, correct?
Correct, if the customer fails a 3ds flow there should be no auth and aside from trying again to complete the payment you don't need to take any action (eg, cancel/refund)
perfect. thanks so much for all the answers. I think this clears it up