#lovelock
1 messages · Page 1 of 1 (latest)
Hi
3DS is requested by the card's bank issuer. The customer can disable that in their bank account if that's supported and can be disbaled.
Ah, so it's not something that can be disbaled on our side?
We also have a piece of automation that takes a payment from customers using their existing card via the API, this never asks for bank verification.
Of course, it's through the API so it cant do 3d secure
Ah, so it's not something that can be disbaled on our side?
Correct.
We also have a piece of automation that takes a payment from customers using their existing card via the API, this never asks for bank verification.
Yes you can authenticate and save the card for future usage, which will reduce the 3DS auth rates. But your integration need to expect that at any time the card's bank issuer can request another 3DS check