Ruka hadi maudhui makuu
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Crypto · Sheria ya Safari

Mwanzilishi na mnufaika, kwa kila uhamisho.

Didit inabadilishana data ya Travel Rule na inachunguza counterparty wallet kwenye /v3/ transaction call ileile. IVMS-101 payloads, $0.17 kwa managed transfer, $10 ya free credit kila mwezi.

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

Inaaminika na mashirika 3,000+ duniani kote.

Sheria ya Safari inadai nini

Tuma utambulisho. Kagua wallet. Simu moja.

Kila VASP iliyodhibitiwa inapaswa kuwa na pande zote mbili kwenye kila transfer, IVMS-101 packet kwa counterparty VASP, on-chain risk screen kwa yenyewe. Didit inazitoa kama API call moja ya Transactions kwa $0.17 kwa transfer. $10 ya free credit kila mwezi.

Jinsi inavyofanya kazi

Kuanzia kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

Hatua 01 / 04

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

Imejengwa kwa Sheria ya Safari · Bei kama miundombinu

Simu moja. Pakiti ya IVMS-101 + uchunguzi wa pochi. $0.17.

Uhamisho wa crypto unaodhibitiwa sio ukaguzi mmoja, ni mapishi. Washa kila moduli kwa kila mtiririko wa kazi, badilisha mtoa huduma wako wa uchunguzi wa pochi kupitia Bring Your Own Key ili kushuka hadi $0.04 kwa kila uhamisho.
01 · IVMS-101 payload

Pakiti moja ya IVMS-101 kwa kila uhamisho.

Sehemu za mwanzilishi na mnufaika zimejazwa kutoka KYC iliyothibitishwa. Zimepangwa kiotomatiki kwa InterVASP Messaging Standard 101, schema ambayo kila itifaki kuu ya Travel Rule inasoma.
Transactions API
02 · Vizingiti vya kila mamlaka

Viwango vinavyolingana na mamlaka yako.

EU TFR (hakuna kiwango cha chini), US FinCEN ($3,000), UK FCA (£1,000), MAS (SGD 1,500), FINMA (CHF 1,000), VARA (AED 3,500). Mtiririko mmoja wa kazi kwa kila mamlaka; badilisha kupitia metadata ya kipindi.
Mtiririko wa kazi wa sekta ya crypto
03 · Utangamano wa itifaki

Kila itifaki ya Travel Rule. Mkataba mmoja.

TRP, Sumsub Travel Rule, Notabene, Veriscope, OpenVASP, Shyft, zote zinafikiwa kupitia payload ileile ya IVMS-101. Chagua mtandao mmoja au kubali yote; mkataba mmoja, ankara moja.
Workflow Orchestrator
04 · Mtiririko wa pochi inayojihifadhi

Lengo linalojihifadhi? Bado limefunikwa.

Hakuna VASP mshirika wa kubadilishana naye, Didit inakusanya utambulisho wa mnufaika kutoka kwa mtumiaji, inafanya changamoto za uthibitisho wa udhibiti juu ya viwango vya EU vya ukaguzi wa kina, inachunguza pochi lengwa, inahifadhi rekodi ya muundo wa IVMS.
Maswali Maalum
05 · Skrini ya pochi pamoja na sheria

Travel Rule + skrini ya pochi. Simu ileile.

$0.001 transaction-monitoring base + $0.15 Wallet Screening = $0.151 kwa transfer. Au leta wallet-screening provider wako mwenyewe na uiendeshe kwenye mkataba uleule.
Moduli ya Wallet Screening
06 · Kifurushi cha ushahidi kwa kila uhamisho

Kifurushi kimoja kwa kila uhamisho. Inaingia kwenye ukaguzi.

Payload ya IVMS-101, uamuzi wa skrini ya pochi, sifa ya VASP mshirika, mihuri ya muda ya HMAC iliyosainiwa. Imehifadhiwa EU. Inahifadhiwa miaka 5 kwa chaguo-msingi; inaweza kupanuliwa kulingana na mwongozo wa msimamizi.
Usalama na Uzingatiaji
Unganisha

Kikao kimoja. Muamala mmoja. Webhook moja.

Thibitisha mtumiaji mara moja. Tuma kila uhamisho na sehemu za IVMS + pochi ya mpinzani. Soma uamuzi uliotiwa saini. Toa crypto.
POST /v3/session/KYC
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_casp_onboard",
    "vendor_data": "user-42"
  }'
201Imeundwa{ hali Imeidhinishwa · Inapitiwa · Imekataliwa }
Sehemu za mwanzilishi kwa kila uhamisho zinatokana na uamuzi huu uliosainiwa.nyaraka →
POST /v3/transactions/IVMS + KYT
$ 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_kind": "crypto" },
    "subject": { "full_name": "J. Pérez" },
    "counterparty": { "full_name": "R. Beneficiary", "payment_method": { "account_id": "bc1qa3…hk22" }}
  }'
201Imeundwa{ hali IMEIDHINISHWA · INAPITIWA · IMEKATALIWA · INAMSUBIRI_MTUMIAJI }
Pakiti ya IVMS-101 + ukaguzi wa wallet unaendeshwa upande wa server. Hakuna simu ya pili.nyaraka →
Ujumuishaji tayari kwa agent

Tengeneza mfumo wa Travel Rule kwa amri moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent itajenga workflow, itajaza sehemu za IVMS kutoka kwenye session ya KYC, itaendesha wallet screen, na kuunganisha webhook.
didit-integration-prompt.md
You are integrating Didit into a Virtual Asset Service Provider (VASP) / Crypto-Asset Service Provider (CASP) to satisfy the Travel Rule on every crypto transfer. Two obligations:

  1. Verify the user (KYC) — identity, liveness, face match, device + IP, AML. The originator data on every outbound transfer comes from this verified profile.
  2. Submit each transfer with originator + beneficiary fields (IVMS-101) AND screen the counterparty wallet — one /v3/transactions/ call.

Bundle pricing (verified live 2026-05-16):
  - User Verification (KYC) bundle: $0.33 per user (Sessions API)
  - Transactions API call: $0.02 base + $0.15 managed wallet screen = $0.17 per managed transfer
  - Or bring your own wallet-screening provider and run it inside Didit — same contract, same price
  - First $10 of free credit every month

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 from the no-code Workflow Builder with ID Verification + Passive Liveness + Face Match 1:1 + Device & IP Analysis + AML Screening.
  - Transaction Monitoring + Wallet Screening enabled in the Business Console (Transactions > Settings).

STEP 1 — Verify the user with the Sessions API (one-time onboarding)

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id with KYC + AML modules>",
      "vendor_data": "<your user id>",
      "callback": "https://<your-app>/casp/onboard/callback",
      "metadata": {
        "purpose": "casp_onboarding"
      }
    }

  Response: 201 Created with the hosted session URL. Sub-2-second median verdict on completion.

STEP 2 — Read the signed webhook on KYC completion

  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.

  Capture the user's full name, date of birth, address, and any registered identity-document number from the decision payload. These fields populate the IVMS-101 originator block on every subsequent transfer.

STEP 3 — Submit every transfer with IVMS-101 + wallet screen in one call

  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 transfer reference>",
      "transaction_category": "finance",
      "include_crypto_screening": true,
      "transaction_details": {
        "direction": "OUTBOUND",
        "amount": "0.45",
        "currency": "ETH",
        "currency_kind": "crypto",
        "action_type": "transfer"
      },
      "subject": {
        "entity_type": "individual",
        "vendor_data": "<your user id>",
        "full_name": "<originator name from KYC>",
        "address": "<originator address from KYC>",
        "dob": "<originator dob from KYC, YYYY-MM-DD>"
      },
      "counterparty": {
        "entity_type": "individual",
        "full_name": "<beneficiary name>",
        "address": "<beneficiary address if known>",
        "payment_method": {
          "method_type": "crypto_wallet",
          "account_id": "<counterparty wallet address>"
        }
      }
    }

  REQUIRED fields the API rejects if missing:
    - subject.vendor_data + subject.full_name
    - counterparty.full_name
    - transaction_details.direction + currency + currency_kind + amount
    - counterparty.payment_method.account_id (the wallet address)

  Didit packages the subject + counterparty fields into an IVMS-101 payload, hands them off to the connected Travel Rule protocol (TRP / Sumsub TR / Notabene / Veriscope), runs Wallet Screening on the counterparty address server-side, and returns one verdict.

  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,
      "travel_rule": { "status": "EXCHANGED", "protocol": "<network>", "ivms_packet_id": "<id>" },
      "props": {
        "wallet_risk_score": 0,
        "sanctions_hit": false,
        "aml_provider": "<provider slug>",
        "aml_screening_type": "WALLET_SCREENING",
        "aml_screening_status": "COMPLETED"
      },
      "cost_breakdown": {
        "total_price": 0.17,
        "items": [
          { "usage_type": "transaction_aml_monitoring", "price": 0.15 },
          { "usage_type": "transaction_monitoring", "price": 0.02 }
        ]
      }
    }

  Transaction status enum (exact case, UPPER_SNAKE_CASE): APPROVED | IN_REVIEW | DECLINED | AWAITING_USER.
  Wallet-screen severity (UPPER): LOW | MEDIUM | HIGH | CRITICAL | UNKNOWN.

  Branch logic:
    APPROVED       → release the crypto.
    IN_REVIEW      → hold the transfer, route to analyst queue.
    DECLINED       → refuse the transfer, log the IVMS attempt for the audit.
    AWAITING_USER  → redirect the user to the remediation URL on the response.

STEP 4 — Inbound transfers: ingest the counterparty's IVMS packet

  When you RECEIVE a transfer from another VASP:
    - The connected Travel Rule protocol delivers the originator IVMS data to you BEFORE the on-chain transfer settles.
    - Submit it via the same POST /v3/transactions/ with direction: "INBOUND" and the originator fields on subject and your own beneficiary on counterparty.
    - Wallet Screening runs on the originator wallet (subject.payment_method.account_id).
    - Verdict drives whether to credit the user.

STEP 5 — Self-hosted (unhosted) wallet transfers

  For transfers TO a self-hosted wallet (no counterparty VASP to exchange with):
    - Collect the beneficiary identity from the user via a custom questionnaire ($0.10).
    - Above local enhanced-due-diligence thresholds, prompt the user to sign a short message with the beneficiary wallet's private key as proof of control.
    - Submit the transaction with the captured beneficiary fields + wallet address.
    - Didit still runs Wallet Screening on the destination and stores the IVMS-format record for the audit.

STEP 6 — Continuous AML on the user is automatic

  Every approved user is re-screened daily against 1,300+ sanctions, PEP, and adverse-media lists. There is NO separate endpoint to call. When a previously-clean user crosses an AML threshold, the session status updates and a signed webhook fires.

WEBHOOK EVENT NAMES
  - Sessions: status changes flow through the standard session webhook.
  - Transactions: transaction.created · transaction.updated · transaction.status.changed · transaction.alert.generated.
  Verify X-Signature-V2 on every payload.

CONSTRAINTS
  - Session statuses Title Case With Spaces; transaction statuses UPPER_SNAKE_CASE. Don't mix.
  - EU Transfer of Funds Regulation has NO de minimis threshold for crypto — every transfer carries originator + beneficiary data.
  - US Travel Rule kicks in at $3,000; UK at £1,000; Singapore at SGD 1,500; Switzerland at CHF 1,000. Apply per-workflow.
  - Default record retention is 5 years post-transfer per most AML regimes; extensible per supervisor guidance.
  - Wallet Screening MUST run BEFORE the crypto leaves — a post-transfer screen is useful for audit but useless for blocking.

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, $10 of free credit 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
SOC 2 · Type II — AICPA · 2026
SOC 2 · Type I — AICPA · 2026
ISO/IEC 27001 — Usalama wa habari · 2026
EU financial sandbox — Tesoro · SEPBLAC · BdE
FIDO Alliance — Mwanachama Mshirika · 2026
iBeta Level 1 PAD — NIST / NIAP · 2026
GDPR — EU 2016/679
HIPAA — 45 CFR §160 · §164
DORA — EU 2022/2554
MiCA — EU 2023/1114
Miongozo ya EBA ya kuingiza wateja mtandaoni — EBA/GL/2022/15
AMLD6 · eIDAS 2.0 — EU-aligned kwa muundo
Jugendschutz geprüft — FSM · JMStV §4(2) · 2026

Namba za uthibitisho

Namba za uthibitisho
  • $0.17
    Kwa kila uhamisho unaosimamiwa, Transaction Monitoring base + Wallet Screening.
  • 1,300+
    Vikwazo, Watu Walio Wazi Kisiasa (PEP), na orodha za habari hasi huchunguzwa kwa kila mtumiaji.
  • 5+
    Itifaki za Travel Rule zinazoweza kufanya kazi pamoja kwenye IVMS-101 payload moja, TRP, Sumsub TR, Notabene, Veriscope, OpenVASP, Shyft.
  • $10
    Free credit kila mwezi, kwenye kila akaunti.
Mipango minne, akaunti moja

Anza bure. Lipa kadri unavyotumia. Kuza hadi Enterprise.

Mkopo wa bure wa $10 kila mwezi. Kisha lipa tu kwa ukaguzi unaokamilika: bei za orodha kwenye Bure, punguzo la 4% kwenye Growth na punguzo la 10% kwenye Scale. Mikataba maalum, uhifadhi wa data, na makubaliano ya kiwango cha huduma (SLAs) kwenye Enterprise.

Bure

$0/ mwezi · hakuna kadi

Jaribu kila check na free credit.

Kila kitu unachohitaji kuanzia:
  • $10 ya free credit kila mwezi
  • Kila check katika nchi 220+, kwa bei ya orodha
  • 1,000 monitored transactions kwa mwezi zimejumuishwa
  • Watumiaji 50,000 wa kwanza wa Authentication kwa mwezi bure
  • Workflow builder, SDKs na API, members 2
  • Usaidizi wa AI Msaidizi wa AI ndani ya console na docs.
Timu nyingi

Growth

$99/ mwezi

Kwa timu zinazoanza kutumia. Au $1,128 kwa mwaka.

Kila kitu kilichopo kwenye Bure, pamoja na:
  • $115 ya credit kila mwezi
  • Punguzo la 4% kwa kila bei ya Didit
  • 10,000 monitored transactions kwa mwezi zimejumuishwa
  • Investigator na Drop-off agents, case management
  • Members 10, preset roles, miaka 5 ya data retention
  • Usaidizi kwa barua pepe na chat Majibu ndani ya siku 1 ya kazi.

Scale

$299/ mwezi

Kwa timu zenye idadi kubwa. Au $3,408 kwa mwaka.

Kila kitu kilichopo kwenye Growth, pamoja na:
  • Mkopo wa $350 kila mwezi
  • Punguzo la 10% kwa kila bei ya Didit
  • Miamala 100,000 inayofuatiliwa kwa mwezi imejumuishwa
  • White label: brand yako kwenye domain yako
  • Wanachama wasio na kikomo, majukumu maalum, uptime SLA
  • Usaidizi wa kipaumbele Ndani ya saa 24, pamoja na simu ya ushirikiano na ukaguzi wa usanidi.

Enterprise

Maalummkataba wa mwaka

Kwa matumizi makubwa na manunuzi.

Kila kitu kilichopo kwenye Scale, pamoja na:
  • Ahadi yako ya kila mwaka ndiyo credit yako
  • Punguzo na rate card huwekwa na mkataba wako
  • Company single sign-on (SSO) na SCIM
  • Custom data retention na uptime SLA
  • Cross-organization fraud network signals
  • Timu maalum Private Slack channel na timu yako maalum.

Mpango mmoja na salio moja la credit inashughulikia kila bidhaa: Identity Verification, Authentication na Transaction Monitoring. Growth na Scale ni malipo ya mwezi hadi mwezi, au $1,128 na $3,408 kwa mwaka ukilipa mapema.

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, 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, ijue biashara yako), kuchunguza pochi za crypto (KYT, ijue miamala yako), na kufuatilia miamala kwa wakati halisi, kwenye stack iliyojengwa kuwa:

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

Miundombinu iliyo chini: aina 14,000+ za nyaraka katika lugha 54, vyanzo vya data 1,000+, na ishara za udanganyifu 200+ kwenye kila session. Miundombinu ya Didit hujifunza kwa nguvu kutoka kila session na inaboresha kila siku.

Sheria ya Travel Rule ni nini, kwa lugha rahisi?

Sheria ya Travel Rule inasema kwamba thamani inapohamishwa kati ya watoa huduma wawili waliodhibitiwa, baadhi ya taarifa za mteja, jina, namba ya akaunti, anwani, lazima zisafiri pamoja na thamani yenyewe.

Ilianza katika fedha za jadi (Sheria ya Usiri wa Benki ya Marekani ya 1970), ilipanuliwa kimataifa na Kikosi Kazi cha Hatua za Kifedha (FATF) mwaka 2019, na sasa inatumika kwa crypto kila mahali. Muundo wa kawaida wa malipo ni InterVASP Messaging Standard 101 (IVMS-101), schema ya JSON ambayo kila itifaki kuu ya Travel Rule inatumia.

Lengo la mdhibiti ni rahisi: kuzuia wahalifu kuosha mapato bila kujulikana kupitia minyororo ya watoa huduma kwa kuhakikisha data ya utambulisho inafuata thamani kila hatua.

Nani anapaswa kutii, na kuanzia lini?

Kila Mtoa Huduma wa Mali Halisi (VASP) au Mtoa Huduma wa Mali za Crypto (CASP) aliyedhibitiwa, kubadilishana, on/off-ramps, pochi za ulinzi, madalali, madawati ya OTC, taasisi za malipo zinazohusika na malipo ya crypto.

Mamlaka zinazotumika:

  • Umoja wa Ulaya, Kanuni ya Uhamishaji wa Fedha ilianza kutumika kikamilifu Desemba 30, 2024 pamoja na MiCA. Inatumika kwa kila CASP iliyopewa leseni katika EU.
  • Marekani, Sheria ya Travel Rule ya FinCEN imetumika tangu 1996 katika fedha za jadi; mwongozo wa FinCEN wa 2019 uliipanua kwa crypto na kupunguza vizingiti.
  • Uingereza, sheria za cryptoasset za FCA zilianza kutumika Septemba 2023.
  • Singapore, Uswisi, UAE, Brazil, Japan, Korea Kusini, zote zinatumika, kila moja ikiwa na kizingiti tofauti kidogo na muundo wa ujumbe.

FATF hufanya tathmini za pamoja za utekelezaji wa kila nchi. Mamlaka zisizotii zinakabiliwa na hatari ya kuwekwa kwenye orodha ya kijivu.

Uthibitishaji unachukua muda gani kwa mtumiaji wangu wa mwisho?

Mchakato mzima kwa kawaida huchukua chini ya sekunde 30 kuanzia 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 nyuma, Didit inarudisha matokeo kwa chini ya sekunde mbili kwa p99, ikipimwa kuanzia wakati mtumiaji anamaliza selfie hadi wakati webhook yako inapoanza. Upigaji picha wa simu umeboreshwa kwa simu za polepole na mitandao ya polepole: ukandamizaji wa picha unaoendelea, upakiaji wa polepole wa software development kit, na uhamishaji wa kugusa mara moja kutoka kompyuta hadi simu kupitia msimbo wa QR ikiwa mtumiaji anaanza kwenye wavuti.

Ni data gani inapaswa kusafiri, na inasafiri vipi?

Seti ya data ya chini kabisa ya FATF ni:

  • Mwanzilishi, jina kamili, akaunti/pochi, anwani halisi AU namba ya kitambulisho cha kitaifa AU tarehe na mahali pa kuzaliwa
  • Mfaidika, jina kamili, akaunti/pochi, anwani halisi (inategemea mamlaka)
  • Uhamishaji wenyewe, kiasi, mali, muhuri wa muda

Data inasafiri kupitia itifaki ya Travel Rule kati ya watoa huduma wawili, si kwenye blockchain, si kwenye memo ya muamala. Soko la leo limegawanyika: watoa huduma huchagua moja au zaidi ya TRP, Sumsub Travel Rule, Notabene, Veriscope, OpenVASP, na Shyft. Lugha inayoshirikiwa ni IVMS-101, ambayo kila itifaki inasoma na kuandika.

Mpokeaji wa uhamisho anathibitisha data kabla ya kuweka fedha kwenye akaunti ya mfaidika.

Nini kinatokea ikiwa mtumiaji atashindwa, ataacha, au muda wake utaisha?

Kila kipindi kinaishia 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 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. Rudisha au muda wake uishe.
  • Expired, kiungo cha kipindi kimeisha muda wake. Unda kipindi kipya.

Webhook iliyosainiwa inawaka kwa kila mabadiliko ya hali, kwa hivyo database yako inabaki 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 maeneo mbadala kwa mamlaka ambazo wadhibiti wao wanahitaji.

Usimbaji fiche kila mahali. AES-256 ikiwa imetulia kwenye kila database, hifadhi ya vitu, na backup. Usalama wa Tabaka la Usafirishaji 1.3 ikiwa inasafirishwa kwenye kila API call, webhook, na session ya Business Console. Data ya kibayometriki imesimbwa kwa kutumia Customer Master Key tofauti.

Uhifadhi ni wako kudhibiti. Uhifadhi wa chaguo-msingi ni usio na kikomo (unlimited) isipokuwa ukisanidi muda mfupi zaidi, kati ya siku 30 na miaka 10 kwa kila programu, na unaweza kufuta session yoyote binafsi wakati wowote kutoka kwenye dashboard au API.

Vyeti: SOC 2 Aina ya 1 & Aina ya 2, 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 kwenye /security-compliance.

Je, Didit inatii sheria kwa tasnia yangu?

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

  • GDPR + UK GDPR, mgawanyo wa majukumu kati ya mdhibiti wa data na mchakataji wa data, Mkataba kamili wa Uchakataji wa Data umechapishwa, mamlaka kuu ya usimamizi imetajwa (AEPD ya Uhispania).
  • AMLD6 + EU AML Single Rulebook, orodha 1,300+ za vikwazo, watu wenye nyadhifa za kisiasa (PEP) na habari hasi kwenye vyombo vya habari huchunguzwa kwa wakati halisi.
  • eIDAS 2.0, eID tano za kitaifa ziko hai leo (MitID, BankID Uswidi, Finnish Trust Network, Smart-ID, Mobile-ID); kukubali EUDI Wallet kunakuja hivi karibuni.
  • MiCA (Markets in Crypto-Assets), tayari kwa huduma za kununua crypto kwa fedha za kawaida (on-ramps), masoko ya kubadilishana na watunzaji wa mali.
  • DORA, Digital Operational Resilience Act, ustahimilivu wa uendeshaji wa huduma za kifedha za EU.
  • BIPA, CUBI, Washington HB 1493, CCPA / CPRA, faragha ya kibayometriki ya Marekani (Illinois, Texas, Washington) na faragha ya watumiaji ya California.
  • UK Online Safety Act, vizuizi vya umri na majukumu ya usalama wa watoto.
  • FATF Travel Rule, data ya mtumaji na mnufaika kwenye uhamishaji wa crypto, inaingiliana na IVMS-101.

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 kuandika msimbo kupitia seva yetu ya Model Context Protocol (MCP).
  • Wikiendi moja kwa muunganisho tayari kwa uzalishaji na uthibitishaji wa webhook iliyosainiwa, majaribio tena, na mchakato wa kurekebisha wakati mtumiaji anakataliwa.

Njia tatu za kuunganisha, chagua inayofaa stack yako:

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

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.

Data inayokosekana au isiyolingana inashughulikiwa vipi?

Maisha halisi mara chache hayatoi pakiti safi za Travel Rule, washirika hutuma data isiyokamilika, sehemu hazilingani na jina la KYC, miundo ya anwani inatofautiana. Njia mbili:

  • Data muhimu inayokosekana (hakuna jina la mwanzilishi, hakuna pochi ya mshirika) → muamala unarudisha DECLINED na mtumiaji anaombwa kutuma tena
  • Kutolingana kidogo (tahajia tofauti kidogo ya jina, jina la kati linakosekana) → muamala unarudisha IN_REVIEW na kesi inafunguliwa kwenye Business Console na tofauti imeangaziwa
  • Uchunguzi wa kina zaidi unahitajika (uhamisho wa thamani kubwa, eneo hatarishi) → muamala unarudisha AWAITING_USER na Didit inaunda kipindi cha kurekebisha kiotomatiki, ikirudisha URL ya uthibitishaji kwenye jibu

Timu yako ya kufuata sheria inachunguza kesi, inaomba data zaidi ikiwa inahitajika, na kuidhinisha au kukataa kutoka ndani ya Console. Maelezo ya mkaguzi, uamuzi, na muhuri wa muda hurekodiwa kwa ajili ya kifurushi cha ukaguzi.

Ufuatiliaji unaoendelea unaonekanaje chini ya Travel Rule?

Data ya Travel Rule inakusanywa kwa kila uhamisho, si kwa kila uhusiano, hakuna "kuburudisha" kwa pakiti ya Travel Rule. Lakini watumiaji walio nyuma ya uhamisho lazima wafuatiliwe mfululizo chini ya kifurushi cha EU AML na mifumo sawa.

Didit inaendesha:

  • Ufuatiliaji endelevu wa AML kwa kila mtumiaji aliyethibitishwa, uchunguzi upya wa kila siku kiotomatiki dhidi ya vikwazo 1,300+, PEP, na orodha za habari mbaya, $0.07 kwa mtumiaji kwa mwaka kwenye akaunti zenye kiasi kikubwa
  • Injini ya sheria ya Ufuatiliaji wa Muamala kwa kila uhamisho, kasi, kiasi, jiografia, kategoria ya pochi ya mshirika, mifumo ya upangaji
  • Uburudishaji wa Uchunguzi wa Pochi kwenye anwani za mshirika zinazoendelea, ikiwa pochi iliyokuwa safi hapo awali baadaye itapigwa marufuku, mfumo unaionyesha

Zote tatu zinalisha sehemu moja ya Usimamizi wa Kesi, kwa hivyo mkaguzi mmoja anaona picha kamili kwa kila mtumiaji.

Ni rekodi gani ninahitaji kuhifadhi, na wapi?

Wadhibiti wengi wanahitaji angalau miaka 5 ya rekodi kwenye kila uhamisho wa Travel Rule na utambulisho wa mtumiaji, wakati mwingine muda mrefu zaidi ikiwa msimamizi wako ataomba.

Mfumo wa uhifadhi wa Didit:

  • Ushahidi wote umehifadhiwa katika Umoja wa Ulaya, vituo vya data vilivyodhibitiwa vya EU, hakuna uhamisho wa mpaka kwa wateja wa EU
  • Rekodi kwa kila uhamisho, malipo kamili ya IVMS-101, matokeo ya uchunguzi wa pochi, uamuzi, muhuri wa muda wa HMAC uliosainiwa
  • Rekodi kwa kila mtumiaji, ushahidi wa KYC (hati, kibayometriki, AML, kifaa + IP), masasisho juu ya uhusiano
  • Imehifadhiwa kwa muda usiojulikana wakati usajili wako unatumika, hakuna bili ya uhifadhi kwa kila rekodi
  • Inaweza kusanidiwa kwa kila mtiririko wa kazi ikiwa msimamizi wako anaagiza muda maalum (kifurushi cha AML kinaruhusu upanuzi hadi miaka 10 kwenye mahusiano hatarishi)
  • Hamisha wakati wowote kupitia Business Console au API

Didit ndio jukwaa pekee la KYC lenye uthibitisho rasmi wa serikali ya nchi mwanachama wa EU, Hazina ya Hispania, Banco de España, na SEPBLAC kwa pamoja walithibitisha huduma hiyo kuwa salama zaidi kuliko uthibitishaji wa ana kwa ana. Ripoti hiyo inaingia moja kwa moja kwenye kifurushi chako cha idhini ya CASP.

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