Detect identity theft that passes credential checks

A correct password proves someone has the credentials, not that they are the customer. DetectX® Digital Identity checks the whole online or mobile banking session against your rules and the user’s own past sessions. A broken rule raises an alert, and a high-confidence rule can end the session while it is still live.

  1. 1Observe
  2. 2Compare
  3. 3Detect
  4. 4Platform tour
Digital Identity alerts in the AlertViewer's Behavioral category: counted among the alert sources on the dashboard, listed in the Behavioral queue with the rule each violated and its score, and opened on the session data and each rule's message and score.
DetectX - One Platform. Total Compliance (FINAL CAPTIONS)

One Platform. Total Compliance.

The DetectX® Approach

The right password does not prove the right person.

Digital identity is the profile of how a user behaves in online and mobile banking: how they type and navigate, the device they use and where they connect from. DetectX® checks each session against your rules and the user’s own past sessions, and can raise an alert or end the session while it is still live.

Is this really the user? Adapters in your online and mobile banking apps listen to each session. The Data Collection Module checks what they send against your rules and the user’s own history, and carries out the action you configured.

Online bankingWeb AdapterLoaded with your web application, listening to the session.
Mobile bankingMobile AdapterCollects the same data and sends it the same way.
Through your web application firewallData Collection ModuleStructures the session data, calculates values such as typing speed, and checks them against your rules.
High-confidence rulesIndividual rulesHistorical rules
How session data is prepared
Rule brokenAlert, or End the SessionThe action you configured, while the session is live.
Your analystWorks the AlertIn AlertViewer, in its own Digital Identity section.
Your datamartSession StoredEach session added to the user’s history.

The firewall ends a session on instruction from the Data Collection Module. Session data is stored where a DetectX® datamart is in place.

Key Benefits & Impact

A session shows who is really there.

A login check ends the moment the user is in. DetectX® Digital Identity keeps checking how the session behaves, against your rules and the user’s own past, and acts while the session is still live.

Is This Really the User?

The right password, checked against the right behaviour.

Where a session comes from and how the user types, clicks and navigates are compared with their own past sessions. A session can pass every login check and still not behave like the person who owns the account.

How behaviour is profiled over time
Act While It Is Live

Stopped while the user is still connected.

For each high-confidence rule you choose the action: record it, raise an alert, or raise an alert and end the session. Your firewall ends it while the user is still connected.

How session alerts are worked
Every Important Moment

Not only at login.

Your app marks the events that matter, such as a payment, buying securities or a password change. Each one is checked, so a session that turns suspicious after login is still caught.

How session data is prepared
Signals Without Friction

Doubt recorded, customers not disturbed.

A less severe value is stored as a warning instead of an alert, so genuine customers are not interrupted. Transaction Filtering can still use the warning to interrupt a payment from that session.

The rules that check each payment
Rules You Set

Your limits, your rules, your scores.

Your team sets the threshold, warning level and action for each high-confidence rule, and builds its own rules in the Rule Designer. Each alert carries a default score, so an analyst can see which family raised it.

Building rules in the Rule Designer
Web and Mobile

Online and mobile, checked the same way.

A web adapter and a mobile adapter send the same kind of data to the same rules. On mobile, motion and orientation data are added, so a session that does not move like a phone in a hand stands out.

Spotting patterns in behaviour

Why DetectX®

Most checks stop at the login. DetectX® watches the whole session.

  • The whole session, not the loginA correct password and code, and the check is overEvery event your app marks, such as a payment or a password change, is checkedInside a session
  • Behaviour, not only credentialsTyping nine times faster than usual goes unseenHow the user types, navigates and connects is compared with their own past sessionsBehavioural Analysis
  • Act while it is liveFound later, if at allRecord, raise an alert, or raise an alert and end the session through your firewallHow session alerts are worked
  • Your definition of suspiciousOnly what the login provider checksYour own rules, built in the Rule Designer, alongside the high-confidence rulesBusiness Rules Design & Engine
  • Real users left aloneEvery extra check felt by every customerA session that matches the user’s past goes straight throughKey benefits
  • Into the payment flowThe session and the payment checked apartSession alerts and warnings can interrupt a payment through Transaction FilteringTransaction Filtering

How Digital Identity Works

Try it yourself: three steps, from a mobile banking session to the alert it raises.

A password and a code prove someone has the credentials, not that they own them. DetectX® reads how the whole session behaves and checks it against your thresholds while it is still live. Every step is yours to drive.

Illustrative exampleInvented Names & Data

Explore the DetectX® Platform

Start with Digital Identity. Add what you need next.

Every DetectX® solution runs on the same underlying platform and shares its capabilities, AlertViewer and audit trail. Pick a solution to see what it adds to Digital Identity.

All solutions

Digital Identity FAQs

What compliance teams ask before choosing DetectX®.

Something we have not covered?Talk to our team

Digital identity is the profile of how a user behaves in online and mobile banking: how they type, click and navigate, the device they use, and where they connect from. DetectX® Digital Identity checks each session against that profile and your rules. A session that passes the login but does not behave like the user can raise an alert or be ended.

No. Authentication still runs at login. Digital Identity starts where authentication stops: it checks the rest of the session, including each payment or password change your app marks. A session with the right credentials but the wrong behaviour still stands out.

Three kinds of session data:

  • How the session is used. Typing, focus, page navigation and scroll speed, clicks, and the route through the app.
  • What the device reports. Browser and screen, plus orientation, acceleration and gyroscope data on mobile.
  • Where the session comes from. IP address, country and connection details, supplied by your web application firewall.

The Data Collection Module turns raw movement into values your rules can test, such as typing speed.

You set the action for each high-confidence rule: no action, an alert, or an alert and the session ended through your firewall. A less severe value can be stored as a warning instead, without interrupting the user. Alerts open in AlertViewer’s Digital Identity section, with the rule, its message and its score.

Yes. Your team sets the threshold, warning level and action for each high-confidence rule in the DetectX® admin tool, without a code change. Your own rules are built in the Rule Designer like any other DetectX® rule. Each rule family has its own default score, so an analyst can see where an alert came from.

Yes, with Transaction Filtering. Alerts and warnings from Digital Identity can be used in Transaction Filtering rules to interrupt a payment made in the same session. This works even where the session itself was allowed to continue.

Digital Identity · DetectX®

See Digital Identity in a demo

Book a session. Bring your questions about the session data collected, the three families of rules and how alerts reach the AlertViewer.

Three families of rules
High-confidence, individual and historical, each rule configured with its own score.
Beyond the login
The whole online and mobile banking session, not a single credential check.
One platform
Identity alerts in the same AlertViewer as screening and monitoring.