eranga-3ds

[modest coral]

3ds can always be an issue

Even if a card has been set up properly

It's up to the bank on whether or not they want to require it again in the future

[oak rapids]

eranga-3ds

[shadow vine]

So adding a credit card on the customer portal doesn't necessarily mean we can charge it later.

How are we supposed to handle subscription kind of scenario where the user might add their payment information using the customer portal, and will not be online when our systems try to charge for the subscription?

[modest coral]

This is true of every integration

Banks can require 3ds at any point

Your integration needs to be robust enough and have a flow to bring the user back online to auth the transaction in case the bank requires 3ds

Even with subscriptions this is possible (although not as likely)

[shadow vine]

I see. Thank you for your insight @modest coral 🙏

Is there a way we can strengthen this by reducing the probability of bank requiring 3D authentication.

Maybe like using a checkout session at the beginning of the subscription (or at somepoint when the user is on free trial using "setup" as mode of checkout session)?

[modest coral]

So the customer portal flow you're referring to already does this

It uses setupintents to give you the best possible chance of success for future off session charges

[shadow vine]

I see. Thank you for the help.