#Coach Leyton
kind bison
cloud ledge
My apologies for the large question
quartz oak
Hi there, is this a question about how to handle 3DS for the payment for the 1st invoice created in a subscription?
cloud ledge
Yes. Could also occur when updating a subscription too I suppose, so in that case, it wouldn't be the first invoice on that subscription
"updating" meaning changing the "plan" (not a Stripe Plan, it's a custom entity of my own). The user could, in theory, provide new card details when changing their "plan"
quartz oak
Yes, your integration should be resilient and handle the 3DS when required.
You should listen to payment_intent.requires_action event. When it happens, you should bring your customer to your website where you can call stripe.confirmCardPayment() with the payment_intent.client_secret to start the 3DS flow.
cloud ledge
Okay, I'll give that a go. Or at least, something similar to that. So "confirmCardPayment" is the solution to 3DS or other things that cause an "requires_action" on a payment intent?
quartz oak
The card issuer and your radar rules determine whether a PaymentIntent requires 3DS (i.e., requires_action status). The it happens, you can use confirmCardPayment() to trigger a 3DS flow.
https://dashboard.stripe.com/settings/billing/automatic there's also a Manage payments that require confirmation option that you can enable to allow Stripe to send emails to customers to confirm 3DS.