Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Uandikishaji wa BNPL

Andikisha wakati wa kuomba. Fuatilia kila awamu.

$0.33 kumwajiri mkopaji, $0.02 kwa malipo ya awamu, AML inayoendelea imejumuishwa. Uthibitishaji 500 bure kila mwezi, sandbox kwa sekunde 60.

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

Inaaminika na mashirika 2,000+ duniani kote.

Mchoro wa kifilamu, giza, usioeleweka wa ukaguzi wa Buy-Now-Pay-Later, paneli nne za kioo zinazoelea, zinazopitisha mwanga katika mtazamo wa 3D kwenye rangi nyeusi safi, zikipitishwa na mstari mweupe wa Didit Blue na kuwekewa fremu na mabano manne ya skana yanayong'aa. Kila paneli ina motifu ndogo, nyeupe-nyeupe isiyo dhahiri inayowakilisha ukaguzi wa awamu (mstari wa muda wa awamu nne-dot, muhtasari wa kadi ya mkopo, chati ya pau inayopanda, pete ya maendeleo ya duara).

BNPL inadaiwa nini

Mkopaji wakati wa maombi. Kila awamu baada ya hapo.

Mpango wa BNPL si uamuzi mmoja, ni mfuatano. Didit inamkagua mkopaji wakati wa kulipa, inaweka kumbukumbu ya kila awamu kwenye API ya Miamala, na inachunguza upya kwa vikwazo au PEP (Watu Walio Hatari Kisiasa) kiotomatiki katika kipindi chote cha mpango. $0.33 wakati wa kuomba, $0.02 kwa awamu, AML inayoendelea imejumuishwa. 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. Gawanya kwa masharti, fanya majaribio ya A/B, hakuna code inayohitajika.

  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 inasimamia kamera, ishara za mwanga, uhamishaji wa 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 zilizosainiwa kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga API inapohitajika. Au fungua console kukagua kila kipindi, kila ishara, na kudhibiti kesi zako mwenyewe.

Imejengwa kwa BNPL · Bei kama miundombinu

Vipengele sita. $0.33 wakati wa kuomba, $0.02 kwa kila awamu.

Uzingatiaji wa BNPL si ukaguzi mmoja, ni mapishi. Kagua wakati wa kuomba, weka kumbukumbu ya kila awamu, sasisha AML katika mpango mzima, jenga kifurushi cha ukaguzi.
Soma nyarakaPata API key
01 · Kifurushi cha BNPL

Simu moja. Ukaguzi tano.

Kitambulisho, uhai, kulinganisha uso, kifaa + IP, AML, vimeunganishwa kwa $0.33 kwa mkopaji. Imethibitishwa na iBeta Level 1 anti-spoof, uamuzi chini ya sekunde mbili, nyaraka 14,000+ katika nchi 220+.
Moduli ya Uthibitishaji wa Mtumiaji
02 · Hatari ya Kifaa + IP

Ishara 200+ za udanganyifu wakati wa kuomba.

Kugundua VPN / Tor / proxy, mfiduo wa kituo cha data, kutofautiana kati ya anwani ya bili na jiografia ya IP, akaunti nyingi kwa kila kifaa, kasi wakati wa kulipa, yote yamezingatiwa katika alama moja ya hatari kwa kila maombi.
Uchambuzi wa Kifaa & IP
03 · Ufuatiliaji unaoendelea

AML inaburudishwa katika mpango mzima, si tu wakati wa kuomba.

AML inayoendelea inamfuatilia mkopaji kila siku kwa vikwazo vipya, PEP (Watu Walio Hatari Kisiasa), na matukio mabaya ya vyombo vya habari, kwa $0.07 kwa mtumiaji kwa mwaka. Hakuna endpoint tofauti, kiotomatiki kwenye kipindi chochote chenye AML iliyowezeshwa.
Moduli ya Uchunguzi wa AML
04 · Uwezo wa kumudu + kifurushi cha ukaguzi

Kifurushi kimoja kwa kila mkopaji · Tayari kwa FCA-export.

Sehemu za mkopaji zilizothibitishwa pamoja na stack ya ishara za ukaguzi (KYC, AML, Kifaa + IP, vigezo vya mpango) zimeunganishwa katika rekodi moja iliyosainiwa, inayoweza kusafirishwa kwa UK FCA (Financial Conduct Authority), Australian ASIC, au mamlaka nyingine yoyote inayofanya ukaguzi wa BNPL.
Nyaraka za Webhooks
05 · Kushindwa kulipa awamu ya kwanza

Baini mifumo ya FPD wakati wa kuomba.

Mifumo ya vikundi, makundi ya nyaraka zilizoibiwa, matumizi tena ya kitambulisho katika mipango ya BNPL, kasi kwa kila kifaa, barua pepe ya muda + kifaa kipya, inasasishwa kila siku na kuzuiwa kabla ya mpango kuidhinishwa. Hariri vizingiti kwa kila mfanyabiashara.
Kesi ya matumizi ya kuchukua akaunti
06 · Nchi mbalimbali

Stack moja. Kila eneo.

Sheria za UK FCA BNPL (2026), EU Consumer Credit Directive II, leseni za wakopeshaji za jimbo kwa jimbo za Marekani, Australia ASIC, pamoja na orodha za uangalizi za AML za kila eneo. Nyaraka 14,000+ katika nchi 220+.
Ufuatiliaji wa Miamala
Unganisha

Kipindi kimoja wakati wa kuomba. Muamala mmoja kwa kila awamu.

Kagua mkopaji. Toza awamu. Soma uamuzi uliosainiwa. Rudia katika mpango mzima.
POST /v3/session/Omba
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_bnpl_apply",
    "vendor_data": "borrower-42",
    "metadata": { "plan_id": "plan-9182" }
  }'
201Imeundwa{ Inarudisha URL ya kipindi kilichopangishwa. }
Shikilia mpango hadi webhook itakaposema status: Approved.nyaraka →
POST /v3/transactions/Awamu
$ curl -X POST https://verification.didit.me/v3/transactions/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "transaction_id": "plan-9182-inst-1",
    "transaction_details": { "direction": "INBOUND", "amount": "125.00", "currency": "GBP", "currency_kind": "fiat" },
    "subject": { "vendor_data": "borrower-42", "full_name": "Jamie Mfano" },
    "mshirika": { "jina_kamili": "Mfanyabiashara Ltd" }
  }'
201Imeundwa{ hali IMEIDHINISHWA · INAANGALIWA · IMETUPILIWA MBALI · INAMSUBIRI MTUMIAJI · $0.02 }
Kugundua kasi na muundo kumejengwa ndani kwa kila awamu.nyaraka →
Ujumuishaji tayari kwa agent

Anzisha mfumo wa BNPL underwriting kwa prompt moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent huunda mtiririko wa maombi, huweka kumbukumbu kila awamu, hutia saini webhook, na huunganisha kifurushi cha ukaguzi.
didit-integration-prompt.md
You are integrating Didit into a Buy-Now-Pay-Later (BNPL) checkout flow — Klarna / Affirm / Clearpay / Tabby / Tamara / Kueski archetype. The recipe handles three obligations on every BNPL plan:

  1. Verify the borrower at checkout — identity, liveness, face match, device + IP, AML against 1,300+ sanctions / PEP / adverse-media lists. ONE call to the Sessions API.
  2. Log every instalment charge — Transaction Monitoring catches velocity, structuring, and chargeback patterns. ONE call to the Transactions API per instalment.
  3. Continuous AML — the borrower is rescreened automatically across the lifetime of the plan. NO separate endpoint to call.

Cost:
  - Borrower Know Your Customer (KYC) bundle: $0.33 per application (Sessions API)
  - Transaction monitoring per instalment charge: $0.02 (Transactions API)
  - Ongoing AML monitoring: $0.07 per user per year (automatic on any session with AML enabled)
  - 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 that bundles ID Verification + Passive Liveness + Face Match 1:1 + Device & IP Analysis + AML Screening.
  - Transaction Monitoring enabled in the Business Console (Transactions > Settings).

STEP 1 — Underwrite the borrower at checkout

  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 bundle>",
      "vendor_data": "<your borrower id, max 256 chars>",
      "callback": "https://<your-app>/bnpl/apply/callback",
      "metadata": {
        "purpose": "bnpl_application",
        "plan_id": "<your internal plan reference>",
        "merchant_id": "<merchant id>",
        "principal_amount": "500.00",
        "currency": "GBP"
      }
    }

  Response: 201 Created with the hosted session URL. Embed the URL inline in the BNPL widget at checkout. Sub-2-second median verdict on completion.

STEP 2 — Read the signed webhook on application completion

  Didit POSTs to your callback. Session statuses are Title Case With Spaces:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your borrower 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.

  On Approved + clean AML + acceptable Device & IP, approve the plan and schedule the instalments. On Declined or AML hit, decline. On In Review or AWAITING_USER, hold the plan and route to your underwriting analyst queue.

STEP 3 — Log every instalment charge

  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": "<plan-id>-instalment-1",
      "transaction_category": "finance",
      "transaction_details": {
        "direction": "INBOUND",
        "amount": "125.00",
        "currency": "GBP",
        "currency_kind": "fiat",
        "action_type": "deposit"
      },
      "subject": {
        "entity_type": "individual",
        "vendor_data": "<your borrower id>",
        "full_name": "<borrower full name>"
      },
      "counterparty": {
        "entity_type": "individual",
        "full_name": "<merchant or BNPL settlement counterparty>"
      }
    }

  REQUIRED fields the API rejects if missing:
    - subject.vendor_data + subject.full_name
    - counterparty.full_name
    - transaction_details.direction + currency + currency_kind + amount

  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,
      "cost_breakdown": {
        "total_price": 0.02,
        "items": [{ "usage_type": "transaction_monitoring", "price": 0.02 }]
      }
    }

  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.

  Per-instalment cost: $0.02 (transaction-monitoring base).

  Branch logic:
    APPROVED       → charge the card / pull the bank transfer.
    IN_REVIEW      → hold the instalment, route to analyst queue.
    DECLINED       → hard-fail the instalment, mark the plan delinquent.
    AWAITING_USER  → redirect the borrower to the remediation session URL.

STEP 4 — Continuous AML monitoring is automatic

  Any session with AML enabled is rescreened DAILY by Didit's continuous monitoring at $0.07 per user per year. There is NO separate endpoint to call.

  When a previously-approved borrower crosses an AML threshold, the session status changes to "In Review" or "Declined" automatically and your webhook fires the update. Hold the remaining instalments and route the case to your collections / fraud team.

STEP 5 — Returning borrowers re-use the verified identity

  When a borrower comes back for a second plan, open a new session against their existing vendor_data — Didit reuses the previously verified document and face match where policy allows, and you avoid paying for the full bundle again. Pair with Reusable KYC for the lightest path.

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 use Title Case With Spaces (Approved, In Review). Transaction statuses use UPPER_SNAKE_CASE (APPROVED, IN_REVIEW). They live in different APIs — don't mix them in the same code path.
  - Never approve a BNPL plan before the X-Signature-V2 webhook lands with status Approved + AML clear.
  - 200+ fraud signals are evaluated on every session at no extra cost — surface the score via the session decision payload, don't re-query.
  - Default record retention is 5 years post-relationship per the EU AML package; UK FCA rules and similar national rules sit on top.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/transaction-monitoring/overview
  - https://docs.didit.me/transaction-monitoring/transactions
  - https://docs.didit.me/core-technology/aml-screening/continuous-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.
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 mkopaji wakati wa maombi, KYC + Kifaa + IP + AML, API call moja.
  • $0.00
    Ada kwa kila awamu ikiwa na ugunduzi wa kasi na muundo uliojengwa ndani.
  • <0s
    Uamuzi kamili wa KYC kwa kila maombi, kwenye Android za kiwango cha chini.
  • 0
    Uthibitishaji wa bure kila mwezi, kwa 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's Buy-Now-Pay-Later (BNPL), in plain English?

BNPL lets a shopper take goods home today and pay for them in instalments, typically four payments over six weeks, sometimes longer plans with interest.

The industry shape:

  • Klarna · Affirm · Clearpay (Afterpay) · Tabby · Tamara · Kueski · Atome are the major standalone providers
  • Apple Pay Later, PayPal Pay in 4, Shopify Installments are payment-network-embedded variants
  • The merchant gets paid in full at checkout; the BNPL provider takes the credit risk

The regulatory shift: BNPL used to sit in a soft-touch consumer-credit grey zone. As of 2025-2026, the UK FCA (Financial Conduct Authority) brings BNPL under formal regulation, the EU Consumer Credit Directive II (CCD II) extends to BNPL, and US state lenders apply existing licensing law. The compliance bar is now: real ID, real underwriting, real monitoring, real audit pack.

Why does BNPL need identity verification, not just a card check?

Because BNPL extends credit, not just processes a card.

  • A card check proves the card is valid right now. It doesn't prove who's holding it.
  • BNPL approves a multi-week payment plan against a person, if the card later fails, the BNPL provider eats the loss.
  • Fraud rings exploit BNPL precisely because card auth is weaker than full underwriting, stolen identities + stolen cards + drop addresses are a textbook pattern.

Real identity verification (ID + face + AML) cuts first-payment default (FPD) at the source. The shopper presents a real document and a real face; Didit binds the application to a single human, not just a token.

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.

Who has to underwrite this way? Isn't BNPL still unregulated?

Not anymore. The regulatory map circa 2026:

  • United Kingdom, the FCA brings BNPL under formal Consumer Credit Act regulation starting 2026; full affordability checks, audit trails, and complaint handling required
  • European Union, Consumer Credit Directive II (CCD II, Directive (EU) 2023/2225) applies to BNPL from late 2026, lifting the small-credit exemption that previously sheltered it
  • United States, state-by-state lender licensing already applies in most states; the CFPB issued an interpretive rule treating Pay-in-4 as a credit-card product
  • Australia, ASIC (Australian Securities and Investments Commission) brings BNPL under the National Consumer Credit Protection Act from 2025

The shape of the compliance bar is the same in every region: verify the borrower, screen for sanctions and PEPs, monitor across the plan, keep a 5+ year audit trail. Didit ships that bar globally.

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.

What does the affordability + audit pack look like for the FCA?

Every borrower produces an exportable pack:

  • borrower_pid, your pseudonymous borrower id
  • kyc_status, Approved / Declined / In Review (Title Case With Spaces)
  • aml_status, Clear / Hit / Manual review
  • device_risk, score + top contributing signals
  • plan_parameters, instalment count, total amount, currency, merchant id
  • signature, X-Signature-V2 HMAC SHA-256

Pipe to your collections + compliance systems and to your regulator-facing reporting layer. Default retention is 5 years post-relationship per the EU AML package; the UK FCA's BNPL rules will sit on top. Aligned with SOC 2 Type 1, ISO/IEC 27001, and the General Data Protection Regulation, all of which Didit holds.

What about cross-border BNPL, can Didit handle the whole footprint?

Yes. The same /v3/ API covers every market:

  • United Kingdom · EU · EEA, FCA, Consumer Credit Directive II, plus the EU sanctions and PEP lists
  • United States, state-by-state lender licensing, CFPB credit-card treatment for Pay-in-4, OFAC SDN screening
  • Latin America, Brazil (LGPD + Pix), Mexico, Chile, Argentina, local IDs and watchlists
  • APAC, Australia ASIC, Singapore MAS, Indonesia OJK, Japan FSA, local IDs and watchlists
  • MEA, UAE, KSA, Egypt, local IDs and watchlists

One contract, one API key, one Workflow Builder. Per-region rules tuned per workflow, Didit handles 14,000+ document types across 220+ countries, sub-2-second verdict on entry-level Android, 48+ languages in the hosted UI.

How fast can a small team integrate this?

Four wires, one afternoon:

  • Open business.didit.me, sandbox key in 60 seconds, no credit card
  • Build a workflow in the Workflow Builder that bundles ID + Liveness + Face Match + Device & IP + AML Screening
  • Wire POST /v3/session/ to the apply step + the signed webhook to your decision engine
  • Wire POST /v3/transactions/ to every instalment charge + handle the four-value status enum

The Didit MCP (Model Context Protocol) server is included free, paste the integration prompt above into Claude Code, Cursor, Codex, Replit Agent, Devin, or Aider and the agent scaffolds the whole thing against the live /v3/ API.

Related

Moduli zinazohusiana + mifumo ya kazi

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