jeffreyb

[cedar galleon]

hi! if you want to have a process where you save the card, authenticate it that point, and then subsequent payments don't require 3DS, you'd use the 3155 card from that link

[main zealot]

Right, is there an instance in production where a customer might have a card that requires authentication all the time like the 3184 card?

[cedar galleon]

yep! For example I believe all cards in India work that way. More generally though, it's the case that banks can give exemptions on off-session merchant-initiated-transactions (confirming a PaymentIntent with off_session:true) and that's what that card simulates. Sometimes the exemption won't be granted, so you at least need a recovery flow for handling cases where auth is needed, though it wouldn't be the happy or usual path, more of a possibility. https://stripe.com/docs/payments/save-and-reuse?platform=web#charge-saved-payment-method

[main zealot]

Since we currently charge the customer straight after the creation of payment intent, how could an off session customer be notified to authenticate?

I've seen that we could send an email to the customer, but what would that email contain?

[cedar galleon]

Since we currently charge the customer straight after the creation of payment intent,
do you mean SetupIntent?

you should never do this:

• create SetupIntent
• confirm SetupIntent with a card
• create+confirm PaymentIntent on that card, immediately

that integration has a bunch of problems and you would not build things that way.

instead you would

• create a PaymentIntent, passing setup_future_usage
• confirm the PaymentIntent with a card
• the card has been saved for any future payments you want to do later

https://stripe.com/docs/payments/save-during-payment

you only use SetupIntents when you're saving a card now without charging and are going to charge it ~hours/days later

[cedar galleon]

we only send emails for that if it's a recurring payment using our Subscriptions API, and you can see a preview in a section at https://dashboard.stripe.com/settings/billing/automatic . For non subscription payments, you have to capture the error and contact the user directly(we briefly mention that in https://stripe.com/docs/payments/save-and-reuse?platform=web#charge-saved-payment-method)