Skip to main content
Diditが750万ドルを調達、本人確認と不正対策のインフラを構築
Didit
マーケットプレイス出品者KYB

ワンコールですべての出品者を認証。登録情報、所有者、AMLをまとめて。

企業情報を取得し、すべての実質的支配者を特定し、それぞれにKYCを実行します。出品者1人あたり$2.00、所有者1人あたり$0.33です。毎月500回まで無料。

無料で始めるドキュメントを読む
支援元
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

世界中の2,000以上の組織から信頼されています。

映画のような暗い抽象的なマーケットプレイスKYBのイラスト, 純粋な黒の背景に、発光するDiditブルーの線で結ばれ、4つのスキャナーブラケットで囲まれた、垂直に積み重ねられた4枚の半透明なガラスパネル。各パネルには、小さな抽象的な淡い白色のモチーフ（店舗、登記書類、所有権チャート、印鑑）が描かれています。

マーケットプレイスの義務

企業を把握し、所有者を特定する。出品開始前に。

EUデジタルサービス法と新しいAMLパッケージにより、出品者の本人確認は法的な義務となりました。Diditはこれを単一のワークフローとして提供します。登記情報の検索、所有者の抽出、各所有者のKYC、書類のOCR処理まで、すべて同じ出品者レコードに紐付けられます。出品者1人あたり$2.00、所有者1人あたり$0.33。毎月500件の確認が無料です。

仕組み

サインアップから認証済みユーザーまで、4つのステップで完了。

  1. ステップ 01

    ワークフローを作成

    ID、生体認証、顔照合、制裁リスト、住所、年齢、電話番号、メールアドレス、カスタム質問など、必要なチェックを選択します。ダッシュボードでフローにドラッグ＆ドロップするか、同じフローをAPIにポストします。条件分岐やA/Bテストもコード不要で実行できます。

  2. ステップ 02

    連携

    Web、iOS、Android、React Native、Flutter SDKを使ってネイティブに組み込むか、ホストされたページにリダイレクトします。または、メール、SMS、WhatsAppなど、どこからでもユーザーにリンクを送るだけ。あなたのスタックに合った方法を選んでください。

  3. ステップ 03

    ユーザーがフローを完了

    Diditはカメラ、照明の指示、モバイル連携、アクセシビリティをホストします。ユーザーがフローを実行している間、200以上の不正信号をリアルタイムでスコアリングし、すべてのフィールドを信頼できるデータソースと照合します。2秒以内に結果が出ます。

  4. ステップ 04

    結果を受け取る

    リアルタイムの署名付きWebhookにより、ユーザーが承認、却下、または審査に送られた瞬間にデータベースが同期されます。必要に応じてAPIをポーリングすることも可能です。または、コンソールを開いてすべてのセッション、すべての信号を検査し、ケースを管理することもできます。

マーケットプレイス向けに構築 · インフラのような価格設定

1つのワークフロー。出品者1人あたり$2.00。

規制対象のマーケットプレイス出品者確認は、単一のチェックではありません。登記情報の検索、所有者の抽出、所有者ごとのKYC、AMLスクリーニング、書類のOCR処理、継続的なモニタリングといった要素の組み合わせです。ワークフローごとに各モジュールを切り替えることができます。
ドキュメントを読むAPIキーを取得
01 · 登記情報検索

販売者の法的記録をリアルタイムで確認。

英国のCompanies House、スペインのMercantil、ドイツのHandelsregister、ブラジルのJunta Comercialなど、200以上の国の公的機関から直接取得。法人名、登録番号、ステータス、設立日。スクレイピングや古いデータは一切ありません。
ビジネス認証モジュール
02 · 実質的支配者抽出

25%以上の全所有者を網羅。

実質的支配者（UBO）の抽出により、出品者の25%以上を所有するすべての個人を特定し、クローズドループKYCに備えます。登記情報源から取締役や株主を抽出し、自己申告ではなく証明可能なリストを作成します。
ビジネス認証モジュール
03 · 所有者ごとのKYC

全所有者のクローズドループID。

各実質的支配者には、ID確認、パッシブ生体認証、顔照合（1:1）、デバイス+IP分析、AMLを含むホスト型KYCセッションが提供されます。所有者1人あたり$0.33。結果は親KYBレコードに紐付けられ、一度の承認で出品者全体の承認が完了します。
ユーザー認証モジュール
04 · 法人AML

1,300以上のリストで企業をスクリーニング。

制裁リスト、政治的要人（PEP）リスト、ネガティブメディアリストを毎日更新し、14言語に対応。ヒットがあった場合は自動的にケースが作成され、承認前に出品者をゲートします。企業とすべての所有者をカバーします。
AMLスクリーニングモジュール
05 · 書類収集 + OCR

署名済みのエビデンスパックを1つに集約。

法人設立証明書、納税登録、事業所住所証明書は、ホスト型フローを通じて収集され、OCRで読み取られます。登記記録と相互チェックされるため、改ざんされたアップロードは監査ログに記録される前に拒否されます。
データベース検証モジュール
06 · 継続的なモニタリング

オンボーディング後も認証状態を維持。

出品者とすべての所有者に対する日次AML継続モニタリング（$0.07/ユーザー/年）、解散に関する登記ステータス監視、所有者の25%以上の変更があった場合の警告、書類の有効期限切れリマインダー。出品者が販売を続ける限り、コンプライアンスを維持します。
ワークフローオーケストレーター
連携

1セッション。1Webhook。すべての出品者に対応。

KYBセッションを開始し、署名付きの判定結果を読み込み、出品者を有効化します。
POST /v3/session/KYB
$ 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_kyb_marketplace",
    "vendor_data": "seller-42",
    "expected_country": "GB"
  }'
201作成済み{ "url": "verify.didit.me/..." }
このURLを販売者にメールで送信してください。ステータス更新はWebhookを通じて通知されます。ドキュメント →
GET /v3/session/{id}/decision/決定
$ curl https://verification.didit.me/v3/session/$SESSION/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Decision payload (excerpted):
{ "session_kind": "business", "status": "APPROVED",
  "decision": { "company": { "legal_name": "Maker Goods Ltd.", "registry_status": "ACTIVE" }, 
    "key_people": [ ... kyc_session_url per owner ... ]
  } }
200OKstatus APPROVED · IN_REVIEW · DECLINED · AWAITING_USER
各所有者のkyc_session_urlは、親KYBに紐付けられます。ドキュメント →
エージェント対応統合

マーケットプレイス販売者KYBを1つのプロンプトで実装。

Claude Code、Cursor、Codex、Devin、Aider、またはReplit Agentに貼り付けてください。スタックを記入すると、エージェントがワークフローを構築し、出品者ごとにセッションを起動し、所有者ごとにリンクされたKYCを駆動し、Webhookを接続します。
didit-integration-prompt.md
You are integrating Didit into a marketplace that lists third-party sellers (Etsy, Shopify, Faire, Amazon Handmade, OnBuy archetype). EU Digital Services Act Article 30 and the new EU Anti-Money Laundering (AML) package require you to verify the seller (KYB) before any listing goes live, and to keep that verification fresh while they sell.

Four obligations on every seller:

  1. Pull the company's registry record (legal name, registration number, status, incorporation date) from the authoritative government source.
  2. Extract every Ultimate Beneficial Owner (UBO) — anyone owning 25% or more — and run a closed-loop KYC on each one.
  3. Screen the company AND every UBO against sanctions, Politically Exposed Persons (PEP), and adverse-media lists.
  4. Collect the corporate evidence (certificate of incorporation, tax registration, proof of business address) and watch the seller continuously for status changes, UBO turnover, AML hits, and document expiry.

Pricing (verified live):
  - KYB session (registry + company AML + documents + key-people flow): $2.00 per seller, pay-per-call
  - Linked KYC per UBO: $0.33 per UBO (ID + Passive Liveness + Face Match + IP + AML)
  - Ongoing AML monitoring: $0.07 per user per year
  - 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 for KYB from the Workflow Builder. The workflow's type (KYC or KYB) drives the session shape — no explicit business flag is needed on the request.
  - A workflow_id for KYC bundled with ID + Passive Liveness + Face Match + IP + AML, used for the linked UBO sessions.

STEP 1 — Create the KYB session

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<your KYB workflow id>",
      "vendor_data": "<your seller id, max 256 chars>",
      "callback_url": "https://<your-app>/sellers/kyb/callback",
      "expected_country": "GB",
      "metadata": {
        "seller_id": "<your internal seller id>",
        "marketplace_segment": "handmade"
      }
    }

  Response: 201 Created with the hosted session URL. Email it to the seller or embed it in your onboarding UI. Behind the scenes, Didit runs:
    - kyb_registry — live registry lookup against the country's authoritative source
    - kyb_company_aml — sanctions / PEP / adverse media on the company
    - kyb_documents — document collection + Optical Character Recognition (OCR) (incorporation, TIN, proof of address)
    - kyb_key_people — UBO + director extraction with linked-KYC sessions

STEP 2 — Read the signed webhook on KYB completion

  Didit POSTs to your callback. KYB SESSION statuses are UPPER_SNAKE_CASE:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "session_kind": "business",
      "vendor_data": "<your seller id>",
      "status": "APPROVED",
      "decision": {
        "company": {
          "legal_name": "Maker Goods Ltd.",
          "registration_number": "1029847",
          "country_code": "GB",
          "registry_status": "ACTIVE"
        },
        "features": [
          { "node_id": "kyb_registry", "status": "APPROVED" },
          { "node_id": "kyb_company_aml", "status": "APPROVED", "total_hits": 0 },
          { "node_id": "kyb_documents", "status": "APPROVED" },
          { "node_id": "kyb_key_people", "status": "APPROVED",
            "key_people": [
              { "uuid": "<uuid>", "name": "Sara Ortega", "role": "director", "is_ubo": true, "ownership_percentage": 60, "kyc_status": "Approved", "kyc_session_url": "https://verify.didit.me/..." },
              { "uuid": "<uuid>", "name": "Niels Janssen", "role": "shareholder", "is_ubo": true, "ownership_percentage": 30, "kyc_status": "Approved", "kyc_session_url": "https://verify.didit.me/..." }
            ]
          }
        ]
      }
    }

  SESSION status enum (KYB · UPPER_SNAKE_CASE):
    NOT_STARTED | IN_PROGRESS | AWAITING_USER | APPROVED | DECLINED | IN_REVIEW | RESUBMITTED | ABANDONED | EXPIRED

  FEATURE status enum (inside decision.features[].status · UPPER_SNAKE_CASE):
    NOT_FINISHED | APPROVED | DECLINED | IN_REVIEW | RESUB_REQUESTED | AWAITING_USER

  Note: kyc_status on key_people IS Title Case ("Approved" / "Declined" / "Pending") — those are KYC sessions linked from inside the KYB feature, not KYB features themselves.

  Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.

STEP 3 — Linked KYC on each UBO is automatic

  When the seller completes the hosted KYB flow and submits the UBO list, Didit spawns a child KYC session per UBO using the KYC workflow you configured on the KYB workflow. Each child session has its own session_id and its own hosted URL on the kyc_session_url field inside the key-people block.

  You don't need to call POST /v3/session/ again for the UBOs — they're stitched to the parent KYB session automatically. You DO need to drive each UBO through their hosted KYC URL (email it, SMS it, embed it in your seller dashboard).

  Per-UBO KYC session status is Title Case With Spaces (KYC convention):
    Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned

  Linked-KYC pricing: $0.33 per UBO.

STEP 4 — Retrieve the decision

  GET https://verification.didit.me/v3/session/{sessionId}/decision/
  Headers:
    x-api-key: <your api key>

  Returns the full KYB decision payload — company block, AML hits, document OCR, every UBO with their kyc_status and kyc_session_url. Use this for audit-pack export and for re-rendering the seller status in your admin UI.

STEP 5 — Decide

  Branch logic:
    APPROVED       → activate the seller, allow listings.
    IN_REVIEW      → keep listings off, wait for analyst webhook update.
    DECLINED       → refuse onboarding, log the decision_reason_code.
    AWAITING_USER  → nudge the seller to complete the pending step (typically UBO list submission).

  Pre-DSA Article 30: store the trader information (legal name, registration number, address, contact) in your trader-information record alongside the decision payload.

STEP 6 — Ongoing monitoring is automatic when enabled

  Enable Ongoing AML on the seller and on each UBO ($0.07/user/year). The session status updates automatically as new sanctions hits land, dissolutions are filed in the registry, or document expirations approach. Your webhook fires on every state change.

  No separate endpoint to call — the same workflow drives it.

WEBHOOK EVENT NAMES
  - status.updated — session status changed (filter on data.session_kind === "business" for KYB).
  - data.updated — session data changed (registry refresh, key-people submission, document upload, ongoing AML hit).
  - business.status.updated — the linked Business entity changed.
  - business.data.updated — Business entity data changed.

  Verify X-Signature-V2 on every payload. The webhook secret is per-environment — sandbox key is separate from production.

CONSTRAINTS
  - KYB session statuses use UPPER_SNAKE_CASE (APPROVED, IN_REVIEW, DECLINED). KYC session statuses use Title Case (Approved, In Review, Declined). They live in different APIs — don't mix them in the same code path.
  - Default record retention is 5 years post-relationship per the EU AML package; some jurisdictions go higher.
  - You cannot replace the registry lookup with a self-attested form — DSA Article 30 requires the data to come from an authoritative source.

Read the docs:
  - https://docs.didit.me/business-verification/integration-guide
  - https://docs.didit.me/business-verification/statuses
  - https://docs.didit.me/business-verification/webhooks
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/retrieve-session
  - https://docs.didit.me/integration/webhooks

Start free at https://business.didit.me — sandbox key in 60 seconds, 500 KYC verifications free every month, no credit card.
さらに詳しい情報が必要ですか？モジュールの全ドキュメントをご覧ください。docs.didit.me →
設計段階からのコンプライアンス

ワンクリックで新しい国に進出。 面倒な作業は私たちにお任せください。

私たちは現地法人を設立し、ライセンスを取得し、ペネトレーションテストを実施し、認証を取得し、新しい規制すべてに準拠します。新しい国で認証を提供するには、トグルを切り替えるだけです。220以上の国で稼働しており、四半期ごとに監査とペネトレーションテストを実施しています。EU加盟国の政府が対面認証よりも安全だと正式に認めた唯一のIDプロバイダーです。
セキュリティ＆コンプライアンス資料を読む
EU金融サンドボックス
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
情報セキュリティ · 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準拠

実績データ

実績データ
  • $0.00
    KYBセッションあたり, 登記、AML、書類、主要人物フロー。
  • $0.00
    受益者（25%以上）ごとのリンクされたKYC。
  • 0+
    政府登記カバー率が有効な国。
  • 0
    毎月、すべてのアカウントで無料のKYC認証。
3つのティア、1つの料金表

無料で開始。従量課金。エンタープライズまで対応。

毎月500回まで無料認証を永続的に提供。本番環境では従量課金。エンタープライズプランではカスタム契約、データレジデンシー、SLA（サービスレベルアグリーメント）に対応します。
無料

無料

月額$0。クレジットカード不要。

  • 無料KYCバンドル（本人確認 + パッシブ・ライブネス + 顔照合 + デバイス＆IP分析）, 毎月500回まで
  • ブロックリストユーザー
  • 重複検出
  • すべてのセッションで200以上の不正シグナル
  • Diditネットワーク全体でのKYC再利用
  • ケース管理プラットフォーム
  • ワークフロービルダー
  • 公開ドキュメント、サンドボックス、SDK、MCP (Model Context Protocol) サーバー
  • コミュニティサポート
無料で始める
最も人気
従量課金

従量課金

使った分だけお支払い。25以上のモジュール。モジュールごとの公開価格、月額最低料金なし。

  • フルKYC（本人確認 + 生体認証 + IP / デバイス）が$0.33
  • 10,000以上のAMLデータセット, 制裁、PEP、ネガティブ情報
  • データベース検証のための1,000以上の政府データソース
  • トランザクションモニタリングが1トランザクションあたり$0.02
  • ライブKYBが1企業あたり$2.00
  • ウォレットスクリーニングが1チェックあたり$0.15
  • ホワイトラベル検証フロー, あなたのブランド、私たちのインフラ
全料金を見る無料で始める
エンタープライズ

エンタープライズ

カスタムMSA & SLA。大量利用や規制対象プログラム向け。

  • 年間契約
  • カスタムMSA、DPA、SLA
  • 専用SlackおよびWhatsAppチャンネル
  • オンデマンドの手動レビュー担当者
  • リセラーおよびホワイトラベル条件
  • 限定機能とパートナー連携
  • 専任CSM、セキュリティレビュー、コンプライアンスサポート
お問い合わせ

無料で開始 → チェック実行時のみ支払い → カスタム契約、SLA、データレジデンシーが必要な場合はエンタープライズプランへ。

FAQ

よくある質問

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 does KYB actually mean for a marketplace?

Know Your Business (KYB) is the process of verifying that a company is real, that it's still trading, and that you know who actually owns and controls it. For a marketplace it has three pieces:

  • Verify the company, name, registration number, status, and incorporation date pulled from the country's official registry
  • Find the beneficial owners, every person owning 25% or more of the company
  • Run KYC on each owner, same identity check you'd run on a consumer signup, just multiplied by the number of owners

It's the business-side equivalent of KYC (Know Your Customer). On a marketplace that lists third-party sellers, you owe it before any listing goes live. Didit ships the whole recipe as one workflow for $2.00 per seller + $0.33 per owner.

Who actually has to do this?

Any marketplace that lets a third party offer goods or services to consumers and takes payment for it. That covers:

  • Goods marketplaces, Etsy, Shopify, Faire, Amazon Handmade, OnBuy archetype
  • Service marketplaces, Fiverr, Upwork, Bark, ClassPass for studios
  • Travel and stays, Booking, Airbnb hosts who operate as businesses
  • Food and delivery, restaurant partners on Uber Eats, DoorDash, Deliveroo
  • Mobility, drivers and operators on Uber, Bolt, Cabify

In the European Union the Digital Services Act (the EU's online-platform rulebook) makes seller verification a hard requirement, with material fines for non-compliance. The UK, US, and most of Latin America have parallel obligations under their own consumer-protection and anti-money-laundering rules.

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 goes wrong if I skip KYB?

Three things, in order of how often they bite a marketplace:

  • Fraud sellers, fake businesses listing real goods they don't have, collecting payment, vanishing. The marketplace eats the chargebacks and the brand damage.
  • Sanctioned counterparties, selling on behalf of a designated entity or person. In the EU and US this is strict liability; the marketplace owes the fines regardless of intent.
  • Regulator enforcement, under the EU Digital Services Act the European Commission can fine a very-large online platform up to 6% of global turnover. National regulators have parallel enforcement under consumer-protection law.

The historical record on this is unforgiving. Almost every major marketplace has been fined for letting unverified sellers operate. KYB is the standard control.

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.

How do statuses work?

Two enum sets, one per session kind:

  • KYB session, APPROVED, IN_REVIEW, DECLINED, AWAITING_USER, plus the resubmitted / abandoned / expired states the docs cover
  • Linked KYC session per owner, Approved, In Review, Declined, Resubmitted, Expired, Not Finished, Kyc Expired, Abandoned

The casing difference is deliberate, UPPER_SNAKE for the KYB session, Title Case for the KYC session. They sit in different APIs; don't mix them in the same code branch.

For a webhook handler, switch on the parent KYB status. AWAITING_USER is the most common interim state, it usually means the seller still has to submit the owner list or re-upload a document. The state transitions to IN_REVIEW or APPROVED automatically once they do.

What does ongoing monitoring look like?

Verification at signup is necessary but not sufficient, sellers change over time, owners move in and out, and sanctions lists update daily. Didit's ongoing monitoring catches all of it:

  • Ongoing AML on the company and every owner, daily delta refresh at $0.07 per user per year
  • Registry status watch, dissolutions, strike-offs, and adverse filings trigger a webhook the day they hit the source
  • Ownership change detection, if a new UBO crosses the 25% threshold, the seller is automatically queued for re-KYB
  • Document expiry, passport, ID card, and address proof expirations fire a 30-day-out reminder

Everything flows through the same status.updated webhook you already wired for onboarding. No new endpoint, no extra integration.

How does Didit compare on price?

Most KYB providers price between $8 and $50 per check, often with floor commits in the thousands of dollars per month and per-country surcharges. The Middesk / Persona KYB / Onfido Business archetype.

Didit's published price is $2.00 per KYB session + $0.33 per linked KYC. No floor, no commit, no per-country surcharge, no hidden registry fees. Pay only for what runs.

That's 3–5× cheaper than the incumbent stack on the same regulatory output. The economics matter because seller verification is a per-listing cost, at scale the difference between $2 and $25 is the difference between accepting a seller and refusing them. Full pricing at /pricing.

Related

関連モジュール + ワークフロー

本人確認と不正対策のインフラ。

KYC、KYB、取引監視、ウォレットスクリーニングを一つのAPIで。5分で統合できます。

無料で始めるお問い合わせ
AIにこのページの要約を依頼する