Ruka hadi maudhui makuu
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Crypto on-ramp

Thibitisha mnunuzi. Kagua wallet. Katika mtiririko mmoja wa kazi.

Didit inafanya kazi moja inayoshughulikia utambulisho wa mnunuzi na wallet anayotumia, kabla ya crypto kuondoka. Uthibitishaji 500 bila malipo kila mwezi.

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

Inaaminika na mashirika 2,000+ duniani kote.

On-ramp inapaswa kuwa na nini

Mjue mnunuzi. Jua pochi. Kabla ya fedha kuhamishwa.

Kila on-ramp inayodhibitiwa inahitaji pande zote mbili, KYC kwa mnunuzi + KYT kwa wallet anayotumia, kwa kila ununuzi. Didit inazileta kama mtiririko mmoja wa kazi: $0.33 KYC + $0.17 muamala (ukaguzi wa wallet uliosimamiwa umejumuishwa) = $0.50 kwa ununuzi. BYOK kwenye mtoa huduma wa wallet inashusha hadi $0.37. 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, liveness, face match, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko wa kazi kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna code inayohitajika.

  2. Hatua 02

    Unganisha

    Pachika moja kwa moja na SDK yetu ya Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu kiungo kwa mtumiaji wako, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.

  3. Hatua 03

    Mtumiaji anapitia mchakato

    Didit inasimamia kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mchakato, tunapima ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya kuaminika. Matokeo chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizosainiwa kwa wakati halisi huweka hifadhidata yako ikiwa sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Uliza API inapohitajika. Au fungua koni ili kukagua kila kikao, kila ishara, na kudhibiti kesi kwa njia yako.

Imejengwa kwa ajili ya on-ramps · Bei kama miundombinu

Ukaguzi sita. API calls mbili. $0.50 kwa kila ununuzi.

Ununuzi wa on-ramp unaodhibitiwa sio ukaguzi mmoja, ni mapishi. Washa kila moduli kwa kila mtiririko wa kazi, badilisha mtoa huduma wako wa ukaguzi wa wallet kupitia BYOK ili kushuka hadi $0.37 kwa kila ununuzi.
01 · Kifurushi cha KYC cha Mnunuzi

Hundi tano, simu moja.

ID, liveness, face match, kifaa + IP, AML, zimeunganishwa kwa $0.33 kwa kila mnunuzi. Imethibitishwa na iBeta Level 1 anti-spoof, uamuzi chini ya sekunde mbili, inasaidia nyaraka 14,000+ katika nchi 220+.
Moduli ya Uthibitishaji wa Mtumiaji
02 · Ukaguzi wa wallet (KYT)

Pima hatima kabla ya crypto kuondoka.

Inakamata wallets zilizowekewa vikwazo, mixers, exchange-high-risk, fedha zilizoibiwa. $0.15 kwa kila ukaguzi uliosimamiwa, au $0.02 kwa kila ukaguzi na key yako ya mtoa huduma. EVM, Bitcoin, TRON, Solana, L2s kuu.
Moduli ya Kuchunguza Wallet
03 · Ukaguzi wa AML

Chunguza kila mnunuzi dhidi ya orodha 1,300+.

Vikwazo, Watu Waliofichuliwa Kisiasa (PEP), habari mbaya, zinasasishwa kila siku, katika lugha 14. Hits hufungua kesi kiotomatiki na kuzuia ununuzi kabla ya idhini.
Moduli ya Kuchunguza AML
04 · Sheria ya Kusafiri (TFR)

Mwanzilishi + mnufaika kwenye kila uhamisho.

IVMS-101 payloads zinabadilishwa kupitia TRP, Sumsub Travel Rule, Notabene, Veriscope. Hakuna €1,000 de minimis chini ya EU TFR, kila uhamisho hubeba data ya mwanzilishi + mnufaika.
Muhtasari wa Sheria ya Usafiri wa Crypto
05 · Vikomo vya Muamala

Mipaka inayoendana na hatari ya mnunuzi.

Kasi ya wakati halisi, kiasi, chain, na vizingiti vya jiografia kwa kila mtiririko wa kazi. Inakamata mifumo ya uundaji kiotomatiki. Hariri sheria katika Workflow Builder isiyo na code bila ku-redeploy.
Moduli ya Ufuatiliaji wa Miamala
06 · Ufikiaji wa Off-ramp

On-ramp na off-ramp. Mfumo mmoja wa kazi.

Session ile ile ya /v3/ inashughulikia uondoaji: KYC muuzaji, KYT wallet chanzo, AML mnunuzi, faili ya Travel Rule packet. Mkataba mmoja, ankara moja, audit pack moja kwa pande zote mbili.
Mifumo ya kazi ya sekta ya Crypto
Unganisha

Session moja. Ukaguzi mmoja wa awali. Webhook moja.

Fungua session ya KYC. Kagua mapema wallet anayotumia. Soma uamuzi uliosainiwa. Toa crypto.
POST /v3/session/KYC
$ 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_onramp_kyc",
    "vendor_data": "buyer-42",
    "metadata": { "destination_wallet": "0x2dc1...81f9" }
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Zuia ununuzi hadi webhook iliyotiwa saini iseme status: Approved.nyaraka →
POST /v3/transactions/KYT
$ curl -X POST https://verification.didit.me/v3/transactions/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "transaction_id": "buy-42",
    "transaction_details": { "direction": "OUTBOUND", "currency_kind": "crypto" },
    "subject": { "vendor_data": "buyer-42", "full_name": "Jamie Example" },
    "counterparty": { "full_name": "Destination wallet", "payment_method": { "account_id": "0x2dc1...81f9" }}
  }'
201Imeundwa{ status IMEIDHINISHWA · INAPITIWA · IMETUPILIWA MBALI · INAMSUBIRI MTUMIAJI }
Uchunguzi wa pochi unafanywa upande wa server wakati currency_kind: "crypto". Hakuna simu ya pili.nyaraka →
Ujumuishaji tayari kwa agent

Anzisha mtiririko wa KYC + KYT wa on-ramp kwa prompt moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent atajenga mtiririko wa kazi, atazuia ununuzi kwenye skrini ya wallet, atawezesha ufuatiliaji endelevu, na kuunganisha webhook.
didit-integration-prompt.md
You are integrating Didit into a fiat-to-crypto on-ramp. Two obligations on every buy:

  1. Verify the buyer (KYC) — identity, liveness, face match, device + IP, AML against 1,300+ sanctions / PEP / adverse-media lists. ONE call to the Sessions API.
  2. Screen the destination wallet (KYT) — risk-score the address against sanctioned wallets, mixers, high-risk counterparties BEFORE the crypto leaves. ONE call to the Transactions API with currency_kind: "crypto".

Bundle pricing (verified live against POST /v3/transactions/, 2026-05-16):
  - KYC bundle: $0.33 per buyer (Sessions API)
  - Transactions API call: $0.02 base (transaction-monitoring) + $0.15 wallet screening (Didit's default managed provider) = $0.17 per buy
  - Total managed: $0.33 + $0.17 = $0.50 per fully-screened buy
  - Total with BYOK on the wallet provider: $0.33 + $0.04 = $0.37 per buy
  - First 500 KYC verifications free every month, forever

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60s, no card).
  - Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
  - A workflow_id from the Workflow Builder that bundles ID Verification + Passive Liveness + Face Match 1:1 + Device & IP Analysis + AML Screening.
  - Transaction Monitoring enabled in the Business Console (Transactions > Settings) with crypto screening turned on.

STEP 1 — Verify the buyer with the Sessions API

  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 buyer id, max 256 chars>",
      "callback": "https://<your-app>/onramp/kyc/callback",
      "metadata": {
        "purpose": "crypto_onramp_buy",
        "buy_id": "<your internal tx reference>"
      }
    }

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

STEP 2 — Read the signed webhook on KYC completion

  Didit POSTs to your callback. Session statuses are Title Case With Spaces:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your buyer id>",
      "status": "Approved",
      "id_verification": { "status": "Approved" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "ip_analysis": { "status": "Approved" },
      "aml": { "status": "Approved", "hits": [] }
    }

  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 — HMAC SHA-256 of the raw bytes with your webhook secret.

STEP 3 — Screen the destination wallet BEFORE crediting the buy

  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 buy reference>",
      "transaction_category": "finance",
      "include_crypto_screening": true,
      "transaction_details": {
        "direction": "OUTBOUND",
        "amount": "0.25",
        "currency": "ETH",
        "currency_kind": "crypto",
        "action_type": "withdrawal"
      },
      "subject": {
        "entity_type": "individual",
        "vendor_data": "<your buyer id>",
        "full_name": "<buyer full name>"
      },
      "counterparty": {
        "entity_type": "unhosted_wallet",
        "full_name": "<destination wallet label>",
        "payment_method": {
          "method_type": "crypto_wallet",
          "account_id": "<destination 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
    - For crypto: a wallet address on counterparty.payment_method.account_id (OUTBOUND) or subject.payment_method.account_id (INBOUND post-transfer)

  Wallet screening runs server-side when currency_kind = "crypto" and there is a wallet address in the right participant. No separate endpoint.

  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,                       // null when score is 0; LOW | MEDIUM | HIGH | CRITICAL | UNKNOWN otherwise
      "props": {
        "wallet_risk_score": 0,
        "sanctions_hit": false,
        "pep_counterparty": false,
        "aml_provider": "<provider slug>",    // identifies the screening provider used on this call
        "aml_screening_type": "WALLET_SCREENING",
        "aml_screening_status": "COMPLETED"
      },
      "provider_results": [{ "provider": "<provider slug>", "result_type": "WALLET_SCREENING", "status": "SCREENED", ... }],
      "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.
  When a transaction enters AWAITING_USER, Didit creates a linked remediation session automatically and returns a verification URL on the response.

  Real per-transaction cost (verified live):
    - Plain fiat transaction monitoring: $0.02
    - Crypto transaction with managed wallet screening: $0.17 ($0.02 TM base + $0.15 wallet screen on Didit's managed flow)
    - Crypto transaction with BYOK wallet screening: $0.04 ($0.02 TM base + $0.02 wallet screen)

  Branch logic:
    APPROVED       → send the crypto.
    IN_REVIEW      → hold the buy, route to analyst queue.
    DECLINED       → refund the fiat, block the address.
    AWAITING_USER  → redirect the buyer to the remediation session URL.

STEP 4 — Ongoing AML monitoring is automatic

  Any session with AML enabled is rescreened DAILY by Didit's continuous monitoring at $0.07 per user per year. There is NO separate endpoint to call — the same workflow does it.

  When a previously-approved buyer crosses an AML threshold, the session status changes to "In Review" or "Declined" automatically and your webhook fires the update.

STEP 5 — Off-ramp uses the same two endpoints

  Selling crypto for fiat:
    - KYC the seller via POST /v3/session/ (same as Step 1).
    - Screen the source wallet via POST /v3/transactions/ with direction: "INBOUND" and the source wallet address on subject.payment_method.account_id.

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 use Title Case With Spaces (Approved, In Review). Transaction statuses use UPPER_SNAKE_CASE (APPROVED, IN_REVIEW). They live in different APIs — don't mix them in the same code path.
  - Wallet Screening MUST run BEFORE the crypto leaves — a post-transfer screen is useful for audit but useless for blocking.
  - Default record retention is 5 years post-relationship per the EU AML package; extend per your supervisor's guidance.
  - 200+ fraud signals are evaluated on every KYC session at no extra cost — surface the score via the session decision payload, don't re-query.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/transaction-monitoring/overview
  - https://docs.didit.me/transaction-monitoring/aml-screening
  - 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
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.00
    Kwa kila ununuzi uliokaguliwa kikamilifu, kifurushi cha KYC + muamala na ukaguzi wa wallet.
  • 0+
    Vikwazo, Watu Walio Hatari Kisiasa (PEP), na orodha za habari mbaya hukaguliwa kwa kila mnunuzi.
  • <0s
    Matokeo ya KYC kamili kwa kila kipindi, kwenye Android ya kiwango cha chini.
  • 0
    Uthibitishaji wa bure kila mwezi, kwenye 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
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, 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, 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

Nyayo 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 inaboresha kila siku.

Njia ya kuingia ya crypto ni nini, na kwa nini inahitaji ukaguzi miwili?

Njia ya kuingia ni huduma inayomruhusu mtu kulipa kwa kadi au uhamisho wa benki na kupokea crypto kwenye pochi yake. Fikiria MoonPay, Ramp, Transak, na wateja wa Didit kama vile AhoraCrypto na GBTC Finance.

Mambo mawili yanaweza kwenda vibaya kwenye kila ununuzi, kwa hivyo unahitaji ukaguzi miwili:

  • Mthibitishe mnunuzi, je, ni halisi, je, ndiye anayejifanya kuwa, je, yuko kwenye orodha ya vikwazo
  • Chunguza pochi inayolengwa, je, anwani hiyo imeonekana kwenye mixer, hack, au kundi lililowekewa vikwazo

Mnunuzi safi bado anaweza kutuma fedha kwenye pochi mbaya, na pochi safi bado inaweza kufadhiliwa na mnunuzi mbaya. Ukaguzi wote, kila ununuzi. Didit inazitoa kama mtiririko mmoja wa kazi kwa $0.50 kwa kila ununuzi ($0.33 KYC + $0.17 muamala na uchunguzi wa pochi unaosimamiwa), au $0.37 unapoleta ufunguo wako wa uchunguzi wa pochi.

KYC dhidi ya KYT, tofauti ni nini?

KYC inahusu mtu: jina, hati, uso, vikwazo, na mahali anapoingia. Unaifanya mara moja wakati wa kujisajili na kuiboresha baadaye.

KYT inahusu wallet: iko wapi kwenye grafu ya on-chain, imefanya miamala na nani, na kama imewekewa alama. Unaifanya kwenye kila muamala.

On-ramp iliyodhibitiwa inahitaji zote mbili. Didit inakupa mfumo mmoja unaofanya KYC kwa mnunuzi na KYT kwa wallet lengwa katika mtiririko mmoja, hakuna sehemu za ziada zinazohitajika.

Uthibitishaji unachukua muda gani kwa mtumiaji wangu?

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 back end, Didit inarudisha matokeo kwa chini ya sekunde mbili kwa p99, kipimo kinachoanzia wakati mtumiaji anamaliza selfie hadi wakati webhook yako inapoanza. Upigaji picha wa simu umeboreshwa kwa simu za polepole na mitandao dhaifu: ukandamizaji wa picha unaoendelea, upakiaji wa polepole wa software development kit, na uhamishaji wa haraka kutoka kompyuta hadi simu kupitia QR code ikiwa mtumiaji anaanza kwenye wavuti.

Off-ramp pia?

Ukaguzi huo huo, mwelekeo tofauti:

  • Thibitisha muuzaji, mchakato wa KYC sawa na wa mnunuzi
  • Chunguza wallet chanzo, crypto inatoka WAPI, kabla hujaikubali. Inabaini mixers, mapato ya ransomware, anwani zilizowekewa vikwazo

Mfumo mmoja unashughulikia kununua na kuuza. Mkataba mmoja, ankara moja, rekodi moja ya ukaguzi kwa pande zote mbili.

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

Kila session huishia kwenye mojawapo ya statuses saba zilizo wazi, hivyo code yako inajua nini cha kufanya kila wakati:

  • Approved, ukaguzi wote umefaulu. Endeleza mtumiaji.
  • Declined, ukaguzi mmoja au zaidi umeshindwa. Unaweza kumruhusu mtumiaji kutuma upya hatua maalum iliyoshindwa (kwa mfano, piga tena selfie) bila kurudia mchakato mzima.
  • In Review, imewekewa 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.
  • Abandoned, mtumiaji alifungua kiungo lakini hakumaliza kwa wakati. Mshirikishe tena au muda wake uishe.
  • Expired, muda wa kiungo cha session umeisha. Unda session mpya.

Webhook iliyosainiwa inawaka kwenye kila mabadiliko ya status, hivyo database yako inabaki sawa kila wakati. Sessions zilizoachwa na zilizokataliwa ni bure.

Data ya mteja wangu inakaa wapi na inalindwaje?

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 wasimamizi wake wanahitaji.

Usimbaji fiche kila mahali. AES-256 ikiwa imetulia kwenye kila database, hifadhi ya vitu, na backup. Transport Layer Security 1.3 ikiwa safarini 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 chaguomsingi 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 Type 1 (ukaguzi wa Type 2 unaendelea), ISO/IEC 27001:2022, iBeta Level 1 PAD, na uthibitisho wa umma kutoka Tesoro / SEPBLAC / CNMV ya Hispania kwamba uthibitishaji wa utambulisho wa mbali wa Didit ni salama zaidi kuliko kumthibitisha mtu ana kwa ana. Ripoti kamili inapatikana /security-compliance.

Je, Didit inatii sheria za tasnia yangu?

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

  • GDPR + UK GDPR, mgawanyo wa mtawala / mchakataji, Mkataba kamili wa Uchakataji Data umechapiswa, mamlaka kuu ya usimamizi imetajwa (AEPD ya Hispania).
  • AMLD6 + EU AML Single Rulebook, orodha 1,300+ za vikwazo, watu walio wazi kisiasa, na orodha za habari mbaya zinachunguzwa kwa wakati halisi.
  • eIDAS 2.0, inalingana na EU Digital Identity Wallet; tayari kwa utambulisho unaoweza kutumika tena.
  • MiCA (Markets in Crypto-Assets), tayari kwa crypto on-ramps, exchanges, na custodians.
  • DORA, Digital Operational Resilience Act, uthabiti 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 wa California.
  • UK Online Safety Act, udhibiti wa umri na majukumu ya usalama wa watoto.
  • FATF Travel Rule, data ya mwanzilishi na mnufaika kwenye uhamishaji wa crypto, inaoana na IVMS-101.

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

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

Njia tatu za kuunganisha, chagua inayofaa 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 front-end.

Dashboard moja, bili moja, bei moja ya kulipa kwa mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua unapatikana docs.didit.me/integration/integration-prompt.

Je, inashughulikia Travel Rule?

Ndiyo. EU Travel Rule (Kanuni ya Uhamishaji wa Fedha) inasema CASPs lazima zibadilishane data ya mwanzilishi na mnufaika kwenye kila uhamishaji wa crypto, hakuna kiwango cha chini cha crypto katika EU.

Didit inashughulikia hili kwa:

  • IVMS-101 payloads, kiwango ambacho kila itifaki kuu ya Travel Rule inazungumza
  • Ushirikiano na TRP, Sumsub Travel Rule, Notabene, na Veriscope
  • Ufuatiliaji wa Miamala unaweka alama uhamishaji ambapo data ya mwanzilishi au mnufaika haipo au haifanani

Mfumo mmoja, pande zote mbili, KYC kwa mtumiaji, data ya Travel Rule kwenye uhamishaji.

Nini kinatokea ikiwa mnunuzi atawekewa alama baada ya kununua?

Didit inachunguza upya kila mnunuzi aliyeidhinishwa kila siku dhidi ya orodha zile zile 1,300+ zilizotumika wakati wa kujisajili. Ni otomatiki, hakuna endpoint tofauti ya kupiga, hakuna usanidi wa ziada, hakuna gharama ya ziada kwenye mipango mingi (na $0.07 kwa mtumiaji kwa mwaka kwenye akaunti zenye matumizi makubwa).

Mnunuzi aliyekuwa safi hapo awali anapovuka kiwango cha AML:

  • Status ya session inabadilika kuwa In Review au Declined kiotomatiki
  • Webhook iliyosainiwa inafika kwenye back-end yako na hits mpya
  • Kesi inafunguliwa kwenye Business Console na ushahidi wa awali wa onboarding kwa kubofya mara moja
  • Timu yako ya kufuata sheria inaweza kuwasilisha Ripoti ya Shughuli za Kutiliwa Mashaka (SAR) kutoka ndani ya kesi

Kwa msingi wa wanunuzi milioni moja, hiyo ni dola chache kwa mnunuzi kwa mwaka, nafuu zaidi mara nyingi kuliko foleni ya ukaguzi wa mikono.

Inachukua muda gani kusafirisha?

Sandbox kwa dakika 5. Uzalishaji kwa wikiendi.

  • Jisajili kwenye Business Console, ufunguo wa sandbox kwa sekunde 60, hakuna kadi
  • Jenga workflow kwenye no-code Workflow Builder, chagua modules za KYC + washa uchunguzi wa crypto kwenye mipangilio ya Transactions
  • Weka call moja kwenye hatua yako ya KYC (POST /v3/session/) na moja kwenye hatua yako ya kununua (POST /v3/transactions/)
  • Thibitisha webhook iliyosainiwa, iliyoidhinishwa inafungua ununuzi, iliyokataliwa inazuia fedha

Ikiwa unapendelea wakala wa AI aijenge (Claude Code, Cursor, Codex, Devin, Aider, Replit Agent), bandika prompt ya muunganisho kutoka sehemu iliyo hapo juu na wakala atajenga mtiririko. SDKs asili za Web, iOS, Android, React Native, na Flutter zote zinashiriki mfumo mmoja wa session.

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