Skip to main content
Diditが750万ドルを調達、本人確認と不正対策のインフラを構築
Didit
IDウォレット · EU eIDAS 2.0

一度認証。どこでも再利用。

1回$0.33のKYC後、Didit署名付きクレデンシャルを発行します。ユーザーは、選択的開示により他のすべてのDidit対応プラットフォームで提示できます。永続的に無料で、EU IDウォレットのルールブックに準拠しています。

無料で始めるドキュメントを読む
支援元
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

世界中の2,000以上の組織から信頼されています。

映画のような暗い抽象的なコンプライアンスのイラスト, 純粋な黒のキャンバス上に、発光するDidit Blueの垂直線で結ばれ、4つの光るスキャナーブラケットで囲まれた、3Dパースペクティブの4つの浮遊する半透明のダークガラスパネル。各パネルには、署名付きクレデンシャルを保持するIDウォレットを表す小さな淡い白の抽象的なモチーフ（ウォレットのシルエット、EUの12星リング、クレデンシャルカード、鍵の形）が描かれています。

再利用可能なIDがもたらすもの

ユーザーのポケットにIDを。 受け入れるすべての人にとって無料です。

すべてのDidit KYCは、署名付きの再利用可能なIDクレデンシャルをユーザーのウォレットに発行します。 すべての受け入れプラットフォームは、選択的開示により無料で検証します。 一度の認証で、Diditを受け入れるすべてのビジネスで利用可能。毎月500件の認証が無料です。

仕組み

サインアップから認証済みユーザーまで、4つのステップ。

  1. ステップ 01

    ワークフローを作成

    ID、生体認証、顔照合、制裁リスト、住所、年齢、電話番号、メールアドレス、カスタム質問など、必要なチェックを選択します。ダッシュボードでフローにドラッグ＆ドロップするか、同じフローをAPIに投稿します。条件分岐やA/Bテストもコード不要で実行できます。

  2. ステップ 02

    連携

    Web、iOS、Android、React Native、Flutter SDKでネイティブに組み込みます。ホストされたページにリダイレクトすることも、メール、SMS、WhatsAppなど、どこでもユーザーにリンクを送信するだけでも可能です。あなたのスタックに合った方法を選んでください。

  3. ステップ 03

    ユーザーがフローを完了

    Diditは、カメラ、照明の指示、モバイル連携、アクセシビリティをホストします。ユーザーがフローを実行している間、200以上の不正信号をリアルタイムでスコアリングし、すべてのフィールドを信頼できるデータソースと照合します。結果は2秒未満で得られます。

  4. ステップ 04

    結果を受け取る

    リアルタイムの署名付きWebhookにより、ユーザーが承認、拒否、またはレビューに送られた瞬間にデータベースが同期されます。必要に応じてAPIをポーリングすることも、コンソールを開いてすべてのセッション、すべての信号を検査し、ケースを管理することもできます。

再利用可能なIDのために構築 · インフラストラクチャのような価格設定

1回のKYC。その後のすべてのプラットフォームで無料。

真の再利用可能なIDは単一の機能ではなく、システムです。発行、保持、提示、選択的開示、更新、失効。すべてが1つの`/v3/`セッションで完結します。
ドキュメントを読むAPIキーを取得
01 · 一度検証

1回のKYCで1つのクレデンシャルを発行。

ユーザーは初回に標準の$0.33バンドルを実行します。完了後、Diditがクレデンシャルに署名し、DiditアプリまたはArchitecture Reference Frameworkに対応する任意のEUデジタルIDウォレットにプッシュします。
ユーザー検証モジュール
02 · 選択的開示

検証者が必要とする情報のみを開示。

生年月日を明かすことなく18歳以上であることを証明します。住所を明かすことなく国籍を証明します。選択的開示JSON Web Tokens (SD-JWT) により、開示される情報はすべて暗号的に署名されます。
再利用可能なKYCモジュール
03 · ウォレット連携

すべてのEUDI互換ウォレットに対応。

Diditが発行するクレデンシャルは、Diditアプリおよび任意のEU加盟国のデジタルIDウォレット（Cartera Digital、IT Wallet、各国のウォレット）で機能します。すべてのプラットフォームで、検証可能なクレデンシャルのためのOpenIDプレゼンテーションフローは共通です。
Diditアプリをダウンロード
04 · 発行者・保有者・検証者

3つの役割。1つのクレデンシャル。

発行者はKYC後にクレデンシャルに署名します。ユーザーはそれを自身のウォレットに保管します。検証者は、開示されたフィールドのみについて発行者の署名を検証します。これは標準的な検証可能クレデンシャルの信頼の三角形です。
セキュリティとコンプライアンス
05 · クレデンシャルの鮮度

クレデンシャルの鮮度を自動で維持。

継続的なAMLは、ユーザーを毎日再スクリーニングします。書類の有効期限切れ、氏名変更、制裁対象者への該当など、すべてクレデンシャルに自動的に反映されます。古いクレデンシャルは提示時に拒否されます。
AMLスクリーニングモジュール
06 · 受信は無料

すべての受信プラットフォームで無料。

発行はすべてのKYCに含まれます。ウォレットストレージはユーザーのデバイス上で行われます。提示、選択的開示、署名検証はすべて永続的に無料です。大量アカウントの場合、継続的なAML更新はユーザーあたり年間$0.07です。
再利用可能なKYCモジュール
連携

1つのエンドポイント。2つのパス。1つのWebhook。

セッションを開始します。ホストされたフローは、提示されたクレデンシャルを受け入れるか、完全なKYCを実行します。いずれの場合も、署名された判定結果を読み取ります。
POST /v3/session/Accept
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_accept_reusable",
    "vendor_data": "user-42",
    "metadata": { "request_fields": ["full_name", "age_over_18"] }
  }'
201作成済みホスト型フローがクレデンシャルを検出、または完全なKYCを実行
Diditクレデンシャルが提示された場合は無料。完全なKYCが実行された場合は$0.33。ドキュメント →
GET /v3/session/{sessionId}/decision/読み取り
$ curl https://verification.didit.me/v3/session/$SID/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# 開示されたフィールドと発行者チェーンを返します
# reusable_identity.presented が true の場合。
# 完全なKYCエビデンスパックを返します
# 新規KYCが実行された場合。
200OKステータス：承認済み・審査中・却下・期限切れ
クレデンシャルが提示されたか、新規KYCが実行されたかにかかわらず、同じエビデンスパック。ドキュメント →
エージェント対応統合

再利用可能なIDフローを1つのプロンプトで実装。

Claude Code、Cursor、Codex、Devin、Aider、またはReplit Agentに貼り付けてください。スタック情報を入力すると、エージェントがワークフローを構築し、ウォレット検出をマウントし、開示フィールドを宣言し、Webhookを接続します。
didit-integration-prompt.md
You are integrating Didit's Reusable Identity / eIDAS 2.0 acceptance into your platform. Two flows:

  1. Issue — when a new user runs a full KYC on your platform, they leave with a Didit-signed Reusable Identity credential in their wallet (the Didit app or any EU Digital Identity Wallet).
  2. Accept — when a user arrives at your platform already holding a Didit-signed credential, the session detects it and short-circuits, returning Approved without re-running the full KYC.

Bundle pricing (verified live 2026-05-16):
  - First verification (issuance side): $0.33 per user (Sessions API full KYC bundle)
  - Issuance: free — the signed credential is included with every KYC
  - Reuse on the verifying side: free, forever
  - Selective disclosure: free
  - Continuous Anti-Money Laundering (AML) refresh: $0.07 per user per year (automatic)
  - First 500 verifications free every month, forever

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
  - Webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header.
 HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature.  - A workflow_id from the no-code Workflow Builder with:
    * ID Verification + Passive Liveness + Face Match 1:1 + Device & IP Analysis + AML Screening (for issuance)
    * Reusable Identity acceptance turned on (for acceptance — toggle in the Workflow Builder)
  - Optional: the Didit mobile SDK (iOS / Android / React Native / Flutter) for native deep-link wallet handoff.

STEP 1 — Open a session that accepts a Reusable Identity if presented

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id with Reusable Identity acceptance on>",
      "vendor_data": "<your user id>",
      "callback": "https://<your-app>/onboarding/callback",
      "metadata": {
        "purpose": "platform_onboarding",
        "request_fields": ["full_name", "age_over_18", "country_of_residence"]
      }
    }

  Optional in body: declare the exact fields you need disclosed via metadata.request_fields. Didit's hosted flow will prompt the user to approve only those specific fields when they present a Reusable Identity credential.

  Response: 201 Created with the hosted session URL. Redirect the user.

STEP 2 — The hosted flow detects (or runs) the verification

  Two paths from this one endpoint:

  Path A — User has a Didit-signed credential
    - The hosted flow detects the credential via a wallet-handoff prompt (universal link on mobile, popup-bridge on desktop)
    - The user approves the disclosure of the requested fields
    - Didit validates the issuer signature + credential freshness server-side
    - Session returns Approved with the disclosed fields populated on the decision payload
    - Cost: $0 on the verifying side

  Path B — User does NOT have a credential
    - The hosted flow runs the full KYC bundle (ID + Liveness + Face Match + Device & IP + AML)
    - At completion, Didit issues a Reusable Identity credential to the user's wallet
    - Session returns Approved with the full decision payload
    - Cost: $0.33 on the verifying-and-issuing side

  Same endpoint, same webhook, same status enum. The path is transparent to your back-end.

STEP 3 — Read the signed webhook

  Didit POSTs to your callback. Session statuses (Title Case With Spaces):

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your user id>",
      "status": "Approved",
      "id_verification": { "status": "Approved" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "ip_analysis": { "status": "Approved" },
      "aml": { "status": "Approved", "hits": [] },
      "reusable_identity": {
        "presented": true,
        "issuer": "<issuing-platform name>",
        "issued_at": "<timestamp>",
        "disclosed_fields": ["full_name", "age_over_18", "country_of_residence"]
      }
    }

  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.

  When reusable_identity.presented is true, the user re-presented an existing credential and the verification was free; when false, a fresh KYC was run and billed at $0.33.

STEP 4 — Retrieve the full decision later

  GET https://verification.didit.me/v3/session/{sessionId}/decision/
  Headers:
    x-api-key: <your api key>

  Returns the full payload including: document scan + extracted Machine-Readable Zone (MRZ) data, biometric similarity, AML hits, device + IP risk signals, 200+ fraud signals, HMAC signature, and (if presented) the credential issuance chain.

  Same evidence pack regardless of issuance vs reuse — the verifier never sees less than a fresh KYC would deliver.

STEP 5 — Continuous AML monitoring is automatic

  Every approved user (issued OR presented) is re-screened daily against 1,300+ sanctions, PEP, and adverse-media lists at $0.07 per user per year on heavy-volume accounts. When a previously-clean user crosses an AML threshold, the credential's AML field is updated automatically; every receiving platform sees the refreshed status on next presentation.

  When the user revokes a credential from their wallet, your receiving platform's webhook fires with status: Expired and the credential is dropped from the user's account.

STEP 6 — Selective disclosure at presentation time

  Pass the exact fields you need via metadata.request_fields at session creation. Recommended minimum-disclosure patterns:

  - Age-gate (UK Online Safety Act, France SREN): ["age_over_18"]
  - Country-gate: ["country_of_residence"]
  - Full name + verified-human: ["full_name", "verified_human"]
  - AML-clear gate (lending): ["aml_clear", "full_name"]
  - Full identity (banking, payments): ["full_name", "date_of_birth", "address", "document_number", "aml_clear"]

  The user sees a single approval prompt listing the requested fields. Anything not listed is never disclosed to your platform.

WEBHOOK EVENT NAMES
  - Sessions: status changes flow through the standard session webhook (verify X-Signature-V2 HMAC SHA-256).
  - Credential lifecycle: status: Expired fires when a holder revokes the credential.

CONSTRAINTS
  - Session statuses use Title Case With Spaces. Don't UPPER_SNAKE_CASE them.
  - Reusable Identity acceptance is OFF by default; turn it on in the Workflow Builder.
  - Selective disclosure is the privacy default — fields not in metadata.request_fields are never returned, even if the credential carries them.
  - Default record retention is 5 years post-relationship per the EU AML package.
  - 200+ fraud signals are evaluated on every session, issued or presented, at no extra cost.

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/reusable-kyc/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.00
    初回検証ごとに発生, ユーザーがDidit KYCバンドルに料金を支払うのはこの時だけです。
  • Free
    すべての受け入れプラットフォームで。再利用、提示、選択的開示のたびに。
  • 0
    EU加盟国。Diditクレデンシャルは、Architecture Reference Frameworkに基づいて構築されたすべてのEUDIウォレットと相互運用可能です。
  • 0
    毎月、すべてのアカウントで無料検証が可能です。
3つのティア、1つの料金表

無料で開始。従量課金。エンタープライズまで対応。

毎月500回まで無料認証を永続的に提供。本番環境では従量課金。エンタープライズプランではカスタム契約、データレジデンシー、SLA（サービスレベルアグリーメント）に対応します。
無料

無料

月額$0。クレジットカード不要。

  • 無料KYCバンドル（本人確認 + パッシブ・ライブネス + 顔照合 + デバイス＆IP分析）, 毎月500回まで
  • ブロックリストユーザー
  • 重複検出
  • すべてのセッションで200以上の不正シグナル
  • Diditネットワーク全体でのKYC再利用
  • ケース管理プラットフォーム
  • ワークフロービルダー
  • 公開ドキュメント、サンドボックス、SDK、MCP (Model Context Protocol) サーバー
  • コミュニティサポート
無料で始める
最も人気
従量課金

従量課金

使った分だけお支払い。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 is eIDAS 2.0, in plain English?

eIDAS 2.0, short for electronic IDentification, Authentication and trust Services, is the EU's 2024 update to its identity rulebook. The headline change is the European Digital Identity Wallet (often shortened to EUDI Wallet): a smartphone app every EU citizen and resident will be entitled to by the end of 2026.

The wallet holds verifiable credentials, a digital driving licence, a verified-identity attestation, an academic diploma, issued by trusted parties and presented to relying parties with cryptographic proof, optionally with selective disclosure (prove you are over 18 without revealing your full date of birth).

For businesses, eIDAS 2.0 is about both accepting wallet-presented credentials and issuing the credentials your users carry.

Who has to support the EUDI Wallet, and when?

Mandatory acceptance is rolling in by sector:

  • Public services, every EU member state must offer wallet-based identification for tax filing, social security, voting registration by 2026
  • Very Large Online Platforms (VLOPs) under the Digital Services Act, must accept wallet credentials when an identity check is required
  • Banks and payment service providers, wallet acceptance built into the upcoming PSD3 / Payment Services Regulation
  • Telecoms operators, SIM registration, age-restricted services
  • Healthcare and academic credential issuers, voluntary at first, increasing pressure over the decade

Outside the mandatory list, every EU business has the option to issue and accept wallet credentials voluntarily, and most regulated businesses will, because the user experience is dramatically better than re-running a full KYC.

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.

How is reusable identity different from federated login (Sign in with Apple, Google)?

Federated login proves an account exists with the identity provider, the receiving business gets an email address and maybe a name. That is not regulatory-grade identity.

Reusable identity carries:

  • A government-document-grade verification (passport, national identity card scanned and OCR'd)
  • A biometric link to the human presenting the credential (selfie matched to the document portrait)
  • A liveness check that catches deepfakes, masks, replay attacks
  • An AML status screened against sanctions, PEP, and adverse-media lists
  • A signed attestation from a regulated provider, time-stamped, with a verifiable trail

The verifier gets the same regulatory comfort it would get from running its own KYC, without the cost, the friction, and the conversion drop.

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.

How is the privacy story under GDPR?

Reusable identity is a privacy upgrade on the legacy KYC stack:

  • Selective disclosure is built in, the verifier sees only the fields needed, not the underlying document
  • No central registry, the credential lives in the user's wallet, not on a Didit-owned ledger of who-presented-what-to-whom
  • Per-presentation consent, the user approves each disclosure explicitly
  • EU-resident storage, the issuer-side evidence pack stays in EU data centres; the wallet itself is on the user's device
  • Right to be forgotten, when a user revokes a credential, the receiving platform must drop it from its records under GDPR; Didit's per-platform revocation API makes this one call

The legal basis for processing on the receiving side is legitimate interest under GDPR, the user has explicitly presented a credential to access the service. Didit's standard Data Processing Agreement (DPA) covers the joint-controller relationship.

What if the user changes their identity document or moves country?

Three trigger types:

  • Document renewal (passport expires, new national identity card issued) → the user re-runs a lightweight refresh in the Didit app; the credential is reissued with the new document fingerprint
  • Material identity change (new legal name, gender marker change, country of residence change) → full re-verification at $0.33; the old credential is revoked and a new one issued
  • AML status change (a previously-clean user becomes a PEP or hits a sanctions list) → Didit's continuous monitoring flags the change automatically, the credential's AML field is updated, and every receiving platform sees the refreshed status on next presentation

The receiving platform never has to chase the user for updates, the credential carries its own freshness signal, and stale credentials are rejected at presentation time.

What evidence does a regulator see for a reused verification?

The verifier (the receiving platform) gets the same per-presentation evidence pack the original verifier got, plus the chain of issuance:

  • The original KYC evidence, document scan, biometric similarity, AML hits, device + IP risk signals, signed timestamps
  • The issuance chain, which Didit-powered platform issued the credential, when, on which workflow
  • The presentation log, when this user presented to your platform, which fields they disclosed, your verifier's verdict
  • The current AML status, refreshed daily by Didit's continuous monitoring
  • The HMAC SHA-256 signature on every field, so chain-of-custody is provable

Didit is the only KYC provider with a formal EU member-state government attestation, Spain's Treasury, Banco de España, and SEPBLAC jointly attested the service as safer than in-person verification. That attestation extends to every reused presentation.

Related

関連モジュール + ワークフロー

本人確認と不正対策のインフラ。

KYC、KYB、取引監視、ウォレットスクリーニングを一つのAPIで。5分で統合できます。

無料で始めるお問い合わせ
AIにこのページの要約を依頼する