Bili za huduma, taarifa za benki, barua za serikali, zinasomwa, kuchambuliwa, kulinganishwa na kitambulisho, kuthibitishwa dhidi ya rejista ya anwani ya nchi. $0.20 kwa kila ukaguzi. Uthibitishaji 500 bure kila mwezi.
Inaaminika na mashirika 2,000+ duniani kote.
Kile ambacho jukwaa lililodhibitiwa linadaiwa
Anwani iliyoandikwa mwenyewe inashindwa ukaguzi. Bili ya huduma iliyochanganuliwa ambayo haijalinganishwa na 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 kilichosainiwa kwa $0.20 kwa kila ukaguzi.
Chagua ukaguzi unaotaka, ID, 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.
$ 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_proof_of_address",
"vendor_data": "user-42",
"expected_country": "ES"
}'URL iliyopangishwa · mtumiaji anapakia kitambulisho + selfie + POA.$ curl https://verification.didit.me/v3/session/$SESSION/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
# Decision payload (excerpted):
{ "proof_of_address": { "status": "Approved", "address": { ... } },
"database_validation": { "service": "es_catastro_address", "result": { "registry_match": true } } }registry_match kweli → uthibitisho wa makazi wenye uhakika mkubwa.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.
Kwa ajili ya kuunda, kujaribu, na watumiaji wako wa kwanza.
Moduli 25+, bei wazi. Punguzo la kiotomatiki kwa wingi.
Kwa kiasi kikubwa na programu zilizodhibitiwa.
Punguzo la wingi hutumika kiotomatiki kadri matumizi yanavyoongezeka — hakuna mazungumzo, hakuna simu ya mauzo.
Didit ni miundombinu ya utambulisho na udanganyifu, jukwaa ambalo tulitamani lingekuwepo tulipokuwa tukijenga bidhaa sisi wenyewe: wazi, rahisi kubadilika, na rafiki kwa waendelezaji, ili lifanye kazi kama sehemu halisi ya stack yako badala ya black box unayounganisha.
API moja inashughulikia kuthibitisha watu (KYC, know your customer), kuthibitisha biashara (KYB, know your business), kuchunguza pochi za crypto (KYT, know your transaction), na kufuatilia miamala kwa wakati halisi, kwenye stack iliyojengwa kuwa:
Nyayo chini: aina 14,000+ za nyaraka katika lugha 48+, vyanzo vya data 1,000+, na ishara za udanganyifu 200+ kwenye kila kipindi. Miundombinu ya Didit hujifunza kwa nguvu kutoka kila kipindi na inaboresha kila siku.
Uthibitisho wa Anwani ni kama jina linavyosema, ushahidi kwamba mtu unayemuingiza kwenye mfumo anaishi kweli kwenye anwani anayodai. Nyaraka za kawaida ni:
Kwa nini wadhibiti wanajali: anwani iliyohifadhiwa ni msingi wa utunzaji wa kumbukumbu za kupambana na utakatishaji fedha, ripoti za makazi ya kodi (FATCA / CRS), na mamlaka ya kisheria ya utekelezaji wowote wa baadaye. Anwani iliyoandikwa mwenyewe haiwezi kuthibitishwa; Uthibitisho wa Anwani unaoungwa mkono na hati ya hivi karibuni + ukaguzi dhidi ya kitambulisho ndio kiwango. Didit inatoa "recipe" kamili kwa $0.20 kwa kila ukaguzi.
Sababu tatu ambazo wadhibiti mara kwa mara hukataa anwani zilizojitolea:
"Recipe" ya Uthibitisho wa Anwani, kukamata, OCR, kulinganisha, uthibitisho wa rejista, inatoa hati ya kiwango cha mdhibiti kwa chini ya dakika tano kwenye simu ya mtumiaji. $0.20 kwa kila ukaguzi kutoka mwanzo hadi mwisho.
Mchakato mzima kwa kawaida huchukua chini ya sekunde 30 kutoka mwanzo hadi mwisho, chukua kitambulisho, piga picha hati, piga selfie, umemaliza. Huu ndio mchakato wa haraka zaidi sokoni. Watoa huduma wa zamani wa KYC kwa kawaida huchukua zaidi ya sekunde 90 kwa mchakato huo huo.
Kwa upande wa "back end", Didit inarudisha matokeo kwa chini ya sekunde mbili kwa p99, ikipimwa kutoka wakati mtumiaji anamaliza selfie hadi wakati webhook yako inapoanza. Ukamataji wa simu umeboreshwa kwa simu za polepole na mitandao ya polepole: ukandamizaji wa picha unaoendelea, upakiaji wa polepole wa SDK, na uhamishaji wa kugusa mara moja kutoka kompyuta hadi simu kupitia QR code ikiwa mtumiaji anaanza kwenye wavuti.
Ukisimama tu kwenye "pakia bili yako ya huduma", mshambuliaji mwenye nia mbaya anaweza:
"Recipe" ya Didit inakamata yote manne kwa kuweka tabaka tatu za uthibitisho juu ya OCR:
Haya yote yanaendeshwa upande wa server. Wakala haoni upakiaji ghafi, bali matokeo yaliyothibitishwa tu.
Kila kipindi kinaishia kwenye mojawapo ya hali saba zilizo wazi, kwa hivyo code yako inajua nini cha kufanya kila wakati:
Approved, kila ukaguzi umefaulu. Endeleza mtumiaji.Declined, ukaguzi mmoja au zaidi umeshindwa. Unaweza kumruhusu mtumiaji kuwasilisha tena hatua maalum iliyoshindwa (kwa mfano, piga tena selfie) bila kurudia mchakato mzima.In Review, imewekwa alama kwa ukaguzi wa kufuata sheria. Fungua kesi kwenye console, angalia kila ishara, amua kuidhinisha au kukataa.In Progress, mtumiaji yuko katikati ya mchakato.Not Started, kiungo kimetumwa, mtumiaji bado hajafungua. Tuma ukumbusho ikiwa itakaa muda mrefu sana.Abandoned, mtumiaji alifungua kiungo lakini hakumaliza kwa wakati. Mshirikishe tena au muda wake uishe.Expired, kiungo cha kipindi kimeisha muda wake. Unda kipindi kipya.Webhook iliyosainiwa inawaka kwenye kila mabadiliko ya hali, kwa hivyo database yako inabaki sawa kila wakati. Vipindi vilivyoachwa na vilivyokataliwa ni bure.
Data ya uzalishaji huchakatwa na kuhifadhiwa katika Umoja wa Ulaya kwa chaguo-msingi, kwenye Amazon Web Services. Mikataba ya biashara inaweza kuomba maeneo mbadala kwa mamlaka ambazo wasimamizi wake wanahitaji.
Usimbaji fiche kila mahali. AES-256 ikiwa imetulia kwenye kila database, hifadhi ya object, na backup. Transport Layer Security 1.3 ikiwa safarini kwenye kila API call, webhook, na kipindi cha Business Console. Data ya kibayometriki imesimbwa kwa kutumia Customer Master Key tofauti.
Uhifadhi ni wako kudhibiti. Uhifadhi chaguomsingi ni usio na kikomo (unlimited) isipokuwa ukisanidi muda mfupi zaidi, kati ya siku 30 na miaka 10 kwa kila application, na unaweza kufuta kipindi chochote cha kibinafsi wakati wowote kutoka kwenye dashboard au API.
Vyeti: SOC 2 Type 1 & Type 2, ISO/IEC 27001:2022, iBeta Level 1 PAD, na uthibitisho wa umma kutoka Tesoro / SEPBLAC / CNMV ya Hispania kwamba uthibitishaji wa utambulisho wa mbali wa Didit ni salama zaidi kuliko kumthibitisha mtu ana kwa ana. Ripoti kamili inapatikana /security-compliance.
Didit inatii sheria kwa chaguo-msingi kwa wadhibiti muhimu kwa miundombinu ya utambulisho:
Memo ya kina, kila cheti, kila barua ya mdhibiti: /security-compliance.
Njia tatu za kuunganisha, chagua inayofaa stack yako:
Dashibodi sawa, bili sawa, bei sawa ya kulipa kwa mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua unapatikana kwenye docs.didit.me/integration/integration-prompt.
Wadhibiti wengi wanataka hati ya Uthibitisho wa Anwani iwe na tarehe ndani ya siku 90 zilizopita wakati wa uthibitishaji, chochote cha zamani kinachukuliwa kuwa kimepitwa na wakati kwa dhana kwamba mtumiaji anaweza kuwa amehamia tangu wakati huo.
OCR ya Didit inasoma tarehe ya hati na kuiangalia dhidi ya muhuri wa muda wa uthibitishaji kiotomatiki:
within_90_day_window: true → uthibitisho unapita ukaguzi wa hivi karibuniwithin_90_day_window: false → kipindi kinabadilika kuwa In Review na mtumiaji anaombwa kupakia hati ya hivi karibuni zaidiKwa sehemu za wateja wenye hatari ndogo unaweza kusanidi mtiririko wa kazi ili kupanua dirisha hadi siku 180, au kulipunguza hadi siku 60 kwa sehemu za hatari kubwa. Usanidi ni kwa kila mtiririko wa kazi, sio kwa kila kipindi, kwa hivyo mabadiliko yanatumika sawasawa. Sheria ya UK Right to Rent inatumia siku 90; mwongozo wa EU AML kwa ujumla unakubali siku 90-180 kulingana na msimamizi.
Wadhibiti wengi huomba anwani iliyohifadhiwa ithibitishwe tena mara kwa mara:
Upyaji wa Didit ni POST /v3/session/ sawa dhidi ya mtiririko wako wa kazi wa Uthibitisho wa Anwani na vendor_data ya mteja aliyepo. Hati mpya inachukua nafasi ya ile ya awali kwenye faili ya mteja; zote mbili zinahifadhiwa kwenye "audit trail". Panga upyaji kutoka kwenye "customer-data pipeline" yako, Didit haianzishi upyaji kiotomatiki kwa sababu mzunguko unategemea sera yako ya hatari.
Watoa huduma wengi wa KYC huweka bei ya Uthibitisho wa Anwani kati ya $0.50 na $2.00 kwa kila ukaguzi, mara nyingi kama kipengee tofauti juu ya msingi wa KYC wa juu, na ada za ziada za nchi kwa uthibitisho wowote wa rejista. Mfano wa Onfido / Jumio / Veriff.
Bei iliyochapishwa ya Didit ni $0.20 kwa Uthibitisho wa Anwani + $0.15 kwa Uthibitishaji wa Kitambulisho cha msingi (unahitajika kama nanga ya kulinganisha) = $0.35 kwa "recipe" iliyounganishwa. Uthibitishaji wa Database unaongeza gharama tofauti kwa kila nchi, kwa kawaida $0.05-$0.20. Hakuna kiwango cha chini, hakuna kiwango cha chini kabisa, hakuna ada ya ziada kwa kila nchi.
Hiyo ni takriban mara 3-5 nafuu zaidi kuliko stack iliyopo kwenye matokeo sawa ya udhibiti. Kwa watumiaji 50,000 kwa mwezi, akiba dhidi ya mtoa huduma wa POA wa $1.50 ni karibu $65,000 kwa mwaka. Bei kamili inapatikana kwenye /pricing.
API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.