Assess risks and users
Map login, payment, recovery and admin flows, user devices and regulatory requirements.
Biometric authentication is generally more secure and faster than OTP because it is phishing-resistant when built on device-bound keys, while SMS and email OTPs can be intercepted, phished or stolen through SIM swaps. Biometrics on a phone usually unlock a cryptographic key stored on the device, so the fingerprint or face never leaves the device. OTP still has a role for first-time sign-up, account recovery and users without biometric devices. For most apps the best choice is passkeys (biometric unlock of a FIDO credential) as the default, with app-based or SMS OTP only as a fallback. PerfectionGeeks designs and implements both, along with adaptive multi-factor authentication.
Touch ID and Android fingerprint sensors; fast and familiar.
Face ID and Android face unlock; Apple states the chance of a random person unlocking Face ID is less than 1 in 1,000,000.
Used mostly as a background risk signal in banking and call centres rather than as the only factor.
The server sends a code to the user's phone number. Easy for everyone, but exposed to SIM swapping, interception and phishing.
Sent to the user's inbox. Useful for low-risk sign-in and recovery, but only as secure as the email account.
Apps such as Google Authenticator or Microsoft Authenticator generate time-based codes on the device. More secure than SMS, but users can still be tricked into typing codes into phishing sites.
A prompt in a trusted app asks the user to approve. Use number matching to prevent "MFA fatigue" attacks.
| Factor | Biometric (device-based, passkeys) | SMS / email OTP | Authenticator app OTP |
|---|---|---|---|
| Phishing resistance | High: bound to the real website or app | Low: codes can be phished or relayed | Medium-low: codes can be phished |
| SIM swap risk | None | High for SMS | None |
| Speed for the user | A glance or touch, typically a few seconds | Wait for and type a code | Open app and type a code |
| Works offline | Yes, for device unlock | Needs mobile signal or email | Yes |
| Device dependency | Needs a device with biometrics; synced passkeys help with device changes | Needs access to the phone number or inbox | Needs the authenticator device |
| Accessibility | Not suitable for every user; always provide an alternative | Widely usable | Requires app setup |
| Running cost | Very low per login | Per-message SMS fees, higher internationally | Very low |
| Privacy | Biometric stays on the device | Phone number or email shared | Minimal data |
| Best use | Daily login, payment approval, high-value actions | Sign-up verification, account recovery, fallback | Fallback MFA, admin and workforce access |
Passkeys: Combining Biometrics and Cryptography
Liveness and spoofingFor face verification during onboarding or remote identity checks, use certified liveness detection to stop photos, masks and deepfakes. Device biometrics used for passkeys rely on the platform's own anti-spoofing.Recovery is the real attack surfaceAttackers target the weakest path, often account recovery by SMS or email. Make recovery as strong as login: verified identity, cooling-off periods for sensitive changes and alerts to existing devices.
| Method | Main strengths | Main weaknesses | How to reduce risk |
|---|---|---|---|
| Device biometrics with passkeys | Phishing-resistant, no shared secret, nothing to steal from the server | Device loss, account recovery is the weak point, not usable by everyone | Strong recovery flows, multiple registered devices, fallback options |
| Biometrics stored on a server | Works across devices | A breached biometric template cannot be changed like a password | Avoid; if required, encrypt templates, use liveness detection and keep data minimal |
| SMS OTP | Universal, no app needed | SIM swaps, SS7 interception, phishing and relay attacks, delivery delays | Use only as fallback, add device and risk signals, rate limits |
| Email OTP | Familiar, no phone needed | Only as secure as the inbox, phishable | Low-risk use only, short expiry |
| Authenticator app OTP | No SIM risk, works offline | Phishable, seed theft if poorly stored | Combine with risk checks, move to passkeys over time |
| Push approval | Simple to approve | MFA fatigue and approval spamming | Number matching, context in the prompt, rate limits |
Using device biometrics through the operating system usually means your servers never receive biometric data, which greatly reduces privacy obligations. Confirm requirements with your compliance team for each market.
| Region or standard | What it says |
|---|---|
| NIST SP 800-63B (US) | Classes SMS and voice OTP as a "restricted" authenticator and favours phishing-resistant options such as FIDO2 |
| PSD2 Strong Customer Authentication (EU, UK) | Payments need two of knowledge, possession and inherence (biometrics); OTP and biometrics both qualify when implemented correctly |
| Reserve Bank of India | 2025 directions on authentication for digital payments, effective April 2026, allow alternatives to SMS OTP such as biometrics and device-based methods |
| Central Bank of the UAE | Instructed banks to phase out SMS and email OTP for transactions in favour of in-app authentication |
| GDPR (EU, UK) | Biometric data used for identification is special category data: explicit consent or another legal basis, data minimisation and impact assessments |
| US state laws (for example Illinois BIPA, Texas, Washington) | Notice and consent rules for collecting biometric identifiers; strict penalties under BIPA |
| PCI DSS v4 | Requires multi-factor authentication for access to cardholder data environments |
| Scenario | Recommended approach |
|---|---|
| Consumer mobile app daily login | Passkeys or device biometrics; OTP only for recovery |
| Banking and payment approval | Biometric or passkey approval in the app, with transaction details shown; risk-based step-up |
| Healthcare and patient portals | Passkeys plus authenticator app fallback; strong recovery |
| B2B SaaS and admin access | Passkeys or security keys for admins, SSO with MFA for users |
| First-time sign-up | Email or SMS OTP to verify contact details, then offer passkey enrolment |
| Users without biometric devices | Authenticator app OTP or device PIN-based passkeys |
| Call centres | Voice biometrics as a risk signal plus knowledge checks and in-app confirmation |
Biometric app login, passkeys for web banking and in-app biometric approval of payments and new payees, replacing SMS OTP for most transactions.
Fast clinician sign-in on shared devices, patient portal passkeys and strong recovery to protect health records.
Passkey checkout login, biometric approval for saved payment methods and OTP only for guest verification.
Passkeys and security keys for admins, SSO with phishing-resistant MFA and device posture checks.
Citizen and student portals with passkeys, plus accessible OTP alternatives.
Map login, payment, recovery and admin flows, user devices and regulatory requirements.
Passkeys or biometrics as default, OTP for verification and fallback, step-up rules for high-risk actions.
WebAuthn and FIDO2 for passkeys, Apple LocalAuthentication and Android BiometricPrompt for app unlock, keychain and keystore for key storage, and a proven OTP provider for SMS or email.
Multiple devices, recovery codes or verified identity checks, cooling-off periods and alerts.
Device fingerprinting, location, behaviour and transaction risk scores to decide when to step up.
Security testing, accessibility testing and gradual rollout with passkey enrolment prompts after successful logins.
These are planning ranges; your estimate depends on platforms, user volume and compliance needs. SMS OTP has ongoing per-message costs that rise with volume and international users, while passkeys and device biometrics have almost no per-login cost.
| Scope | What is included | Typical cost | Timeline |
|---|---|---|---|
| OTP authentication | SMS or email OTP with rate limiting and fraud checks, using a provider such as Twilio Verify or AWS | $3,000–$10,000 plus per-message fees | 1–3 weeks |
| Biometric app login | Face ID, Touch ID and Android biometric unlock with secure key storage | $5,000–$15,000 | 2–4 weeks |
| Passkeys for app and web | WebAuthn server, enrolment, sign-in, synced passkeys, recovery flows | $15,000–$40,000 | 4–8 weeks |
| Adaptive MFA platform | Passkeys, OTP fallback, risk engine, admin console, audit logs, compliance reporting | $40,000–$150,000 | 3–6 months |
FIDO2/WebAuthn, OAuth 2.0 and OpenID Connect, platform biometric APIs.
Threat modelling, secure recovery and penetration testing before launch.
PSD2 SCA, NIST guidance, GDPR and regional banking rules built into the design.
Move existing users from passwords and SMS OTP to passkeys without disrupting sign-in.
Related Reading
Tell us about your app, users and compliance needs. We will review your current login and recovery flows and recommend the right mix of passkeys, biometrics and OTP, with a cost and timeline.