Verify the user, screen the wallet, file the evidence, in one call. $0.33 per check. 500 free every month. EU-attested verification depth.
Trusted by 2,000+ organizations worldwide.
What MiCA demands
Every EU crypto platform has to do all three, on every customer, at scale. Didit ships them as one workflow at $0.33 per check, with 500 free every month.
Pick the checks you want, ID, liveness, face match, sanctions, address, age, phone, email, custom questions. Drag them into a flow in the dashboard, or post the same flow to our API. Branch on conditions, run A/B tests, no code required.
$ 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" }
}'{ "url": "verify.didit.me/..." }// 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);
}status Approved · Declined · In ReviewYou 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 — $0.02 monitoring + $0.15 wallet screen, or bring your own screening provider (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",
"decision": {
"id_verifications": [{ "node_id": "id_verification_1", "status": "Approved" }],
"liveness_checks": [{ "node_id": "liveness_1", "status": "Approved" }],
"face_matches": [
{ "node_id": "face_match_1", "status": "Approved", "similarity_score": 0.94 }
],
"ip_analyses": [{ "node_id": "ip_analysis_1", "status": "Approved" }],
"aml_screenings": [{ "node_id": "aml_1", "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.
For building, testing, and your first users.
25+ modules, publicly priced. Automatic volume discounts.
For large volumes and regulated programs.
Volume discounts apply automatically as usage grows — no negotiation, no sales call.
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:
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.
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:
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.
Any business offering one of the ten CASP services defined in Article 3(1)(15) to EU 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.
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.
Three regulations, three jobs, all of them apply to a CASP at once:
Didit covers all three in one workflow:
One contract, one invoice, one audit pack.
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.
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, 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.
Didit ships compliant by default for the regulators that matter to identity infrastructure:
Detailed memo, every certificate, every regulator letter: /security-compliance.
Three integration paths, pick whichever fits your stack:
Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.
Yes. Wallet Screening (Know-Your-Transaction) scores every deposit address before you credit the user.
Returns:
sanctioned, mixer, exchange-high-risk, stolen funds, darknet, ransomware, phishing, scamPricing:
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.
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:
GET /v3/session/... or bulk ZIP from the ConsoleWhen a user closes their account, evidence retention starts ticking from the off-boarding date, same model regulators expect from traditional financial institutions.
Yes, Didit is the only KYC provider with a formal EU member-state government attestation.
The Spanish Financial Sandbox, run jointly by:
…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:
Every certificate is reachable from /security-compliance and downloadable on demand.
One API for KYC, KYB, Transaction Monitoring, and Wallet Screening. Integrate in 5 minutes.