Strong Customer Authentication, 3DS and Passkeys, Explained
How Strong Customer Authentication led to 3DS2 and passkeys, which authentication flows you can use, what SCA requires in Europe, and when an SCA retry pays off.
SCA hides more complexity than it shows, and that complexity is where you can optimize.
Local practice runs from SCA compliance to cutting your 3DS2 costs. Get it right and you stay protected, pay less, and meet each regulator's requirements. To optimize, you need to know what works on live traffic as well as on paper, and that takes knowing the ecosystem well enough to place the right bets.
So the real question is whether your setup meets each market's rules while keeping performance where you want it.
In 30 minutes, you will walk away with:
Every 3DS setup trades some conversion for protection
Every Decision Has a Trade-off
How to tell whether liability shift applies to a given transaction.
Local Regulatory Requirements
How to know each market's requirements and adjust your payments to meet them.
More Providers, More Variables
Routing across several providers protects approvals. Each provider, though, treats an existing authentication in its own way.
Built for the people who own approval rates and chargebacks
Designed for Heads of Payments, payments and fraud managers, and the product and engineering leads behind checkout. It fits best if you route cards across several providers or sell to cardholders worldwide. If you have ever absorbed a chargeback on a payment you thought 3DS protected, this session explains why.
Antoine is Head of Product at Yuno, with nearly 10 years of experience in payments. In this session, he walks through how 3DS works in practice, from the first authentication to the final authorization.