Uthibitisho wa makazi kutoka hati yoyote inayounga mkono.
Bili za matumizi, taarifa za benki, barua za serikali — zinasomwa, kuchambuliwa, kuangaliwa dhidi ya kitambulisho, kuthibitishwa dhidi ya rejista ya anwani ya nchi. $0.20 kwa kila ukaguzi. Uthibitishaji 500 bila malipo kila mwezi.
Usiweke imani kwenye anwani iliyoandikwa. Soma bili, thibitisha usajili.
Anwani iliyochapishwa mwenyewe inashindwa ukaguzi. Bili ya matumizi iliyochanganuliwa ambayo haijaangaliwa
dhidi ya kitambulisho inashindwa ukaguzi. Didit inatoa mapishi kamili ya Uthibitisho wa
Anwani — kunasa, OCR, jina + anwani inalingana na kitambulisho, pamoja na
uthibitishaji wa rejista ya nchi katika mamlaka 18+ — kama kifurushi kimoja cha ushahidi kilichotiwa saini
kwa $0.20 kwa kila ukaguzi.
Jinsi inavyofanya kazi
Kutoka kujisajili hadi mtumiaji aliyethibitishwa katika hatua nne.
Hatua 01
Unda mtiririko wa kazi
Chagua ukaguzi unaotaka — kitambulisho, uhai, ulinganifu wa uso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwa API yetu. Tawi kwenye masharti, endesha majaribio ya A/B, hakuna msimbo unaohitajika.
Hatua 02
Unganisha
Pachika kiasili na Web, iOS, Android, React Native, au Flutter SDK yetu. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu mtumiaji wako kiungo — kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.
Hatua 03
Mtumiaji anapitia mtiririko
Didit inasimamia kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapata alama za ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vyenye mamlaka. Matokeo chini ya sekunde mbili.
Hatua 04
Unapokea matokeo
Webhooks zilizotiwa saini kwa wakati halisi huweka hifadhidata yako ikiwa sawa wakati mtumiaji anaidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga API inapohitajika. Au fungua koni ili kukagua kila kipindi, kila ishara, na kudhibiti kesi kwa njia yako.
Imejengwa kwa ajili ya kufuata sheria · Bei kama miundombinu
Ukaguzi sita. $0.20 kwa Uthibitisho wa Anwani.
Uthibitisho wa Anwani wa kiwango cha mdhibiti sio tu OCR — ni mapishi ya kunasa, kuchambua, kuangalia, uthibitishaji wa rejista, na bahasha ya ukaguzi. Washa kila moduli kwa kila mtiririko wa kazi.
Bili ya huduma, taarifa ya benki, barua ya serikali, mkataba wa kukodisha, rehani, mkataba wa simu/intaneti — zote ndani ya siku 90. Mtiririko uliopangishwa humwongoza mtumiaji kupitia unasi; SDK huonyesha mtiririko huo ndani ya programu yako asili.
OCR huchota anwani kwenye sehemu za kawaida — mstari wa 1, mstari wa 2, jiji, msimbo wa posta, nchi, iliyotolewa_saa — na kuiweka sawa katika bili ya huduma ya Kiingereza, taarifa ya benki ya Kihispania, Anmeldung ya Kijerumani. Wakati huo huo tunaangalia uhalisi: udanganyifu wa kiwango cha pikseli, mabaki ya kunakili-kubandika, uchezaji wa fonti/kiolezo, uchapishaji upya wa azimio la chini, na kutofautiana kwa EXIF. Hati iliyoghushiwa au iliyobadilishwa inashindwa kukaguliwa kabla haijafika kwenye kumbukumbu yako ya ukaguzi.
Tarehe ya hati imechunguzwa dhidi ya dirisha la siku 90 kiotomatiki.
03 · Kukagua kitambulisho
Linganisha na kitambulisho cha msingi.
Anwani iliyochanganuliwa inalinganishwa na anwani kwenye kitambulisho cha msingi, na jina kwenye uthibitisho linalinganishwa na jina kwenye kitambulisho. Inanasa bili ghushi, majina yasiyolingana, upakiaji uliopitwa na wakati, na bili za mtu mwingine kwenye anwani hiyo hiyo.
Jina kwenye POA = jina kwenye kitambulishoOCR + IDPitisha
Anwani kwenye POA = anwani kwenye kitambulishoOCR + IDPitisha
Msimbo wa posta ni halali (nchi)DatabasePitisha
Tarehe ya hati ndani ya siku 90OCRPitisha
Jiji tofauti → ukaguzi wa binadamuPolicyKagua
Inanasa bili ghushi, anwani zisizolingana, upakiaji uliopitwa na wakati.
04 · Uthibitishaji wa rejista
Thibitisha dhidi ya chanzo chenye mamlaka cha nchi.
Ambapo nchi inaiunga mkono — UK Royal Mail PAF, Spain Catastro / Padrón, France BAN, Germany municipal Anmeldung, US USPS, na zaidi — anwani iliyochanganuliwa inatafutwa dhidi ya rejista yenye mamlaka moja kwa moja.
Imethibitishwa na rejista ambapo nchi inaiunga mkono.
Nchi 18+
UK Royal Mail PAFMsimbo wa posta + anwani imethibitishwa
Spain Catastro / PadrónAnwani + rekodi ya manispaa
France BANBase Adresse Nationale
Germany DATEV / AnmeldungUsajili wa manispaa
Inapitishwa kiotomatiki na msimbo wa nchi ulioparswa.
05 · Ufikiaji wa kimataifa
Nchi 220+, lugha 48+.
Nyaraka zinazokubalika kwa kila eneo — Ulaya huelekea bili ya huduma/benki/barua ya baraza, Amerika Kusini huelekea rejista ya kodi, Marekani huelekea benki/huduma/kukodisha, APAC huelekea barua ya serikali. Mjenzi wa Mtiririko wa Kazi hukuruhusu kuzuia nyaraka zinazokubalika kwa kila sehemu ya nchi.
Kila uamuzi wa Uthibitisho wa Anwani umetiwa saini na kuwekewa muhuri wa muda — picha halisi ya hati, malipo ya anwani iliyochanganuliwa, maamuzi ya ukaguzi wa msalaba, na matokeo ya uthibitishaji wa rejista. Inaweza kusafirishwa inapohitajika kupitia Dashibodi ya Biashara au API. Vituo vya data vya EU kwa chaguo-msingi.
Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Wakala huunda mtiririko wa kazi, huwasha kipindi, huchanganua anwani katika sehemu halisi, huendesha uthibitishaji wa sajili, na kuunganisha webhook.
didit-integration-prompt.md
You are integrating Didit's Proof of Address into a regulated onboarding flow (bank, fintech, lender, crypto exchange, EU payment institution). Regulators want a current address on every customer file; the legacy "ask the user to type it" approach fails audit because the typed address is unverified.
Four obligations on every Proof of Address:
1. Capture an acceptable document — utility bill, bank statement, government letter, lease, mortgage, mobile / internet contract — dated within the last 90 days.
2. Read the address fields with Optical Character Recognition (OCR) and parse them into the canonical address envelope (line 1, line 2, city, postal code, country).
3. Cross-check the address against the address on the underlying ID document AND against the name on both — a mismatched address or a mismatched name fails the check.
4. Where the country supports it, validate the parsed address against the authoritative address registry (UK Royal Mail PAF, Spain Catastro / Padrón, France BAN, Germany DATEV, US USPS).
Pricing (verified live):
- Proof of Address: $0.20 per check
- ID Verification (required as the cross-check anchor): $0.15 per check
- Database Validation (per-country registry validation, optional): variable per service
- Combined bundle (ID + Liveness + Face Match + Proof of Address): $0.55 per user
- First 500 verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60s, no card).
- Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
- A workflow_id from the Workflow Builder bundling ID Verification + Passive Liveness + Face Match 1:1 + Proof of Address. Add a Database Validation node for the country-specific address registry where available.
STEP 1 — Create the session
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<your proof-of-address workflow id>",
"vendor_data": "<your user id, max 256 chars>",
"callback_url": "https://<your-app>/onboarding/poa/callback",
"expected_country": "ES",
"metadata": {
"purpose": "regulatory_address_capture",
"user_id": "<your internal id>"
}
}
Response: 201 Created with the hosted session URL. SMS or email the URL to the user; they complete ID capture + selfie + Proof of Address upload on their phone in under five minutes.
STEP 2 — Read the signed webhook on completion
Didit POSTs to your callback. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"id_verification": { "status": "Approved", "document_type": "passport", "country_code": "ES" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"proof_of_address": {
"status": "Approved",
"document_type": "utility_bill",
"issuer": "Iberdrola",
"issued_at": "2026-04-12",
"address": {
"line1": "C. Diagonal 612",
"line2": "3a",
"city": "Barcelona",
"postal_code": "08021",
"country": "ES"
},
"cross_check": {
"name_match": true,
"address_match_with_id": true,
"within_90_day_window": true
}
},
"database_validation": {
"status": "Approved",
"service": "es_catastro_address",
"result": { "registry_match": true }
}
}
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 — Decide
Branch logic:
Approved → file the canonical address payload on the customer record.
In Review → hold the onboarding, wait for analyst webhook update.
Declined → refuse onboarding, log the decline reason (typically: document over 90 days old, name mismatch, address mismatch with the ID).
Resubmitted → user updated the upload; re-read the decision.
The Proof of Address sub-result is independent of the parent session — even if the parent session is Approved, the proof_of_address.status might be In Review if the cross-check flagged a different city. Switch on proof_of_address.status when you persist the address.
STEP 4 — Persist the canonical address envelope
When proof_of_address.status === "Approved", save the entire address object to your customer record as the regulatory current address. Use the canonical fields (line1, line2, city, postal_code, country) — Didit normalises across document layouts so the same shape works for an English utility bill, a Spanish bank statement, and a German Anmeldung.
Keep the issuer + issued_at fields for your audit log — they prove the document type and the recency window the regulator audited.
STEP 5 — Registry validation result
When the workflow includes a Database Validation node, the database_validation block returns the per-country registry-validation outcome:
- es_catastro_address — Spanish Catastro property registry
- uk_royal_mail_paf — UK Postcode Address File
- fr_ban — France Base Adresse Nationale
- de_anmeldung — German municipal registration check
- us_usps — US Postal Service address validation
A registry-match-false result on a country that supports validation is a signal worth manual review even if the OCR pass succeeded — most fake addresses fail registry validation immediately.
STEP 6 — Refresh on a cadence (optional)
Most regulators ask for the address on file to be re-confirmed every 1-3 years (longer for low-risk customers, shorter for high-risk). Add a periodic Proof of Address session to your account-refresh cadence — same workflow, same hosted URL flow.
WEBHOOK EVENT NAMES
- status.updated — session status changed.
- data.updated — session data changed (resubmission, document re-upload).
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).
- Acceptable documents must be dated within the last 90 days by default; some workflows extend to 180 days for low-risk customer segments.
- The address on the Proof of Address document MUST cross-check against the address on the underlying ID OR against a previously-Approved address on file. If neither match, the proof flips to In Review automatically.
- Default record retention is 5 years post-relationship per the EU AML package.
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/database-validation/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.
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+ zinafanya kazi, zinakaguliwa na kujaribiwa 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.
Kwa Kila Uthibitisho wa Anwani — OCR + ukaguzi mtambuka + uthibitishaji wa sajili.
0+
Nchi zilizo na uthibitishaji wa sajili ya anwani yenye mamlaka iliyojengwa ndani.
0+
Nchi zinazoungwa mkono kwa ujumla, na hati zinazokubalika kwa kila eneo.
0
Uthibitishaji wa bure kila mwezi, kwenye kila akaunti.
Ngazi tatu, orodha moja ya bei
Anza bure. Lipa kwa matumizi. Panua hadi Biashara.
Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, makazi ya data, na SLA (Mikataba ya Kiwango cha Huduma) kwenye Biashara.
Bure
Bure
$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.
Kifurushi cha KYC cha bure (Uthibitishaji wa Kitambulisho + Uhai Usio na Kazi + Kulinganisha Uso + Uchambuzi wa Kifaa na IP) — 500 / mwezi, kila mwezi
Watumiaji Waliozuiliwa
Kugundua Marudio
Ishara 200+ za udanganyifu kwenye kila kipindi
KYC inayoweza kutumika tena kwenye mtandao wa Didit
Jukwaa la Usimamizi wa Kesi
Mjenzi wa Mtiririko wa Kazi
Hati za umma, sandbox, SDKs, seva ya MCP (Model Context Protocol)