Skip to main content
KYB (Know Your Business) verifies a company or business rather than a person. It applies to parties with partyType: ORGANISATION and is tracked on kybStatus — a different field with different values from KYC.

​
States

Read kybStatus from Get a party:
KYB does not reuse the KYC values. The pending state is PENDING, not VERIFICATION_PENDING, and the failure state is DENIED, not REJECTED. Only VERIFIED is shared.If you branch on verification status, read the field that matches the party’s type — a check written against VERIFICATION_PENDING silently never matches an organisation.

​
Create the party

name is required for organisations — and it must be the legal entity name, not a trading or display name, because it’s what gets checked against registry records and what appears as the beneficiary name on bank rails. vatNumber is optional but speeds verification along where you have it. firstName and lastName don’t apply to organisations.
Downstream bank-account provisioning requires the account holder to have a legal name. An organisation party with no name fails virtual-bank-account creation with party-name-required.

​
One route: hosted verification

Organisations verify through the hosted verification link. POST /parties/{partyId}/verification returns the KYB flow URL automatically — the party’s stored partyType decides which flow you get, so there is no parameter to set.
Sumsub token sharing is not available for organisations. It’s KYC-only. Supplying party.sumsubToken with partyType: ORGANISATION is rejected with 400 verification-kyc-only.

​
What gets collected

KYB verifies the business itself — registry existence, incorporation details, ownership structure — and typically also identifies its representatives and beneficial owners. That makes it a heavier process than individual KYC, and usually a slower one. Practically: expect KYB to sit in PENDING longer than KYC sits in VERIFICATION_PENDING, and don’t build UI that treats a multi-day pending state as an error.

​
After the verdict

The verdict flips kybStatus on the party and clears the account’s kycStatus for money movement. Note that the account field is called kycStatus regardless of whether its holder is an individual or an organisation — there is no kybStatus on an account. Register a webhook rather than polling for days.

​
If it’s denied

DENIED is terminal for that attempt. You can mint a fresh link — a DENIED party isn’t VERIFIED, so it won’t hit party-already-verified. For a disputed decision, quote the party’s ivCaseReference from Get verification linkage to Venly support.

​
Organisations as pay-out recipients

A verified organisation is often the beneficiary of a pay-out rather than the account holder. That needs a cleared kybStatus and an ACTIVE PAYOUT_RECIPIENT role on the paying account — see the recipient gate. A cleared KYB alone is not enough; a missing role surfaces as 422 recipient-not-authorized.

​
Next steps

Hosted verification link

The route organisations use.

Individual KYC

The natural-person equivalent.

Roles & entities

How an organisation party relates to accounts and pay-outs.

Troubleshooting

Every verification error code.