CompassAvi-3ds-supported | Stripe Developers | Page 1

trim surge Jan 7, 2022, 11:11 PM

#

Do you have any specific examples we could take a look at?

heavy notch Jan 7, 2022, 11:15 PM

#

sure: pm_1KFQoaA25IW7gj6b0gMljODj

#

but pretty much any of the existing payment methods (I've tried at least 5-6) are coming back with that flag being true

#

and again, this was not happening at all before. the only ones that were coming back true were the ones from the stripe example credit cards under the 3d secure section.

#

haven't changed anything on my end, so just wondering if there was some switch that got flipped for 3d secure for 2022 or maybe just in the test environment?

trim surge Jan 7, 2022, 11:18 PM

#

It's possible - what happens when you try creating a Payment Method with the 378282246310005 test card? This should explicitly not be supported by 3DS

heavy notch Jan 7, 2022, 11:19 PM

#

checking

#

@trim surge that one is false

#

ugh, so did a few of these flip over to being 3d secure supported?

#

or not a few, but quite a lot of these test cards

trim surge Jan 7, 2022, 11:26 PM

#

Yeah my guess would be that there's a change on our end that changed this behavior - typically for tests where having a set 3DS is important we recommend that you only rely on the test cards where we specify what the 3DS behavior is. Is there are a reason the 378282246310005 returning 3DS supported is giving you problems?

heavy notch Jan 7, 2022, 11:28 PM

#

I needed a quick way to detect 3d secure payments/payment methods so that I avoid them (putting up verbiage to the end-user for now). this is just temporary until I have bandwidth to support 3d secure which should be fairly soon. I was using it to buy some time.

#

it seemed to work in the test environment quite well, until today.

#

not sure how it would work live

trim surge Jan 7, 2022, 11:33 PM

#

three_d_secure_usage would just tell you whether 3DS is supported at all for the card though - it's not telling you whether 3DS is actually required for all it's transactions.

heavy notch Jan 7, 2022, 11:35 PM

#

and I really can't get that information until I try to process a payment further down the chain, correct? with "next_action"?

trim surge Jan 7, 2022, 11:36 PM

#

Yeah, you wouldn't be able to truly know if a payment really requires 3DS until it was actually attempted/confirmed

heavy notch Jan 7, 2022, 11:38 PM

#

so, at this point, if I wanted to detect and stop, I'd actually have to go forward with the payment intent creaton and then if I see next_action, scale it back (delete the payment intent).

past bane Jan 7, 2022, 11:39 PM

#

Hello! I'm taking over for karbi. Yep, there's no way to know ahead of time if any given transaction will require 3D Secure or not. You have to try it and see.

#

Many, many cards support 3D Secure but rarely or never require it.

#

The decision to require authentication during a transaction is ultimately up to the card issuer, and they can decide it's require for any reason.

heavy notch Jan 7, 2022, 11:45 PM

#

Thanks @past bane ... to buy some time, the way to detect this is by next_action, correct?

#

I already do this on the front-end when trying to add a payment method.. I suppose I can do the same when processing a payment

past bane Jan 7, 2022, 11:47 PM

#

When you say buy some time, what is the major barrier to preventing you from handling the authentication process?

#

Also, are you currently using Payment Intents?

#

If so you can set error_on_requires_action to fail the payment if authentication is required: https://stripe.com/docs/api/payment_intents/create#create_payment_intent-error_on_requires_action

#

That would allow you to treat those transactions as declines (because that's what they are if you don't support the authentication process).

heavy notch Jan 7, 2022, 11:59 PM

#

@past bane Just time to implement, that's it. Probably only a few weeks out, but still need that time. Yes, using payment intents.. I'll look into that flag, thanks!

#CompassAvi-3ds-supported