Console Guides

Identity Verification (KYC)

Verify your own organization to unlock billing and stablecoin payments, then optionally configure a webhook so your own end-users' and business customers' verification results get forwarded to your system.

Find it

Verification is in the sidebar under the Operations group. This page covers two distinct things: your own organization's platform KYC (a one-time gate, powered by Didit), and a separate white-label compliance webhook for verifying and monitoring your own end-users and businesses — the webhook section is owner/admin only.

Status, Compliance webhook

KYC page with a Status card showing Approved and a verified date, and a Compliance webhook card with a webhook URL field and a Default workflows section for KYC and KYB
An approved org — billing and stablecoin payments are unlocked — with a compliance webhook configured for white-label end-user verification
  1. Not started, In progress, Approved, or Declined. Anything short of Approved shows a Start verification / Continue verification button, which opens Didit's hosted flow in a new tab.
  2. Where your own system receives signed callbacks for your end-users' and businesses' verification events. Leave it empty and save (or use Clear) to disable delivery entirely.
  3. Which verification workflow to use when you start a session without naming one explicitly — one default for individual identity (KYC), one for business verification (KYB). Prices shown already include Mudbase's markup over Didit's wholesale rate.

Events, Signing secret

Event subscription checkboxes grouped by category, Save/Send test event/Clear buttons, a Signing secret card showing Configured, and the top of the Recent compliance events table
Three events selected out of the full set, plus an active signing secret
  1. Persists the webhook URL, selected events, and workflow defaults.
  2. Sends one real, signed kyc.test payload to your configured URL — disabled until a URL and signing secret both exist. Ignores your event selection.
  3. Clears the webhook URL, disabling delivery without touching your event selection or secret.
  4. Regenerate secret immediately invalidates the previous one — the new value is shown exactly once, in a modal, right after generating it.

Recent compliance events

Recent compliance events table with five rows showing event type, status, whether Mudbase forwarded it, and when it was received — a mix of forwarded and failed deliveries
Five real Didit webhook deliveries — two forwarding failures alongside three successful ones
  1. What Didit sent Mudbase, and whether it was forwarded to your endpoint. The Forwarded column shows Yes (200) on success or Failed (with an HTTP status when one exists) — useful for spotting a misconfigured or unreachable webhook URL without checking server logs.
Note
The org's own platform-KYC status (Status above) lives on the Org document directly — kycStatus and kycVerifiedAt — and is checked live by the billing-setup and stablecoin endpoints on every request, not just once at an earlier "unlock" step. If your org's KYC is later revoked or flagged, access to those features is lost immediately rather than continuing on a stale approval.