Behavioral Biometrics for Banks: Seven Buying Mistakes and What to Do Instead
Most behavioral biometrics deals go wrong before signature: web-only pilots, glossy detection rates and consent gaps. Here are seven mistakes to fix during your evaluation.
What you're actually buying when you buy session signals
Banks buy behavioral biometrics for one reason: to catch scams and account misuse during the session, before money leaves, without adding friction for genuine customers. Behavioral biometrics for banks measure how a person types, swipes, holds a phone and moves through an app. Vendors usually combine that with device intelligence, meaning signals about the device, network and environment the session runs on.
The technology works. The buying process often doesn't. Seven mistakes show up again and again in RFPs and pilots, and each can be fixed before you sign. Each one below ends with what to do instead.
Mistake: Treating consent and lawful basis as the vendor's problem
A vendor's "GDPR compliant" slide settles nothing. You are the controller. Behavioral data counts as personal data almost everywhere, and in some regimes it can become biometric or sensitive data depending on how it's used.
- EU and UK GDPR: If signals are used to uniquely identify a person, they can count as special category biometric data. Banks that use them only to score session risk often rely on legitimate interests, backed by a data protection impact assessment. Separately, ePrivacy rules on accessing data on a user's device can apply to SDK collection.
- India's DPDP Act: The law is built around consent, and its "legitimate uses" are narrow. With the implementing rules being phased in, many banks are planning clear notices and consent capture at onboarding or app update.
- Brazil's LGPD: Biometric data is sensitive. Article 11, however, allows processing without consent for fraud prevention and security in identification and authentication. Transparency and data minimization still apply.
- Elsewhere: Singapore's PDPA, the UAE's PDPL and South Africa's POPIA each set their own rules on notice, purpose and cross-border transfers.
What to do instead: Ask every vendor for a field-level data inventory: raw keystrokes or derived features, where the data is processed, how long it's kept, and whether it's pooled across clients to train models. Have privacy counsel in each market approve the lawful basis before the pilot starts. If a vendor can't produce that inventory, or offers one hosting region where you face data-residency obligations, treat it as a red flag.
Mistake: Piloting on web traffic when customers live in the app
Web pilots are tempting. They need only a JavaScript tag, with no app release and no store review. But at many retail banks the mobile app carries most logins and payments. Mobile fraud also looks different: remote-access tools, screen overlays, malicious Android accessibility services, and a live phone call while a payment is set up. A web pilot tells you very little about those cases.
What to do instead: Put the mobile SDK in the pilot from day one, and plan for a full app release cycle. Depending on your QA process, that can take several weeks. Test on both iOS and Android, and ask for a written list of which signals each operating system allows, since iOS typically permits fewer. Measure SDK size, startup time and crash rate alongside detection.
Mistake: Judging vendors on detection rate alone
"Detects 90% of account takeover" means nothing until you know how many alerts it took to get there. A model that flags everything catches everything.
Here's a hypothetical. Say a bank runs 2 million digital sessions a month. Vendor A flags 0.5%, which is 10,000 alerts a month, or about 330 a day. Vendor B flags 0.1%, about 2,000 a month, and catches slightly less fraud. If we assume an analyst works 60 to 80 alerts a day, Vendor A needs roughly five analysts and Vendor B needs one. A higher detection rate may not cover that cost.
| Metric to demand | What a good answer looks like | Red flag |
|---|---|---|
| Alerts per 10,000 sessions | Reported at the threshold you would actually run | Only quoted at the vendor's best threshold |
| False-positive ratio | Legitimate sessions flagged per confirmed fraud case, measured on your data | "Industry benchmark" figures only |
| Value detection rate | Share of fraud losses caught, not just case count | Case counts only |
| Customer friction | Step-ups per 1,000 genuine sessions | Not measured |
What to do instead: Ask for detection and alert volume at three or four thresholds on your own pilot data. Then cost the analyst time each threshold implies.
Mistake: Testing for account takeover but not social engineering
Account takeover, where a fraudster is in the session, is the easier problem. The harder one is the authorized scam: the genuine customer logs in correctly and sends money while a fraudster coaches them by phone. Social engineering fraud detection relies on different signals: hesitation, payee details typed as if dictated, an active call, unusually long sessions and odd navigation.
In a growing number of markets, the bank now bears some or all of these losses. Examples include the UK's mandatory reimbursement rules for authorized push payment fraud, Singapore's Shared Responsibility Framework and Australia's Scams Prevention Framework. Proposed EU payment rules point the same way. Details differ by country, so check what applies to you.
What to do instead: Build a labeled test set that includes confirmed scam cases where the customer passed authentication. Ask each vendor to show which signals fired on those cases, and which interventions they support beyond blocking: a targeted warning, a cooling-off delay or a call-back.
Mistake: Buying behavioral signals in isolation from device intelligence
Behavioral signals and device intelligence catch different things. Emulators, rooted devices, proxies and SIM-swap indicators come from device and network data. Coaching and bot-like input patterns come from behavior. Many banks already pay for device intelligence through a fraud platform or authentication provider, so a new contract can easily duplicate it.
When you build a shortlist of BioCatch alternatives, compare vendors whose core strengths differ:
- BioCatch, which is behavioral-first
- LexisNexis ThreatMetrix, built around a device and identity network
- Mastercard's NuData
- Feedzai, which offers behavioral biometrics inside a broader fraud platform
- Sardine
- ThreatFabric, which is strong on mobile malware
Regional availability and hosting options differ, so check both for every market you operate in.
What to do instead: Inventory the signals you already have. Then judge each vendor on the lift it adds over your current stack, not on what it catches alone.
Mistake: Accepting scores that arrive after the money moves
A risk score that reaches the case queue ten minutes after a faster-payments transfer only documents the loss. Behavioral biometrics software helps only if its output reaches your decision engine at the moment of decision.
What to do instead: List your decision points: login, adding a payee, changing limits and confirming a payment. Require a synchronous score at each one, with an agreed p95 latency, often a few hundred milliseconds. Check that scores feed your existing rules engine and case manager without custom middleware. Ask for reason codes analysts can read. You'll need them when a customer disputes a block or takes a complaint to an ombudsman.
Mistake: Signing a pricing model that punishes growth
Pricing models differ more than headline quotes suggest. The figures below are typical 2026 market ranges. They vary widely by contract, region and volume, so confirm them with vendors.
| Model | Indicative range (USD) | Watch for |
|---|---|---|
| Per active user per year | Roughly $0.10 to $1.00 | How "active" is defined |
| Per session or API call | Roughly $0.002 to $0.02 | Overages as app engagement grows |
| Annual platform minimum | Often six figures for mid-size banks | Separate fees for each channel |
| Implementation services | Tens of thousands to several hundred thousand, one-time | Mobile SDK work billed separately |
What to do instead: Prefer pricing tied to customer count over session count, because a successful app increases sessions. Cap overages, and get web and mobile priced in a single quote. In any multi-year term, include a performance exit clause linked to the alert and detection metrics agreed during the pilot.
A pilot plan that avoids all seven mistakes
- Get privacy counsel's approval for each market before any data flows.
- Run 8 to 12 weeks, covering both web and mobile.
- Score historical and live sessions against your own labeled cases of account takeover and authorized scams.
- Report detection, alert volume and friction at several thresholds.
- Measure lift over your existing device intelligence.
- Confirm synchronous scoring at every decision point.
- Lock pricing and exit terms before the pilot ends, while you still have leverage.
Decision rule: choose the vendor that adds the most fraud value, in money terms, at an alert volume your current team can actually work. The highest headline detection rate is the wrong yardstick.
Common questions
Is behavioral biometrics data classed as biometric data under privacy law?
It depends on the jurisdiction and on how you use the data. Under GDPR, data used to uniquely identify a person can count as special category biometric data. Brazil's LGPD treats biometrics as sensitive but allows fraud-prevention processing without consent. Get each market's lawful basis confirmed by qualified privacy counsel before deployment.
How long should a behavioral biometrics pilot run?
Most banks need 8 to 12 weeks to cover both web and mobile and to collect enough confirmed fraud cases to measure against. Shorter pilots usually skip the mobile app or end before scam cases mature into confirmed labels. Add time for an app release cycle if the SDK isn't already in your app.
Can behavioral biometrics detect authorized push payment scams?
Partly. The signals that matter are signs of coaching, such as hesitation, dictated typing, an active phone call and unusual navigation, rather than signs of an impostor. Test vendors on your own confirmed scam cases where the customer authenticated normally, and check what interventions they support beyond declining the payment.
Do we need separate device intelligence if we buy behavioral biometrics?
Usually you need both kinds of signal, but you may not need another contract. Many fraud platforms and authentication providers already supply device intelligence. Inventory what you have, then measure each vendor on the lift it adds over your current stack.
Written by the Apexlink Suite editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.