Rules Triggered Challenges
Privakey can be leveraged anytime a service needs a secure response to a challenge. In the case of a rules triggered challenge, Privakey will send an automated notification to the user’s registered devices with a custom message that describes what the customer needs to authorize.
In this case, the Bank of Tomorrow has enabled Privakey to send a notification to users’ devices if a fraud risk engine is triggered. The user will then assert a strong yes or no respond back to the sender without the need for phone calls, interrogations or SMS messages. If the user did in fact spend $1,500 at BadActor.com they would be asked for a second factor to authorize the transaction. If they didn’t, all they would have to do is press “deny”.
Other examples of when a rules triggered authorization would be enabled include: if a user triggers a protective threshold, such as adding a new shipping address to a retail account or if a user is attempting to access sensitive information on a shared, voice-controlled computing device (i.e. Amazon Echo or Google Home). In all cases, the same Privakey-enabled, consistent, and user-friendly process can be leveraged to verify your user’s intent and protect them from unauthorized access and transactions.