zenoitulos

[wicked copper]

ANy future payment always has a chance of another 3ds authentication flow

That said, the "setup" you do on your platform is expected to be usable by a card cloned to a connected account, too

[wicked copper]

You can't guarantee that won't happen, and your integration needs to be prepared to contact the customer for authentication if the issuer declines the later payment as authentication_required

[unique walrus]

so when you say "...the "setup" you do on your platform is expected to be usable".... can you elaborate on the word "usable"? Like should I understand that as Stripe does ?something? to try to "skip" 3DS for the future payments in the cloned payment method case but cannot guarantee this?

[sonic jungle]

👋

... should I understand that as Stripe does ?something? to try to "skip" 3DS for the future payments in the cloned payment method case but cannot guarantee this?
Correct, stripe will try its best to get a 3DS exemption for cloned payment method. But if issuers do prompt for authentication then your integration needs to be able to bring back customer on-session and have them authenticate the payment

[unique walrus]

ok, got it. Thank you for answering