#denciopal-3DS

1 messages · Page 1 of 1 (latest)

tired plume
#

Hi @prisma cargo the live 3DS page is provided by the issuing banks, so it's up to the issuing bank if they have implemented a timeout on the page.

prisma cargo
#

Ahhh.. I see. So no way for us to set maximum payment time to complete stripe else we reject it

tired plume
#

You can always check the PaymentIntent status and decide the course of action. i.e., if the PaymentIntent status is requires_action, you can call stripe.handleNextAction to launch the 3DS flow for the same PaymentIntent.

prisma cargo
#

yes, some users are stuck for a while here

and we have to wait for them to return back to the app

tired plume
#

stuck for a while -> you mean the 3DS page is not loading or the user need some time to complete the 3DS authentication flow?

prisma cargo
#

some users take time. to finish the 3d flow

#

maybe they have to wait for the OTP

#

and 2 cases where we have to release the tickets as 10mins has pass and the user has not return back to the app

#

but the payment go thru eventually after more than 10mins

#

so when they came back to the app, the ticket is gone already

tired plume
#

I see. Maybe you can think about a way to encourage customers to save their payment methods in your app/webpage first? so that they can easily use the saved payment method to purchase the ticket later.

prisma cargo
#

that makes sense

prisma cargo
#

thanks a lot

tired plume
#

No problem!