Ruka hadi maudhui makuu
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Uthibitisho wa Anwani

Thibitisha anwani yoyote.
Kutoka kwa bili, benki, au barua.

Thibitisha makazi kutoka kwa bili ya huduma, taarifa ya benki, barua ya serikali, au mkataba wa kukodisha. Tunasoma hati, tunatoa anwani, tunalinganisha jina na kitambulisho kilichothibitishwa, na tunarudisha matokeo yaliyopangwa. $0.20 kwa ukaguzi, 500 bure/mwezi.

Inaungwa mkono na
Y CombinatorRobinhood Ventures
Firecrawl
Slash
Crnogorski Telekom
UCSF Neuroscape
Bit2Me
Shiply

Inaaminika na mashirika 2,000+ duniani kote.

Didit Uthibitisho wa Anwani, pakia bili ya huduma au taarifa; tunai-OCR upande wa seva.

Bili + taarifa ya benki

Toa anwani.
Linganisha jina.

Tunasoma hati, tunatoa anwani na jina, na tunalinganisha zote mbili dhidi ya utambulisho uliothibitishwa. Bili ya huduma, taarifa ya benki, mkataba wa kukodisha, barua ya kodi , $0.20 kwa ukaguzi.

Jinsi inavyofanya kazi

Kutoka 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 kwa API yetu. Panga masharti, fanya majaribio ya A/B, hakuna msimbo unaohitajika.

  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, vidokezo vya 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 vyenye mamlaka. 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 kikao, kila ishara, na kudhibiti kesi kwa njia yako.

Imejengwa kwa waendelezaji · Imejengwa dhidi ya udanganyifu · Wazi kwa muundo

Uwezo sita. Feature flag moja. PROOF_OF_ADDRESS.

Kila uwezo hapa chini ni swichi kwenye moduli moja. Hakuna viwango vya kuongeza mauzo, hakuna SKU tofauti, hakuna simu za nyongeza. Ziwasha kwa kila mtiririko wa kazi au zipitishe moja kwa moja kwenye simu ya API.
01 · Nyaraka zinazokubalika

Bili, taarifa za benki, barua za serikali, mikataba ya pango.

Aina nne, bili ya huduma (umeme, maji, gesi, intaneti, simu), taarifa ya benki (akaunti, kadi ya mkopo, rehani, mkopo), iliyotolewa na serikali (tathmini ya kodi, kadi ya mpiga kura, cheti cha makazi), na nyinginezo (mkataba wa pango, barua ya mwajiri, bima, hati ya kiapo iliyothibitishwa). JPG, PNG, TIFF, au PDF hadi 15 MB. Kurasa nyingi huchakatwa kwa inference moja.
02 · Uchimbaji + uhalisi

Soma kila sehemu ya anwani. Gundua kila udanganyifu.

OCR (optical character recognition) huchota anwani ghafi na kuiweka katika muundo maalum, mtaa, jiji, mkoa, msimbo wa posta, aina ya anwani. Latitude na longitude zimejumuishwa. Mchakato huohuo hufanya uchunguzi wa uhalisi wa hati: kugundua udukuzi wa pixel, mabaki ya copy-paste / clone-stamp, utofauti wa fonti + kerning, ishara za picha bandia zilizotengenezwa na AI, na kutolingana kwa metadata. Hati zilizodukuliwa huwekwa kwenye `In Review` na onyo lililoandikwa, hazikubaliwi kimya kimya.
03 · Ukaguzi wa uhalali wa muda

Uhalali unaoweza kusanidiwa. Siku 90 kwa default.

Weka muda wa uhalali wa hati kwa kila application, siku 30, 60, 90, au muda wowote unaochagua. Default ni 90. Tunachota tarehe ya kutolewa na kuilinganisha na timestamp ya uwasilishaji; chochote kilicho cha zamani kuliko kizingiti hupungua kiotomatiki na `EXPIRED_DOCUMENT`. Hati zisizo na tarehe ya kutolewa inayoweza kuchanganuliwa, au zenye tarehe ya baadaye, huibua maonyo unayoweza kuelekeza kwenye ukaguzi wa mikono.
04 · Jina lilingane na KYC

Bili inalingana na ID. Au hailingani.

Maonyo matatu ya kutolingana kwa jina huibuka wakati jina la hati linatofautiana na utambulisho uliothibitishwa, thamani uliyotuma kupitia API, au uthibitisho mwingine wa anwani katika session hiyohiyo. Kizingiti cha kulinganisha kinachoweza kusanidiwa (kwa kawaida 90–95%) huvumilia jina la kati na tofauti za tahajia. Kila onyo huendana na Decline, Review, au Approve kwa kila application.
05 · Anwani iliyochanganuliwa na kupangwa

OCR inarudisha string. Didit inarudisha schema.

Kila jibu linajumuisha object ya anwani iliyochanganuliwa, mtaa, jiji, mkoa, msimbo wa posta, aina ya anwani, pamoja na kuratibu ghafi. Iweke kwenye rekodi ya mteja wako, fraud model, au routing ya utoaji. Hakuna regex, hakuna post-processing, hakuna parser ya nchi. Muundo uleule iwe hati ilitolewa USA, Hispania, Brazil, au Singapore.
06 · Tayari kwa kufuata sheria

Ushahidi wa AMLD6 na FATF Recommendation 10. $0.20 kwa kila ukaguzi.

Uthibitishaji wa anwani unahitajika na AMLD6 (EU's 6th Anti-Money Laundering Directive) customer-due-diligence na FATF Recommendation 10. Kila uamuzi huja na URL ya hati iliyosainiwa, array ya maonyo tayari kwa ukaguzi, na uchunguzi wa udanganyifu wa PDF overlay, afisa wako wa compliance ana ushahidi wote. Bei ya umma ya kulipia kwa kila simu, hakuna mkataba.
Unganisha

Endpoints mbili. JSON ileile. Bei ileile.

Unda kikao unapotaka UI yetu iliyopangishwa kushughulikia kunasa na kupakia kurasa nyingi. Piga endpoint inayojitegemea wakati tayari una hati. Muundo wa ripoti ni ule ule kwa njia zote mbili.
POST /v3/session/Hosted UI
$ 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_poa_eu",
    "vendor_data": "user-42"
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Tunahost capture UI. Multi-page PDF + auto-capture inashughulikiwa kwako.nyaraka →
POST /v3/poa/Server kwa server
$ curl -X POST https://verification.didit.me/v3/poa/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -F "document=@utility-bill.pdf" \
  -F "full_name=John A. Smith"
200OK{ "status": "Imeidhinishwa", "document_type": "BANK_STATEMENT" }
Wewe unamiliki data iliyokusanywa. Tunakurudishia ripoti kamili papo hapo.nyaraka →
Ujumuishaji tayari kwa agent

Tuma Uthibitisho wa Anwani kwa amri moja.

Bandika kizuizi kilicho hapa chini kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza kishika nafasi cha my_stack na mfumo wako, lugha, na matumizi. Agent itaweka Didit, kuunda mtiririko wa kazi, kuunganisha webhook, na kutuma.
didit-integration-prompt.md
# Didit Proof of Address — integrate in 5 minutes

You are integrating Didit's Proof of Address (PoA) module into <my_stack>.
Follow these steps exactly. Every URL, header, and enum value below is
canonical — do not paraphrase or "improve" them.

## 1. Provision an account
- Sign up: https://business.didit.me (no credit card required).
- Or provision programmatically: POST https://apx.didit.me/auth/v2/programmatic/register/
  (returns an API key bound to the workspace + application).

## 2. Two integration paths — pick one

### Path A — Workflow Builder (hosted UI)
Best when you want Didit to handle document capture, multi-page upload,
auto-capture, mobile handoff, and accessibility for you.

1. Create a workflow that contains the PROOF_OF_ADDRESS feature:
   POST https://verification.didit.me/v3/workflows/
   Authorization header:  x-api-key: <your-api-key>
   Body: workflow_label, features array with the single entry
         { feature: "PROOF_OF_ADDRESS" }   (UPPERCASE — strict enum)
   Optional config: accepted document_type filters
   (UTILITY_BILL, BANK_STATEMENT, GOVERNMENT_ISSUED_DOCUMENT,
   OTHER_POA_DOCUMENT) and per-warning threshold overrides.

2. Create a verification session for an end user:
   POST https://verification.didit.me/v3/session/
   Body: workflow_id (from step 1), vendor_data (your own user id).
   Response: session_url — redirect the user to it.

3. Listen for webhook callbacks (see "Webhooks" below).

### Path B — Standalone server-to-server API
Best when you already have a captured document image or PDF (mobile SDK
capture, native onboarding app, reseller pipeline).

POST https://verification.didit.me/v3/poa/
Content-Type: multipart/form-data
Body fields:
  - document     (required, file — JPG, JPEG, PNG, TIFF, or PDF, <= 15 MB)
  - vendor_data  (optional string, your user id)
  - full_name    (optional string, name to cross-check against the document)
  - address      (optional string, address to cross-check against the document)

Response: JSON report with the parsed address, document_type, issuer,
issue_date, name_on_document, and a warnings array.

## 3. Webhooks (Path A only — Path B returns synchronously)
- Register a webhook destination once via
  POST https://verification.didit.me/v3/webhook/destinations/
  Body: url, subscribed_events: ["session.verified", "session.review_started",
                                  "session.declined"]
- Response includes secret_shared_key — store it.
- 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.

## 4. Reading the report (both paths return the same shape)
The poa object includes:
- status: "Approved" | "Declined" | "In Review" | "Not Finished"
- issuing_state: ISO 3166-1 alpha-3 country code
- document_type: "UTILITY_BILL" | "BANK_STATEMENT" |
                 "GOVERNMENT_ISSUED_DOCUMENT" | "OTHER_POA_DOCUMENT" |
                 "UNKNOWN"
- issuer: string (the issuing institution or company)
- issue_date: YYYY-MM-DD
- expiration_date: YYYY-MM-DD or null
- document_language: ISO 639-1 language code
- name_on_document: string (full name extracted from the document)
- poa_address: raw extracted address string
- poa_formatted_address: normalized human-readable address string
- poa_parsed_address: structured object with street_1, street_2, city,
  region, postal_code, address_type, and raw_results.geometry.location
  (lat / lng for geocoding)
- document_file: signed URL to the captured document (expires in 60 minutes)
- document_metadata: optional file_size, content_type, creation_date,
  modified_date, and overlay_manipulation forensic block for PDFs (detected
  flag, signals such as duplicate_font_subset or glyph_fragmentation, and
  manipulated_regions in PDF page coordinates)
- warnings: Array<{ risk, additional_data, log_type, short_description,
                    long_description }>

Auto-decline risks (always enforced by Didit, not configurable):
- POA_DOCUMENT_NOT_SUPPORTED_FOR_APPLICATION
- EXPIRED_DOCUMENT
- INVALID_DOCUMENT_TYPE
- MISSING_ADDRESS_INFORMATION

Configurable risks (action per workflow — Decline, Review, or Approve):
- NAME_MISMATCH_WITH_PROVIDED
- NAME_MISMATCH_ID_VERIFICATION
- POA_NAME_MISMATCH_BETWEEN_DOCUMENTS
- POOR_DOCUMENT_QUALITY
- DOCUMENT_METADATA_MISMATCH
- SUSPECTED_DOCUMENT_MANIPULATION
- UNSUPPORTED_DOCUMENT_LANGUAGE
- ADDRESS_MISMATCH_WITH_PROVIDED
- UNABLE_TO_EXTRACT_ISSUE_DATE
- UNPARSABLE_OR_INVALID_ADDRESS
- ISSUER_NOT_IDENTIFIED
- UNABLE_TO_VALIDATE_DOCUMENT_AGE
- FUTURE_ISSUE_DATE

## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: PROOF_OF_ADDRESS, ID_VERIFICATION, LIVENESS,
  FACE_MATCH, AML, IP_ANALYSIS.
- document_type enum is UPPERCASE_SNAKE: UTILITY_BILL, BANK_STATEMENT,
  GOVERNMENT_ISSUED_DOCUMENT, OTHER_POA_DOCUMENT, UNKNOWN.
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Always verify webhook signatures before trusting payload data.
- Status casing matches exactly: "Approved", "Declined", "In Review",
  "Not Finished" (title-cased, space-separated).
- Documents must be issued within 90 days of submission — older documents
  trigger the EXPIRED_DOCUMENT auto-decline regardless of policy.
- The PoA document must be different from the document submitted for ID
  Verification — same image triggers POA_DOCUMENT_NOT_SUPPORTED.

## 6. Accepted document types (do not paraphrase to users)
- Utility Bill — Electricity, Water, Gas, Internet, Phone, Cable TV,
  Satellite TV, Trash Collection, Sewage, Heating, Combined Utilities,
  Municipal Services.
- Bank Statement — Account Statement, Credit Card Statement, Bank Letter
  Confirming Address, Mortgage Statement, Loan Statement, Savings,
  Checking, Investment, Business Account, Credit Union, Debit Card,
  Line of Credit.
- Government-Issued Document — Tax Assessment, Voter Registration Card,
  ID document, Residency Certificate, Government Letter, Census Letter,
  Property Tax Bill, Vehicle Registration, Social Security Statement,
  Unemployment Benefits Letter, Pension Statement, Court Summons,
  Municipal Permit, Immigration Document.
- Other Proof of Address — Lease Agreement, Rental Agreement, Employer
  Letter Confirming Address, Insurance Policy, School Enrollment Letter,
  Notarized Affidavit, Solicitor Letter, Payroll Stub, Employment
  Verification Letter, Retirement / Brokerage Account Statement.

Image requirements: JPG, JPEG, PNG, TIFF, or PDF. Maximum file size 15 MB.
Full-color, all corners visible, no digital editing, all pages included
for multi-page documents.

## 7. Pricing reference (public)
- Standalone /v3/poa/ call: $0.20 per check.
- Bundled inside a Didit workflow (KYC plus PoA): $0.20 per check on top
  of the bundle base.
- 500 free verifications every month, forever, on every account.

## 8. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test documents: deterministic synthetic bills returned in sandbox
  (Approved by default; trigger Declined by submitting the canonical
  "expired" test bill from the sandbox sample pack).
- Switch to live: flip the application's environment toggle in console.

When in doubt: https://docs.didit.me/core-technology/proof-of-address/overview
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
Jugendschutz geprüft
FSM · JMStV §4(2) · 2026
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
    Aina za nyaraka, bili ya huduma, taarifa ya benki, hati ya serikali, nyinginezo.
  • 0d
    Umri wa juu zaidi wa tarehe ya kutolewa kabla ya kukataliwa kiotomatiki.
  • <0s
    Uthibitishaji kamili wa Proof of Address.
  • $0.00
    Kwa kila ukaguzi wa Proof of Address unaojitegemea.
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
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
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

Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.

FAQ

Maswali ya kawaida

Didit ni nini?

Didit ni miundombinu ya utambulisho na udanganyifu, jukwaa ambalo tulitamani lingekuwepo tulipokuwa tukijenga bidhaa sisi wenyewe: wazi, rahisi kubadilika, na rafiki kwa watengenezaji, ili lifanye kazi kama sehemu halisi ya stack yako badala ya sanduku jeusi unalounganisha.

API moja inashughulikia kuthibitisha watu (KYC, mjue mteja wako), kuthibitisha biashara (KYB, mjue biashara yako), kuchunguza pochi za crypto (KYT, mjue muamala wako), na kufuatilia miamala kwa wakati halisi, kwenye stack iliyojengwa kuwa:

  • Haraka, chini ya sekunde 2 p99 kwenye kila kipindi
  • Inaaminika, inatumika na kampuni 1,500+ katika nchi 220+
  • Salama, SOC 2 Aina ya 1, ISO 27001, GDPR-native, na kuthibitishwa rasmi na mdhibiti wa kifedha wa Uhispania kuwa salama zaidi kuliko kumthibitisha mtu ana kwa ana

Alama ya 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 inaboreshwa kila siku.

Uthibitisho wa Anwani ni nini?

Uthibitisho wa Anwani (PoA) ni uthibitishaji wa makazi ya mtu kwa kutumia bili ya huduma, taarifa ya benki, barua ya serikali, au mkataba wa kukodisha, iliyopigwa picha, iliyotolewa kwa kutumia Optical Character Recognition (OCR), iliyothibitishwa, na kurudishwa kama anwani iliyopangwa kwa sekunde.

Didit inashughulikia upigaji picha wa hati, inachanganua mtoaji na tarehe ya kutolewa, inaendesha uchunguzi wa kugundua udanganyifu, inalinganisha jina na Hati ya Utambulisho iliyothibitishwa, inarekebisha anwani kuwa sehemu zilizopangwa (street_1, city, region, postal_code), na kuiweka kwenye ramani.

$0.20 kwa kila ukaguzi. Marejeleo kamili: docs.didit.me/core-technology/proof-of-address.

Uthibitisho wa Anwani unagharimu kiasi gani?

$0.20 kwa simu ya pekee ya POST /v3/poa/, au $0.20 inapounganishwa kwenye mtiririko wa Didit juu ya msingi wa kifurushi.

Hakuna kiwango cha chini cha kila mwezi, hakuna mkataba, hakuna mshangao wa ziada, bei kwenye didit.me/pricing ndiyo bei kwenye ankara. Punguzo la kiasi huanza kiotomatiki unapoendelea kukua.

Uthibitishaji ni wa haraka kiasi gani kwa mtumiaji wangu wa mwisho?

Mtiririko kamili kwa kawaida huchukua chini ya sekunde 30 kuanzia mwanzo hadi mwisho, chukua kitambulisho, piga picha hati, piga selfie, umemaliza. Hiyo ndiyo kasi zaidi sokoni. Watoa huduma wa zamani wa KYC kwa kawaida huchukua zaidi ya sekunde 90 kwa mtiririko huo huo.

Kwa upande wa nyuma, Didit inarudisha matokeo kwa chini ya sekunde mbili kwa p99, ikipimwa kutoka wakati mtumiaji anamaliza selfie hadi wakati webhook yako inawaka. Upigaji picha 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 msimbo wa QR ikiwa mtumiaji anaanza kwenye wavuti.

Umbo la majibu ni nini?

Kitu kimoja cha poa JavaScript Object Notation (JSON) kwenye ripoti ya kipindi na kwenye Application Programming Interface (API) ya pekee:

  • status, Approved, Declined, In Review, Not Finished.
  • document_type, issuer, issue_date (YYYY-MM-DD), expiration_date, document_language.
  • name_on_document, poa_address (mwandiko ghafi wa Optical Character Recognition (OCR)), poa_formatted_address (iliyorekebishwa).
  • poa_parsed_address, iliyopangwa street_1, street_2, city, region, postal_code, address_type, na kuratibu za jiometri za raw_results kwa ajili ya geocoding.
  • Uniform Resource Locator (URL) ya document_file iliyosainiwa ambayo inaisha muda wake baada ya dakika 60.

Uwasilishaji wa Portable Document Format (PDF) pia unajumuisha kizuizi cha uchunguzi cha document_metadata.overlay_manipulation. Marejeleo kamili: docs.didit.me/core-technology/proof-of-address/report-proof-of-address.

Nini kinatokea ikiwa mtumiaji atashindwa, kuacha, au muda wake kuisha?

Kila kipindi huangukia kwenye mojawapo ya hali saba zilizo wazi, kwa hivyo msimbo wako unajua nini cha kufanya kila wakati:

  • Approved, kila ukaguzi umefaulu. Mpeleke mtumiaji mbele.
  • Declined, ukaguzi mmoja au zaidi umeshindwa. Unaweza kumruhusu mtumiaji kutuma tena hatua maalum iliyoshindwa (kwa mfano, piga tena selfie) bila kuendesha tena mtiririko mzima.
  • In Review, imewekwa alama kwa ukaguzi wa kufuata. Fungua kesi kwenye console, angalia kila ishara, amua kuidhinisha au kukataa.
  • In Progress, mtumiaji yuko katikati ya mtiririko.
  • Not Started, kiungo kimetumwa, mtumiaji bado hajafungua. Tuma ukumbusho ikiwa inakaa 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 inakaa sawa kila wakati. Vipindi vilivyoachwa na vilivyokataliwa ni bure.

Data ya mteja wangu inakaa wapi na inalindwa vipi?

Data ya uzalishaji inachakatwa na kuhifadhiwa katika Umoja wa Ulaya kwa chaguo-msingi, kwenye Amazon Web Services. Mikataba ya biashara inaweza kuomba mikoa mbadala kwa mamlaka ambazo wadhibiti wao wanahitaji.

Usimbaji fiche kila mahali. AES-256 wakati wa kupumzika kwenye kila database, hifadhi ya kitu, na chelezo. Transport Layer Security 1.3 wakati wa usafiri kwenye kila simu ya API, webhook, na kipindi cha Business Console. Data ya biometriska imesimbwa chini ya Kitufe tofauti cha Mwalimu wa Mteja.

Uhifadhi ni wako kudhibiti. Uhifadhi wa chaguo-msingi ni usio na kikomo (usio na ukomo) isipokuwa ukisanidi mfupi, kati ya siku 30 na miaka 10 kwa kila programu, na unaweza kufuta kipindi chochote cha kibinafsi wakati wowote kutoka kwenye dashibodi au API.

Vyeti: SOC 2 Aina ya 1 (ukaguzi wa Aina ya 2 unaendelea), ISO/IEC 27001:2022, iBeta Level 1 PAD, na uthibitisho wa umma kutoka Tesoro / SEPBLAC / CNMV ya Uhispania kwamba uthibitishaji wa utambulisho wa mbali wa Didit ni salama zaidi kuliko kumthibitisha mtu ana kwa ana. Ripoti kamili kwenye /security-compliance.

Je, Didit inatii sheria kwa tasnia yangu?

Didit inatii sheria kwa chaguo-msingi kwa wadhibiti muhimu kwa miundombinu ya utambulisho:

  • GDPR + UK GDPR, mgawanyo wa mtawala / mchakataji, Mkataba kamili wa Uchakataji wa Data ulichapishwa, mamlaka kuu ya usimamizi imetajwa (AEPD ya Uhispania).
  • AMLD6 + EU AML Single Rulebook, vikwazo 1,300+, mtu aliye wazi kisiasa, na orodha za vyombo vya habari hasi zilizochunguzwa kwa wakati halisi.
  • eIDAS 2.0, EU Digital Identity Wallet imepangiliwa; tayari kwa utambulisho unaoweza kutumika tena.
  • MiCA (Markets in Crypto-Assets), tayari kwa njia za kuingia za crypto, kubadilishana, na walinzi.
  • DORA, Sheria ya Ustahimilivu wa Uendeshaji wa Dijitali, ustahimilivu wa uendeshaji wa huduma za kifedha za EU.
  • BIPA, CUBI, Washington HB 1493, CCPA / CPRA, faragha ya biometriska ya Marekani (Illinois, Texas, Washington) na faragha ya watumiaji wa California.
  • Sheria ya Usalama Mtandaoni ya Uingereza, majukumu ya kuweka umri na usalama wa watoto.
  • FATF Travel Rule, data ya mwanzilishi na mnufaika kwenye uhamishaji wa crypto, IVMS-101 inayoendana.

Memo ya kina, kila cheti, kila barua ya mdhibiti: /security-compliance.

Ninaweza kuunganisha na kuanza kuthibitisha watumiaji haraka kiasi gani?
  • Sekunde 60 kwa akaunti ya sandbox kwenye business.didit.me, hakuna kadi ya mkopo.
  • Dakika 5 kwa uthibitishaji unaofanya kazi kupitia Claude Code, Cursor, au wakala yeyote wa kuweka msimbo kupitia seva yetu ya Model Context Protocol (MCP).
  • Wikiendi moja kwa ujumuishaji tayari wa uzalishaji na uthibitishaji wa webhook iliyosainiwa, majaribio tena, na mtiririko wa kurekebisha wakati mtumiaji anakataliwa.

Njia tatu za ujumuishaji, chagua inayolingana na stack yako:

  • Pachika asili na Web, iOS, Android, React Native, au Flutter SDK yetu.
  • Elekeza upya mtumiaji kwenye ukurasa wa uthibitishaji uliopangishwa, hakuna SDK.
  • Tuma kiungo kwa barua pepe, SMS, WhatsApp, au chaneli yoyote, hakuna kazi ya mbele.

Dashibodi sawa, bili sawa, bei sawa ya kulipa kwa mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua kwenye docs.didit.me/integration/integration-prompt.

Miundombinu ya utambulisho na udanganyifu.

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

Uliza AI ifupishe ukurasa huu