無料
無料
月額$0。クレジットカード不要。
- 無料KYCバンドル（本人確認 + パッシブ・ライブネス + 顔照合 + デバイス＆IP分析）, 毎月500回まで
- ブロックリストユーザー
- 重複検出
- すべてのセッションで200以上の不正シグナル
- Diditネットワーク全体でのKYC再利用
- ケース管理プラットフォーム
- ワークフロービルダー
- 公開ドキュメント、サンドボックス、SDK、MCP (Model Context Protocol) サーバー
- コミュニティサポート
世界中の2,000以上の組織から信頼されています。
規制対象プラットフォームが負うべきもの
チップを読み取り、署名を検証。書類スキャンを凌駕します。
eパスポートチップのデータは、発行国によって暗号署名されています。その署名チェーンを検証し、セルフィーを高解像度のチップ顔写真と照合することで、書類が本物であるという銀行レベルの確証が得られます。DiditのNFCフローは5秒以内に完了し、NFCが利用できない場合はOCRにフォールバックします。iOS、Android、React Native、Flutter用のネイティブSDKも提供しています。
仕組み
サインアップから本人確認済みユーザーまで、4つのステップで完了。
- ステップ 01
ワークフローを作成
本人確認、ライブネス、顔照合、制裁リスト、住所、年齢、電話番号、メールアドレス、カスタム質問など、必要なチェックを選択します。ダッシュボードでフローにドラッグ＆ドロップするか、同じフローをAPIにポストします。条件分岐やA/Bテストもコード不要で実行できます。
- ステップ 02
連携
Web、iOS、Android、React Native、FlutterのSDKでネイティブに組み込むか、ホストされたページにリダイレクトします。または、メール、SMS、WhatsAppなど、どこからでもユーザーにリンクを送信するだけです。あなたのスタックに合った方法を選んでください。
- ステップ 03
ユーザーがフローを実行
Diditはカメラ、照明の指示、モバイル連携、アクセシビリティをホストします。ユーザーがフローを実行している間、200以上の不正信号をリアルタイムでスコアリングし、すべてのフィールドを信頼できるデータソースと照合して検証します。結果は2秒以内に表示されます。
- ステップ 04
結果を受け取る
リアルタイムの署名付きWebhookにより、ユーザーが承認、拒否、またはレビューに送られた瞬間にデータベースが同期されます。必要に応じてAPIをポーリングすることも可能です。または、コンソールを開いてすべてのセッション、すべての信号を検査し、ケースを独自の方法で管理することもできます。
01 · NFCチップ読み取り
パスポートをタップしてチップを読み取ります。
ユーザーは視覚ページを読み取り（MRZがチップキーを導出）、書類をスマートフォンにタップすると、チップからデータグループ1（個人データ）、データグループ2（高解像度顔写真）、データグループ11（個人詳細）が返されます。チップ読み取り1回あたり$0.15。エンドツーエンドで2〜4秒。
NFC検証モジュールDidit · NFC Reading
Tap to read the e-passport chip.
Step 2 / 4
Hold the passport to the phone
- MRZ key derivedAuto
- BAC / PACE handshakeChip
- DG1, DG2, DG11 readChip
- ICAO signature verifiedPKD
- Face match to portrait$0.05
02 · ICAO署名チェーン
政府署名を検証済み。
パッシブ認証は、ICAO公開鍵ディレクトリを介して、チップの文書署名証明書と国の署名CAを照合して検証します。チップ認証とアクティブ認証は、サポートされている場合に実行されます。ICAO Doc 9303に準拠しています。
NFC検証モジュールDidit · ICAO 9303 chain
The government signature, verified.
SignatureSource of trustVerdict
- Passive Authentication (PA)ICAO PKD · CSCAPass
- Chip Authentication (CA)Chip · session keyPass
- Active Authentication (AA)Chip · RSA challengePass
- Data group integrityDG1, DG2, DG11, DG13Pass
ICAO Doc 9303 conformant · Bank-grade onboarding depth.
03 · チップの顔写真との顔照合
セルフィーとチップの顔写真を照合。
チップ上のDG2顔写真は、視覚ページに印刷された写真よりもはるかに高解像度です。これとライブセルフィーを照合することで、はるかに正確な結果が得られます。コサイン類似度0.85以上で合格、0.92以上で銀行レベル。1照合あたり$0.05。
顔照合（1:1）モジュールDidit · Face Match 1:1
Selfie matched to the chip portrait.
Chip portrait · DG2
High-res · gov-signed
Live selfie
Score 0.94 · iBeta L1
Cosine similarity ≥ 0.85 → Pass · ≥ 0.92 → bank-grade.
04 · パッシブライブネス
セルフィーにアンチスプーフィングを適用。
iBetaレベル1プレゼンテーション攻撃検出（PAD）認定済み。印刷された写真、画面のリプレイ、シリコンマスク、ディープフェイクを単一の静止セルフィーで検出し、チャレンジプロンプトは不要です。1チェックあたり$00.10。
パッシブ・ライブネスモジュールDidit · Passive Liveness
Anti-spoof on the selfie.
AttackSignalCaught
- Printed photoTexture · moiréPass
- Screen replayRefresh + glarePass
- Silicone maskMicro-skin patternsPass
- Deepfake (video)Temporal consistencyPass
Single still · no challenge prompts.$0.10 per check
05 · AMLスクリーニング
チップで検証された本人情報をスクリーニング。
制裁リスト、政治的要人（PEP）、ネガティブメディアを1,300以上のリストからスクリーニング, 毎日更新され、14言語に対応。ヒットがあった場合は自動的にケースが作成され、承認前にオンボーディングを停止します。
AMLスクリーニングモジュールDidit · AML
Screen the chip-verified identity.
HitSource listStatus
- Subject · cleanOFAC SDNPass
- Subject · cleanEU consolidatedPass
- PEP · foreign ministerDow Jones PEPReview
14 languages · daily delta refresh$0.20 / check
06 · MRZ + OCRへのフォールバック
NFCが利用できない場合は、適切にフォールバックします。
NFC非対応のスマートフォン、チップ非搭載の書類、またはNFC許可拒否の場合でも、同じワークフローが視覚ページの高精度MRZ + OCRによる本人確認（$0.15）にフォールバックします。同じホストURL、同じWebhook、同じステータスで処理されます。
本人確認モジュールDidit · ID Verification
Fallback when NFC is unavailable.
- Phone has no NFCiPhone 6 / lower-end Android
- Chip not presentPre-2014 passport / state ID
- Chip read failedCracked chip · MRZ-only path
- OCR + MRZ fallbackID Verification ($0.15)
Workflow Builder routes automatically when NFC drops.
連携
1セッション。ネイティブSDK。数秒で銀行レベルの本人確認。
NFCセッションを開きます。SDKがチップの読み取りを駆動します。署名された判定結果を読み取ります。
POST /v3/session/NFC
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"workflow_id": "wf_nfc_onboarding",
"vendor_data": "user-42",
"expected_country": "ES"
}'201作成済みネイティブSDKでURLを開くと、NFCタップが起動します。
iOS / Android / React Native / Flutter SDKはすべてNFCに対応しています。ドキュメント →
GET /v3/session/{id}/decision/判定
$ curl https://verification.didit.me/v3/session/$SESSION/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
# Decision payload (excerpted):
{ "nfc_verification": { "passive_authentication": "Approved" },
"face": { "matched_against": "chip_portrait", "similarity_score": 0.94 } }200OKchip_portraitと照合 → eIDASレベルの保証。
NFCが利用できない場合、ワークフローはMRZ + OCRにフォールバックします。ドキュメント →
エージェント対応統合
NFC eパスポートのオンボーディングを1つのプロンプトで実装。
Claude Code、Cursor、Codex、Devin、Aider、またはReplit Agentに貼り付けてください。お使いのスタックに合わせて設定すると、NFCワークフローが構築され、ネイティブSDKが連携されます。NFCが利用できない場合はMRZ + OCRにフォールバックし、署名付きWebhookを読み取ります。
didit-integration-prompt.md
You are integrating Didit's NFC e-passport reading into a regulated onboarding flow (bank, fintech, crypto exchange, eIDAS-grade public service). NFC chip reading lifts onboarding from document-scan-grade to bank-grade in one extra step on the user's phone.
Five obligations on every onboarding:
1. Read the e-passport / e-ID chip via NFC — DG1 (MRZ), DG2 (portrait), DG11 (personal details).
2. Verify the government signature chain — Passive Authentication (PA) against the ICAO Public Key Directory, Chip Authentication (CA), Active Authentication (AA).
3. Match the live selfie to the high-resolution DG2 portrait extracted from the chip.
4. Run Passive Liveness on the selfie — iBeta Level 1 anti-spoof certified, defeats printed photos, screen replays, masks, and deepfakes.
5. Screen the chip-verified identity against sanctions, Politically Exposed Persons (PEP), and adverse-media lists.
Fallback automatically when NFC is unavailable (no chip, NFC blocked by iOS or by user permission, chip damaged): the workflow drops to high-accuracy MRZ + OCR on the visual page using ID Verification.
Pricing (verified live):
- NFC Reading: $0.15 per chip read
- ID Verification (fallback or always-on belt-and-braces): $0.15 per check
- Passive Liveness: $0.10 per check
- Face Match 1:1: $0.05 per match
- AML Screening: $0.20 per check
- Bundle (NFC + Liveness + Face Match + AML): $0.50 per onboarded user when NFC succeeds; $0.50 also when the workflow falls back to ID Verification
- First 500 KYC verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60s, no card).
- Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
- A workflow_id from the Workflow Builder bundling NFC Reading + ID Verification (fallback) + Passive Liveness + Face Match 1:1 + AML Screening.
- The Didit hosted flow or the native SDKs (web SDK, iOS, Android, React Native, Flutter) — NFC chip reading requires the native NFC stack, so plain web-only deployments fall back to MRZ + OCR automatically.
STEP 1 — Create the NFC session
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<your nfc onboarding workflow id>",
"vendor_data": "<your user id, max 256 chars>",
"callback_url": "https://<your-app>/onboarding/kyc/callback",
"expected_country": "ES",
"metadata": {
"channel": "native_ios",
"purpose": "high_assurance_onboarding"
}
}
Response: 201 Created with the hosted session URL. Open it via the native SDK (iOS NFC requires CoreNFC entitlement) or in the hosted webview; the user taps the e-passport against the phone's NFC reader, the chip data is read in 2-4 seconds.
STEP 2 — The chip-read sequence (handled by the SDK / hosted flow)
Inside the hosted flow, in this order:
a. The user presents the data page so the device camera reads the Machine-Readable Zone (MRZ). The MRZ provides the BAC / PACE key needed to handshake with the chip.
b. The user taps the passport to the phone. PACE (preferred) or BAC handshake establishes a secure session with the chip.
c. The chip returns Data Group 1 (MRZ data — name, DOB, expiry, document number), Data Group 2 (the high-resolution portrait), and Data Group 11 (personal details where available).
d. Passive Authentication verifies the Document Signer Certificate against the country's Country Signing CA via the ICAO Public Key Directory. Chip Authentication and Active Authentication run if supported by the issuing country.
e. The user takes a single selfie (Passive Liveness, no challenge prompts).
f. The selfie is matched 1:1 against the DG2 portrait.
STEP 3 — Read the signed webhook on completion
Didit POSTs to your callback. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"nfc_verification": {
"status": "Approved",
"passive_authentication": "Approved",
"chip_authentication": "Approved",
"active_authentication": "Approved",
"data_groups_read": [1, 2, 11]
},
"id_verification": { "status": "Approved", "document_type": "passport", "country_code": "ES" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94, "matched_against": "chip_portrait" },
"aml": { "status": "Approved", "hits": [] }
}
Session status enum (exact case):
Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned
Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.
STEP 4 — Decide
Branch logic:
Approved → onboard the user with bank-grade assurance.
In Review → hold the account, wait for analyst webhook update.
Declined → refuse onboarding, log the decline reason.
Resubmitted → user updated something; re-read the decision.
When face.matched_against === "chip_portrait", you can mark the identity as eIDAS High-grade (Substantial / High depending on your local regulator's reading). When it falls back to "id_document_portrait" (the visual page), it's still bank-grade by document-scan standards but not chip-anchored.
STEP 5 — Fallback paths
iPhones below iPhone 7, or any phone with NFC disabled, or a document without a chip (pre-2014 in some countries) → the workflow surfaces "NFC unavailable" and routes to the ID Verification + MRZ + OCR path. Same hosted URL, same webhook, same statuses. The fallback is configured in the Workflow Builder, not in your code.
Some Android devices won't read every chip due to NFC antenna placement — Didit's iOS / Android SDKs surface a graceful retry hint before failing over to OCR.
STEP 6 — Ongoing monitoring
Enable Ongoing AML at $0.07/user/year to keep the identity fresh. NFC re-reads aren't required for ongoing — the chip data was captured at onboarding and the binding is permanent for the document's validity period.
WEBHOOK EVENT NAMES
- status.updated — session status changed.
- data.updated — session data changed (resubmission, NFC retry, ongoing AML hit).
Verify X-Signature-V2 on every payload. The webhook secret is per-environment — sandbox key is separate from production.
CONSTRAINTS
- Session statuses use Title Case With Spaces (Approved, In Review).
- NFC chip reading requires the native NFC stack — iOS, Android, React Native, Flutter SDKs handle it; pure web falls back to MRZ + OCR.
- The chip portrait (DG2) is far higher-resolution than the visual page — matching the selfie to it is meaningfully more accurate than matching to a phone-camera-captured ID photo.
- Document Signer Certificate trust is anchored to the ICAO Public Key Directory; some countries (eg. small island states) do not publish to the PKD and will return a Passive Authentication warning rather than Approved.
- Default record retention is 5 years post-relationship per the EU AML package.
Read the docs:
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/sessions-api/retrieve-session
- https://docs.didit.me/core-technology/nfc-verification/overview
- https://docs.didit.me/core-technology/face-match/overview
- https://docs.didit.me/integration/webhooks
Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.さらに詳しい情報が必要ですか？モジュールの全ドキュメントをご覧ください。docs.didit.me →
設計段階からのコンプライアンス
ワンクリックで新しい国に進出。 面倒な作業は私たちにお任せください。
私たちは現地法人を設立し、ライセンスを取得し、ペネトレーションテストを実施し、認証を取得し、新しい規制すべてに準拠します。新しい国で認証を提供するには、トグルを切り替えるだけです。220以上の国で稼働しており、四半期ごとに監査とペネトレーションテストを実施しています。EU加盟国の政府が対面認証よりも安全だと正式に認めた唯一のIDプロバイダーです。
セキュリティ＆コンプライアンス資料を読むEU金融サンドボックス
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
情報セキュリティ · 2026
SOC 2 · Type I
AICPA · 2026
iBeta Level 1 PAD
NIST / NIAP · 2026
GDPR
EU 2016/679
DORA
EU 2022/2554
MiCA
EU 2023/1114
AMLD6 · eIDAS 2.0
設計段階からのEU準拠
実績データ
実績データ
- $0.00NFCチップ読み取り1回あたり, 政府署名検証済み。
- 2-4sエントリーレベルのAndroidで、タップから判定までのチップ読み取り時間。
- <0sチップの顔写真とのセルフィー顔照合。
- 0毎月、すべてのアカウントで無料検証をご利用いただけます。
3つのティア、1つの料金表
無料で開始。従量課金。エンタープライズまで対応。
毎月500回まで無料認証を永続的に提供。本番環境では従量課金。エンタープライズプランではカスタム契約、データレジデンシー、SLA（サービスレベルアグリーメント）に対応します。
最も人気
従量課金
従量課金
使った分だけお支払い。25以上のモジュール。モジュールごとの公開価格、月額最低料金なし。
- フルKYC（本人確認 + 生体認証 + IP / デバイス）が$0.33
- 10,000以上のAMLデータセット, 制裁、PEP、ネガティブ情報
- データベース検証のための1,000以上の政府データソース
- トランザクションモニタリングが1トランザクションあたり$0.02
- ライブKYBが1企業あたり$2.00
- ウォレットスクリーニングが1チェックあたり$0.15
- ホワイトラベル検証フロー, あなたのブランド、私たちのインフラ
エンタープライズ
エンタープライズ
カスタムMSA & SLA。大量利用や規制対象プログラム向け。
- 年間契約
- カスタムMSA、DPA、SLA
- 専用SlackおよびWhatsAppチャンネル
- オンデマンドの手動レビュー担当者
- リセラーおよびホワイトラベル条件
- 限定機能とパートナー連携
- 専任CSM、セキュリティレビュー、コンプライアンスサポート
無料で開始 → チェック実行時のみ支払い → カスタム契約、SLA、データレジデンシーが必要な場合はエンタープライズプランへ。
FAQ
よくあるご質問
What is Didit?
Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.
One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:
- Fast, sub-2-second p99 on every session
- Reliable, in production with 1,500+ companies across 220+ countries
- Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person
The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.
What's actually inside an e-passport chip?
Modern passports (and increasingly modern national ID cards in the EU) carry a tiny contactless chip, the same kind of chip you tap to pay with a card. The chip holds:
- Data Group 1 (DG1), the same machine-readable text as the visual page (name, date of birth, document number, expiry)
- Data Group 2 (DG2), the portrait of the holder, at much higher resolution than the photo printed on the visual page
- Data Group 11 (DG11), extra personal details when the issuing country chooses to publish them (full address, nationality detail)
- A digital signature from the issuing government over the entire data set
That last bit is the magic. The chip is cryptographically bound to the issuing country, which means an attacker can't forge or tamper with what it returns, they'd have to forge a government signature. Didit reads the chip via NFC on the user's phone in 2-4 seconds for $0.15 per read.
Why is NFC stronger than a regular ID scan?
Three reasons, in order of how much they matter:
- Cryptographic authenticity, the chip data is signed by the issuing country. A document-scan check can be fooled by a high-quality forgery; a chip-read check fails unless the forger has the country's private signing key.
- Higher-resolution portrait, the chip carries a far better-quality photo than the one printed on the data page. Matching a selfie against the chip portrait is meaningfully more accurate.
- Tamper-proof binding, the chip is sealed inside the document. Changing the chip data would require physical access to the issuing country's production line.
For most onboarding flows, document-scan is good enough. For bank, fintech, eIDAS-grade public service, and any flow where a single false positive costs real money, NFC chip reading is the standard control.
How fast is the verification for my end user?
The full flow normally takes under 30 seconds end-to-end, pick up the ID, snap the document, snap the selfie, done. That is the fastest in the market. Legacy KYC providers usually take more than 90 seconds for the same flow.
On the back end, Didit returns the result in under two seconds at p99, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.
What's ICAO 9303?
ICAO Doc 9303 is the international specification for machine-readable travel documents (MRTDs), every modern passport in the world is built to this spec. Three pieces matter for NFC verification:
- Passive Authentication (PA), checks that the chip data is signed by the issuing country's signing certificate, and that the signing certificate chains up to the country's master Country Signing Certificate Authority. Trust is anchored in the ICAO Public Key Directory (PKD), a shared directory of country signing certificates.
- Chip Authentication (CA), establishes a secure channel with the chip so an attacker can't replay a recording of an earlier chip exchange.
- Active Authentication (AA), sends a random challenge to the chip, the chip signs it with its private key, and the response proves the chip is the original physical chip (not a cloned chip with copied data).
Didit runs all three and exposes each verdict separately in the decision payload. ICAO Doc 9303 conformant means the chip-read path is the same one border agents use at airport e-gates.
What happens if a user fails, abandons, or expires?
Every session lands on one of seven clear statuses, so your code always knows what to do:
Approved, every check passed. Move the user forward.Declined, one or more checks failed. You can allow the user to resubmit the specific failed step (for example, re-take the selfie) without re-running the whole flow.In Review, flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.In Progress, user is mid-flow.Not Started, link sent, user has not opened it yet. Send a reminder if it sits too long.Abandoned, user opened the link but did not finish in time. Re-engage or expire.Expired, the session link aged out. Create a new session.
A signed webhook fires on every status change, so your database always stays in sync. Abandoned and declined sessions are free.
Where does my customer data live and how is it protected?
Production data is processed and stored in the European Union by default, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.
Encryption everywhere. AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.
Retention is yours to control. Default retention is indefinite (unlimited) unless you configure shorter, between 30 days and 10 years per application, and you can delete any individual session at any time from the dashboard or the API.
Certifications: SOC 2 Type 1 (Type 2 audit in progress), ISO/IEC 27001:2022, iBeta Level 1 PAD, and a public attestation from Spain''s Tesoro / SEPBLAC / CNMV that Didit''s remote identity verification is safer than verifying someone in person. Full report at /security-compliance.
Is Didit compliant for my industry?
Didit ships compliant by default for the regulators that matter to identity infrastructure:
- GDPR + UK GDPR, controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
- AMLD6 + EU AML Single Rulebook, 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
- eIDAS 2.0, EU Digital Identity Wallet aligned; reusable-identity ready.
- MiCA (Markets in Crypto-Assets), ready for crypto on-ramps, exchanges, and custodians.
- DORA, Digital Operational Resilience Act, EU financial-services operational resilience.
- BIPA, CUBI, Washington HB 1493, CCPA / CPRA, US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
- UK Online Safety Act, age-gating and child-safety obligations.
- FATF Travel Rule, originator and beneficiary data on crypto transfers, IVMS-101 interoperable.
Detailed memo, every certificate, every regulator letter: /security-compliance.
How fast can I integrate and start verifying users?
- 60 seconds to a sandbox account at business.didit.me, no credit card.
- 5 minutes to a working verification through Claude Code, Cursor, or any coding agent via our Model Context Protocol (MCP) server.
- A weekend to a production-ready integration with signed-webhook verification, retries, and a remediation flow when a user is declined.
Three integration paths, pick whichever fits your stack:
- Embed natively with our Web, iOS, Android, React Native, or Flutter SDK.
- Redirect the user to the hosted verification page, zero SDK.
- Send a link by email, SMS, WhatsApp, or any channel, zero front-end work.
Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.
What if the chip read fails?
Three common failure modes, all handled by the workflow:
- NFC unavailable on the device, iPhone 6 or earlier, NFC permission denied, tablet without NFC. The flow surfaces "NFC unavailable" and falls back to ID Verification on the visual page.
- Chip not present in the document, pre-2010 passport, older national ID. The MRZ tells the flow there's no chip; falls back to ID Verification.
- Chip damaged or unreadable, physical damage, antenna placement issues on certain Android phones, RF interference. The flow offers up to three retry attempts before falling back.
The fallback path is the same /v3/session/, same webhook, same statuses. The decision payload tells you which path succeeded so you can route on it, face.matched_against === "chip_portrait" for the NFC path, "id_document_portrait" for the OCR fallback. Bank-grade workflows can reject the OCR fallback and require a fresh attempt on a different device.
Does NFC make this eIDAS-grade?
Under eIDAS 2, the EU's electronic-identification framework, a chip-verified e-passport with biometric matching can support Substantial or High assurance, depending on the workflow's surrounding controls.
Didit's role is to deliver the underlying identity-binding evidence:
- ICAO 9303 chip-signed identity data → Substantial assurance baseline
- High-resolution chip-portrait face match → high-confidence binding
- Passive liveness → spoof-resistance evidence
- AML screen → sanctions / PEP / adverse-media discharge
Whether the complete flow reaches Substantial or High depends on the consuming wallet, the trust framework, and the regulator's interpretation in your country. Didit is the only KYC provider with a formal EU-government attestation, Spain's Treasury, Banco de España, and SEPBLAC jointly attested the service as safer than in-person verification. That report is the most-cited starting point for an eIDAS High discussion.
How does Didit compare on price?
Most NFC providers price between $1.50 and $5.00 per chip read, often with minimums in the thousands of euros per month and per-country surcharges for chip-signing-cert subscriptions. The Onfido / Jumio / Veriff archetype.
Didit's published price is $0.15 per NFC chip read + $0.50 for the full bundle (NFC + Liveness + Face Match + AML). No floor, no minimum, no per-country surcharge. The first 500 verifications free every month absorbs most pilots entirely.
That's roughly 10-30× cheaper than the incumbent stack on the same regulatory output. At a 10,000-user month, the saving versus a $2.00-per-chip incumbent is around $18,500. At European-bank volumes (100,000+ KYCs / month) the saving compounds into mid-six-figures annually. Full pricing at /pricing.