Step-up authentication
Step-up authentication asks a user for stronger proof of identity only when the risk of an action is higher, such as a one-time code or biometric check on a large payment, instead of challenging every action equally. It concentrates friction where it is most useful.
In more detail
The idea is to match the challenge to the risk. A routine balance check needs little, while adding a payee or sending an unusual amount warrants a stronger check. This keeps most customers moving freely and spends friction only on the minority of actions that look risky.
Two points are easily confused. First, the challenge is issued by whichever system controls the login or payment, with a risk signal supplied to it; a system that only receives events after the fact can recommend a challenge but cannot issue one. Second, step-up does not defend against social engineering, since a deceived customer will pass the stronger check just as readily as an honest one.
Example
A customer who normally logs in from one phone signs in from another and tries to add a payee. The risk signal is high, so the app asks for a fingerprint check. A routine balance check on the usual phone triggers no challenge.
Related capability
Related terms
Discuss your transaction monitoring requirements
Tell us which transaction flows you need to monitor, which systems Akoben would integrate with, and how your fraud team works today.
Request a demo