#Ioanna

1 messages · Page 1 of 1 (latest)

magic lakeBOT
blissful sage
#

Hi there

#

So you want to error if 3DS is required?

karmic jacinth
#

Yeah or not allow the user to add a 3DS payment method because there is a certain type of card that regardless the setup will always require authentication

blissful sage
#

How are you collecting PaymentMethods?

#

Are you using a SetupIntent?

karmic jacinth
#

Yes

blissful sage
#

Gotcha

#

Hmmm yeah so we only support errors_on_requires_action for PaymentIntents and not SetupIntents

#

Why do you not want to have a customer go through 3DS exactly?

karmic jacinth
#

Because basically the way this works is they set up their payment intent and when they use a credit to perform and action on the web app I hold the funds and capture them on action completed. And noe I've ended up with a bunch of payments I can't capture

blissful sage
#

I'm not sure I understand. If they complete 3DS on set up then we apply for an exemption from 3DS in the future and (the vast majority of the time) they should not be required to authenticate again for the off-session charge

#

Can you provide me an example I can look at?

karmic jacinth
#

ofc 1 sec

#

pi_3Mg3DxK9qmDpbyxA0CW5MHM5

#

and somehow his first credit got charged just fine: pi_3Mg2sSK9qmDpbyxA1BAuljVY

#

which has confused me quite a bit

blissful sage
#

Thanks looking

karmic jacinth
#

This test card seem to replicate the error

#

The weird thing is that normally I would expect to not be allowed to capture the funds either if I need authorisation to collect them

blissful sage
#

Well you are attempting to authorize when you create/confirm the PI

karmic jacinth
#

ok is there a workaround?

blissful sage
#

So yeah this example does look like the issuer was just weird and still forced 3DS even though the card was set up correctly initially.

#

There is no way to predict this from happening

karmic jacinth
#

got it ook thank you very much!