Skip to main content
Diditが750万ドルを調達、本人確認と不正対策のインフラを構築
Didit
MiCA · 暗号資産コンプライアンス

暗号資産ユーザーをオンボーディングし、MiCAに準拠しましょう。

ユーザー認証、ウォレットスクリーニング、証拠提出をワンコールで。1チェックあたり$0.33。毎月500回無料。EU認定の認証深度。

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

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

映画のようなダークな抽象的なコンプライアンススタックのイラスト。純粋な黒の背景に、Didit Blueの光る線が通り、4つの光るスキャナーブラケットで囲まれた、3Dパースペクティブで積み重ねられた4枚の半透明なガラスパネル。各パネルには、小さな薄い白の抽象的なモチーフ（12個の点リング、スキャンライン、点列、円）が描かれています。

MiCAが求めるもの

ユーザーを認証し、ウォレットをスクリーニング。証拠を保持します。

すべてのEU暗号プラットフォームは、すべての顧客に対して、大規模にこれら3つの要件をすべて満たす必要があります。 Diditは、これらを1つのワークフローとして提供し、1チェックあたり$0.33で、毎月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をポーリングすることも可能です。または、コンソールを開いてすべてのセッション、すべての信号を検査し、ケースを管理することもできます。

コンプライアンス対応 · インフラ並みの価格

6つのチェック。1つのバンドル。ユーザーあたり$0.33。

MiCAのオンボーディングは単一のチェックではなく、複数の要素の組み合わせです。ワークフローごとに各モジュールを切り替えるか、直接組み込むことができます。
ドキュメントを読むAPIキーを取得
01 · KYCバンドル

5つのチェックをワンコールで。

ID、ライブネス、顔認証、デバイス+IP、AMLをバンドルし、ユーザーあたり$0.33。iBetaレベル1のアンチスプーフィング認証済みで、2秒未満で結果が出ます。
ID認証モジュール
02 · AMLスクリーニング

1,300以上のリストと照合し、全ユーザーをスクリーニング。

制裁、PEP、ネガティブメディア情報を毎日更新し、14言語に対応。ヒットがあった場合は自動的にケースが作成されます。MiCA第60条の監査にも対応しています。
AMLスクリーニングモジュール
03 · ウォレットスクリーニング

入金前にすべてのデポジットをスコアリング。

制裁対象ウォレット、ミキサー、盗難資金を検出します。1チェックあたり$0.15、またはご自身のプロバイダーキーを使用する場合は$0.02です。EVM、Bitcoin、TRON、Solanaに対応しています。
ウォレットスクリーニングモジュール
04 · 継続的なモニタリング

全ユーザーを毎日再スクリーニング。

制裁リストとPEPリストが更新されると、承認済みユーザーは自動的に再スクリーニングされます。新たなヒットがあった場合、元の証拠にワンクリックでアクセスできるケースが作成されます。年間ユーザーあたり$0.07です。
継続的なAMLの概要
05 · EU認証

EU政府が認定した唯一のKYCプラットフォーム。

スペイン財務省、スペイン銀行、SEPBLACは、Diditが対面認証よりも安全であると共同で証明しました。レポートをダウンロードし、MiCA第16条の資料として提出してください。
セキュリティとコンプライアンス
06 · すべての暗号プラットフォーム向けに構築

あらゆるアーキタイプに共通のワークフロー。

取引所、オンランプ、カストディアルウォレット、トークン化プラットフォーム、決済機関など、すべて同じMiCA要件に対応します。契約、請求書、監査資料はすべて1つにまとめられます。
暗号業界のワークフロー
連携

1回の呼び出し。1つのWebhook。その上にモニタリング。

1回の呼び出しでセッションを開始します。Webhookから署名付きの判定結果を読み取ります。承認されたユーザーをモニタリングに登録します。
POST /v3/session/MiCA
$ 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_mica_user_verification",
    "vendor_data": "user-42",
    "metadata": { "purpose": "mica_onboarding" }
  }'
201作成済み{ "session_url": "verify.didit.me/..." }
署名付きウェブフックがstatus: Approvedを返すまで、入金をブロックします。ドキュメント →
POST /webhooks/didit判定
// X-Signature-V2 verified upstream
if (payload.status === "承認済み") {
  unlockDeposits(payload.vendor_data);
  enrollOngoingAml(payload.id_verification);
} else if (payload.status === "拒否済み") {
  logHits(payload.aml.hits);
  blockAndReview(payload.vendor_data);
}
200OKステータス: 承認済み · 拒否済み · レビュー中
ペイロードを読み取る前にX-Signature-V2を検証してください。ドキュメント →
エージェント対応統合

MiCAオンボーディングをプロンプト一つで実装。

Claude Code、Cursor、Codex、Devin、Aider、Replit Agentに貼り付けてください。スタック情報を入力すると、エージェントがワークフローを構築し、入金をゲートし、モニタリングを登録し、ウォレットの事前チェックを連携します。
didit-integration-prompt.md
You are integrating Didit's MiCA-aligned crypto user-verification workflow. MiCA is the EU's crypto rulebook; a regulated Crypto-Asset Service Provider (CASP) owes three things on every new customer:

  1. Customer Due Diligence (CDD) — verify identity, screen for sanctions, file the evidence.
  2. Ongoing monitoring — re-screen approved users as watchlists update.
  3. Wallet screening for any crypto outflow — score the destination address before the transfer.

Didit ships all three on one workflow:
  - KYC bundle at $0.33 per user (Sessions API)
  - Continuous AML monitoring at $0.07 per user per year (automatic on any session with AML enabled)
  - Wallet screening at $0.17 per crypto transaction managed, or $0.04 BYOK (Transactions API)
  - First 500 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 ID Verification + Passive Liveness + Face Match 1:1 + Device & IP Analysis + AML Screening.
  - Transaction Monitoring enabled in the Business Console (Transactions > Settings) with crypto screening on, if you handle crypto outflows.

STEP 1 — Verify the user with the Sessions API

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id with KYC + AML modules>",
      "vendor_data": "<your user id>",
      "callback": "https://<your-app>/casp/kyc/callback",
      "metadata": {
        "purpose": "mica_onboarding",
        "casp_reference": "<your internal reference>"
      }
    }

  Response: 201 Created with a hosted-flow URL. Redirect the user. Sub-2-second median verdict.

STEP 2 — Read the signed webhook on KYC 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",
      "id_verification": { "status": "Approved" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "ip_analysis": { "status": "Approved" },
      "aml": { "status": "Approved", "hits": [] }
    }

  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 3 — Continuous AML monitoring is automatic

  Every approved user is re-screened daily against the same 1,300+ sanctions, PEP, and adverse-media lists used at onboarding. There is NO separate endpoint to call.

  When a previously-clean user crosses a threshold, the session status updates to "In Review" or "Declined" and your webhook fires the same payload shape as the original onboarding event with the new AML hits. A case opens automatically in the Business Console.

STEP 4 — Wallet screening on crypto outflows (Transactions API)

  Required only if you transfer crypto on behalf of the user. Run BEFORE the crypto leaves.

  POST https://verification.didit.me/v3/transactions/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body (required fields verified live):
    {
      "transaction_id": "<your internal reference>",
      "transaction_category": "finance",
      "include_crypto_screening": true,
      "transaction_details": {
        "direction": "OUTBOUND",
        "amount": "0.25",
        "currency": "ETH",
        "currency_kind": "crypto",
        "action_type": "withdrawal"
      },
      "subject": {
        "entity_type": "individual",
        "vendor_data": "<your user id>",
        "full_name": "<user full name>"
      },
      "counterparty": {
        "entity_type": "unhosted_wallet",
        "full_name": "<destination wallet label>",
        "payment_method": {
          "method_type": "crypto_wallet",
          "account_id": "<destination wallet address>"
        }
      }
    }

  REQUIRED fields the API rejects if missing:
    - subject.vendor_data + subject.full_name
    - counterparty.full_name
    - transaction_details.direction + currency + currency_kind + amount
    - For crypto: wallet address on counterparty.payment_method.account_id (OUTBOUND) or subject.payment_method.account_id (INBOUND post-transfer)

  Wallet screening runs server-side when currency_kind = "crypto" and there is a wallet address in the right participant. No separate endpoint.

  Transaction status enum (exact case, UPPER_SNAKE_CASE): APPROVED | IN_REVIEW | DECLINED | AWAITING_USER.
  When a transaction enters AWAITING_USER, Didit creates a linked remediation session automatically and returns a verification URL on the response.

  Branch logic:
    APPROVED       → ship the crypto.
    IN_REVIEW      → hold, route to analyst queue.
    DECLINED       → block, refund, log.
    AWAITING_USER  → redirect the user to the remediation session URL.

WEBHOOK EVENT NAMES
  - Sessions: status changes flow through the standard session webhook.
  - Transactions: transaction.created · transaction.updated · transaction.status.changed · transaction.alert.generated.

  Verify X-Signature-V2 on every payload.

EVIDENCE + RECORD RETENTION
  Every approved user comes with a signed evidence pack (document, biometric match, AML hits, device + IP) stored in the EU. Default retention 5 years post-relationship; configurable per workflow.

  Didit holds the only formal EU-government attestation for a KYC platform — issued jointly by Spain's Tesoro, Banco de España, and SEPBLAC. The report files directly into the MiCA evidence pack.

CONSTRAINTS
  - Session statuses use Title Case With Spaces (Approved, In Review). Transaction statuses use UPPER_SNAKE_CASE (APPROVED, IN_REVIEW). Don't mix them in the same code path.
  - Default record retention is 5 years post-relationship; extend per your supervisor's guidance.
  - 200+ fraud signals are evaluated on every KYC session at no extra cost — surface the score via the session decision payload.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/core-technology/aml-screening/overview
  - https://docs.didit.me/transaction-monitoring/aml-screening
  - 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準拠

実績データ

実績データ
  • EU-attested
    EU政府（スペイン財務省、スペイン銀行、SEPBLAC）によって承認された唯一のKYCプラットフォームです。
  • 0+
    すべてのユーザーに対し、制裁、政治的要人（PEP）、およびネガティブメディアリストをスクリーニングします。
  • <0s
    エントリーレベルのAndroid端末で、セッションごとのエンドツーエンドの結果を提供します。
  • 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 MiCA, in one sentence?

MiCA, Regulation (EU) 2023/1114, the Markets in Crypto-Assets Regulation, is the European Union's first uniform rulebook for crypto-asset issuance, public offerings, admission to trading, and the services around them. It replaces 27 different national Virtual Asset Service Provider (VASP) regimes with one harmonised licence valid across the entire EU single market.

Supervision is layered:

  • Each member state's National Competent Authority (NCA) issues the licence and runs day-to-day supervision
  • The European Securities and Markets Authority (ESMA) publishes Level 2/3 standards and supervises significant CASPs
  • The European Banking Authority (EBA) supervises significant stablecoin issuers and writes Anti-Money Laundering (AML) guidance

Didit ships every piece a Crypto-Asset Service Provider (CASP) needs to satisfy MiCA's customer-due-diligence, ongoing-monitoring, and evidence-retention duties, one workflow, $0.33 per user, 500 verifications free every month, integrate in 5 minutes.

Which crypto businesses are in scope?

Any business offering one of the ten CASP services defined in Article 3(1)(15) to EU clients:

  • Custody and administration of crypto-assets on behalf of clients
  • Operation of a trading platform for crypto-assets
  • Exchange of crypto-assets for funds (on/off-ramp)
  • Exchange of crypto-assets for other crypto-assets
  • Execution of orders for crypto-assets on behalf of clients
  • Placing of crypto-assets
  • Reception and transmission of orders
  • Advice on crypto-assets
  • Portfolio management of crypto-assets
  • Transfer services for crypto-assets on behalf of clients

In practice that captures centralised exchanges, on/off-ramps, custodial wallets, brokers, OTC desks, advisory services, payment institutions handling crypto, and tokenisation platforms. Truly decentralised protocols with no identifiable operator and pure peer-to-peer transfers sit outside the regime.

Didit customers across the MiCA perimeter: AhoraCrypto (Bank-of-Spain-registered on/off-ramp), GBTC Finance (exchange + 20+ physical stores), TucanPay (EU↔LatAm payments), Agape Smart Money (international money transfers in 30+ countries). Same workflow, same /v3/ API, different deposit + trade flows downstream.

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 MiCA different from 6AMLD and the EU Travel Rule?

Three regulations, three jobs, all of them apply to a CASP at once:

  • MiCA, Regulation (EU) 2023/1114. Conduct regulation. Licenses the crypto business; sets capital, governance, custody, market-abuse, and disclosure duties.
  • The EU AML package, Directive (EU) 2018/1673 (AMLD6) + the new Anti-Money-Laundering Regulation (EU) 2024/1624 + the new AMLA Regulation (EU) 2024/1620. Anti-money-laundering / counter-terrorist-financing. Sets Customer Due Diligence (CDD), Politically Exposed Persons (PEP) checks, sanctions screening, Suspicious Activity Reports (SARs), ongoing monitoring.
  • The TFR, Regulation (EU) 2023/1113. The Travel Rule for crypto. The EU's implementation of Financial Action Task Force (FATF) Recommendation 16, originator + beneficiary data must travel with every crypto transfer.

Didit covers all three in one workflow:

  • Conduct (MiCA): evidence pack, Article 60 CDD, EU-resident storage, attestation
  • AML / 6AMLD: AML Screening against 1,300+ sanctions / PEP / adverse-media lists, Ongoing Monitoring at $0.07 per user per year, signed webhooks for new hits
  • Travel Rule (TFR): IVMS-101 payloads, TRP / Sumsub TR / Notabene / Veriscope interop

One contract, one invoice, one audit pack.

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.

Does it screen incoming deposit wallets too?

Yes. Wallet Screening (Know-Your-Transaction) scores every deposit address before you credit the user.

Returns:

  • 0-100 risk score + categorical labels: sanctioned, mixer, exchange-high-risk, stolen funds, darknet, ransomware, phishing, scam
  • Counterparty cluster + attribution to the upstream entity where known
  • Daily delta refresh against the underlying provider feeds

Pricing:

  • $0.15 per check on the managed flow (Didit handles the underlying on-chain-analytics contract for you)
  • $0.02 per check when you Bring Your Own Key (BYOK) from your existing on-chain-analytics provider, Didit becomes the routing + normalisation layer over the API key you already paid for

Chain coverage: Ethereum + EVM-compatible chains (Polygon, BNB, Arbitrum, Optimism, Base), Bitcoin, TRON, Solana, plus the major Layer 2s. New chains added as provider coverage expands.

Hits route into the same Case Management surface as AML hits, one queue, one reviewer workflow, one audit trail.

What records do I need to keep, and for how long?

MiCA Article 67-68, CASPs must retain records of services, activities, orders, and transactions for at least 5 years (extendable to 7 on competent-authority request).

The EU AML package, CDD records must be retained for 5 years after the end of the business relationship, with member-state discretion to extend up to 10 years.

The TFR, Travel Rule data must travel with the transfer and be retained per the same AML retention timeline.

Didit's retention model:

  • All evidence stored in the European Union, regulated EU data centres, no cross-border transfer for EU customers
  • Signed + timestamped, every payload carries an HMAC signature so chain-of-custody is provable for an examiner
  • Retained indefinitely while your subscription is active, no per-record retention bill, no expiry surprises
  • Configurable per workflow if your NCA mandates a specific duration (e.g. extend to 10 years for high-risk client categories)
  • Export anytime via GET /v3/session/... or bulk ZIP from the Console

When a user closes their account, evidence retention starts ticking from the off-boarding date, same model regulators expect from traditional financial institutions.

Is there an attestation I can show our MiCA examiner?

Yes, Didit is the only KYC provider with a formal EU member-state government attestation.

The Spanish Financial Sandbox, run jointly by:

  • Tesoro (the Spanish Treasury)
  • Banco de España (the Spanish central bank)
  • SEPBLAC (Servicio Ejecutivo de la Comisión de Prevención del Blanqueo de Capitales, Spain's Financial Intelligence Unit)

…jointly attested Didit's NFC + active-biometric verification as safer than in-person verification. The report is downloadable from your Business Console and slots directly into your MiCA Article 16 (CASP authorisation) and Article 60 (CASP conduct) packs.

Additional third-party certifications kept current:

  • ISO/IEC 27001, Information Security Management System
  • SOC 2 Type 1, service-organisation controls
  • iBeta Level 1 PAD, Presentation Attack Detection (the standard for face-liveness anti-spoof)
  • finReg360 EBA memo, independent legal review against the EBA's MiCA guidelines

Every certificate is reachable from /security-compliance and downloadable on demand.

Related

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

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

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

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