NFC Verification Beyond Document Images
The Machine Readable Zone (MRZ) is the coded text used to access the NFC chip. The Security Object helps verify its data.
- Read chip identity data
- Check Security Object integrity
- Retrieve the chip portrait
- Combine NFC with liveness
Scale NFC Verification Globally
Add chip-based authentication to an identity platform built for international onboarding and configurable verification journeys.
Verify Chip Data with NFC Verification
okID reads the embedded chip and returns three key sources of identity evidence.
Read Chip Data
Retrieve structured data from supported electronic passports and identity cards.
- MRZ details
- Identity information
- Structured chip data
Check Data Integrity
Use the Security Object to check whether the chip data remains authentic.
- SOD verification
- Cryptographic evidence
- Chip data validation
Retrieve Chip Portrait
Access the identity photo stored inside the document chip.
- Embedded portrait
- Chip-based evidence
- Verification record output
How okID NFC Verification Works
Configure the flow, guide the user to an NFC-enabled device, and return the result to your system.
Step 01
Step 02
Step 03
Step 04
Step 05
Step 06Step 01Set the Flow
Enable NFC and the other verification modules required for the journey.
Step 02Create Verification
Your backend creates a verification ID with its secure API key.
Step 03Move to Mobile
Use a direct mobile journey or let desktop users continue through a QR code.
Step 04Capture the Document
The user completes the configured identity document step.
Step 05Read the Chip
okID extracts MRZ data, checks the Security Object, and retrieves the chip portrait.
Step 06Return the Result
Receive the outcome through the API, webhook, or dashboard.
Build Trust with NFC ID Verification
Add stronger identity evidence to your verification flow without compromising integration flexibility, data control, or user experience.
One Verification Journey
Combine NFC, document verification, liveness, terms, and form modules.
Smooth Mobile Handoff
Move desktop users to an NFC-enabled phone through a QR code.
Configurable Data Controls
Manage retention and redact MRZ, portrait, or template data.
Build the Verification Flow You Need
Bring the right checks together in one flexible flow, tailored to how your business verifies customers.
Captures and evaluates passports, ID cards, driving licences, and residence permits through layered document checks.
Compares a live selfie with the portrait on the identity document to check whether they show the same person.
Available only in the Netherlands, this check screens Dutch identity documents for reported lost or stolen status.
Configure NFC Verification Your Way
Adapt the verification journey using API key settings and routing options.
Enable NFC reading
Add document or liveness checks
Use separate API keys
Direct mobile flow
QR device handoff
Mobile-only journey
Set retention days
Redact MRZ data
Redact portraits or templates
Configure webhooks
Set return URLs
Use API or dashboard results
Protect Data During NFC Authentication
okID keeps API credentials on the server, protects production communication, and supports configurable data controls.
NFC Identity Verification
Use Cases
Use chip-based identity evidence in workflows where reliable
document checks matter.
Read chip data from supported ePassports and eID cards before approving a new bank account.
Read supported travel documents during airline, hotel, event, or travel onboarding.
Bring electronic document checks to public and municipal services that need reliable identity evidence.
Strengthen KYC evidence for lending, payments, and investment products with higher fraud exposure.
Meet stricter onboarding expectations with chip-verified document data instead of document images alone.
NFC Identity Verification Use Cases
Use chip-based identity evidence in workflows where reliable document checks matter.
Read chip data from supported ePassports and eID cards before approving a new bank account.
Read supported travel documents during airline, hotel, event, or travel onboarding.
Bring electronic document checks to public and municipal services that need reliable identity evidence.
Strengthen KYC evidence for lending, payments, and investment products with higher fraud exposure.
Meet stricter onboarding expectations with chip-verified document data instead of document images alone.
Trusted NFC Authentication for Regulated Teams
Regulated teams use okID to connect liveness with document, NFC, and compliance checks.
Know Before You Launch NFC Verification
Review common questions about NFC verification, chip reading, and integration before you begin.
Still have a question? Ask a Question
A failed verification ID cannot be reused. Your backend must create a new ID before another attempt.
Supported chip-enabled passports and identity cards. Availability depends on the country and document type.
It helps detect counterfeit or altered documents by checking the authenticity and integrity of chip data.
Data is transferred securely, encrypted, and protected through access controls and configurable retention settings.
The public documentation does not confirm an automatic non-NFC fallback. Confirm the alternative journey during implementation.
Yes. Add custom metadata when creating the verification and receive it again through the webhook.
Your system should support successful, rejected, and manual-review outcomes.
Create a new verification ID and restart the required flow. The previous failed ID cannot be reused.
okID retries unsuccessful webhooks up to three times using exponential backoff.
Yes. Use separate API keys with their own modules, webhooks, and data settings.
Your team can configure retention periods and redaction settings for each API key.
Add NFC
Verification to Your Flow
Add chip-based document evidence to your existing identity journey across web and mobile applications.
Built by Bluem, with ISAE 3402 Type II assurance.