/ THE SHORT ANSWER
Banks, fintechs, insurers, brokers, telecom operators, and public services can now integrate Aadhaar face authentication directly into Android and iOS apps and test the full journey in a controlled sandbox. The release is intended to remove reliance on a separate FaceRD app and simplify RBI-related multi-factor authentication use cases.
- 01The SDK embeds the journey in native Android and iOS apps.
- 02The sandbox supports consent, capture, liveness, authentication, errors, and response validation.
- 03UIDAI says Aadhaar face authentication has processed more than 500 crore transactions.
- 04Production rollout still requires risk-based fallback and user support.
/ dotSuper point of view
A smoother biometric journey can improve completion rates, but only if consent, liveness, fallback, security, accessibility, and error recovery are tested as one system.
What UIDAI launched
UIDAI has released an Aadhaar Face Authentication SDK for native Android and iOS applications and a controlled sandbox for integration testing. The aim is to let users complete face authentication inside the organization’s own app.
The SDK includes AI and machine-learning-based liveness and anti-spoofing capabilities, encryption, and support for consumer smartphones according to the government release.
- Native mobile integration
- Liveness and anti-spoofing
- Encrypted authentication data
- Reduced dependency on a separate FaceRD app
What the sandbox supports
The sandbox is designed to test user provisioning, consent, face capture, liveness checks, authentication, error handling, and response validation before production onboarding.
It also supports failure scenarios including invalid digital signatures, network interruptions, timeouts, and spoofing attempts. These cases should become repeatable acceptance tests, not one-time demonstrations.
- Consent and provisioning
- Capture and liveness
- Network and timeout failures
- Spoof and invalid-signature scenarios
The controls banks and fintechs need
Biometric matching is one part of an authentication decision. Teams must also define transaction risk, device integrity, account history, fallback methods, retry limits, support escalation, and fraud monitoring.
Fallback is especially important for users with accessibility needs, camera limitations, poor connectivity, changed appearance, or repeated false rejects.
- Measure false acceptance and false rejection
- Rate-limit retries and detect automation
- Provide secure non-biometric fallback
- Log consent and decision evidence
What this page cannot conclude
- 01The adoption and transaction figures are reported by UIDAI.
- 02Detailed technical and onboarding requirements should be taken from current UIDAI documentation.
- 03Biometric authentication has accessibility, privacy, and error risks that vary by use case.
Sources
- 01UIDAI launches Aadhaar Face Authentication SDK and SandboxPress Information Bureau, Government of India · accessed Sep 11, 2026
- 02Aadhaar authenticationUnique Identification Authority of India · accessed Sep 11, 2026
Our editorial standard · Found an error? Send a correction with its source.
/ CITE OR SHARE THIS GUIDE
Make the evidence easy to verify.
When you reference this guide, link to its canonical URL. That gives readers one stable place for the evidence, limitations and future updates.
dotSuper Research Desk. (September 11, 2026). Aadhaar Face Authentication SDK and Sandbox: What Banks and Fintechs Need to Test. dotSuper. https://dotsuper.net/feeds/daily-briefing/2026-09-11-aadhaar-face-authentication-sdk-sandbox