KYC / KYB
Verify people and businesses before they can act.
Identity verification for individuals and companies through pluggable providers — with a status other modules gate their own steps on.
Image slot — asset to come
Screenshot: a verification status screen, anonymised.
- 2
- Verification kinds
- Per tenant
- Provider choice
- 0
- Steps that skip verification
One flow, two audiences
Individuals go through KYC; companies go through KYB — the same flow serves both, launched as a task in onboarding.
- Identity verification for individual users
- Business verification with company documents
- A company's verification starts with its director's personal KYC
- Age and data validation before anything is submitted
Image slot — asset to come
Screenshot: the verification start screen, anonymised.
Pluggable providers
The tenant picks its verification provider in settings — Sumsub or Persona — and the flow stays the same.
- A per-tenant primary provider setting, with sandbox mode
- Embedded verification widget, or in-app collection with a hosted hand-off
- Swap the provider without retraining your team
Image slot — asset to come
Screenshot: the provider settings card, keys masked.
The paperwork, slot by slot
Business verification gathers exactly the corporate documents reviewers need.
- Commercial register and transparency register extracts
- Shareholders agreement and shareholders list
- Power of attorney when the signer is not in the register
- PDF upload with per-file size limits
A status everything else trusts
Submitting is not passing. A verification is complete only when the provider confirms it — and other modules key off that.
- Clear states from not-started through verified or failed
- Updates arrive by provider webhook, with polling and a manual re-check
- The next step — like opening a wallet — unlocks only after “verified”
- Forced re-verification can be triggered when compliance requires it
Image slot — asset to come
Screenshot: a task list with a step locked behind verification, anonymised.
Worth knowing: It verifies identity; it does not move money. Wallet-side compliance at a payment institution is the PSP module's separate axis.
What every module inherits.
- Installs from the marketplace with no redeploy — the menu and the permission list update immediately.
- Creates its own tables, in its own schema, inside that customer's database.
- Packages are cryptographically signed when they are built, and the signature is checked before the host unpacks one.
- Uninstall switches a module off and keeps its data. Dropping the tables is a separate, deliberate choice.
Works with
Want to see KYC / KYB running?
Thirty minutes, a live workspace, and an honest answer about what each module does and doesn't do yet. Missing a module? A custom build is a fixed-scope project, from €25.000.
Book a call