Skip to content
Try one-tap loginBook a demo

Moment 05 · Payment

Every payment is checked against the SIM, phone and payee bound before it.

Try one-tap loginBook a demo
// 001The real person, bound to their own phone and SIM.Sign-up// 002One tap, and the SIM bound at sign-up is checked.Login// 003The face from sign-up, checked before anything is bound again.New phone or SIM// 004The payee scored, from the phone and SIM already bound.New payee// 005The SIM bound at login is the SIM expected at payment.Payment

What the payment checks. Against what came before.

  • Not read here

    The face

    Not asked.

  • Checked

    The number and SIM

    The SIM bound at login is the SIM expected at payment, in the same phone.

  • Checked

    The phone

    The same phone, with nobody else driving it through a shared screen or a remote-control app.

  • Checked

    The payee

    The payee scored when it was added is scored again before the money leaves.

  • Checked

    The session

    A call that has run across the payment journey, a shared screen, dictated typing.

Where fraud shows. And the decision.

HoldA coached paymentA customer kept on a call for 41 minutes, told to move money to stay safe.HoldSomeone else driving the phoneA screen-sharing or remote-control app, installed at the caller’s request.
HoldMoney to a muleThe payee has received from many unrelated senders since it was added.

What DeepID reads. One call, one decision.

The decision. Hold, in the example.

Signs of coercion or a mule payee

  • Why

    On a call with an unknown number for 41 minutes, screen shared with a remote-access app, payee linked to 14 other accounts.

  • The customer sees

    “Payment paused. Your money hasn’t left your account. We’ll call you on +91 •••• 3210.”

  • A good customer

    Usual payments go straight through. A held payment comes with a call back on the registered number.

Your FRM receivesHOLD · active call · screen share · mule-linked payee

What to measure. Agreed before the pilot.

Where they start
  • HoldsPayments paused before money left.
  • Call-backsCustomers who stopped once called.
  • LossScam loss, against today.
  • FrictionGood payments held.

Use cases. Step by step.

Rules it supports.

  • India, Singapore, Malaysia, Australia and Saudi Arabia

    Device, behaviour, scam and payee signals read at login, new payee and payment, returned as one decision with its reasons.

    The rules, market by market

  • Singapore, Malaysia and the Philippines

    Cool-off and hold decisions after a new device, SIM or payee, or when a payment looks coerced, set per market and journey.

    The rules, market by market

  • India, Singapore and Australia

    Decision logs with their reasons and the message shown to the customer, and versioned policies, as evidence of what the bank did.

    The rules, market by market

Start with sign-up, login or payments.

Pick one, test it on your own traffic before you commit, and add the others on the same SDK when you’re ready.

Book a demoTry one-tap login