Endesha mchakato wa uthibitishaji kwenye domain yako, na nembo yako, rangi zako, na mtumaji wako, hakuna chapa ya Didit popote watumiaji wako wanapoangalia. $0.20 kwa kila kipindi juu ya bei ya moduli.
Robinhood Ventures
Inaaminika na mashirika 2,000+ duniani kote.
Chapa yako, uamuzi wetu
Pangisha mtiririko kwenye domain yako. Badilisha nembo, rangi, maandishi, na kadi ya hakikisho la kiungo. Bei ya moduli inabaki vile vile, $0.20 kwa kila kipindi ndio nyongeza pekee.
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, endesha majaribio ya A/B, hakuna code inayohitajika.
Pachika kiasili na Web, iOS, Android, React Native, au Flutter SDK yetu. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu kiungo kwa mtumiaji wako, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.
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 mamlaka. Matokeo chini ya sekunde mbili.
Webhooks zilizosainiwa kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Uliza API inapohitajika. Au fungua console kukagua kila kipindi, kila ishara, na kudhibiti kesi zako mwenyewe.
# Console -> White Label -> Kihariri cha Mtindo
colors: paleti ya chapa
logos: mraba + mstatili
typography: font ya chapa + uzito
domain: verify.acme.com
email_from: verify@acme.com
# Workflow -> Mipangilio -> Chaguzi
include_custom_style: trueChapa yako · `verify.acme.com` · TLS auto$ 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_acme_kyc",
"vendor_data": "user-42"
}'{ "session_url": "verify.acme.com/..." }# Didit White Label — integrate in 5 minutes
You are integrating Didit's White Label (custom branding + custom domain)
into <my_stack>. White Label is a CONFIGURATION on top of any workflow —
not a separate API endpoint. Follow these steps exactly. Every URL,
header, and field 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. Configure White Label in the console
White Label settings live at Console -> White Label -> Style Editor. Five
groups, every one is customizable:
- Colors — buttons, text, panels, backgrounds (every color element)
- Typography — upload a brand font, set heading + body weights
- Logos — square + rectangular variants, served on every screen
- Layout — border radius for panels, buttons, inputs
- Login screen — show or skip the user-login step entirely
- Custom domain — host the verification UI on your own subdomain
(e.g. verify.acme.com) instead of verify.didit.me
Custom-domain setup:
1. Console -> White Label -> Custom Domain -> Add domain
2. We return a CNAME target. Point your subdomain CNAME at it.
3. Click Verify. We provision a TLS certificate via Let's Encrypt /
ACME (automatic renewal, no action required from you).
4. Domain becomes live within minutes.
Custom email-from:
- Console -> White Label -> Email -> set the "From" name + reply-to address.
- DKIM / SPF records returned for you to add to DNS.
## 3. Enable White Label on each workflow
The customization does NOT auto-apply. You enable it per workflow:
1. Console -> Workflows -> open the workflow you want to brand.
2. Click Settings (gear icon).
3. Under Options, find "Include custom style".
4. Enable the toggle. Save.
Workflows without the toggle keep the default Didit branding — useful for
sandbox flows you do not want to brand yet.
## 4. Use the white-labeled workflow from your stack
Once the workflow has white-label enabled, you call it the same way as any
other Didit workflow:
POST https://verification.didit.me/v3/session/
Authorization header: x-api-key: <your-api-key>
Body:
- workflow_id (required, your white-labeled workflow id)
- vendor_data (optional, your own user id)
- callback (optional, URL we redirect to after the flow)
Response: { session_url } — redirect the user there. The UI they see is
your brand (your logo, your colors, your typography), on your domain
(verify.acme.com), with your "From" name on every email we send to the
user mid-flow.
## 5. Webhooks
- 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", "session.kyc_expired"]
- 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.
## 6. Hard rules - do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Status casing matches exactly: "Approved", "Declined", "In Review",
"Not Finished" (title-cased, space-separated).
- White Label is a configuration on a workflow — there is NO standalone
/v3/white-label/ endpoint. Do not invent one.
- Removing visible Didit branding does NOT remove your obligations as the
controller of the user journey. You still surface your privacy notice,
link Didit's Verification Privacy Notice + End User Terms, and collect
explicit consent before document + biometric capture where the law
requires it. See https://docs.didit.me/console/white-label for the full
controller-side checklist.
## 7. Reseller / OEM positioning
White Label is the same product your agency, integrator, or compliance-
consulting firm uses to resell Didit under your own name to your own
customers:
- Pricing: $0.20 per session on top of the underlying module price (e.g.
full Know Your Customer (KYC) bundle at $0.33 + $0.20 white label = $0.53 per session, or
standalone ID at $0.15 + $0.20 = $0.35).
- 500 free verifications per month stay applied to your own meter,
regardless of how many resold tenants you have.
- One contract with Didit, one invoice — your customers see only your
brand and your support address.
- Custom email-from + custom domain mean your customers never see Didit
branding mid-flow. We still surface the legally-required disclosures
per the controller-side checklist above.
## 8. Pricing reference (public)
- White Label add-on: $0.20 per session, on top of the underlying module
price. A full KYC bundle goes from $0.33 to $0.53 per white-labeled
session; a standalone $0.15 ID Verification goes to $0.35.
- 500 free verifications every month, forever, on every account — applies
regardless of whether the flow is white-labeled.
- No setup fee, no certificate cost, no per-domain charge.
## 9. Verify your integration
- Sandbox starts on signup at https://business.didit.me - no separate flag.
- Test custom domain locally by adding a /etc/hosts entry pointing your
brand subdomain at our CNAME target before DNS is live.
- Switch to live: flip the application's environment toggle in console.
When in doubt: https://docs.didit.me/console/white-label
$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.
Lipa tu kwa unachotumia. Moduli 25+. Bei za umma kwa kila moduli, hakuna ada ya chini ya kila mwezi.
MSA & SLA maalum. Kwa idadi kubwa na programu zilizodhibitiwa.
Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.
Didit ni miundombinu ya utambulisho na udanganyifu, jukwaa ambalo tulitamani lingekuwepo tulipokuwa tukijenga bidhaa sisi wenyewe: wazi, rahisi, na rafiki kwa waendelezaji, 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:
Alama ya miguu chini: aina 14,000+ za hati katika lugha 48+, vyanzo vya data 1,000+, na ishara 200+ za udanganyifu kwa kila kipindi. Miundombinu ya Didit hujifunza kwa nguvu kutoka kwa kila kipindi na inaboresha kila siku.
White Label huendesha mchakato mzima wa uthibitishaji wa Didit chini ya chapa yako, domain yako maalum (verify.acme.com), nembo yako, palette yako ya rangi, uchapaji wako, mtumaji wako wa barua pepe, favicon yako. Hakuna chapa ya Didit inayoonekana kwa watumiaji wako.
API (Application Programming Interface) ileile ya /v3/. Mchakato uleule wa kukamata ulioandaliwa. Mkataba uleule wa webhook wa HMAC (Hash-based Message Authentication Code) wa X-Signature-V2. Bomba lilelile lililothibitishwa na Spain Tesoro / Banco de España (BdE) / Spanish Financial Intelligence Unit (SEPBLAC).
$0.20 kwa kila kipindi juu ya bei ya moduli ya msingi. Marejeleo kamili: docs.didit.me/console/white-label.
$0.20 kwa kila kipindi, juu ya bei ya moduli ya msingi.
$0.33 hadi $0.53 kwa kila kipindi cha white-labeled.$0.15 huenda hadi $0.35.Hakuna ada ya kuanzisha, hakuna gharama ya cheti, hakuna malipo kwa kila domain. Bei za umma: didit.me/pricing.
Mchakato mzima kwa kawaida huchukua chini ya sekunde 30 kuanzia mwanzo hadi mwisho, chukua kitambulisho, piga picha hati, piga picha ya selfie, umemaliza. Hiyo ndiyo kasi zaidi sokoni. Watoa huduma wa zamani wa KYC kwa kawaida huchukua zaidi ya sekunde 90 kwa mchakato uleule.
Kwa upande wa nyuma, Didit hurejesha matokeo kwa chini ya sekunde mbili kwa p99, ikipimwa kutoka wakati mtumiaji anamaliza selfie hadi wakati webhook yako inawaka. Ukamataji wa simu umeboreshwa kwa simu za polepole na mitandao ya polepole: ukandamizaji wa picha unaoendelea, upakiaji wa polepole wa SDK (Software Development Kit), na uhamishaji wa kugusa mara moja kutoka desktop kwenda simu kupitia msimbo wa QR ikiwa mtumiaji anaanza kwenye wavuti.
Dakika tatu, hakuna kazi ya cheti.
1. Kwenye Business Console nenda kwenye White Label → Custom Domain → Add domain. 2. Tunarejesha lengo la CNAME (Canonical Name). 3. Elekeza CNAME ya subdomain ya chapa yako kwake. 4. Bofya Verify.
Tunatoa cheti cha TLS (Transport Layer Security) kupitia Let's Encrypt na itifaki ya ACME (Automatic Certificate Management Environment), tunaweka upya kiotomatiki, na domain inaanza kutumika ndani ya dakika chache.
Hakuna ununuzi wa cheti, hakuna mzunguko wa funguo, hakuna safari ya kwenda na kurudi ya DNS (Domain Name System) na timu yako ya usalama. Usasishaji ni wa kiotomatiki kwa maisha yote ya domain.
Kila kipindi huishia kwenye mojawapo ya hali saba zilizo wazi, kwa hivyo msimbo wako unajua nini cha kufanya kila wakati:
Approved, kila ukaguzi umepita. Endeleza mtumiaji.Declined, ukaguzi mmoja au zaidi umeshindwa. Unaweza kumruhusu mtumiaji kutuma tena hatua maalum iliyoshindwa (kwa mfano, piga tena selfie) bila kuendesha upya mchakato 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 mchakato.Not Started, kiungo kimetumwa, mtumiaji bado hajafungua. Tuma ukumbusho ikiwa itakaa muda mrefu sana.Abandoned, mtumiaji alifungua kiungo lakini hakumaliza kwa wakati. Rudisha ushiriki au muda wake uishe.Expired, kiungo cha kipindi kimepitwa na wakati. Unda kipindi kipya.Webhook iliyosainiwa huwaka kwa kila mabadiliko ya hali, kwa hivyo database yako inabaki sawa kila wakati. Vipindi vilivyoachwa na vilivyokataliwa ni bure.
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. TLS (Transport Layer Security) 1.3 wakati wa usafiri kwenye kila simu ya API, webhook, na kipindi cha Business Console. Data ya biometriska imesimbwa kwa ufunguo tofauti wa Mteja Mkuu.
Uhifadhi ni wako kudhibiti. Uhifadhi wa chaguo-msingi ni usio na kikomo (unlimited) 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 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 ileile, bili ileile, bei ileile ya kulipia-kwa-mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua unapatikana docs.didit.me/integration/integration-prompt.
API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.