From weak signals to one decision
A call, slow typing or a new payee each mean little alone. This lesson shows how they are read together, and how one decision with its reasons is chosen from allow, step up, cool off, hold and block.
Reading a banking session
Why one signal is not enough
An active call during a payment raises false alarms on its own: customers take calls while they bank. So do slow typing and a new payee. A rule on any one of them either misses the scam or stops thousands of genuine payments.
Reading them together
Read in the same session, the same signals mean something else. A call that began before the app was opened, a shared screen, account details typed a few characters at a time and a payee linked to other accounts describe a coached payment, not a busy customer.
The decision and its reasons
DeepID returns one decision for the moment, with the reason codes behind it, risk first. The actions are graduated:
- Allow when everything holds.
- Step up to a stronger check, such as a face match against sign-up.
- Cool off a new payee with a lower limit for a period your policy sets.
- Hold the payment and call the customer back on the registered number.
- Block when the evidence is clear, such as an emulator or an injected camera stream.
The customer reads it too
Every action comes with a message written for the customer, and the bank’s team receives the same decision with the same reasons. Policies are versioned, so the team can show which rule applied and when.