Overview
The NFC Passport Reading API extracts verified, tamper-evident data directly from the chip embedded in a biometric passport. Unlike OCR, NFC reads the cryptographically signed chip data — providing a higher-assurance extraction that is significantly harder to forge.
Key Features
- Reads data directly from the passport’s NFC chip — not just the printed page
- Cryptographically verified data: name, date of birth, nationality, expiry
- Encrypted storage of chip-extracted data and passport image
- Seamlessly hands off to a liveness check after reading
- Mobile-first flow with hosted UI — no NFC SDK integration required on your end
How It Works
Initiate
Your server calls the API and receive token and URL.
Install
The user scans the deeplink to install the mobile application on their NFC-capable mobile device.
Scan
The user taps their passport to the phone and then uses the camera to perform a liveness check.
Result
We return the verified chip data (name, DOB, nationality, expiry) as well as the liveness results in a webhook.
Common Use Cases
High-assurance identity verification
Use NFC chip data as the authoritative source for KYC
Border and access control
Verify the chip matches the physical passport holder
Premium onboarding
Offer a fast, tap-to-verify experience for users with biometric passports
One click services API
API Overview
Example Parameters
| Parameter | Description |
|---|---|
reference | Your internal reference ID for this session |
redirect_url | Where to send the user after completion |
Example Request
POST /nfc
{
"reference": "cust_00456",
}Example Response
{
"status": "success",
"session_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
"token": "ABC123",
"deeplink": "https://verify.oneclickservices.com.au/deeplink/ABC123",
"expiry": "1776241063",
}JWT WEBHOOK
| Parameter | Value |
|---|---|
| realface |
| 0.87516615 |
firstname | John |
lastname | Doe |
dob | 1970-01-01 |
expiry | 2026-12-31 |
country | AU |