#dimka06-3ds

1 messages · Page 1 of 1 (latest)

dry lava
#

@mortal swan hi! do you have more details, what does "doesn't work" mean exactly, what errors do you get?

mortal swan
#

Yeah of course @dry lava ! When i use a card which need 3Ds is required normally, nothing appear. Often payment pass and there is no problem , but sometime payment is rejected with error " refused card"

dry lava
#

sounds like you should write to our support team really with specific examples

#

do you have an example of a PaymentIntent pi_xxx that doesn't look right to you? I can have a look.

#

also you should not be 'testing' your own site with live payment details if that's what you're doing

mortal swan
#

Yeah i will find one to you

#

It's little difficult because it's not for my own site, i created a click and collect platform with "connect" and it's already in production ! i have to create an other vps for development ahah

#

pm_1JdewTRBCY6RxlshWexWmH1z

#

One example which failed 🙂

dry lava
#

thanks, will look in a sec

dry lava
#

sorry, got distracted

#

that example (https://dashboard.stripe.com/payments/pi_3JderyRBCY6Rxlsh08zmKcqO) is just a 3D Secure failure at the protocol level, as we tried to run 3D Secure, and it didn't work, which usually means the customer's bank had a problem, or the customer is not set up correctly with their bank. It can happen unfortunately, 3D Secure doesn't always work and it relies on the customer's bank to be working properly!

#

nothing you can do but ask the customer to try a different payment method or contact their bank.

#

This will happen from time to time and is a normal part of taking payments in an environment with 3D Secure. If you feel like you're seeing this happen more often than you're comfortable with you could write to our support team with some more examples so we can try to see if there's a systemic reason, but this is unfortunately somewhat common as SCA starts to roll out (https://support.stripe.com/questions/strong-customer-authentication-sca-enforcement-date) and bank's systems are getting more load.

mortal swan
#

No problem @dry lava 🙂
Thing i find weird is that for our test , we were using credit card which need normally 3D secure with other platform but on our platform 3D secure didn't show up ! it's weird no ?

dry lava
#

can't say!

#

it's not a science

#

also bear in mind we try to not do 3D Secure unless it's needed

#

since it's bad for customer conversion

mortal swan
#

And in France it seems that it's already in application so i don't really understand ! It's just that we don't want problem with
jurisdiction

dry lava
#

there's no problem on your side really

#

like I said, it's a low-level protocol error and usually it means the customer's bank has a problem

#

nothing you can do but ask the customer to try a different payment method or contact their bank.

mortal swan
#

So you think everything is good whit my integration and there is no problem ?

dry lava
#

I can't say that for sure from just a quick conversation on Discord but that example you shared seems normal enough

#

as I said, this will happen from time to time and is a normal part of taking payments in an environment with 3D Secure unfortunately, but if you think the rate of errors is unusually high you can contact our support team

mortal swan
#

Ok Thanks @dry lava , it was only 1 error on 100 succeed so for the moment we will say it's normal

#

It's impressive that Stripe succeed to not use 3Ds , i don't understand how it's possible

dry lava