lafafm-3DS | Stripe Developers | Page 1

dusk crescent Nov 11, 2021, 1:29 PM

#

Hi there 👋 are you manually handling 3DS, or are you leveraging our flows that handle 3DS?

mint saddle Nov 11, 2021, 1:34 PM

#

Manually

dusk crescent Nov 11, 2021, 1:41 PM

#

Can you give me an overview of the steps you're currently taking when you add the new card for the customer?

mint saddle Nov 11, 2021, 1:47 PM

#

Yes, sure

#

Collecting card information via Stripe.js card element
Passing payment method to backend
Attaching it to the customer, and setting it as default Payment method

#

In step 1 - we're transforming card element to payment method via stripejs.createPaymentMethod

#

We have no 3ds verification on the card change at the moment, just want to implement it

dusk crescent Nov 11, 2021, 1:55 PM

#

Thanks for that! So as it stands, it does look like those steps won't trigger an authorization. I think you have two options here:

Use the next charge on the subscription as the authorization flow and be ready to handle 3DS then
or
Use a setup intent when creating the payment method so that authorization flows are triggered then

mint saddle Nov 11, 2021, 1:57 PM

#

Ok, but the second step wouldn't help us in case of the highlighted card, right?

#

E.g. even if I made a setupintent for that card - customer would still need to authorize next payment (via email possible)

dusk crescent Nov 11, 2021, 2:00 PM

#

Correct, and it's a good test card to use. Ultimately, whether or not a customer must complete a 3DS flow is up to their bank. When we set up a card we give the bank every reason we can to allow future charges to occur without the extra authentication, but they can still require it anyway. So it's always good to test with that card and be prepared to catch the 3DS events at time of charge as well.

#lafafm-3DS