Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Crypto · Sheria ya Safari

Mwanzilishi na mnufaika, kwa kila uhamisho.

Didit hubadilishana data ya Sheria ya Safari na kuchunguza pochi ya mpinzani kwenye simu moja ya /v3/ transaction. IVMS-101 payloads, $0.17 kwa uhamisho unaosimamiwa, uthibitishaji 500 bila malipo kila mwezi.

Inaungwa mkono na
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Inaaminika na mashirika 2,000+ duniani kote.

Mchoro wa kufuata sheria wa giza, wa kufikirika, paneli nne zinazoelea, zisizo na uwazi za kioo cheusi katika mtazamo wa 3D kwenye turubai nyeusi kabisa, zikipitishwa na mstari wima wa Didit Blue unaong'aa na kuwekewa fremu na mabano manne ya skana yanayong'aa. Kila paneli hubeba motifu ndogo nyeupe isiyo dhahiri (mishale miwili, bahasha ya ujumbe, kukabidhiana kwa watu wawili, njia ya uhamisho) inayowakilisha ubadilishanaji wa data ya mwanzilishi na mnufaika.

Sheria ya Safari inadai nini

Tuma utambulisho. Kagua wallet. Simu moja.

Kila VASP inayodhibitiwa inadaiwa nusu zote mbili kwenye kila uhamisho, pakiti ya IVMS-101 kwa VASP mpinzani, uchunguzi wa hatari wa mnyororo kwa yenyewe. Didit huwasilisha kama simu moja ya API ya Miamala: $0.17 inayosimamiwa, $0.04 na Bring Your Own Key kwenye mtoa huduma wa pochi. Uthibitishaji 500 bila malipo kila mwezi.

Jinsi inavyofanya kazi

Kuanzia kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

    Chagua ukaguzi unaotaka, kitambulisho, uhai, kulinganisha uso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna msimbo unaohitajika.

  2. Hatua 02

    Unganisha

    Pachika asili na SDK yetu ya Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu mtumiaji wako kiungo, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.

  3. Hatua 03

    Mtumiaji anapitia mtiririko

    Didit huandaa kamera, ishara za mwanga, kukabidhiana kwa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapima ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya kuaminika. Matokeo chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizotiwa saini kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Uliza API inapohitajika. Au fungua console kukagua kila kikao, kila ishara, na kudhibiti kesi kwa njia yako.

Imejengwa kwa Sheria ya Safari · Bei kama miundombinu

Simu moja. Pakiti ya IVMS-101 + uchunguzi wa pochi. $0.17.

Uhamisho wa crypto unaodhibitiwa sio ukaguzi mmoja, ni mapishi. Washa kila moduli kwa kila mtiririko wa kazi, badilisha mtoa huduma wako wa uchunguzi wa pochi kupitia Bring Your Own Key ili kushuka hadi $0.04 kwa kila uhamisho.
01 · IVMS-101 payload

Pakiti moja ya IVMS-101 kwa kila uhamisho.

Sehemu za mwanzilishi na mnufaika zimejazwa kutoka KYC iliyothibitishwa. Zimepangwa kiotomatiki kwa InterVASP Messaging Standard 101, schema ambayo kila itifaki kuu ya Travel Rule inasoma.
Transactions API
02 · Vizingiti vya kila mamlaka

Viwango vinavyolingana na mamlaka yako.

EU TFR (hakuna kiwango cha chini), US FinCEN ($3,000), UK FCA (£1,000), MAS (SGD 1,500), FINMA (CHF 1,000), VARA (AED 3,500). Mtiririko mmoja wa kazi kwa kila mamlaka; badilisha kupitia metadata ya kipindi.
Mtiririko wa kazi wa sekta ya crypto
03 · Utangamano wa itifaki

Kila itifaki ya Travel Rule. Mkataba mmoja.

TRP, Sumsub Travel Rule, Notabene, Veriscope, OpenVASP, Shyft, zote zinafikiwa kupitia payload ileile ya IVMS-101. Chagua mtandao mmoja au kubali yote; mkataba mmoja, ankara moja.
Workflow Orchestrator
04 · Mtiririko wa pochi inayojihifadhi

Lengo linalojihifadhi? Bado limefunikwa.

Hakuna VASP mshirika wa kubadilishana naye, Didit inakusanya utambulisho wa mnufaika kutoka kwa mtumiaji, inafanya changamoto za uthibitisho wa udhibiti juu ya viwango vya EU vya ukaguzi wa kina, inachunguza pochi lengwa, inahifadhi rekodi ya muundo wa IVMS.
Maswali Maalum
05 · Skrini ya pochi pamoja na sheria

Travel Rule + skrini ya pochi. Simu ileile.

$0.02 msingi wa ufuatiliaji wa miamala + $0.15 usimamizi wa Wallet Screening = $0.17 kwa kila uhamisho. Ukiwa na Bring Your Own Key kwa mtoa huduma wa pochi, skrini ya pochi inashuka hadi $0.02, jumla ya $0.04.
Moduli ya Wallet Screening
06 · Kifurushi cha ushahidi kwa kila uhamisho

Kifurushi kimoja kwa kila uhamisho. Inaingia kwenye ukaguzi.

Payload ya IVMS-101, uamuzi wa skrini ya pochi, sifa ya VASP mshirika, mihuri ya muda ya HMAC iliyosainiwa. Imehifadhiwa EU. Inahifadhiwa miaka 5 kwa chaguo-msingi; inaweza kupanuliwa kulingana na mwongozo wa msimamizi.
Usalama na Uzingatiaji
Unganisha

Kikao kimoja. Muamala mmoja. Webhook moja.

Thibitisha mtumiaji mara moja. Tuma kila uhamisho na sehemu za IVMS + pochi ya mpinzani. Soma uamuzi uliotiwa saini. Toa crypto.
POST /v3/session/KYC
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_casp_onboard",
    "vendor_data": "user-42"
  }'
201Imeundwahali Imeidhinishwa · Inapitiwa · Imekataliwa
Sehemu za mwanzilishi kwa kila uhamisho zinatokana na uamuzi huu uliosainiwa.nyaraka →
POST /v3/transactions/IVMS + KYT
$ curl -X POST https://verification.didit.me/v3/transactions/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "transaction_id": "tx-9001",
    "transaction_details": { "direction": "OUTBOUND", "currency_kind": "crypto" },
    "subject": { "full_name": "J. Pérez" },
    "counterparty": { "full_name": "R. Beneficiary", "payment_method": { "account_id": "bc1qa3…hk22" }}
  }'
201Imeundwahali IMEIDHINISHWA · INAPITIWA · IMEKATALIWA · INAMSUBIRI_MTUMIAJI
Pakiti ya IVMS-101 + ukaguzi wa wallet unaendeshwa upande wa server. Hakuna simu ya pili.nyaraka →
Ujumuishaji tayari kwa agent

Tengeneza mfumo wa Travel Rule kwa amri moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent itajenga workflow, itajaza sehemu za IVMS kutoka kwenye session ya KYC, itaendesha wallet screen, na kuunganisha webhook.
didit-integration-prompt.md
You are integrating Didit into a Virtual Asset Service Provider (VASP) / Crypto-Asset Service Provider (CASP) to satisfy the Travel Rule on every crypto transfer. Two obligations:

  1. Verify the user (KYC) — identity, liveness, face match, device + IP, AML. The originator data on every outbound transfer comes from this verified profile.
  2. Submit each transfer with originator + beneficiary fields (IVMS-101) AND screen the counterparty wallet — one /v3/transactions/ call.

Bundle pricing (verified live 2026-05-16):
  - User Verification (KYC) bundle: $0.33 per user (Sessions API)
  - Transactions API call: $0.02 base + $0.15 managed wallet screen = $0.17 per managed transfer
  - With Bring Your Own Key (BYOK) on the wallet provider: $0.04 per transfer ($0.02 + $0.02)
  - 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.
  - Transaction Monitoring + Wallet Screening enabled in the Business Console (Transactions > Settings).

STEP 1 — Verify the user with the Sessions API (one-time onboarding)

  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/onboard/callback",
      "metadata": {
        "purpose": "casp_onboarding"
      }
    }

  Response: 201 Created with the hosted session URL. Sub-2-second median verdict on completion.

STEP 2 — Read the signed webhook on KYC completion

  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.

  Capture the user's full name, date of birth, address, and any registered identity-document number from the decision payload. These fields populate the IVMS-101 originator block on every subsequent transfer.

STEP 3 — Submit every transfer with IVMS-101 + wallet screen in one call

  POST https://verification.didit.me/v3/transactions/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body (required fields verified live 2026-05-16):
    {
      "transaction_id": "<your internal transfer reference>",
      "transaction_category": "finance",
      "include_crypto_screening": true,
      "transaction_details": {
        "direction": "OUTBOUND",
        "amount": "0.45",
        "currency": "ETH",
        "currency_kind": "crypto",
        "action_type": "transfer"
      },
      "subject": {
        "entity_type": "individual",
        "vendor_data": "<your user id>",
        "full_name": "<originator name from KYC>",
        "address": "<originator address from KYC>",
        "dob": "<originator dob from KYC, YYYY-MM-DD>"
      },
      "counterparty": {
        "entity_type": "individual",
        "full_name": "<beneficiary name>",
        "address": "<beneficiary address if known>",
        "payment_method": {
          "method_type": "crypto_wallet",
          "account_id": "<counterparty 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
    - counterparty.payment_method.account_id (the wallet address)

  Didit packages the subject + counterparty fields into an IVMS-101 payload, hands them off to the connected Travel Rule protocol (TRP / Sumsub TR / Notabene / Veriscope), runs Wallet Screening on the counterparty address server-side, and returns one verdict.

  Response shape (excerpted from a real successful 201):
    {
      "uuid": "<server transaction uuid>",
      "txn_id": "<your transaction_id echoed back>",
      "status": "APPROVED",
      "score": 0,
      "severity": null,
      "travel_rule": { "status": "EXCHANGED", "protocol": "<network>", "ivms_packet_id": "<id>" },
      "props": {
        "wallet_risk_score": 0,
        "sanctions_hit": false,
        "aml_provider": "<provider slug>",
        "aml_screening_type": "WALLET_SCREENING",
        "aml_screening_status": "COMPLETED"
      },
      "cost_breakdown": {
        "total_price": 0.17,
        "items": [
          { "usage_type": "transaction_aml_monitoring", "price": 0.15 },
          { "usage_type": "transaction_monitoring", "price": 0.02 }
        ]
      }
    }

  Transaction status enum (exact case, UPPER_SNAKE_CASE): APPROVED | IN_REVIEW | DECLINED | AWAITING_USER.
  Wallet-screen severity (UPPER): LOW | MEDIUM | HIGH | CRITICAL | UNKNOWN.

  Branch logic:
    APPROVED       → release the crypto.
    IN_REVIEW      → hold the transfer, route to analyst queue.
    DECLINED       → refuse the transfer, log the IVMS attempt for the audit.
    AWAITING_USER  → redirect the user to the remediation URL on the response.

STEP 4 — Inbound transfers: ingest the counterparty's IVMS packet

  When you RECEIVE a transfer from another VASP:
    - The connected Travel Rule protocol delivers the originator IVMS data to you BEFORE the on-chain transfer settles.
    - Submit it via the same POST /v3/transactions/ with direction: "INBOUND" and the originator fields on subject and your own beneficiary on counterparty.
    - Wallet Screening runs on the originator wallet (subject.payment_method.account_id).
    - Verdict drives whether to credit the user.

STEP 5 — Self-hosted (unhosted) wallet transfers

  For transfers TO a self-hosted wallet (no counterparty VASP to exchange with):
    - Collect the beneficiary identity from the user via a custom questionnaire ($0.10).
    - Above local enhanced-due-diligence thresholds, prompt the user to sign a short message with the beneficiary wallet's private key as proof of control.
    - Submit the transaction with the captured beneficiary fields + wallet address.
    - Didit still runs Wallet Screening on the destination and stores the IVMS-format record for the audit.

STEP 6 — Continuous AML on the user is automatic

  Every approved user is re-screened daily against 1,300+ sanctions, PEP, and adverse-media lists. There is NO separate endpoint to call. When a previously-clean user crosses an AML threshold, the session status updates and a signed webhook fires.

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.

CONSTRAINTS
  - Session statuses Title Case With Spaces; transaction statuses UPPER_SNAKE_CASE. Don't mix.
  - EU Transfer of Funds Regulation has NO de minimis threshold for crypto — every transfer carries originator + beneficiary data.
  - US Travel Rule kicks in at $3,000; UK at £1,000; Singapore at SGD 1,500; Switzerland at CHF 1,000. Apply per-workflow.
  - Default record retention is 5 years post-transfer per most AML regimes; extensible per supervisor guidance.
  - Wallet Screening MUST run BEFORE the crypto leaves — a post-transfer screen is useful for audit but useless for blocking.

Read the docs:
  - https://docs.didit.me/transaction-monitoring/overview
  - https://docs.didit.me/transaction-monitoring/transactions
  - https://docs.didit.me/transaction-monitoring/aml-screening
  - https://docs.didit.me/sessions-api/create-session
  - 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.
Unahitaji maelezo zaidi? Tazama nyaraka kamili za moduli.docs.didit.me →
Inatii kwa muundo

Fungua nchi mpya kwa kubofya mara moja. Tunafanya kazi ngumu.

Tunafungua kampuni tanzu za ndani, tunapata leseni, tunafanya majaribio ya kupenya, tunapata vyeti, na tunalingana na kila kanuni mpya. Ili kusafirisha uthibitishaji katika nchi mpya, geuza swichi. Nchi 220+ ziko hewani, zinakaguliwa na kupimwa kila robo mwaka, mtoa huduma pekee wa utambulisho ambaye serikali ya nchi mwanachama wa EU imemwita rasmi kuwa salama zaidi kuliko uthibitishaji wa ana kwa ana.
Soma faili ya usalama na utiifu
EU financial sandbox
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
Usalama wa habari · 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-aligned kwa muundo

Namba za uthibitisho

Namba za uthibitisho
  • $0.00
    Kwa kila uhamisho unaosimamiwa, Transaction Monitoring base + Wallet Screening.
  • 0+
    Vikwazo, Watu Walio Wazi Kisiasa (PEP), na orodha za habari hasi huchunguzwa kwa kila mtumiaji.
  • 0+
    Itifaki za Travel Rule zinazoweza kufanya kazi pamoja kwenye IVMS-101 payload moja, TRP, Sumsub TR, Notabene, Veriscope, OpenVASP, Shyft.
  • 0
    Uthibitishaji wa bure kila mwezi, kwenye kila akaunti.
Ngazi tatu, orodha moja ya bei

Anza bure. Lipa kulingana na matumizi. Panua hadi Enterprise.

Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, uhifadhi wa data, na SLA (Service Level Agreements) kwenye Enterprise.
Bure

Bure

$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.

  • Kifurushi cha bure cha KYC (Uthibitishaji wa Kitambulisho + Passive Liveness + Face Match + Uchambuzi wa Kifaa & IP), 500 / mwezi, kila mwezi
  • Watumiaji Waliozuiwa
  • Utambuzi wa Marudio
  • Ishara 200+ za udanganyifu kwenye kila session
  • KYC inayoweza kutumika tena kwenye mtandao wa Didit
  • Jukwaa la Usimamizi wa Kesi
  • Workflow Builder
  • Nyaraka za umma, sandbox, SDKs, server ya MCP (Model Context Protocol)
  • Usaidizi wa jamii
Maarufu zaidi
Lipa kulingana na matumizi

Kulingana na Matumizi

Lipa tu kwa unachotumia. Moduli 25+. Bei za umma kwa kila moduli, hakuna ada ya chini ya kila mwezi.

  • KYC kamili kwa $0.33 (Kitambulisho + Biometric + IP / Kifaa)
  • Data za AML 10,000+, vikwazo, PEPs, habari hasi
  • Vyanzo vya data vya serikali 1,000+ kwa Uthibitishaji wa Database
  • Ufuatiliaji wa Miamala kwa $0.02 kwa kila muamala
  • KYB ya moja kwa moja kwa $2.00 kwa kila biashara
  • Uchunguzi wa Wallet kwa $0.15 kwa kila ukaguzi
  • Mtiririko wa uthibitishaji wa Whitelabel, brand yako, miundombinu yetu
Biashara Kubwa

Biashara Kubwa

MSA & SLA maalum. Kwa idadi kubwa na programu zilizodhibitiwa.

  • Mikataba ya kila mwaka
  • MSA, DPA, na SLA maalum
  • Kituo maalum cha Slack na WhatsApp
  • Wakaguzi wa mikono wanapohitajika
  • Masharti ya muuzaji na white-label
  • Vipengele vya kipekee na ushirikiano wa washirika
  • CSM aliyetajwa, ukaguzi wa usalama, usaidizi wa kufuata

Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.

FAQ

Maswali ya kawaida

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 the Travel Rule, in plain English?

The Travel Rule says that when value moves between two regulated providers, certain pieces of customer information, name, account number, address, must travel alongside the value itself.

It started in traditional finance (the US Bank Secrecy Act of 1970), was extended globally by the Financial Action Task Force (FATF) in 2019, and now applies to crypto everywhere. The standard payload format is InterVASP Messaging Standard 101 (IVMS-101), a JSON schema every major Travel Rule protocol speaks.

The regulator's goal is simple: stop bad actors from laundering proceeds anonymously through chains of providers by ensuring identity data follows the value at every hop.

Who has to comply, and from when?

Every regulated Virtual Asset Service Provider (VASP) or Crypto-Asset Service Provider (CASP), exchanges, on/off-ramps, custodial wallets, brokers, OTC desks, payment institutions that touch crypto settlement.

Live jurisdictions:

  • European Union, the Transfer of Funds Regulation took full effect 30 December 2024 alongside MiCA. Applies to every CASP licensed in the EU.
  • United States, the FinCEN Travel Rule has been live since 1996 in traditional finance; FinCEN's 2019 guidance extended it to crypto and lowered thresholds.
  • United Kingdom, the FCA's cryptoasset rules came into force in September 2023.
  • Singapore, Switzerland, UAE, Brazil, Japan, South Korea, all live, each with a slightly different threshold and message format.

FATF runs mutual evaluations of each country's implementation. Non-compliant jurisdictions risk grey-list designation.

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 data has to travel, and how does it move?

The minimum FATF dataset is:

  • Originator, full name, account/wallet, physical address OR national identity number OR date and place of birth
  • Beneficiary, full name, account/wallet, physical address (jurisdiction-dependent)
  • The transfer itself, amount, asset, timestamp

The data moves through a Travel Rule protocol between the two providers, not on-chain, not in the transaction memo. Today's market is fragmented: providers pick one or more of TRP, Sumsub Travel Rule, Notabene, Veriscope, OpenVASP, and Shyft. The shared language is IVMS-101, which every protocol reads and writes.

The receiver of the transfer verifies the data before crediting the beneficiary's account.

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 missing or mismatched data handled?

Real life rarely produces clean Travel Rule packets, counterparties send partial data, fields don't match the KYC name, address formats differ. Two paths:

  • Material missing data (no originator name, no counterparty wallet) → the transaction returns DECLINED and the user is prompted to resubmit
  • Partial mismatch (slightly different name spelling, missing middle name) → the transaction returns IN_REVIEW and a case opens in the Business Console with the diff highlighted
  • Enhanced due diligence required (high-value transfer, high-risk geography) → the transaction returns AWAITING_USER and Didit creates a remediation session automatically, returning a verification URL on the response

Your compliance team triages the case, requests more data if needed, and approves or rejects from inside the Console. Reviewer notes, decision, and timestamps are recorded for the audit pack.

What does ongoing monitoring look like under the Travel Rule?

Travel Rule data is collected per transfer, not per relationship, there is no "refresh" of a Travel Rule packet. But the users behind the transfers must be monitored continuously under the EU AML package and equivalent regimes.

Didit runs:

  • Continuous AML monitoring on every verified user, automatic daily re-screen against 1,300+ sanctions, PEP, and adverse-media lists, $0.07 per user per year on heavy-volume accounts
  • Transaction Monitoring rule engine on every transfer, velocity, amount, geography, counterparty wallet category, structuring patterns
  • Wallet Screening refresh on persistent counterparty addresses, if a previously-clean wallet later becomes sanctioned, the system surfaces it

All three feed the same Case Management surface, so a single reviewer sees the full picture per user.

What records do I need to keep, and where?

Most regulators require at least 5 years of records on every Travel Rule transfer and the underlying user identity, sometimes longer if your supervisor requests it.

Didit's retention model:

  • All evidence stored in the European Union, regulated EU data centres, no cross-border transfer for EU customers
  • Per-transfer record, full IVMS-101 payload, wallet-screen result, verdict, signed HMAC timestamps
  • Per-user record, KYC evidence (document, biometric, AML, device + IP), updates over the relationship
  • Retained indefinitely while your subscription is active, no per-record retention bill
  • Configurable per workflow if your supervisor mandates a specific duration (the AML package allows extension up to 10 years on high-risk relationships)
  • Export anytime via the Business Console or the API

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. The report files directly into your CASP authorisation pack.

Miundombinu ya utambulisho na udanganyifu.

API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.

Uliza AI ifupishe ukurasa huu