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

Kitambulisho, anwani, ustahiki wa kukodisha, katika mtiririko mmoja wa mpangaji.

Kikao kimoja kinashughulikia kitambulisho cha mwombaji, anwani ya sasa, uchunguzi wa vikwazo, na haki ya kukodisha. Dakika tano kwenye simu, kifurushi kilichotiwa saini kwa mwenye nyumba. Uthibitishaji 500 bila malipo kila mwezi.

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 sinema, giza, usio dhahiri wa uchunguzi wa mpangaji, paneli nne za glasi zinazoelea, zinazopitisha mwanga kwenye mandhari nyeusi kabisa zikipitishwa na mstari mweupe wa Didit Blue. Kila paneli ina motifu ndogo isiyo dhahiri (muhtasari wa nyumba, funguo zilizovuka, ubao wa kunakili, pini ya eneo).

Mawakala wa kukodisha wanachodaiwa

Mjue mwombaji. Jua anaweza kukodisha. Kabla hujakabidhi funguo.

Uchunguzi wa kutumia karatasi ni polepole, ghali, na rahisi kughushi. Didit inauondoa kwa kikao kimoja kinachosimamiwa: Kitambulisho + liveness + face match + uthibitisho wa anwani + AML + ukaguzi wa ustahiki wa kukodisha, $0.33 kwa kila mwombaji pamoja na $0.20 kwa uthibitisho wa anwani. Uthibitishaji 500 bila malipo kila mwezi, uamuzi chini ya sekunde 2.

Jinsi inavyofanya kazi

Kuanzia kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

    Chagua ukaguzi unaotaka, Kitambulisho, liveness, face match, 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 code inayohitajika.

  2. Hatua 02

    Unganisha

    Pachika kiasili na SDK yetu ya Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu kiungo kwa mtumiaji wako, 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 zilizotiwa saini kwa wakati halisi huweka hifadhidata yako ikiwa 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 ajili ya kukodisha · Bei kama miundombinu

Ukaguzi sita. Kipindi kimoja. Chini ya dakika tano.

Kifurushi cha ushahidi wa mpangaji si ukaguzi mmoja tu, ni mchanganyiko wa utambulisho, anwani ya sasa, ustahiki wa kukodisha, mapato, AML, na mdhamini wa hiari. Washa kila moduli kulingana na mtiririko wa kazi.
Soma nyarakaPata API key
01 · Kifurushi cha KYC cha Mpangaji

Thibitisha mwombaji kwa simu moja.

ID + liveness + face match + AML, zote kwa $0.33 kwa mwombaji. Imethibitishwa na iBeta Level 1 anti-spoof, uamuzi chini ya sekunde mbili, nyaraka 14,000+ katika nchi 220+.
Moduli ya Uthibitishaji wa Mtumiaji
02 · Uthibitisho wa Anwani

Soma anwani kutoka kwa bili ya huduma, benki, au barua.

Bili ya huduma, taarifa ya benki, au barua ya serikali, OCR inatoa anwani na kuiangalia dhidi ya ID ya msingi. $0.20 kwa kila ukaguzi. Inagundua nyaraka za zamani, anwani zisizolingana, na upakiaji uliochezewa.
Moduli ya Uthibitisho wa Anwani
03 · Ustahiki wa Kukodisha

Haki ya kukodisha na haki ya kukodisha kulingana na mamlaka.

Haki ya Kukodisha ya UK Home Office (share code + visa class), nyaraka za ukaazi za EU (Padrón ES / Anmeldung DE / NIE / TIE), jimbo la ukaazi la Marekani, kitambulisho cha kitaifa cha kodi cha LatAm (CURP, CPF, RUT), huendeshwa kiotomatiki kulingana na nchi ya mwombaji.
Moduli ya Uthibitishaji wa Hifadhidata
04 · Ushahidi wa Mapato

Soma payslip na taarifa ya benki.

OCR ya payslip inatoa mwajiri na malipo halisi; taarifa ya benki inatoa IBAN na muundo wa mapato. Waombaji waliojiajiri wanaweza kupakia marejesho ya kodi badala yake. Custom Questionnaire ($0.10) inakusanya barua ya marejeleo ya mwajiri.
Moduli ya Maswali Maalum
05 · Uchunguzi wa AML

Chunguza kwenye orodha 1,300+ za vikwazo na PEP.

Vikwazo, Watu Walio Wazi Kisiasa (PEP), habari mbaya, husasishwa kila siku, kwa lugha 14. Matokeo mabaya hufungua kesi kiotomatiki na kuzuia maombi kabla ya idhini.
Moduli ya Uchunguzi wa AML
06 · Mtiririko wa Mdhamini

KYC iliyounganishwa kwa mdhamini.

Unahitaji mdhamini? Mtiririko uleule uliopangishwa, $0.33 kwa kila mdhamini, umeunganishwa tena kwenye rekodi kuu ya mpangaji. Kifurushi kimoja cha ukaguzi kilichotiwa saini kinashughulikia kila chama kwenye mkataba wa kukodisha.
Moduli ya Uthibitishaji wa Mtumiaji
Unganisha

Kipindi kimoja. Webhook moja. Kifurushi kimoja cha mpangaji.

Fungua kipindi cha mpangaji. Soma uamuzi uliotiwa saini. Sambaza kifurushi kwa mwenye nyumba.
POST /v3/session/Mpangaji
$ 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_tenant_screening",
    "vendor_data": "applicant-42",
    "expected_country": "GB"
  }'
201Imeundwa{ "url": "verify.didit.me/..." }
Tuma SMS au barua pepe URL. Mwombaji anamaliza ndani ya dakika tano.nyaraka →
GET /v3/session/{id}/decision/Uamuzi
$ curl https://verification.didit.me/v3/session/$SESSION/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Decision payload (excerpted):
{ "status": "Imeidhinishwa",
  "proof_of_address": { "status": "Imeidhinishwa", "address": { ... } },
  "database_validation": { "service": "uk_right_to_rent" } }
200OKhali Imeidhinishwa · Inapitiwa · Imekataliwa · Imewasilishwa tena
Sambaza kifurushi kilichosainiwa kwa mwenye nyumba.nyaraka →
Ujumuishaji tayari kwa agent

Weka mfumo wa ukaguzi wa wapangaji kwa prompt moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent huunda workflow, huanzisha session kwa kila mwombaji, huendesha mtiririko wa mdhamini (kama upo), na huunganisha webhook.
didit-integration-prompt.md
You are integrating Didit into a residential-leasing platform (PropTech / build-to-rent / letting-agent archetype). You owe the landlord (or your platform owes the landlord) an evidence pack on every applicant before the keys come off the hook.

Four obligations on every application:

  1. Verify the applicant's identity — government ID + liveness + face match.
  2. Validate the current address — utility, bank, or registry-issued letter, cross-checked against the ID.
  3. Confirm lease eligibility — Right to Rent (UK) / state-of-residence (US) / residency document (EU) / national tax id (LatAm).
  4. Screen the applicant against sanctions, Politically Exposed Persons (PEP), and adverse-media lists.

Optional: run the same flow against a guarantor and stitch both back to the lease record.

Pricing (verified live):
  - Tenant KYC bundle: $0.33 per applicant (ID + Liveness + Face Match + IP + AML)
  - Proof of Address: $0.20 per check
  - Database Validation (right-to-rent / national id): variable, per-jurisdiction
  - Linked guarantor KYC: $0.33 per guarantor
  - First 500 KYC 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 + Proof of Address + AML Screening + the jurisdiction-specific Database Validation node.
  - Optional: a separate KYC workflow_id for the guarantor.

STEP 1 — Create the tenant session

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<your tenant-screening workflow id>",
      "vendor_data": "<your applicant id, max 256 chars>",
      "callback_url": "https://<your-app>/applications/kyc/callback",
      "expected_country": "GB",
      "metadata": {
        "application_id": "<your internal id>",
        "property_id": "<unit reference>"
      }
    }

  Response: 201 Created with the hosted session URL. SMS or email the URL to the applicant; they complete everything on their phone in under five minutes.

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 applicant id>",
      "status": "Approved",
      "id_verification": { "status": "Approved", "document_type": "passport", "country_code": "GB" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "proof_of_address": { "status": "Approved", "document_type": "utility_bill", "address": { "line1": "10 Long Acre", "city": "London", "postal_code": "WC2E 9LH", "country": "GB" } },
      "aml": { "status": "Approved", "hits": [] },
      "database_validation": { "status": "Approved", "service": "uk_right_to_rent", "result": { "share_code_status": "valid", "expiry_date": "2027-08-12" } }
    }

  Session 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 — (Optional) Spawn a guarantor session

  If the workflow declares a guarantor step, the parent session returns a guarantor_session_url inside the decision payload. Email it to the guarantor and they run the same KYC flow on their phone. The result threads back to the parent tenant record automatically.

  Alternatively, fire a second POST /v3/session/ with a separate guarantor workflow_id and stitch the two together by setting metadata.tenant_session_id on the guarantor call.

STEP 4 — Retrieve the full evidence pack

  GET https://verification.didit.me/v3/session/{sessionId}/decision/
  Headers:
    x-api-key: <your api key>

  Returns the full decision payload — ID block, liveness block, face match, proof-of-address result with the canonical address fields, AML hits, database-validation outcome. Use this for audit-pack export and for rendering the applicant status in your letting-agent dashboard.

STEP 5 — Decide

  Branch logic:
    Approved    → forward the pack to the landlord, advance to lease signing.
    In Review   → hold the application, wait for analyst webhook update.
    Declined    → refuse the application, log the decline reason.
    Resubmitted → applicant updated something; re-read the decision.

  For Database Validation specifically — if the result indicates an expired Right to Rent share code, ask the applicant for a fresh one before moving forward.

STEP 6 — Ongoing monitoring (long leases)

  For multi-year tenancies, enable Ongoing AML at $0.07/user/year. The session status updates automatically when the tenant lands on a new sanctions list or document expirations approach (passport, visa, residency permit). Your webhook fires on every state change.

  No separate endpoint to call — the same workflow drives it.

WEBHOOK EVENT NAMES
  - status.updated — session status changed.
  - data.updated — session data changed (resubmission, expiry, ongoing AML hit).

  Verify X-Signature-V2 on every payload. The webhook secret is per-environment — sandbox key is separate from production.

CONSTRAINTS
  - Session statuses use Title Case With Spaces (Approved, In Review).
  - Default record retention is 5 years per tenant per the EU AML package; UK Right to Rent requires document copies for the tenancy duration + one year.
  - The address on the Proof of Address document MUST match the address on the underlying ID for an Approved outcome; if they differ, the session flips to In Review.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/retrieve-session
  - https://docs.didit.me/core-technology/proof-of-address/overview
  - https://docs.didit.me/core-technology/aml-screening/overview
  - 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 kila mpangaji aliyekaguliwa kikamilifu, kifurushi cha KYC + Uthibitisho wa Anwani.
  • 0+
    Vikwazo, PEP, na orodha za habari hasi zimekaguliwa kwa kila mwombaji.
  • <0s
    Matokeo ya KYC kamili kwa kila session, kwenye Android ya kiwango cha chini.
  • 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 does tenant screening actually involve?

It's the process a landlord or letting agent runs before handing over the keys, to make sure the applicant is who they say they are and can lawfully take the lease. The standard pieces are:

  • Identity verification, government ID + face match + liveness, so you know the person on the phone is the person on the application
  • Address proof, a recent utility bill, bank statement, or government letter showing where they currently live
  • Lease eligibility, country-specific. In the UK that's Right to Rent. In the EU it's a residency document. In the US it's typically a state-of-residence + SSN. In Latin America it's the national tax id.
  • Anti-money-laundering screen, sanctions, Politically Exposed Persons (PEP), adverse media
  • (Optional) income and guarantor evidence, payslips, bank statements, plus a linked KYC on the guarantor when affordability is on the edge

Didit ships all of it as one hosted flow. The applicant completes it on their phone in under five minutes; the agent gets a signed pack back.

Who actually needs to do this?

Anyone leasing residential property to a third party. In practice that means:

  • Build-to-rent operators, Greystar, Equity Residential, Mileway, Quintain archetype
  • Letting agents, Foxtons, Belvoir, Connells, Re/Max
  • PropTech platforms, SpareRoom, Goodlord, Canopy, OpenRent
  • Short-let and co-living, The Collective, Common, Outsite
  • Corporate housing and student PBSA, Unite Students, Vita, Sonder

In the UK, Right to Rent checks are a hard legal requirement under the Immigration Act, with material per-tenant fines for failing to perform them. The EU has parallel obligations under the AML package for any property professional. The US runs it through state landlord-tenant law plus fair-housing rules.

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 goes wrong if a landlord skips this?

Three things, in order of how often they bite:

  • Fraud applicants, fake IDs, photoshopped payslips, applicants impersonating someone with better credit. The landlord loses the rent and the property sits empty during the eviction.
  • Right-to-Rent penalty, in the UK, up to £20,000 per tenant for renting to someone without the right immigration status. Criminal liability for repeat offenders.
  • AML reporting failures, large cash deposits or sanctioned tenants without a filed Suspicious Activity Report (SAR) creates regulator exposure under the EU AML package and the UK Money Laundering Regulations.

The traditional paper-based check is slow, expensive (typically £15-£40 per applicant through legacy providers), and easy to forge. Most agents end up doing a partial check and hoping for the best. Didit eliminates the trade-off, full coverage at $0.53 per applicant (KYC bundle + Proof of Address).

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 are addresses cross-checked?

Three layers of validation run on every Proof of Address upload:

  • OCR extraction, the bill / statement / letter is read and the address is parsed into the canonical address fields (line 1, city, postal code, country)
  • ID cross-check, the extracted address is compared with the address on the underlying ID document. A close match passes; a different city or postal code flips the session to In Review.
  • Registry validation (where available), the address is looked up against the country's authoritative source, UK Royal Mail PAF, Spain Catastro, US USPS, France BAN, etc.

Fraud patterns Didit catches: a Photoshopped utility bill with a forged address, a real bill from a different building, a bill belonging to a different person at the same address, an expired bill (over 90 days old). All three layers run server-side; the agent never sees a raw upload, only the validated result.

What does ongoing monitoring look like?

Verification at the start of the tenancy is necessary but not sufficient, for long leases, tenants change circumstances and sanctions lists update daily. Didit's ongoing monitoring catches:

  • Ongoing AML on the tenant, daily delta refresh at $0.07 per tenant per year
  • Visa / residency permit expiry, fires a webhook 30 days before the document expires so the agent can request a fresh share code
  • New sanctions listing, instant webhook the day the tenant lands on a new list
  • Address change (resubmission), if the tenant updates their address mid-tenancy, the new proof is automatically run through the same validation stack

Everything flows through the same status.updated webhook you wired for onboarding. No new endpoint, no extra integration.

How does Didit compare on price?

Most tenant-screening providers price between £15 and £40 per applicant, Goodlord, Letting a Property, Open Banking-based affordability tools. Most charge per check, plus a per-tenancy admin fee, plus a per-Right-to-Rent surcharge.

Didit's published price is $0.33 for the KYC bundle + $0.20 for Proof of Address = $0.53 per applicant. Database Validation is variable per jurisdiction and typically adds $0.05-$0.20 depending on the service. No floor, no commit, no per-country surcharge.

That's roughly 10× cheaper than the incumbent stack on the same legal output. At a 200-tenant build-to-rent portfolio that turns over once a year, the saving is around £3,000 in screening costs, and the applicant experience is faster, with no paper, no scanning. Full pricing at /pricing.

Related

Moduli zinazohusiana + workflows

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