Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Marekani · BSA / FinCEN

Fuatilia kila muamala. Wasilisha SAR.

Ufuatiliaji wa Miamala kwa Wakati Halisi kwa $0.02 kwa kila simu pamoja na Usimamizi wa Kesi na usafirishaji tayari kwa Ripoti ya Shughuli za Kutiliwa Mashaka. Vifurushi 11 vya sheria vilivyopandikizwa, marekebisho ya kiotomatiki ya AWAITING_USER, uthibitishaji 500 bila malipo kila mwezi.

Anza bureSoma nyaraka
Inaungwa mkono na
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Inaaminika na mashirika 2,000+ duniani kote.

Mchoro wa kufuata sheria wa sinema, giza, usioeleweka, paneli nne zinazoelea, za kioo cheusi, katika mtazamo wa 3D kwenye turubai nyeusi kabisa, zikipitishwa na mstari wima wa Didit Blue unaong'aa na kuwekewa fremu na mabano manne ya skana yanayong'aa. Kila paneli ina motifu ndogo nyeupe-nyepesi isiyo dhahiri (silhouette ya hati, kioo cha kukuza, folda ya kesi, kengele ya tahadhari) inayowakilisha usimamizi wa kesi ya Ripoti ya Shughuli za Kutiliwa Mashaka.

BSA inavyodai

Fuatilia kila uhamisho. Fungua kila kesi. Wasilisha kwa wakati.

Kila taasisi ya kifedha ya Marekani inahitaji ufuatiliaji wa wakati halisi kwa kila muamala pamoja na Ripoti ya Shughuli za Kutiliwa Mashaka ndani ya siku 30 za kugunduliwa. Didit inatoa injini ya sheria, mashine ya hali ya kesi, kitanzi cha marekebisho ya kiotomatiki, na usafirishaji wa schema ya FinCEN, kwa $0.02 kwa kila simu ya muamala. Uthibitishaji 500 bila malipo kila mwezi.

Jinsi inavyofanya kazi

Kuanzia kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

    Chagua ukaguzi unaotaka, ID, uhai, kulinganisha uso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Tawi kwenye masharti, fanya majaribio ya A/B, hakuna msimbo unaohitajika.

  2. 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.

  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 ulaghai kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya 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 zako mwenyewe.

Imejengwa kwa BSA · Bei kama miundombinu

Vifurushi 11 vya sheria. Foleni moja. $0.02 kwa kila muamala.

Kazi halisi ya BSA si ukaguzi mmoja, ni mapishi. Badilisha vifurushi vya sheria kwa kila mtiririko wa kazi. Rekebisha vizingiti. Fungua kesi kiotomatiki. Hamisha SAR. Yote chini ya mkataba mmoja wa /v3/.
Soma nyarakaPata API key
01 · Vifurushi vya sheria

Vifurushi kumi na moja vya sheria vilivyopandikizwa.

Muundo, kasi, mifumo ya mule, hatari za kijiografia, washirika waliofungiwa, mahususi kwa crypto, ukamilifu wa Travel Rule, ongezeko la akaunti mpya, akaunti zisizotumika-zinazotumika, tabaka za mipakani. Zote zinaweza kuhaririwa kwenye Workflow Builder isiyo na code.
Moduli ya Ufuatiliaji wa Miamala
02 · Mashine ya hali ya kesi

FUNGUA → INACHUNGUZWA → SAR_IMETUMWA → IMEFUNGWA.

Kila muamala uliotiwa alama unafungua kesi. Maelezo ya mkaguzi, noti, nyakati, maamuzi yote yanarekodiwa. Kila mabadiliko yametiwa saini na iko tayari kukaguliwa.
Mratibu wa Mtiririko wa Kazi
03 · Usafirishaji tayari kwa SAR

Kifurushi tayari kwa SAR, wakati wa kusafirisha.

FinCEN SAR XML schema, pamoja na kifurushi cha ushahidi kinachounga mkono, kifurushi cha KYC cha mhusika, miamala iliyotiwa alama, data ya mshirika, muktadha wa tabia, maelezo ya mkaguzi, saini ya HMAC. E-File kutoka back-end yako au tuma kwenye zana yako ya uchunguzi.
Moduli ya Uchunguzi wa AML
04 · Marekebisho ya kiotomatiki ya AWAITING_USER

Urekebishaji wa kiotomatiki data inapokosekana.

Muamala unapohitaji data zaidi ya mteja (chanzo cha fedha, anwani iliyosasishwa, selfie mpya), Didit huunda kikao cha kurekebisha kiotomatiki. URL ya uthibitishaji kwenye jibu, webhook iliyotiwa saini baada ya kukamilika, miamala inarudiwa.
Moduli ya Uthibitishaji wa Mtumiaji
05 · Mtiririko wa arifa za moja kwa moja

Arifa za moja kwa moja. Foleni moja.

Kila muamala uliotiwa alama huonekana kwenye Case Console na sheria yake, alama, hali, na mkaguzi aliyepangiwa. Sehemu hiyo hiyo hutumika kwa ugawaji, uchunguzi, uwasilishaji, na kufungwa.
Dashibodi ya Biashara
06 · Hifadhi ya data

Uhifadhi wa miaka 5. EU + makazi ya Marekani.

Uhifadhi usio na kikomo ukiwa umejisajili, EU kwa chaguo-msingi, uhifadhi wa data ya Marekani kwenye mikataba ya biashara. SOC 2 Type 1 na ISO/IEC 27001 imethibitishwa. Udhibiti unaolingana na FFIEC.
Usalama na Uzingatiaji
Unganisha

Simu moja ya muamala. Kesi moja. Usafirishaji mmoja uliosainiwa.

Wasilisha kila uhamisho. Panga kesi zilizotiwa alama. Hamisha SAR. Wasilisha.
POST /v3/transactions/Fuatilia
$ curl -X POST https://verification.didit.me/v3/transactions/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "transaction_id": "tx-9001",
    "transaction_details": { "direction": "OUTBOUND", "currency": "USD", "amount": "9500" },
    "subject": { "full_name": "J. Doe" },
    "counterparty": { "full_name": "Mshirika" }
  }'
201Imeundwahali IMEIDHINISHWA · INAKAGULIWA · IMEKATALIWA · INAMSUBIRI_MTUMIAJI
Miamala iliyotiwa alama inafungua kesi kiotomatiki. $0.02 kwa kila simu.nyaraka →
GET /v3/transactions/{id}/SAR
$ curl https://verification.didit.me/v3/transactions/$TXN/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Inarudisha payload kamili ya kesi,
# mifumo iliyotiwa alama, KYC ya mhusika,
# mhusika mwingine, muktadha wa tabia,
# maelezo ya mkaguzi, saini ya HMAC.
# Pangilia na schema ya XML ya FinCEN SAR.
200OKkesi WAZI · INACHUNGUZWA · SAR_IMETUMWA · IMEFUNGWA
Hamisha ZIP kutoka Console au POST kwa BSA E-Filing kutoka back-end yako.nyaraka →
Ujumuishaji tayari kwa agent

Anzisha ufuatiliaji wa BSA + uwasilishaji wa SAR kwa haraka.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent atajenga workflow, ataunganisha rule bundles, atafungua kesi, ataendesha mzunguko wa marekebisho wa AWAITING_USER, na kuonyesha usafirishaji wa SAR XML.
didit-integration-prompt.md
You are integrating Didit into a US financial institution (bank, money services business, crypto VASP, broker-dealer, casino, mortgage lender) to satisfy Bank Secrecy Act monitoring + Suspicious Activity Report (SAR) filing under the Financial Crimes Enforcement Network (FinCEN). Three obligations:

  1. Monitor every transaction in real time against the eleven seeded rule bundles (structuring, velocity, mule patterns, geographic risk, sanctioned counterparties, etc.).
  2. Open and manage cases on every flagged transaction.
  3. Export the SAR-ready package matching the FinCEN SAR XML schema for filing via the BSA E-Filing System.

Pricing (verified live 2026-05-16):
  - Transaction Monitoring: $0.02 per transaction call
  - Anti-Money Laundering (AML) Screening on flagged subjects: $0.20 per check, $0.07 per user per year for ongoing monitoring
  - User Verification (Know Your Customer (KYC)) for remediation: $0.33 per check
  - First 500 verifications free every month, forever

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
  - Webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header.
 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.  - A workflow_id for KYC sessions (used on remediation), and Transaction Monitoring + Case Management enabled in the Business Console.
  - Optional: integration with the BSA E-Filing System on your back-end OR push to your existing investigation tool (Actimize, NICE, Quantexa, ComplyAdvantage Workflow).

STEP 1 — Monitor every transaction with the Transactions API

  POST https://verification.didit.me/v3/transactions/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body (required fields verified live 2026-05-16):
    {
      "transaction_id": "<your internal transaction id>",
      "transaction_category": "finance",
      "transaction_details": {
        "direction": "OUTBOUND",
        "amount": "9500",
        "currency": "USD",
        "currency_kind": "fiat",
        "action_type": "payment"
      },
      "subject": {
        "entity_type": "individual",
        "vendor_data": "<your user id>",
        "full_name": "<user name from verified KYC>"
      },
      "counterparty": {
        "entity_type": "individual",
        "full_name": "<counterparty name if known>",
        "payment_method": {
          "method_type": "wire",
          "account_id": "<counterparty account or routing reference>"
        }
      }
    }

  REQUIRED fields the API rejects if missing:
    - subject.vendor_data + subject.full_name
    - counterparty.full_name
    - transaction_details.direction + currency + currency_kind + amount

  Response shape (excerpted from a real successful 201):
    {
      "uuid": "<server transaction uuid>",
      "txn_id": "<your transaction_id echoed back>",
      "status": "APPROVED",
      "score": 0,
      "severity": null,
      "cost_breakdown": {
        "total_price": 0.02,
        "items": [{ "usage_type": "transaction_monitoring", "price": 0.02 }]
      }
    }

  Transaction status enum (exact case, UPPER_SNAKE_CASE): APPROVED | IN_REVIEW | DECLINED | AWAITING_USER.

STEP 2 — Branch on the verdict

  APPROVED       → clear the transaction. Webhook may still update later if Ongoing Monitoring catches a delayed signal.
  IN_REVIEW      → hold the transaction. Case opens automatically in the Business Console for analyst triage.
  DECLINED       → refuse the transaction. Case opens at SAR-candidate priority.
  AWAITING_USER  → the workflow needs more data from the customer (source of funds, updated address, refreshed selfie). The response includes a remediation verification URL — send it to the customer.

STEP 3 — Handle AWAITING_USER auto-remediation

  Push the verification URL on the response to the customer (email, app deep-link, push notification). They complete the additional verification in hosted flow on their phone.

  On completion:
    - The remediation session is LINKED to the original transaction (you'll see the linkage in both webhooks).
    - Didit re-runs the relevant rules with the new evidence.
    - The transaction moves to APPROVED (clear) or DECLINED (case opens for SAR consideration).

  The whole loop takes minutes for the user; your team only touches the cases that genuinely need human judgement.

STEP 4 — Case Management — every flagged transaction opens a case

  Cases live in the Business Console with a state machine:

    OPEN          → alert fires, no reviewer yet
    INVESTIGATING → reviewer assigned, gathering context
    SAR_FILED     → SAR exported and filed; case awaits regulator response
    CLOSED        → case resolved, no SAR (with reviewer notes explaining why)

  Each transition is signed, timestamped, and attributed (analyst name + officer name).

  Per case, you get:
    - The flagged transaction(s) + the rule(s) that fired
    - The subject's verified KYC bundle (document, biometric, AML, device + IP)
    - The counterparty data (for crypto: wallet screen; for fiat: counterparty identity if known)
    - Behavioural context (user's transaction history, baseline, velocity)
    - Reviewer narrative (analyst notes, decisions, escalations)

STEP 5 — Export the SAR package

  Two paths:

  Path A — Direct from the Console
    Click "Export SAR XML" on a case. You get a downloadable package matching the FinCEN SAR XML schema. Upload through the BSA E-Filing System manually.

  Path B — Via API + your back-end
    GET https://verification.didit.me/v3/transactions/{id}/
    Headers:
      x-api-key: <your api key>
    The full case payload — every field above — is returned as JSON. Map to the FinCEN schema in your back-end and POST to the BSA E-Filing System programmatically.

STEP 6 — Webhook event names

  Sessions: standard session webhook for remediation completions (verify X-Signature-V2).
  Transactions:
    - transaction.created
    - transaction.updated
    - transaction.status.changed
    - transaction.alert.generated

  Every payload signed with X-Signature-V2 HMAC SHA-256.

STEP 7 — Ongoing AML monitoring is automatic on every verified subject

  Every approved user is re-screened daily against 1,300+ sanctions, PEP, and adverse-media lists at $0.07 per user per year on heavy-volume accounts. When a previously-clean subject crosses an AML threshold, a transaction.alert.generated webhook fires and a case opens automatically.

CONSTRAINTS
  - Session statuses Title Case With Spaces; transaction statuses UPPER_SNAKE_CASE. Don't mix.
  - SAR filing deadlines: 30 days from detection (extendable by 30 days for suspect identification).
  - SAR thresholds: $5,000 aggregate transaction for banks; $2,000 for money services businesses.
  - BSA retention: 5 years on every SAR + supporting documentation.
  - Tipping-off: NEVER disclose the SAR filing to the subject. Encode this in your customer-comms workflow.
  - Default record retention is indefinite while subscribed; configurable per workflow if your supervisor mandates a specific duration.

Read the docs:
  - https://docs.didit.me/transaction-monitoring/overview
  - https://docs.didit.me/transaction-monitoring/transactions
  - https://docs.didit.me/transaction-monitoring/aml-screening
  - https://docs.didit.me/sessions-api/create-session
  - 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.
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
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

Takwimu za kuthibitisha

Takwimu za kuthibitisha
  • $0.00
    Kwa kila simu ya Ufuatiliaji wa Miamala, kila uhamisho unachunguzwa kwa wakati halisi.
  • 0
    Rule bundles zilizopandikizwa zinazohusu uundaji, kasi, mifumo ya mule, hatari ya kijiografia, washirika walioidhinishwa, na matukio mengine ya kawaida ya Sheria ya Usiri wa Benki.
  • 0+
    Vikwazo, Watu Walio Wazi Kisiasa (PEP), na orodha za habari mbaya zinazochunguzwa kwa kila mhusika.
  • 0
    Uthibitishaji wa bure kila mwezi, kwa kila akaunti.
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
Anza bure
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
Tazama orodha kamili ya beiAnza bure
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
Wasiliana nasi

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

FAQ

Maswali ya kawaida

What is Didit?

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:

  • Fast, sub-2-second p99 on every session
  • Reliable, in production with 1,500+ companies across 220+ countries
  • Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person

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.

What is the Bank Secrecy Act, in plain English?

The Bank Secrecy Act (BSA) is the foundational US anti-money-laundering law, passed in 1970 and amended many times since. It requires US financial institutions to help the government detect and prevent money laundering by keeping records, reporting suspicious activity, and reporting large currency transactions.

The rulebook is enforced by the Financial Crimes Enforcement Network (FinCEN), a bureau of the US Treasury. Examinations are run by the institution's primary federal regulator, the OCC for national banks, the Federal Reserve for state-member banks, the Federal Deposit Insurance Corporation (FDIC) for state non-member banks, the National Credit Union Administration (NCUA) for credit unions, and the SEC + FINRA for broker-dealers.

In 2020 the Anti-Money Laundering Act of 2020 modernised the regime, beneficial-ownership reporting, regulatory expansion to cover dealers in antiquities, and the Corporate Transparency Act layered on top.

What is a Suspicious Activity Report?

A Suspicious Activity Report (SAR) is a confidential filing a US financial institution submits to FinCEN whenever it spots a transaction or pattern that may indicate money laundering, fraud, terrorist financing, or other criminal activity.

Filing rules:

  • Threshold, banks file when an aggregate transaction reaches $5,000 and the institution suspects illicit activity. Money services businesses file at $2,000.
  • Timing, file within 30 days of detection, extendable by 30 days if a suspect is being identified.
  • Confidentiality, prohibited from disclosing the filing to the subject. Tipping-off violations carry criminal penalties.
  • Format, submitted via the BSA E-Filing System in the FinCEN SAR XML schema.
  • Retention, keep a copy of the filed SAR plus all supporting documentation for 5 years.

FinCEN uses SARs to build investigative leads; agencies like the FBI, IRS-Criminal Investigation, and DEA query the database constantly.

How fast is the verification for my end user?

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.

What patterns trigger a SAR?

FinCEN's SAR guidance covers many categories; the common ones:

  • Structuring, breaking large transactions into smaller ones to avoid the $10,000 Currency Transaction Report (CTR) threshold. Pattern of $9,500 deposits over a few days.
  • Velocity anomalies, sudden burst of transactions inconsistent with the customer's profile
  • Geographic risk, transactions to or from high-risk jurisdictions, FATF grey-list countries
  • Mule patterns, money flowing in and immediately out, often to multiple beneficiaries
  • Sanctions hits, counterparty matches an OFAC list
  • Identity fraud, synthetic identities, document forgery indicators surfaced post-onboarding
  • Cyber-event-related, transactions connected to a ransomware payment, business email compromise, or account takeover
  • Insider abuse, embezzlement, employee-driven activity

FinCEN expects rule-based and behavioural detection, not just a checklist. A real Transaction Monitoring programme tunes rules to the customer base and the institution's risk profile.

What happens if a user fails, abandons, or expires?

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.

Where does my customer data live and how is it protected?

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.

Is Didit compliant for my industry?

Didit ships compliant by default for the regulators that matter to identity infrastructure:

  • GDPR + UK GDPR, controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
  • AMLD6 + EU AML Single Rulebook, 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
  • eIDAS 2.0, EU Digital Identity Wallet aligned; reusable-identity ready.
  • MiCA (Markets in Crypto-Assets), ready for crypto on-ramps, exchanges, and custodians.
  • DORA, Digital Operational Resilience Act, EU financial-services operational resilience.
  • BIPA, CUBI, Washington HB 1493, CCPA / CPRA, US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
  • UK Online Safety Act, age-gating and child-safety obligations.
  • FATF Travel Rule, originator and beneficiary data on crypto transfers, IVMS-101 interoperable.

Detailed memo, every certificate, every regulator letter: /security-compliance.

How fast can I integrate and start verifying users?
  • 60 seconds to a sandbox account at business.didit.me, no credit card.
  • 5 minutes to a working verification through Claude Code, Cursor, or any coding agent via our Model Context Protocol (MCP) server.
  • A weekend to a production-ready integration with signed-webhook verification, retries, and a remediation flow when a user is declined.

Three integration paths, pick whichever fits your stack:

  • Embed natively with our Web, iOS, Android, React Native, or Flutter SDK.
  • Redirect the user to the hosted verification page, zero SDK.
  • Send a link by email, SMS, WhatsApp, or any channel, zero front-end work.

Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.

What is AWAITING_USER auto-remediation, and why does it matter?

A common monitoring outcome is we need more information from the customer before clearing this transaction, proof of source of funds, an updated address, a re-verified selfie.

Legacy stacks force your operations team to handle this manually: email the customer, wait, chase, re-screen. AWAITING_USER auto-remediation closes the loop automatically:

  • The transaction returns status AWAITING_USER with a remediation verification URL on the response
  • Send the URL to the customer (email, app deep-link, push), they complete the additional verification on their phone in hosted flow
  • The remediation session is linked to the original transaction; on completion, a signed webhook reopens the transaction and Didit re-runs the relevant rules with the new evidence
  • If the user clears, the transaction moves to APPROVED; if not, it moves to DECLINED and a case opens for SAR consideration

Net effect: a remediation loop that used to take days now takes minutes, the audit trail is complete, and your team only touches the cases that genuinely need human judgement.

How does Didit's stack interact with my existing AML investigation tools?

Didit produces SAR-ready evidence; you bring whatever filing and investigation tooling you already use.

Integration patterns:

  • Direct e-filing, pull the case XML via the API and post it to FinCEN's BSA E-Filing system from your own back-end
  • Investigation case management, push case identifiers + payload URLs into Actimize, NICE, Quantexa, ComplyAdvantage Workflow, or your internal queue via webhook
  • Data warehouse, every transaction event lands on your warehouse via webhook for long-horizon analytics
  • AML hits enrichment, Didit's AML Screening produces 1,300+ source-cited hits; chain into your investigation team's preferred enrichment provider for deeper open-source intelligence
  • MCP server, your AI agent (Claude, Cursor, internal copilots) can read cases and propose narrative drafts via the Didit MCP server

Didit's surface is intentionally narrow: it captures, scores, monitors, opens cases, and stores evidence. Whether the SAR file leaves Didit or your downstream system is your call.

What about record retention and EU vs US data residency?

BSA requires 5 years of records on every SAR plus supporting documentation. Didit's defaults:

  • Indefinite retention while your subscription is active, no per-record retention bill, no expiry surprises
  • EU-resident storage by default, regulated EU data centres, with US data-residency available on enterprise contracts for institutions that need it
  • Every payload signed with HMAC SHA-256 so chain-of-custody is provable for an examiner
  • Configurable per workflow if your supervisor mandates a specific duration
  • Export anytime via the Business Console or the API, bulk ZIP per date range or single-record JSON

Didit is SOC 2 Type 1 and ISO/IEC 27001 certified, with the audit reports and controls catalogue available under NDA from /security-compliance. For US institutions specifically, the platform's separation-of-duties, encryption-at-rest, and access-logging meet the standards examiners look for under FFIEC Information Technology guidance.

Related

Moduli zinazohusiana + workflows

Miundombinu ya utambulisho na udanganyifu.

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

Anza bila malipoZungumza nasi
Uliza AI ifupishe ukurasa huu