شغّل سير عمل التحقق على نطاقك الخاص، بشعارك، ألوانك، ومرسلك, بدون أي علامة تجارية لـ Didit في أي مكان يراه المستخدمون. $0.20 لكل جلسة بالإضافة إلى سعر الوحدة.
Robinhood Ventures
موثوق به من قبل أكثر من 2,000 مؤسسة حول العالم.
علامتك التجارية، حكمنا
استضف سير العمل على نطاقك الخاص. غيّر الشعار، الألوان، النصوص، وبطاقة معاينة الرابط. تبقى أسعار الوحدات كما هي, $0.20 لكل جلسة هي الإضافة الوحيدة.
اختر الفحوصات التي تريدها, الهوية، التحقق من الحياة، مطابقة الوجه، العقوبات، العنوان، العمر، الهاتف، البريد الإلكتروني، الأسئلة المخصصة. اسحبها إلى سير عمل في لوحة التحكم، أو انشر نفس سير العمل إلى واجهة برمجة التطبيقات (API) الخاصة بنا. قم بالتفرع بناءً على الشروط، وقم بإجراء اختبارات A/B، لا يلزم أي كود.
قم بالدمج بشكل أصلي باستخدام SDK الخاص بنا للويب، iOS، Android، React Native، أو Flutter. أعد التوجيه إلى صفحة مستضافة. أو ببساطة أرسل لمستخدمك رابطًا, عبر البريد الإلكتروني، الرسائل القصيرة، واتساب، أي مكان. اختر ما يناسب بيئتك التقنية.
تستضيف Didit الكاميرا، إشارات الإضاءة، التسليم عبر الهاتف المحمول، وإمكانية الوصول. بينما يكون المستخدم في سير العمل، نقوم بتقييم أكثر من 200 إشارة احتيال في الوقت الفعلي والتحقق من كل حقل مقابل مصادر البيانات الموثوقة. النتيجة في أقل من ثانيتين.
تُبقي الـ webhooks الموقعة في الوقت الفعلي قاعدة بياناتك متزامنة لحظة الموافقة على المستخدم، أو رفضه، أو إرساله للمراجعة. استعلم من الـ API عند الطلب. أو افتح وحدة التحكم لفحص كل جلسة، كل إشارة، وإدارة الحالات بطريقتك.
CNAME · TLS auto · Let's Encrypt
Time to live
Auto-renew
Protocol
Logo · Palette · Typography · Radius
Live preview
DKIM · SPF · Reply-to
Every user-visible surface · logo replaced
Let's Encrypt · ACME · 90-day auto-renew
$0.20 add-on · One contract · One invoice
Add-on
Free tier
Minimums
# الكونسول -> العلامة البيضاء -> محرر الأنماط
colors: لوحة ألوان العلامة التجارية
logos: مربع + مستطيل
typography: خط العلامة التجارية + الأوزان
domain: verify.acme.com
email_from: verify@acme.com
# سير العمل -> الإعدادات -> الخيارات
include_custom_style: trueinclude_custom_style في كل سير عمل.الوثائق ←$ 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 موجود على نطاقك.الوثائق ←# 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 / شهر. لا يلزم بطاقة ائتمان.
ادفع فقط مقابل ما تستخدمه. أكثر من 25 وحدة. تسعير عام لكل وحدة، بدون رسوم شهرية دنيا.
اتفاقية خدمة رئيسية (MSA) واتفاقية مستوى الخدمة (SLA) مخصصة. للكميات الكبيرة والبرامج المنظمة.
ابدأ مجانًا ← ادفع فقط عند إجراء الفحص ← افتح Enterprise لعقد مخصص، أو SLA، أو إقامة البيانات.
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:
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.
White Label runs the entire Didit verification flow under your brand, your custom domain (verify.acme.com), your logo, your color palette, your typography, your email sender, your favicon. Zero Didit branding visible to your users.
Same /v3/ Application Programming Interface (API). Same hosted capture flow. Same X-Signature-V2 Hash-based Message Authentication Code (HMAC) webhook contract. Same Spain Tesoro / Banco de España (BdE) / Spanish Financial Intelligence Unit (SEPBLAC)-attested pipeline underneath.
$0.20 per session on top of the underlying module price. Full reference: docs.didit.me/console/white-label.
$0.20 per session, on top of the underlying module price.
$0.33 to $0.53 per white-labeled session.$0.15 Identity Document Verification goes to $0.35. No setup fee, no certificate cost, no per-domain charge. Public pricing: didit.me/pricing.
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.
Three minutes, zero certificate work.
1. In the Business Console go to White Label → Custom Domain → Add domain. 2. We return a Canonical Name (CNAME) target. 3. Point your brand subdomain CNAME at it. 4. Click Verify.
We provision a Transport Layer Security (TLS) certificate via Let's Encrypt and the Automatic Certificate Management Environment (ACME) protocol, set up automatic renewal, and the domain goes live within minutes.
No certificate procurement, no key rotation, no Domain Name System (DNS) round-trip with your security team. Renewal is automatic for the lifetime of the domain.
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.
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.
Didit ships compliant by default for the regulators that matter to identity infrastructure:
Detailed memo, every certificate, every regulator letter: /security-compliance.
Three integration paths, pick whichever fits your stack:
Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.
واجهة برمجية واحدة لـ KYC و KYB ومراقبة المعاملات وفحص المحافظ. ادمجها في 5 دقائق.