Face ID and fingerprint login in a business app, explained
Short answer: Face ID or fingerprint login doesn't replace your app's account system; it unlocks something the app already holds on the device, usually a stored sign-in credential or key, after the phone confirms the right person is holding it. Your app never sees the face or fingerprint itself. Build it as a convenience layer on top of a normal sign-in, with a fallback to passcode or password, and ask for biometrics again before sensitive actions.
Customers of booking, loyalty, field-service and member apps increasingly expect to open the app with a glance or a touch. Here's how biometric login works on iOS and Android, when it's worth adding and how to set it up sensibly.
What biometric login actually does
On iOS, Apple's LocalAuthentication documentation describes biometric authentication (Face ID, Touch ID or Optic ID) as a way for users to get secure, effortless access, with a passcode or password as the fallback and for devices without biometrics. It states that your app never gains access to the underlying authentication data, so you can't access fingerprint images, for example; that data is handled by the Secure Enclave, a hardware security processor isolated from the rest of the system. Apple's documentation includes guides on logging a user into an app with Face ID or Touch ID and on accessing Keychain items with them.
On Android, the Android developer guide to biometric authentication explains that apps use the system's biometric prompt and declare which kinds of authentication they accept:
BIOMETRIC_STRONG: a Class 3 biometric, as defined by Android's compatibility definitionsBIOMETRIC_WEAK: a Class 2 biometricDEVICE_CREDENTIAL: the screen lock PIN, pattern or password
The same guide describes tying biometric authentication to cryptography using a CryptoObject, so that a successful prompt unlocks a key that protects sensitive information. Its sample code shows a prompt with a "Use account password" button as the alternative.
In both cases, the phone answers one question: "Is the device owner present?" Your app then uses that answer to release something it stored securely earlier.
How it fits into sign-in
A typical flow:
- First sign-in is normal: email and password, a magic link, or "Sign in with Apple/Google".
- The app offers biometrics: "Use Face ID to sign in next time?" Only if the device supports it and the user agrees.
- The app stores a credential securely, for example a refresh token in the iOS Keychain or protected by an Android Keystore key, with access tied to biometric authentication.
- Next launch: the app shows the biometric prompt; on success, it uses the stored credential to get a fresh session from your server.
- Fallback: if biometrics fail, are cancelled or have changed, the user can enter their passcode or sign in normally.
Your server never receives biometric data. It sees an ordinary authenticated request.
When it's worth adding
Good fit:
- Apps people open often: loyalty, ordering, staff and field apps, booking.
- Apps with information worth protecting but annoying to re-enter: account balances, client details, schedules.
- Staff apps on shared or company devices where quick re-authentication matters.
Less useful:
- Apps used once or twice a year, where users will have forgotten they turned it on.
- Apps with nothing sensitive behind sign-in; a long-lived session might be simpler.
Design decisions to make
Opt-in, not default
Ask after the first successful sign-in, explain the benefit in one line, and let users switch it off in settings.
Choose the strength you accept
On Android, decide whether to allow only strong biometrics or also weaker ones and device credentials. For anything involving money or personal data, strong biometrics with a device-credential fallback is a common choice; check Android's guidance for how each option interacts with cryptographic keys.
Re-authenticate for sensitive actions
Use a fresh biometric prompt before changing payout details, viewing full card or ID information, or approving large orders, even if the user is already signed in.
Handle changes gracefully
If a user adds a new fingerprint or face, platforms can invalidate biometric-bound keys depending on how they were created. Your app should then fall back to normal sign-in and offer to re-enable biometrics.
Write clear prompt text
The prompt should say what's being unlocked: "Sign in to your bookings" rather than a generic "Authenticate".
Keep account recovery separate
Biometrics are local to one device. Losing the phone means signing in normally on the new one, so password reset or other recovery must still work.
Explaining it to customers
A short line in the app's settings or help section avoids worried questions: biometric sign-in uses the phone's own Face ID or fingerprint check, the app never receives or stores face or fingerprint data, and it can be switched off at any time. If staff use the app on shared company devices, explain who can enrol biometrics on those phones and why personal devices are usually handled differently.
Testing checklist
- Device with no biometrics enrolled
- Biometrics enrolled, then removed
- New fingerprint or face added after enabling
- User cancels the prompt
- Too many failed attempts
- App reinstalled
- Account signed out on the server (the stored credential should stop working)
FAQ
Does my app store customers' fingerprints or face data?
No. Apple's documentation states apps never access the underlying biometric data, and Android's biometric prompt works the same way at system level. Your app receives only a success or failure result.
Can biometrics replace passwords entirely?
Not on their own; they unlock credentials stored on one device. Passkeys are a related but separate approach that can replace passwords across devices, often using biometrics to approve each sign-in.
What happens if Face ID fails?
The user can use the device passcode or your app's normal sign-in, depending on how you configure the fallback.
Is fingerprint login secure enough for payments?
It's widely used for that purpose, but the security depends on how you implement it: strong biometrics, keys tied to authentication, and server-side checks. Re-prompt before sensitive actions.
Adding quicker sign-in to your customer or staff app? Tell us how people log in today and we'll map out a biometric option with sensible fallbacks.