Authentication for high-value transactions
Ask for face confirmation when the amount, the destination or the device is out of pattern — and compare it with the person's face enrollment.
- SMS and passwords don't prove presenceThey prove possession of a device or knowledge of a secret — both can be stolen.
- Scams using the victim's own accountThe fraudster operates with the right phone and the right password.
- Friction at the wrong momentAsking for verification on every transaction wears people out; asking on none leaves you exposed.
You decide when to ask for the face
WhenPix amountabove R$ 3,000thenrequire face authentication
WhenDestinationaccount added less than 24 hours agothenrequire face authentication
WhenDevicefirst sign-in from this phonethenrequire face authentication
WhenTimebetween midnight and 6 a.m.thenrequire face authentication
Example · trigger rules live in your system; the verification is one call
The suggested policy
A starting point for this solution. Everything is adjustable in the console, with no deploy, and every session records the policy that applied.
FlowAUTHENTICATION
Referenceface enrollment
CPF lockout5 failures in 60 min
Lockout duration30 min
Questions about this solution
How long does it take?
Capture takes about 30 seconds; evaluation, around 8 seconds on a phone.
What if the person has no face enrollment?
Run an account opening with an ID document first; the enrollment is saved on approval.
Does it work for Pix?
Yes, as a confirmation step before a Pix (Brazil's instant payments) transfer is released.