Know Your Business

KYB API for Business Verification and Screening

In beta, enrich a UK Companies House company record where configured, screen the company and returned people against the sources available to your plan, and keep registry evidence distinct from screening results.

Start in the dashboard. Integrate the API when the workflow is proven.

Decision record

Evidence, not a black box

Reviewable
Coverage
Successful, unavailable, and stale sources remain explicit
Evidence
Publisher context and match reasoning travel with the result
Decision
Actionable, review, or clear semantics stay distinguishable
Audit
The screening state can be reconstructed later

Built around the reviewer

The right workflow starts with the decision you need to defend.

01

Fintechs and payment companies

Onboarding business customers, merchants, and payment recipients.

02

Marketplaces and platforms

Verifying business sellers, suppliers, and partners before transacting.

03

Legal and accounting firms

Checking client companies, directors, and counterparties for AML files.

Clear scope

What the workflow does

  • Uses UK Companies House company, officer and PSC context in the configured beta workflow.
  • Screens the company and returned people against sources available to the account plan.
  • Keeps registry context distinct from sanctions, PEP and watchlist screening outcomes.
  • Records the executed request and screening evidence for review.

Honest boundaries

What it does not claim

  • Does not provide global automated company verification or coverage in every jurisdiction.
  • Does not prove a complete ownership graph or confirm a beneficial owner.
  • Does not turn unavailable registry or screening data into a clear result.
  • Does not certify a company as legitimate or guarantee its standing.
  • Does not provide legal or compliance advice.

One workflow, two entry points

Prove the operation before you automate it.

The dashboard and API share the same screening semantics, so an operational pilot can become a production integration without redefining the decision.

No-code dashboard

Review configured UK Companies House context and the separate screening result side by side.

REST API

Use the beta UK KYB workflow, then inspect its source and screening evidence before acting.

curl -X POST https://api.verifex.dev/v1/screen \
  -H "Authorization: Bearer vfx_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"name": "Acme Trading Ltd", "type": "entity"}'
Evidence by design

The result is useful now. The evidence makes it defensible later.

Each completed request records the company context used, the separate screening result, source and coverage state, a timestamp and a request identifier. Registry context does not prove sanctions status or ownership completeness.

Explore the evidence record

Questions before integration

Read the boundary conditions, not just the feature list.

What is available today?

The automated KYB workflow is beta, uses UK Companies House context where configured, and requires Starter or above. It is not a global automated KYB service.

What company data does Verifex use?

The beta workflow uses UK Companies House company, officer and PSC context where available. GLEIF and ownership workflows are separate product contexts, not proof of sanctions status.

Does KYB confirm beneficial ownership?

No. The workflow can surface company and PSC context, but it does not prove a complete ownership graph or confirm a beneficial owner. See the UBO screening API for ownership-risk analysis.

Is a clear company result a guarantee?

No. A no-hit alone is not a clearance. Treat a result as clear only when Standard Screening is clearance-eligible, source coverage is complete, the candidate set is complete, and the result has zero matches. Otherwise the result remains unresolved and needs your policy or review. Verifex provides screening infrastructure and data-derived results, not legal or compliance advice.

Move from reading to evidence

Run a real workflow and inspect what comes back.

Verifex provides screening infrastructure and data-derived results, not legal or compliance advice. A no-hit alone is not a clearance. Treat a result as clear only when Standard Screening is clearance-eligible, source coverage is complete, the candidate set is complete, and the result has zero matches. Otherwise the result remains unresolved and needs your policy or review.