KYB is the business-level counterpart to KYC
You have probably met KYC — Know Your Customer — as an individual: a service asks for your identity before it lets you transact. KYB is the same idea applied to a legal entity. A crypto payment processor is onboarding a company, not a person, so the verification is about the company: that it is a real, registered business, that the people behind it are who they say they are, and that the nature of the business is understood before any money moves.
The reason this exists is not bureaucratic box-ticking. A payment processor sits in the flow of funds, and that position carries an obligation to know who is using the rails and for what. KYB is how that obligation is met at the start of the relationship. It is the gate that turns an anonymous signup into an accountable merchant account, which is what makes everything afterward — invoices, payouts, refunds — attributable to a known party.
Treat KYB as a one-time onboarding event with a long tail rather than a recurring tax. You go through it once to activate your account. Information you provide may be revisited if your business changes materially — a new beneficial owner, a different line of business — but the heavy lift is the initial review, and the better you prepare for it the faster it clears.
What KYB sets out to establish
KYB is not a single document upload; it is the processor building enough of a picture to satisfy its own compliance program. The specifics vary by jurisdiction and by the processor's policies, but the shape of what it is trying to establish is consistent. The table below describes the categories at a conceptual level — the actual fields and evidence you are asked for appear in the onboarding flow, and you should follow that flow rather than this page for the exact list.
Notice that none of this is about the blockchain. KYB is ordinary business verification — the same kind a bank or any regulated payment partner would run — and it is largely orthogonal to which chains or assets you intend to accept. The crypto part of your integration starts after the entity behind it is known.
| What KYB establishes | Why the processor needs it |
|---|---|
| Legal entity | Confirms the business is real and registered — a named, incorporated counterparty, not an anonymous account. |
| People behind it | Identifies the individuals who own or control the company, so payments trace back to accountable parties. |
| Nature of the business | Establishes what the business does and how it expects to use payments, so activity later can be read against a baseline. |
| Contactable representative | Gives the processor a verified point of contact for the account and for anything that needs follow-up. |
How verification fits the onboarding sequence
KYB is the first gate, not a step you reach after building your integration. The practical sequence is: contact the team to start onboarding, complete the business-verification flow, get verified, then go live. You can usually explore the dashboard and read the docs before verification clears, but the ability to take real payments and move real funds sits on the far side of the gate.
A common and avoidable mistake is to build the entire integration against a live account that has not been verified, then discover at launch that the account cannot yet transact. Sequence it the other way: start verification early, and use the sandbox to build and test in parallel while the review is in flight. The sandbox lets you create invoices, simulate payments, and exercise your webhook handler without needing a verified live account, so your engineering work and the compliance review run side by side instead of one blocking the other.
When verification completes, your account is activated for live operation. From that point the same primitives you exercised in the sandbox — invoices, the hosted checkout, payouts, webhooks — operate against real value. KYB is what separates those two worlds.
- Verification is a gate before live transacting, not a formality after integration.
- Build and test in the sandbox while your KYB review is in flight — the two run in parallel.
- Going live is the activation that follows a clear verification, not a separate manual switch you flip yourself.
- A material change to your business may prompt the processor to revisit information you provided.
Prepare so the review clears in one pass
Most onboarding delays are self-inflicted: information that does not match across documents, a representative who cannot be reached, or a vague description of the business that invites follow-up questions. Each round of clarification adds days. The way to a fast review is to make the picture coherent and complete the first time, so the reviewer has nothing to ask you for.
Get your own facts straight before you start the flow. Know your registered legal name and how it is spelled on official records, who the owners and controllers of the company are, and a plain, honest description of what the business does and how it intends to use crypto payments. Consistency is the thing that matters most — the same legal name, the same addresses, the same people, stated the same way everywhere. Mismatches are the single most common cause of a stalled review.
Describe your business plainly and accurately. A clear, specific account of what you sell and to whom does more to speed a review than a polished marketing pitch. If your model has a feature a reviewer would reasonably want to understand — you run a marketplace and pay out to third parties, say, or you operate in a higher-scrutiny vertical — state it up front rather than leaving it to be discovered. Surfacing it early reads as candor and shortens the conversation.
- Keep your legal name, addresses, and ownership details identical across everything you submit.
- Have a plain, honest description of what the business does and how it will use payments ready.
- Make sure your nominated representative is reachable while the review is open.
- Volunteer the parts of your model a reviewer would reasonably ask about, rather than waiting to be asked.
Where KYB sits in the wider compliance picture
KYB is the onboarding gate, but it is the first piece of a longer compliance posture, not the whole of it. Once you are verified and live, the relationship continues: a payment processor maintains an ongoing awareness of activity against the baseline that onboarding established, and certain events — a refund, a payout to a third party, a settlement above a threshold the processor sets — interact with anti-money-laundering and travel-rule processes that live downstream of verification.
None of that ongoing layer is something you certify or that makes your business itself "regulated" — KYB clears your account to operate, it does not confer a license or a status on you. The cleaner separation to hold in your head is this: KYB answers "who is this business?" once, at the start; the rest of compliance answers "is this specific activity consistent with what we know?" continuously, afterward. The dedicated compliance overview walks the full sequence; this guide is only the front door.
The most useful thing you can do with that framing is to keep your own side of the record clean from day one. Every invoice, payout, and refund you create should carry the references that tie it back to an order, a customer, or a payee in your own system. That attributability is what makes the ongoing layer cheap to satisfy — and it is exactly the discipline KYB sets the expectation for at onboarding.
A note on what KYB is not
Two misreadings are worth heading off. First, KYB does not make your business "compliant" in a blanket sense, and passing it is not a certification you can wave at your own regulator. It clears your account to operate with the processor; your own obligations — licensing, tax, reporting in your jurisdiction — remain yours, and this guide is not legal advice on any of them. If you need to know what applies to your business, that is a conversation for your own counsel.
Second, KYB is not a custody arrangement or a guarantee about your funds. Verifying who you are is separate from how value is held and moved, which is governed by signing, scoped permissions, and an audit trail rather than by the onboarding check. KYB establishes the identity of the account; the controls around the money are a different mechanism entirely. Keeping the two ideas distinct will save you from reading more into a completed verification than it actually means.