Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
KYC Inayoweza Kutumika Tena ya B2B

Shiriki utambulisho uliothibitishwa na washirika wako.
Server-to-server.

Thibitisha mtumiaji au biashara mara moja. Shiriki matokeo na mshirika, wanamuingiza mtu huyo huyo papo hapo. Hakuna mchakato wa pili, hakuna selfie ya pili. Inafanya kazi kwa KYC na KYB. Imeundwa kwa ajili ya Banking-as-a-Service, makundi ya chapa nyingi, fedha zilizopachikwa, na masoko yenye majukwaa madogo.

Anza bureSoma nyaraka
Inaungwa mkono na
Y CombinatorRobinhood Ventures
Didit B2B Reusable KYC, kushiriki KYC ya mshirika server-to-server kupitia tokeni ya kushiriki ya muda mfupi.

Imeundwa kwa ajili ya mifumo ikolojia ya washirika

Thibitisha mara moja.
Ingiza kwenye kila mshirika.

Mtumiaji wako anathibitisha mara moja kwenye programu yako. Mshirika wako, mfadhili wako wa BaaS, chapa dada yako, soko lako la chini, anahitaji rekodi hiyo hiyo. Mtumie tokeni ya kushiriki ya mara moja. Anaipokea na kuingiza uthibitisho kamili. Mtumiaji haoni mchakato wa pili kamwe.

Jinsi inavyofanya kazi

Kutoka programu yako hadi kwa mshirika wako kwa hatua nne.

  1. Hatua 01

    Chagua kipindi kilichothibitishwa

    Chagua uthibitisho wowote uliomalizika, uliokubaliwa, uliokataliwa, au unaopitiwa, na uombe Didit tokeni ya kushiriki. Tokeni huisha muda wake baada ya saa moja kwa chaguo-msingi; unaweza kuongeza muda wake kutoka dakika moja hadi siku nzima.

  2. Hatua 02

    Tuma tokeni kwa mshirika wako

    Mpe mshirika wako tokeni kupitia backend yako mwenyewe, webhook, foleni, REST call. Tokeni inafanya kazi tu kwa mshirika uliyemtaja ulipoitengeneza. Hakuna mwingine anayeweza kuipokea.

  3. Hatua 03

    Mshirika wako anaingiza rekodi

    Mshirika wako anapokea tokeni na kuchagua jinsi ya kumuingiza mtumiaji, amini uamuzi wako na ukubali papo hapo, au ingiza data ghafi na uache timu yao ya kufuata sheria ifanye uamuzi.

  4. Hatua 04

    Kipindi kamili kinaingia kwenye programu yao

    Didit inakili rekodi nzima, nyaraka, selfie, kulinganisha uso, AML, data ya rejista, UBOs, kwenye nafasi ya kazi ya mshirika wako. Sura sawa na uthibitisho mpya, na rekodi safi ya ukaguzi kurudi kwenye asili.

Imeundwa kwa BaaS · fedha zilizopachikwa · makundi ya chapa nyingi

Uthibitisho mmoja. Kila jukwaa la mshirika.

Tengeneza tokeni. Itume. Iingize. Chagua kasi ya kuingiza. Sehemu sita zinazohamia zinashughulikia kila aina ya mfumo ikolojia wa washirika, wito sawa kwa KYC na KYB.
Soma nyarakaPata API key
01 · Tengeneza tokeni ya kushiriki

Tengeneza tokeni ya mara moja kwa mshirika wako.

Chagua uthibitisho uliomalizika na uombe Didit tokeni iliyoelekezwa kwa mshirika mmoja. Muda wa maisha chaguomsingi ni saa moja; unaweza kuongeza muda wake kutoka dakika moja hadi siku nzima. Tokeni inafanya kazi tu kwa mshirika uliyemtaja, hakuna mwingine anayeweza kuipokea kamwe.
Shiriki API ya Kipindi
02 · Ingiza kipindi

Mshirika wako anavuta rekodi kamili.

Mshirika wako anapokea tokeni na Didit inakili uthibitisho mzima kwenye nafasi yao ya kazi, kipindi kipya, data sawa, rekodi kamili ya ukaguzi kurudi kwenye asili. Wanaweka lebo kwa kitambulisho chao cha ndani cha mtumiaji na kuchagua mtiririko wa kazi unaoingia.
Leta API ya Kipindi Kilichoshirikiwa
03 · Amini au kagua upya

Sajili papo hapo, au angalia upya kwa uzingatiaji.

Amini uamuzi wako na umruhusu mshirika wako amkubali mtumiaji mara tu tokeni inapoingia. Au wape data ghafi na uache timu yao ya kufuata sheria ifanye uamuzi. Badilisha kwa kila mshirika, wito sawa, kasi mbili za kuingiza.
Mwongozo wa KYC Inayoweza Kutumika Tena
04 · KYC + KYB · njia zote mbili

Shiriki mtu au biashara nzima.

Wito sawa unafanya kazi kwa aina zote mbili. Shiriki mtu aliyethibitishwa na mshirika wako anapata hati, selfie, kulinganisha, na kila hit ya AML. Shiriki biashara iliyothibitishwa na wanapata rekodi ya rejista, kila Mmiliki wa Manufaa wa Mwisho, kila KYC ya afisa, kila hati, kila uchunguzi.
Uthibitishaji wa Biashara (KYB)
05 · Inafaa kwa mfumo ikolojia wa washirika

Imejengwa kwa biashara ambapo uthibitishaji mmoja unatumika kwa wengi.

Wafadhili wa Banking-as-a-Service. Makundi ya chapa nyingi, neobank pamoja na broker, on-ramp pamoja na exchange. Fedha zilizopachikwa zinazopitia benki washirika. Masoko yenye majukwaa madogo ya kikanda. Wauzaji wa white-label. Mitandao ya wakopeshaji. Popote ambapo mtumiaji mmoja, au biashara moja, anaingizwa mara moja na kuhudumia wengi.
Mratibu wa Mtiririko wa Kazi
06 · Uzingatiaji sheria kwa muundo

Kiwango cha ukaguzi kwa chaguo-msingi.

Didit inatengeneza tokeni tu kwa uthibitisho uliomalizika, hakuna mtiririko uliokamatwa nusu unaovuja kati ya washirika. Tokeni hiyo hiyo haiwezi kuingizwa mara mbili. Pande zote mbili zinasaini makubaliano ya kushiriki data ya GDPR; Didit inasambaza nusu ya kiufundi.
Usalama + uzingatiaji
Unganisha

Wito mbili. Makabidhiano moja.

Unatengeneza tokeni upande wako. Mshirika wako anaiingiza upande wao. Mkataba sawa pande zote mbili, inafanya kazi kwa KYC na KYB.
POST /v3/session/{id}/share/Huduma X · Mint
$ curl -X POST https://verification.didit.me/v3/session/$SID/share/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "for_application_id": "partner-app-uuid",
    "ttl_in_seconds": 3600
  }'
201Imeundwa{ "share_token": "eyJhbGciOi…" }
Mpe tokeni Huduma Y kupitia chaneli ya backend iliyopangwa mapema.nyaraka →
POST /v3/session/import-shared/Huduma Y · Leta
$ curl -X POST https://verification.didit.me/v3/session/import-shared/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "share_token": "eyJhbGciOi…",
    "workflow_id": "wf_partner_kyc",
    "vendor_data": "partner-user-42",
    "trust_review": true
  }'
201Imeundwa{ "status": "Imeidhinishwa", "aina_ya_sesheni": "mtumiaji" }
Weka trust_review: false ili kuweka sesheni katika In Review.nyaraka →
Ujumuishaji tayari kwa agent

Weka KYC ya kushirikiana na washirika kwa amri moja.

Bandika kizuizi kilicho hapa chini kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Agent itaunganisha Didit, kuandaa pande zote mbili za makabidhiano, na kuweka mambo sawa.
didit-integration-prompt.md
# Didit B2B Reusable KYC — partner-to-partner KYC sharing

You are integrating Didit's B2B Reusable Know Your Customer (KYC) into <my_stack>. The recipe is server-to-server: one Didit application (Service X) mints a short-lived JSON Web Token (JWT) share token for a finished session; a partner Didit application (Service Y) imports the token and Didit clones the full verified session into Service Y. Works for both KYC and Know Your Business (KYB) sessions.

Built for Banking-as-a-Service (BaaS) sponsor banks, multi-brand financial groups, embedded finance through partner banks, marketplaces with regional or vertical sub-platforms, on-ramp + exchange ecosystems, white-label resellers, and B2B KYB consortia where the same legal entity onboards once and serves many. Every URL, header, and enum value below is canonical — do not paraphrase or "improve" them.

## 1. Provision both applications
- Sign up: https://business.didit.me (no credit card required).
- Or provision programmatically: POST https://apx.didit.me/auth/v2/programmatic/register/
- Create TWO applications in your Didit organisation. One acts as Service X (mints share tokens), the other as Service Y (imports them). In production these will usually live in different organisations — one per partner.
- Each application has its own `x-api-key`. Service X uses its own key to mint; Service Y uses its own key to import.

## 2. Service X — mint a share token

Service X picks a finished session it owns and posts to the share endpoint:

  POST https://verification.didit.me/v3/session/{sessionId}/share/
  Headers:
    x-api-key: <Service X api key>
    Content-Type: application/json
  Body:
    {
      "for_application_id": "<partner-application-uuid>",
      "ttl_in_seconds": 3600
    }

Bounds on `ttl_in_seconds`: min 60, max 86400, default 3600.

Requirements:
  - The session must be in a FINISHED status: "Approved", "Declined", or "In Review".
  - The API key must hold the `write:sessions` privilege.
  - `for_application_id` must be a real Didit application uuid — usually the partner's app.

Response: 201 Created with the JWT in the `share_token` field plus `for_application_id` and `session_kind` ("user" or "business" — Didit detects this from the source session and embeds it in the token):

  {
    "share_token": "eyJhbGciOiJIUzI1NiJ9...",
    "for_application_id": "partner-app-uuid",
    "session_kind": "user"
  }

## 3. Transmit the token to Service Y

Service X transmits the `share_token` to Service Y over a pre-arranged backend channel — REST, message queue, signed webhook, anything you control. The token is scoped to Service Y's application and useless to any other application.

## 4. Service Y — import the shared session

Service Y posts the token to the import endpoint:

  POST https://verification.didit.me/v3/session/import-shared/
  Headers:
    x-api-key: <Service Y api key>
    Content-Type: application/json
  Body:
    {
      "share_token": "<jwt from step 2>",
      "workflow_id": "<Service Y's own workflow id>",
      "vendor_data": "<Service Y's internal user id>",
      "trust_review": true
    }

`trust_review`:
  - `true`  → the imported session preserves the original status ("Approved" / "Declined" / "In Review"). Service Y onboards the user instantly. Use when Service Y fully trusts Service X's decision (sister brand, regulated partner with a signed data-sharing agreement).
  - `false` → the imported session lands in "In Review" so Service Y's compliance team makes its own call. Safe default for new partner relationships.

Response: 201 Created with a brand-new session in Service Y's application:

  {
    "session_id": "<new uuid>",
    "session_number": <int>,
    "session_kind": "user" | "business",
    "status": "Approved" | "In Review" | "Declined",
    "shared_from_session": "<original session uuid in Service X>",
    "vendor_data": "<Service Y's internal user id>",
    "id_verifications": [...],
    "liveness_checks": [...],
    "face_matches": [...],
    "aml_screenings": [...],
    "database_validations": [...],
    "proof_of_address": [...],
    "phone_verifications": [...],
    "email_verifications": [...]
  }

For a `session_kind: "business"` token Didit clones the KYB shape instead. KYB session statuses are UPPER_SNAKE_CASE (not Title Case like KYC):

  {
    "session_id": "<new uuid>",
    "session_kind": "business",
    "status": "APPROVED",
    "shared_from_session": "<original business session uuid>",
    "vendor_data": "<Service Y's internal business id>",
    "registry_checks": [...],
    "key_people_checks": [...],
    "document_verifications": [...],
    "aml_screenings": [...],
    "questionnaires": [...]
  }

A new User or Business entity is auto-created in Service Y if one with the supplied `vendor_data` doesn't already exist.

## 5. Idempotency, expiration, errors

| Status | Reason |
|--------|--------|
| 401 | Share token invalid or past `exp` — request a new one. |
| 403 | Token not intended for your application, OR session already imported into your app. |
| 404 | Original session no longer exists. |
| 404 | `workflow_id` not found in your application. |

The duplicate-import check is enforced against the (share_token, partner application) pair.

## 6. Webhooks (optional, only when Service Y wants async updates)

Service Y can register a webhook destination once via:

  POST https://verification.didit.me/v3/webhook/destinations/
  Body: url, subscribed_events: ["status.updated"]

Every webhook delivery carries an `X-Signature-V2` header you MUST verify before trusting the payload. 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.

Algorithm:
  1. sortKeys(payload) recursively
  2. shortenFloats (truncate trailing zeros after the decimal point)
  3. JSON.stringify the result
  4. HMAC-SHA256 with the secret_shared_key
  5. Hex-encode, compare to the X-Signature-V2 header.

## 7. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Status casing matches exactly: "Approved", "Declined", "In Review", "Not Finished" (Title Case With Spaces — KYC convention).
- session_kind is lowercase: "user" or "business".
- The share API is BUSINESS-to-BUSINESS sharing. Service X and Service Y are responsible for the data-sharing legal basis under General Data Protection Regulation (GDPR), UK GDPR, and any cross-border transfer rules. Didit ships the technical capability; you ship the data-sharing agreement.

## 8. Pricing reference (public)
- Service X already paid for the original verification (full KYC bundle is $0.30 or KYB session starts at $2.00; see didit.me/pricing).
- Service Y pays nothing on the import side — `POST /v3/session/import-shared/` is included with every plan.
- 500 free verifications every month on every account (applies to fresh captures, not imports).

## 9. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Create two sandbox applications: one as Service X (issuer), the other as Service Y (importer). Use Service X's API key to mint a token for a finished sandbox session, hand the token off, use Service Y's API key to import.
- Switch to live: flip each application's environment toggle in console.

When in doubt:
- https://docs.didit.me/sessions-api/share-session/overview
- https://docs.didit.me/sessions-api/share-session/share
- https://docs.didit.me/sessions-api/share-session/import
- https://docs.didit.me/core-technology/reusable-kyc/share-kyc-via-api
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
  • 60s–24h
    Weka muda wa tokeni kuanzia dakika moja hadi siku nzima.
  • KYC + KYB
    Shiriki mtu binafsi au biashara nzima, simu moja, aina zote mbili.
  • $0.00
    Mshirika wako halipi chochote kuingiza uthibitisho unaoshiriki.
  • 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
Anza bure
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
Tazama orodha kamili ya beiAnza bure
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
Wasiliana nasi

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 B2B Reusable KYC?

B2B Reusable KYC lets one business hand a verified user or company to another business, so the partner onboards the same person without running the verification again.

It works in two steps:

  • Mint a share token. Pick a finished verification in your app, ask Didit for a one-time token tied to one named partner. Default lifetime is one hour; you can stretch it from one minute to a full day. Nobody else can ever redeem it.
  • Your partner imports the session. They redeem the token and Didit clones the full record into their workspace, documents, selfie, face match, AML hits, registry data, Ultimate Beneficial Owners (UBOs). Same shape as a fresh verification, with a clean audit trail back to the original.

Your partner picks the onboarding speed. Trust your decision and approve the user instantly, or pull the data raw and let their compliance team make the call.

Works for both Know Your Customer (KYC) and Know Your Business (KYB), same call, both shapes.

Full reference: docs.didit.me/sessions-api/share-session.

Who is this for?

Any business model where one platform onboards a user once and several partner platforms need that same verification:

  • Banking-as-a-Service (BaaS), your sponsor bank or BIN sponsor needs the same Know Your Customer (KYC) data you already collected. Mint a share token from your application, the sponsor imports it.
  • Multi-brand financial groups, a single user onboards into Brand A and the same group needs them in Brand B (neobank + broker, fintech + lending arm, e-money + crypto on-ramp).
  • Embedded finance / Software-as-a-Service (SaaS) marketplaces, a vertical Software-as-a-Service offers payments or lending through partner banks; share the verification with whichever bank routes the user.
  • Marketplaces with sub-platforms, a parent marketplace verifies sellers once and downstream regional / vertical marketplaces inherit the verification.
  • On-ramps and exchanges, a fiat on-ramp shares the verified user with the exchange that lists assets; no second selfie capture.
  • B2B Know Your Business (KYB) ecosystems, verify a business once (registry + UBOs + AML + documents) and share that record across every partner that onboards the same legal entity.

If you can write a data-sharing agreement with your partner, this API ships the technical half.

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 does the import response look like?

POST /v3/session/import-shared/ returns 201 Created with a brand-new session in your application, fresh session_id and session_number, full payload cloned from the source.

Key fields:

  • status, Approved / Declined / In Review (preserved when trust_review: true, forced to In Review when trust_review: false).
  • session_kind, user (KYC) or business (KYB).
  • shared_from_session, points at the original session in the source application. Canonical signal that this session was imported, not freshly captured.
  • vendor_data, the internal user / business id YOU passed on the import call.
  • KYC relations cloned: id_verifications, liveness_checks, face_matches, aml_screenings, database_validations, proof_of_address, location_checks, phone_verifications, email_verifications.
  • KYB relations cloned: registry_checks, key_people_checks (with their nested KYCs), document_verifications, aml_screenings, questionnaires.

Identical shape to a fresh session, your existing webhook handler reads it the same way.

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.

Related

Moduli zinazohusiana + mtiririko

Miundombinu ya utambulisho na udanganyifu.

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

Anza bila malipoZungumza nasi
Uliza AI ifupishe ukurasa huu