NicksStocks

[potent prairie]

is there way in stripe service that we can user to make sure all the first transaction and recurring off-session transaction can go through 3DS but recurring without user interaction?
The wording here is really difficult to understand. What are you asking?

[sullen haven]

how can we make sure all the recurring transaction are 3DS authenticated currently we are seeing only 1st one shows the transaction is 3DS authenticated but recurring doesnt show that in timeline of transaction

this is asking due to liability shift when dispute happened

sorry @potent prairie question was sent from the different account

[potent prairie]

Are you asking about existing payments or for payments in the future?

In other words: are you asking how to tell if 3DS was used on a payment? Or are you asking how to make sure that 3DS is used for all payments?

[sullen haven]

yes, i am asking to make sure that 3DS is used for all the payment first and recurring. but not sure if possible for recurring transaction do we need user interaction cause first time when user ahve added the payment details it went throught the setupIntent flow

[potent prairie]

Yes, if you want 3DS to re-authenticate for all future transactions, then you would need to bring the customer back into the payment flow. Otherwise, the first time they authenticate via 3DS carries over to future payments

[sullen haven]

yes i want them to do only first time when during SetupIntent after that all future usage of the same payment method i dont want request the 3DS flow. but then does all the future transaction count in liablity shift incase of dispute or not?

[potent prairie]

If you're using subscriptions for future use, I believe it does count toward the liability shift, but we don't have a lot of info on that in this channel. This chat is focused on developers and API integration questions. Our support team will be able to assist you better than I can: https://support.stripe.com/contact/email