Skip to main content
Didit, 신원·사기 방지 인프라 구축 위해 750만 달러 투자 유치
Didit
MiCA · 암호화폐 규정 준수

암호화폐 사용자를 온보딩하고, MiCA 규정을 준수하세요.

사용자를 인증하고, 지갑을 스크리닝하며, 증거를 한 번의 호출로 제출하세요. 건당 $0.33. 매월 500회 무료. EU 인증을 받은 심층 검증.

무료로 시작하기문서 읽기
지원
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

전 세계 2,000개 이상의 기관에서 신뢰합니다.

영화 같은 어두운 추상적인 규제 스택 일러스트레이션, 순수한 검은색 배경에 3D 원근법으로 쌓인 네 개의 떠 있는 반투명 유리 패널이 빛나는 Didit Blue 선으로 연결되어 있고 네 개의 빛나는 스캐너 브래킷으로 둘러싸여 있습니다. 각 패널에는 작은 연한 흰색 추상 모티프(12개 점 링, 스캔 라인, 점 행, 원)가 있습니다.

MiCA가 요구하는 것

사용자를 인증하고 지갑을 스크리닝하세요. 증거를 보관하세요.

모든 EU 암호화폐 플랫폼은 모든 고객에 대해 이 세 가지를 대규모로 수행해야 합니다. Didit은 이를 단일 워크플로우로 제공하며, 건당 $0.33, 매월 500건은 무료입니다.

작동 방식

회원가입부터 인증된 사용자까지, 네 단계로 완료됩니다.

  1. 단계 01

    워크플로우 생성

    원하는 검사 항목(ID, 라이브니스, 얼굴 매칭, 제재, 주소, 연령, 전화, 이메일, 맞춤 질문)을 선택하세요. 대시보드에서 플로우로 드래그하거나, 동일한 플로우를 API에 게시할 수 있습니다. 조건에 따라 분기하고 A/B 테스트를 실행하세요. 코딩은 필요 없습니다.

  2. 단계 02

    통합

    저희의 Web, iOS, Android, React Native, 또는 Flutter SDK를 사용하여 네이티브로 임베드하세요. 호스팅된 페이지로 리디렉션하거나, 이메일, SMS, WhatsApp 등 어디든 사용자에게 링크를 보내기만 하면 됩니다. 귀하의 스택에 맞는 방식을 선택하세요.

  3. 단계 03

    사용자 플로우 진행

    Didit은 카메라, 조명 큐, 모바일 핸드오프, 접근성을 호스팅합니다. 사용자가 플로우를 진행하는 동안, 저희는 200개 이상의 사기 신호를 실시간으로 점수화하고 모든 필드를 신뢰할 수 있는 데이터 소스와 대조하여 확인합니다. 2초 이내에 결과를 받아보세요.

  4. 단계 04

    결과 수신

    실시간 서명된 웹훅은 사용자가 승인, 거부 또는 검토로 전송되는 즉시 데이터베이스를 동기화합니다. 필요에 따라 API를 폴링하거나, 콘솔을 열어 모든 세션, 모든 신호를 검사하고 케이스를 직접 관리할 수 있습니다.

규제 준수를 위해 구축 · 인프라처럼 책정된 가격

6가지 검사. 하나의 번들. 사용자당 $0.33.

MiCA 온보딩은 단일 검사가 아니라 레시피입니다. 워크플로우별로 각 모듈을 토글하거나 직접 연결하세요.
문서 읽기API 키 받기
01 · KYC 번들

5가지 검증을 단 한 번의 호출로.

ID, 라이브니스, 얼굴 매칭, 기기 + IP, AML, 사용자당 $0.33로 번들 제공. iBeta 레벨 1 스푸핑 방지 인증, 2초 미만 결과.
ID 확인 모듈
02 · AML 스크리닝

1,300개 이상의 목록으로 모든 사용자를 심사합니다.

제재, PEP, 부정적 미디어, 매일 업데이트, 14개 언어 지원. 적발 시 자동으로 케이스가 열립니다. MiCA Article 60 감사 준비 완료.
AML 스크리닝 모듈
03 · 지갑 스크리닝

자금이 도착하기 전에 모든 예치금을 평가합니다.

제재된 지갑, 믹서, 도난 자금을 감지합니다. 검사당 $0.15, 또는 자체 제공자 키 사용 시 $0.02. EVM, Bitcoin, TRON, Solana 지원.
지갑 스크리닝 모듈
04 · 지속적인 모니터링

매일 모든 사용자를 재심사합니다.

제재 및 PEP 목록이 업데이트되면 승인된 사용자는 자동으로 재스크리닝됩니다. 새로운 적발 시 원본 증거가 한 번의 클릭으로 접근 가능한 케이스가 열립니다. 사용자당 연간 $0.07.
지속적인 AML 개요
05 · EU 증명

EU 정부가 인증한 유일한 KYC 플랫폼입니다.

스페인 재무부, 스페인 중앙은행, SEPBLAC은 Didit이 대면 확인보다 더 안전하다고 공동으로 증명했습니다. 보고서를 다운로드하여 MiCA Article 16 패키지와 함께 제출하세요.
보안 및 규제 준수
06 · 모든 암호화폐 플랫폼을 위해 구축

모든 유형에 동일한 워크플로를 적용합니다.

거래소, 온램프, 수탁 지갑, 토큰화 플랫폼, 결제 기관, 모두 동일한 MiCA 레시피를 실행합니다. 하나의 계약, 하나의 인보이스, 하나의 감사 패키지.
암호화폐 산업 워크플로우
통합

한 번의 호출. 한 번의 웹훅. 그 위에 모니터링.

한 번의 호출로 세션을 시작하세요. 웹훅에서 서명된 결과를 읽고, 승인된 사용자를 모니터링에 등록하세요.
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 === "Approved") {
  unlockDeposits(payload.vendor_data);
  enrollOngoingAml(payload.id_verification);
} else if (payload.status === "Declined") {
  logHits(payload.aml.hits);
  blockAndReview(payload.vendor_data);
}
200확인상태: 승인됨 · 거부됨 · 검토 중
페이로드를 읽기 전에 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 회원국 정부가 대면 인증보다 더 안전하다고 공식적으로 인정한 유일한 신원 확인 제공업체입니다.
보안 및 규정 준수 문서 읽기
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
    스페인 재무부, 스페인 중앙은행, SEPBLAC 등 EU 정부가 인정한 유일한 KYC 플랫폼입니다.
  • 0+
    모든 사용자에게 제재, 정치적 주요 인물(PEP), 부정적 미디어 목록을 스크리닝합니다.
  • <0s
    엔트리 레벨 Android 기기에서도 세션당 엔드투엔드 결과를 제공합니다.
  • 0
    모든 계정에서 매월 무료 인증을 제공합니다.
세 가지 티어, 하나의 가격표

무료로 시작하고, 사용량에 따라 지불하며, 엔터프라이즈로 확장하세요.

매월 500건의 무료 본인 확인을 영구적으로 제공합니다. 프로덕션 환경에서는 사용한 만큼만 지불하세요. 엔터프라이즈 고객에게는 맞춤형 계약, 데이터 상주 및 SLA(서비스 수준 협약)를 제공합니다.
무료

무료

월 $0. 신용카드 정보가 필요 없습니다.

  • 무료 KYC 번들 (신분증 확인 + 패시브 라이브니스 + 얼굴 매칭 + 기기 및 IP 분석), 매월 500건 제공
  • 차단된 사용자
  • 중복 감지
  • 모든 세션에서 200개 이상의 사기 신호 감지
  • Didit 네트워크 전반에 걸쳐 재사용 가능한 KYC
  • 사례 관리 플랫폼
  • 워크플로 빌더
  • 공개 문서, 샌드박스, SDK, MCP(Model Context Protocol) 서버
  • 커뮤니티 지원
무료로 시작하기
가장 인기
사용한 만큼 지불

사용량 기반 요금제

사용한 만큼만 지불하세요. 25개 이상의 모듈. 모듈별 공개 가격, 월 최소 요금 없음.

  • 전체 KYC $0.33 (신분증 + 생체 인식 + IP / 기기)
  • 10,000개 이상의 AML 데이터셋, 제재, PEP, 부정적 미디어
  • 데이터베이스 검증을 위한 1,000개 이상의 정부 데이터 소스
  • 거래당 $0.02의 거래 모니터링
  • 기업당 $2.00의 실시간 KYB
  • 검사당 $0.15의 지갑 스크리닝
  • 화이트 라벨 검증 플로우, 귀사의 브랜드, Didit의 인프라
전체 가격 목록 보기무료로 시작하기
엔터프라이즈

엔터프라이즈

맞춤형 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에게 이 페이지 요약 요청