#priyanka_26911

1 messages · Page 1 of 1 (latest)

worn tapirBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

old quest
#

is there anyone used setup intenet by considering 3ds enabled cards?

#

Hello! If you set up the Payment Method properly for future use it significantly reduces the chance 3D Secure will be required later, but there's always the possibility it might be required anyway. You need to make sure your off-session payment flow accounts for that possibility and, if authentication is required, you need to get your customer back on-session to complete the payment.

cyan wagon
#

in what cases it might require extra action in case of off_session?

#

In the above document, it is not very clear about 3ds enabled cards

old quest
#

The card issuer can require 3D Secure at any time for any reason.

#

Including for off-session payments that were set up for off-session use.

#

Again, setting them up for off-session use significantly reduces the chance that 3D Secure will be required, but that's all. Nothing can prvent it from happening 100% of the time.

cyan wagon
#

so you mean it may not ask everytime, but it might ask for some transactions

old quest
#

Yes.

#

And when authentication (like 3D Secure) is required you need to bring the customer back on-session to complete the payment. Most people opt to send the customer an email saying their payment failed with a link to a page that lets them complete the failed payment.

cyan wagon
#

okay for how much time that redirect url will have the validity ?

old quest
#

Which redirect URL?

cyan wagon
#

in case of 3ds, there will be a redirect url to enter otp right

old quest
#

No, if an off-session payment fails because it requires 3D Secure it will be a decline.

#

The decline code will be authentication_required and the process will halt at that point.

cyan wagon
#

oh.then how to proceed further ?

old quest
#

You bring your customer on-session and attempt the payment again with them present.

cyan wagon
#

we have a scenario, where wallet top up should happen automatically when wallet balance goes below certain threshold

How to achive this case?

or instead of off_session, can we set usage as on_session while creating setup intent?
SO that for 3ds transactions, it will return back with status as requires_action with redirect url

old quest
#

No, that URL is short-lived and won't work.

#

Here's what you need to do: set up Payment Methods for future off-session use. Most of the off-session payments will likely succeed. For the ones that are declined, for any reason (including 3D Secure/authentication required) bring the customer back on-session and have them try paying again while present.

cyan wagon
#

okay that means future transactions wont work for 3ds enabled cards without user reinitiating transaction again ?

old quest
#

Yes.

#

But only if 3D Secure is required while they're off-session, which should be rare.

#

But if that does happen you treat it like any other decline, like insufficient funds or anything else.

cyan wagon
#

we have exactly same case actually.

#

and when you say URL is short_lived...after how much duration that will be expired ?

old quest
#

Assume it expires immediately. You should never email it or anything like that.

cyan wagon
#

got it.thank you

#

is there any way we can achieve future transactions with 3ds enabled cards without user intervention ?

old quest
#

No, there's no way to guarantee that 3D Secure will not be required.