KYB Explained
ARTICLE KYB Explained: How Payment Providers Verify a Business Before Activation A company can be incorporated, appear in an official registry, possess a registration number, and still be nowhere near the end of payment-provider verification. That is not a contradiction. It refle
ARTICLE
KYB Explained: How Payment Providers Verify a Business Before Activation
A company can be incorporated, appear in an official registry, possess a registration number, and still be nowhere near the end of payment-provider verification.
That is not a contradiction.
It reflects the difference between proving that a legal entity exists and establishing enough about that entity to enter into a payment relationship with it.
A certificate of incorporation can help answer:
Does this company legally exist?
It usually cannot answer, by itself:
Is the entity currently active?
What does the business actually do?
Does its customer-facing activity match the application?
Who owns it?
Who ultimately controls it?
Who manages or directs it?
Is the person submitting the application authorized to act for it?
Which address belongs to which part of the business?
Does the proposed settlement account belong to the appropriate entity?
Does the provider, acquirer, bank, or other relevant party have enough information to proceed with the relationship?
That is the more useful way to understand Know Your Business, or KYB.
KYB is a business-relationship verification process, not simply a company-registry lookup.
For merchants, that distinction explains why an onboarding process can continue even after the company registration has been successfully verified.
What is KYB?
KYB—Know Your Business—is the process of establishing and verifying relevant facts about a legal entity and, where required, the people and relationships connected to it.
Depending on the jurisdiction, regulated context, provider, acquiring arrangement, business model, and risk profile, KYB may involve facts such as:
Legal name
Registration number
Jurisdiction of incorporation
Legal form
Registration or operating status
Registered address
Business activity
Ownership
Beneficial ownership
Control
Directors or managers
Authorized representatives
Banking or settlement relationship
Other information needed for risk or compliance review
The exact process is not universal.
But the conceptual sequence is consistent:
Business declares facts
→ evidence supports those facts
→ relevant information is checked
→ relationships are resolved
→ discrepancies are investigated
→ the provider or other relevant party determines whether verification is sufficient for the relationship to proceed.
That is a much broader process than asking for one incorporation document.
Why does KYB exist?
Financial institutions and payment participants cannot always enter business relationships solely on the basis of a self-declared company name.
International AML/CFT standards provide an important conceptual foundation. FATF's current recommendations call for customer due diligence measures that include identifying and verifying customers, identifying beneficial owners and taking reasonable measures to verify them, and understanding the purpose and intended nature of the business relationship. For legal persons, FATF also emphasizes obtaining information sufficient to understand ownership and control.
The exact legal obligations imposed on a PSP, acquirer, bank, or other institution depend on its jurisdiction and regulatory role.
Card-network rules can create additional merchant-acceptance responsibilities. Visa's April 2026 public rules contain explicit acquirer responsibilities related to merchants and merchant agreements, while Mastercard's June 2026 rules include anti-money-laundering requirements and broader standards governing customer participation and merchant relationships.
For a merchant, the practical interpretation is:
The provider may need to understand both the entity and the network of people, ownership, authority, activities, and financial relationships that make that entity an operating merchant.
KYB is not simply “KYC for companies”
This shorthand is tempting because both processes involve verification.
It is also incomplete.
KYC asks primarily:
Who is this natural person?
Depending on the context, that can involve establishing:
Name
Date of birth
Identity
Address
Nationality
Relationship to the merchant
KYB asks primarily:
What is this business, and who owns, controls, manages, or represents it?
A single merchant onboarding can therefore require both.
For example:
Merchant company
→ KYB
Relevant beneficial owner
→ KYC where required
Director
→ identity verification where required
Authorized representative
→ identity and authority verification where required
This is why successfully verifying the company does not necessarily eliminate person-level checks.
The dedicated KYC vs KYB article should own the full comparison. For this article, the important point is that KYB is about the business relationship, while KYC generally centers on relevant natural persons.
The KYB Verification Stack
The easiest way to understand KYB is to build upward from the simplest business fact.
Layer 1 — Entity existence
The first question is:
Does the claimed legal entity exist?
Potential information may include:
Legal name
Registration number
Incorporation date
Jurisdiction
Legal form
Potential evidence can include:
Official company registry data
Certificate of incorporation
Formation documents
Other official corporate records
Where reliable registry data is available, some facts may be checked independently rather than established solely from documents supplied by the merchant.
But proving existence is only the first layer.
Layer 2 — Legal status
A company may have been validly incorporated at some point without necessarily being in the same status today.
Depending on jurisdiction and available records, verification may consider whether the entity is:
Active
Dissolved
In liquidation
Struck off
Suspended
Otherwise subject to a legally meaningful status
Exact status terminology varies across registries and countries.
This answers a subtly different question from existence:
Existence asks whether the company was created.
Status asks what its legal position is now.
That distinction matters when an incorporation certificate is old but the merchant is applying for a current payment relationship.
Layer 3 — Business activity
A provider may also need to establish:
What does this company actually do?
A company registry may provide an industry classification or declared corporate purpose.
That does not always fully describe the current commercial business.
Useful sources can include:
Merchant application
Website
Product catalog
Customer terms
Commercial contracts
Invoices
Licenses where relevant
Other supporting business evidence
The objective is not merely to find an industry label.
It is to determine whether the business represented to the provider corresponds to the business actually being operated.
For an online merchant, that can mean understanding:
Products or services
Customer type
Transaction model
Subscription structure
Marketplace involvement
Countries served
Delivery or fulfilment model
That deeper underwriting analysis belongs in Underwriting for Online Merchants.
Within KYB, the business-activity layer establishes what business is being verified.
Legal existence is not the same as business legitimacy or provider fit
These concepts should remain separate.
Legal existence
The company exists under the applicable corporate framework.
Business legitimacy
Available information is consistent with an operating business that is what it claims to be.
Provider fit
The provider or acquiring arrangement is prepared to support that:
Business model
Geography
Merchant category
Payment flow
Risk profile
A merchant can be legally incorporated and legitimate while still falling outside a particular PSP's supported model.
A provider decline therefore does not necessarily imply the company itself is illegitimate.
Layer 4 — Ownership
Once the entity has been identified, KYB can move into the relationships behind it.
The next question is:
Who owns this business?
This can begin with registered or declared shareholders.
But ownership can become more complicated when the immediate shareholder is itself another company.
For example:
Merchant Ltd
|
| 100%
v
Holding Co
|
| ownership
v
Natural persons / further entities
Stopping at Holding Co may not resolve the underlying ownership question.
The verification process may need to continue through intermediate entities until the relevant natural-person ownership or control analysis can be completed under the applicable framework.
This is where KYB begins to interact with beneficial ownership verification.
Shareholder does not automatically mean UBO
A shareholder is an owner of shares or another equity interest.
A beneficial owner or ultimate beneficial owner is determined under the applicable ownership and/or control test.
Those concepts can overlap.
They are not automatically identical.
For example:
A company can be the direct shareholder.
A natural person can indirectly own part of the merchant through that company.
Another person can exercise significant control without holding the largest direct shareholding.
The rules defining beneficial ownership vary by jurisdiction and regulated context.
Do not apply a universal rule such as:
Anyone with 25% is always a UBO.
In the United States, for example, FinCEN's current CDD framework for covered financial institutions contains a specific ownership and control formulation, including a 25% ownership prong and a control prong. That is a particular U.S. regulatory framework, not a global KYB definition.
The dedicated Ultimate Beneficial Owner Requirements article should own thresholds and jurisdictional variation.
Layer 5 — Control and directors
Ownership does not always tell you who manages the company.
That introduces another question:
Who legally manages, directs, or otherwise exercises relevant control over the entity?
Potential subjects can include:
Directors
Managers
General partners
Officers
Other controllers recognized under the applicable structure
A director is not automatically an owner.
An owner is not automatically a director.
A UBO is not automatically either.
One person may occupy multiple roles, but KYB should preserve the roles rather than collapsing them.
Conceptually:
Person
Shareholder?
UBO?
Director?
Authorized applicant?
Person A
Yes
Possibly
No
No
Person B
No
Possibly through control
Yes
No
Person C
No
No
No
Yes
The exact verification required for each role depends on context.
The dedicated Director Verification article should own person-level director requirements.
Ownership versus control
This is one of the most important KYB distinctions.
Ownership can be expressed through:
Shares
Equity
Economic interest
Control can sometimes arise through:
Voting rights
Appointment rights
Management authority
Contractual arrangements
Other recognized mechanisms
FATF's framework explicitly addresses both ownership and control when discussing beneficial ownership of legal persons.
That is why a provider mapping a business cannot always stop at a simple shareholder percentage table.
The question is not merely:
Who owns shares?
It can also be:
Who ultimately controls this entity under the applicable rules?
Layer 6 — Authorized representative
The person completing a PSP application may be:
Employee
Finance manager
Payments lead
External consultant
Officer
Director
That person may not be an owner or director.
The provider may therefore need to establish two separate facts:
Who is this individual?
Are they authorized to act for this business?
Those are not the same question.
A corporate email address may support context.
It does not necessarily establish legal authority.
Depending on the relationship, authority might be supported through:
Corporate records
Board or management authorization
Power of attorney
Role evidence
Other accepted documentation
Exact requirements vary.
The useful merchant preparation principle is:
Know which person is submitting the application and be able to explain why that person is authorized to represent the applying entity.
Layer 7 — Address and banking
KYB can also involve business information that connects the legal entity to operational and financial infrastructure.
Two frequent examples are:
Address
Bank account
These should each be understood as verification problems rather than formatting exercises.
Address verification asks: which address?
A merchant may have:
Registered office
Operating address
Correspondence address
Warehouse
Headquarters
Directors' residential addresses
These can legitimately differ.
So the relevant question is not:
Does every document show the same address?
It is:
Which address are we trying to establish, and does the evidence support that specific address relationship?
An unexplained mismatch may require clarification.
It should not automatically be treated as fraud.
The dedicated Address Verification article should own acceptable evidence, mismatches, and country variation.
Bank-account verification asks more than whether the account number is valid
For settlement or payout, a provider may need to establish questions such as:
Does the account exist?
Who owns it?
Is the account holder the merchant legal entity?
If not, why is another entity involved?
Is the account eligible for the intended settlement model?
Does geography create another requirement?
A syntactically valid IBAN or account number does not prove who owns the account.
Likewise, a minor name variation does not automatically prove that the account belongs to someone else.
Legal names can be shortened.
Banks can truncate fields.
Transliteration can differ.
Group treasury structures can be complex.
The correct response to a mismatch is:
resolve the relationship.
Not:
assume fraud.
The dedicated Bank Account Verification article should own those mechanics.
Layer 8 — Risk and compliance review
The final KYB layer is not simply another document.
It is the evaluation of the verified facts in the context of the proposed business relationship.
That can include questions such as:
Is the activity supported?
Is the structure understood?
Have relevant owners/controllers been identified?
Is the applicant authorized?
Are required geographic relationships clear?
Are discrepancies resolved?
Does the business require additional due diligence?
Are there other legal, regulatory, acquiring, banking, or provider-policy conditions?
This is where the distinction between verification and approval becomes important.
A fact can be successfully verified while the broader merchant relationship still remains under:
Underwriting
Risk review
Additional due diligence
Acquirer review
Commercial review
KYB completion does not necessarily equal production activation.
Registry verification is not complete KYB
The strongest misconception to remove is:
“The company exists in the registry, so why isn't KYB done?”
Because the registry may only establish some of the required facts.
A simplified comparison:
Fact
Company registry may help establish
Additional work may still be required
Legal existence
Often
—
Registration number
Often
—
Legal status
Often, depending on registry
Current interpretation
Registered address
Often
Operating address may differ
Business activity
Sometimes
Actual activity may require clarification
Shareholders
Depends on jurisdiction
Indirect ownership may remain
UBOs
Depends on registry/framework
Ownership/control analysis
Directors
Often in some registries
Identity or current authority
Applicant authority
Rarely complete
Separate authority evidence
Bank-account owner
Usually no
Bank verification/evidence
Provider eligibility
No
Risk/commercial/acquiring decision
This is why a fast registry lookup can coexist with a much longer KYB process.
The unresolved work exists between the company record and the complete business relationship.
Document collection is not verification
Another common source of confusion:
“We already sent that document.”
Sending evidence does not automatically mean the underlying fact has been verified.
Consider the sequence:
Merchant declares shareholder A owns 70%
→ submits shareholder register
→ register shows Holding Company B
→ provider checks Holding Company B
→ another owner is identified
→ ownership chain expands
The original document was not necessarily wrong.
It simply revealed that the ownership question continued.
This distinction matters operationally:
Document submitted
Merchant supplied a file or data.
Document reviewed
Someone examined it.
Fact verified
The relevant fact has been sufficiently established under the applicable process.
Relationship approved
Broader compliance/risk requirements have been satisfied to the relevant decision point.
Those milestones should not be treated as interchangeable.
Self-declared information, documentary evidence and independent verification
A robust KYB process can use several evidence levels.
Self-declared information
What the merchant tells the provider.
Examples:
Legal name
ownership
business activity
directors
Documentary evidence
Documents that support those statements.
Examples:
Incorporation certificate
shareholder register
corporate filing
bank evidence
Independent evidence
Information checked against a source not controlled solely by the applicant.
Examples may include:
Official registry
Government database
Banking-verification service
Other reliable electronic source where permitted
No single layer is universally sufficient.
The verification objective determines what evidence is appropriate.
Why KYB becomes slower with complex corporate structures
Consider two merchants.
Merchant A
One operating company.
One natural-person owner.
One director.
One country.
The relationship graph is short.
Merchant B
Operating company
→ regional holding company
→ international parent
→ investment company
→ multiple natural persons.
Nothing about Merchant B's complexity automatically implies wrongdoing.
But each layer creates another relationship that may need to be understood.
For each entity the process may need information such as:
Legal identity
Jurisdiction
Ownership percentage
Parent relationship
Control
Evidence source
Then relevant natural persons must be identified.
This is why KYB should be thought of partly as a relationship-mapping problem.
The dedicated Corporate Structure Verification article should own this in depth.
How ownership arithmetic can help—and where it stops
Suppose, hypothetically:
Person A owns 60% of Holding Co.
Holding Co owns:
50% of Merchant Ltd.
Person A's indirect economic ownership would be:
60% × 50% = 30%.
That calculation can help map economic ownership.
It does not automatically determine legal UBO status.
The applicable framework may also consider:
Control
Voting rights
Entity type
Ownership threshold
Exceptions
Other circumstances
Arithmetic is an input to the analysis.
It is not the law.
Common KYB delays
KYB delays frequently arise because one or more business relationships remain unresolved.
Legal-name mismatch
Application uses:
Example Commerce
Registry says:
Example Commerce Holdings Limited
The trading/legal relationship may simply need clarification.
Wrong registration information
A typo or number belonging to another group entity can prevent an independent match.
Outdated company information
Merchant documents show an old:
Director
address
shareholder
company name
while the registry or current business reflects something else.
Missing ownership layer
Merchant reports:
Holding Co owns 100%.
But does not show who owns Holding Co.
The chain stops too early.
Director versus owner confusion
Merchant provides owner information when the request concerns directors, or vice versa.
The evidence does not answer the intended question.
Applicant authority is unclear
The person completing onboarding is verified personally, but their authority to represent the merchant remains unresolved.
Bank-account mismatch
The proposed settlement account belongs to:
Parent
subsidiary
treasury company
differently named legal entity
That may be legitimate, but the relationship must be explained and accepted.
Business activity is too vague
Descriptions such as:
Ecommerce
Technology
Consulting
Marketplace
may be insufficient to establish the actual payment activity.
Specificity reduces interpretation.
The most useful merchant question during KYB
When onboarding stalls, avoid asking only:
Which document do you need?
Ask:
Which fact or relationship remains unverified?
That question turns a document chase into a verification problem.
For example:
Request: Provide additional ownership information.
Less useful reaction:
What document do you want?
More useful reaction:
Are you trying to establish the shareholder of Holding Co, the ultimate natural-person owner, or control of Merchant Ltd?
Once the verification objective is known, the correct evidence is easier to identify.
What merchants can prepare before KYB starts
A useful merchant readiness package begins with facts, then identifies supporting evidence.
Entity
Know:
Exact legal name
Registration number
Jurisdiction
Legal form
Current status where available
Registered address
Business
Be able to state clearly:
What the company sells
Customer type
How it earns revenue
Countries involved
Payment model
Ownership
Prepare:
Direct shareholders
Intermediate entities
Ownership percentages
Ultimate natural-person ownership/control information where required
Governance
Know:
Current directors
Managers/controllers where relevant
Which individual is authorized to act for the company
Address
Distinguish:
Registered
Operating
Correspondence
Banking
Know:
Account holder
Bank
Account relationship
Any group-company involvement
Cross-border structure
If the merchant belongs to a group, clearly identify:
Applying entity
Parent
Subsidiaries
Holding companies
Jurisdictions
Do not assume the provider can reconstruct this from individual documents.
Create an ownership chart before someone asks for one
For any merchant with more than one ownership layer, an ownership chart can make the relationship materially easier to understand.
Conceptually:
Person A -------- 60% ----+
|
v
Holding Co A
|
70%
|
v
Merchant Ltd
^
|
30%
|
Person B
Include, where relevant:
Entity names
Jurisdictions
Ownership percentages
Natural persons
Control relationships requiring explanation
The chart is an explanatory tool.
It may not replace official evidence.
Keep role labels precise
A KYB package becomes confusing quickly when everyone is simply called:
owner
or:
company representative.
Use actual roles:
Shareholder
Beneficial owner
UBO
Director
Controller
Authorized representative
Parent company
Subsidiary
That makes it easier for both merchant and provider to determine which facts have and have not been established.
KYB Verification Stack
The complete framework can be summarized like this:
RISK / COMPLIANCE REVIEW
Is the complete relationship understood and acceptable?
▲
ADDRESS / BANKING
Where does the entity operate and receive settlement?
▲
AUTHORIZED REPRESENTATIVE
Who can act for the entity?
▲
CONTROL / DIRECTORS
Who manages or controls it?
▲
OWNERSHIP
Who owns it, directly and indirectly?
▲
BUSINESS ACTIVITY
What does the company actually do?
▲
LEGAL STATUS
What is its current legal status?
▲
ENTITY EXISTENCE
Does this legal entity exist?
The essential point is the direction of travel.
KYB starts with the company.
It then moves outward into the relationships required to understand the company as a business customer.
KYB verification status should be tracked by unresolved fact
Merchants managing onboarding operationally can improve visibility by tracking the verification stack.
Verification layer
Merchant status
Entity existence
Confirmed / unresolved
Legal status
Confirmed / unresolved
Business activity
Confirmed / clarification needed
Ownership
Complete / missing layer
UBO/control
Identified / verification pending
Directors
Confirmed / mismatch
Representative
Authorized / evidence pending
Address
Confirmed / mismatch
Bank account
Confirmed / relationship unresolved
Additional risk review
Complete / pending
This is not a regulatory scorecard.
It is an operational tool for finding the dependency blocking activation.
KYB does not necessarily stop after onboarding
Some business facts change.
A merchant may:
Add a shareholder
Change UBO
Change director
Move registered address
Change settlement account
Restructure its corporate group
Enter new business activities
Relevant providers or institutions may require updated information or re-verification in response to such changes.
FATF's framework includes ongoing due diligence and keeping relevant customer information up to date on a risk-sensitive basis. FinCEN's current U.S. CDD FAQs likewise illustrate event-driven updating in a specific U.S. context when relevant legal-entity customer information changes.
Exact monitoring obligations and triggers vary.
The dedicated Ongoing Merchant Monitoring article should own this lifecycle.
Why KYB can slow payment activation
KYB slows a launch when an unresolved fact sits on the critical path.
Conceptually:
Entity confirmed
→ ownership unresolved
→ UBO cannot yet be determined
→ required natural-person verification cannot begin or complete
→ risk review remains open
→ activation waits.
Or:
Entity confirmed
→ bank account belongs to another group company
→ relationship unclear
→ settlement setup remains pending
→ production waits.
This is why simply collecting more documents is not the ideal optimization.
The objective is:
Resolve the specific dependency preventing the next decision.
Necessary verification should not be weakened for speed.
Avoidable delay comes from:
Incomplete relationship mapping
Inconsistent information
Wrong entity
Outdated evidence
Slow merchant response
Vague provider requests
Repeated reviews that do not identify the unresolved fact
The best KYB process makes the dependency visible.
Without that verification, the safest positioning is broader:
An international payments provider can help merchants coordinate the information required to establish business identity and related merchant relationships across payment onboarding, but the exact KYB requirements still depend on the entity, jurisdiction, provider, acquiring arrangement, business model, and applicable risk or compliance framework.
That keeps the focus on the merchant's real problem:
understanding what remains unverified.
Final merchant recommendation
Do not approach KYB by asking:
Which documents should we upload?
Start one level earlier:
Which business facts must be established?
Then map the evidence to each fact.
A useful sequence is:
Does the entity exist?
What is its current status?
What does it actually do?
Who owns it?
Who ultimately owns or controls it where relevant?
Who manages it?
Who is authorized to represent it?
Which address and bank relationships belong to it?
What additional risk or compliance questions remain?
That is why a certificate of incorporation can be perfectly valid and still leave KYB incomplete.
It proves an important fact.
It does not prove the entire business relationship.
And that is the most useful definition of KYB for a merchant trying to launch payments:
KYB is the process of moving from “this company exists” to “we understand which business this is, what it does, who stands behind it, who can act for it, and whether the relevant facts required for this payment relationship have been established.”
This article provides general information and does not constitute legal, regulatory, compliance, tax, accounting, or financial advice. KYC and KYB requirements vary by jurisdiction, regulated activity, provider, financial institution, merchant structure, and risk profile. Merchants should verify current requirements with qualified advisers, relevant authorities, and their payment providers or acquirers.
🙂 🙂 🙂 🙂 🙂 🙂 🙂
The brief makes this the cluster’s foundational business-verification article. Its job is not to turn KYB into a longer corporate-document checklist; it should explain the verification logic that begins with a legal entity and then expands outward to activity, ownership, control, representation, address, banking, and risk.
Brief interpretation
Article-owned question: What does a payment provider still need to establish after confirming that a company legally exists?
Verification subject: The merchant legal entity and the relationships around it.
Verification objective: Establish that the applicant corresponds to a real business, understand what the entity does, identify relevant owners/controllers/directors, establish who is authorized to act for it, and resolve other business facts required for the applicable onboarding relationship.
Key distinction: Registry verification is one layer of KYB, not complete KYB.
Editorial position: Merchants should prepare KYB by mapping the business relationship, not by accumulating documents without understanding what each one proves.
Unique evidence anchor: A certificate of incorporation can establish legal existence, but it does not by itself establish current status, ownership, control, business activity, representation authority, settlement-account ownership, or the overall suitability of the merchant relationship.
Final merchant decision: Which business facts remain unresolved after legal-entity registration has been confirmed?
SEO & EDITORIAL RECOMMENDATIONS
KYB Explained: How Business Verification Works for Merchants
This captures both the brief's primary term and the stronger explanatory query around business verification.
H1
KYB Explained: How Payment Providers Verify a Business Before Activation
Meta title
KYB Explained: Business Verification for Payment Onboarding
Meta description
Learn what KYB means, how payment providers verify legal entities, business activity, ownership, directors and authorized representatives, and why registry verification alone may not complete merchant onboarding.
URL slug
/kyb-explained/
KYB explained
Secondary keywords
Prioritize:
what is KYB
know your business
KYB verification
merchant KYB
business verification
payment provider KYB
business onboarding verification
company verification
Useful semantic terms:
legal entity verification
business identity verification
corporate verification
merchant verification
beneficial ownership
company registration verification
authorized representative
business onboarding
Excerpt
KYB goes beyond confirming that a company exists. Payment providers may need to establish the legal entity, current status, business activity, ownership, control, directors, authorized representatives, addresses and banking relationships before a merchant can be activated.
Featured-snippet opportunity
Use this near the top:
KYB, or Know Your Business, is the process of establishing and verifying relevant facts about a legal entity and the ownership, control, representation and other relationships needed to understand that business customer. A company-registry match may establish legal existence, but it does not necessarily complete KYB.
Search-intent questions worth naturally capturing
What is KYB?
What does KYB stand for?
How does KYB verification work?
What is checked during KYB?
Is KYB the same as KYC?
Why is KYB required after company registration is verified?
Does KYB verify directors?
Does KYB include beneficial owners?
What causes KYB delays?
What information do payment providers verify about businesses?
Do not turn them all into an FAQ.
Internal-link recommendations
KYC Explained
Link from the first KYC/KYB distinction.
Suggested anchor:
how KYC verifies natural persons
KYC vs KYB
Link after explaining that merchant onboarding can require both.
Suggested anchor:
the difference between KYC and KYB
Beneficial Ownership Verification
Link from ownership-chain discussion.
Suggested anchor:
how beneficial ownership is verified
Corporate Structure Verification
Link from multi-layer ownership.
Suggested anchor:
verifying complex corporate structures
Additional contextual links can later point to:
Ultimate Beneficial Owner Requirements
Director Verification
Address Verification
Bank Account Verification
Ongoing Merchant Monitoring
Do not explain those adjacent topics fully in this piece.
Supporting visual
KYB Verification Stack
The visual should be a vertical stack rather than another process timeline.
┌──────────────────────────────────────┐
│ 8. RISK / COMPLIANCE REVIEW │
│ Is the relationship sufficiently │
│ understood for the relevant review? │
├──────────────────────────────────────┤
│ 7. ADDRESS / BANKING │
│ Where is it based and where does │
│ settlement go? │
├──────────────────────────────────────┤
│ 6. AUTHORIZED REPRESENTATIVE │
│ Who can act for the company? │
├──────────────────────────────────────┤
│ 5. CONTROL / DIRECTORS │
│ Who manages or controls it? │
├──────────────────────────────────────┤
│ 4. OWNERSHIP │
│ Who owns it directly/indirectly? │
├──────────────────────────────────────┤
│ 3. BUSINESS ACTIVITY │
│ What does it actually do? │
├──────────────────────────────────────┤
│ 2. LEGAL STATUS │
│ What is its current status? │
├──────────────────────────────────────┤
│ 1. ENTITY EXISTENCE │
│ Does the company legally exist? │
└──────────────────────────────────────┘
REGISTRY CONFIRMATION STARTS THE STACK.
IT DOES NOT NECESSARILY FINISH IT.
Alt text
KYB Verification Stack showing eight layers of business verification: legal entity existence, legal status, business activity, ownership, control and directors, authorized representative, address and banking, and risk or compliance review.
Structured-data recommendation
Use:
Article
BreadcrumbList
Do not add FAQPage solely for SEO.
Source and verification plan
Recommended authoritative sources
FATF
Use current FATF Recommendations for the high-level concepts of:
Customer due diligence
Beneficial ownership
Ownership and control
Ongoing due diligence
FATF is a standards-setting body; its recommendations should not be presented as if they were themselves identical domestic law in every jurisdiction.
FinCEN
Use current FinCEN material only for specifically labeled U.S. examples. Its 2026 consolidated CDD FAQs describe a particular beneficial-ownership framework for covered U.S. financial institutions and illustrate both ownership and control concepts.
Do not convert the U.S. 25% ownership prong into a universal UBO rule.
Visa
Use the current April 18, 2026 Visa rules where payment-network merchant acceptance/acquirer responsibility is materially discussed.
Mastercard
Use the current June 2, 2026 Mastercard rules for network-level merchant/acquiring and AML-related context where relevant.
For country-specific KYB claims, add the applicable:
Legislation
Financial regulator
Financial intelligence unit
Official company registry
immediately before publication.
Claims requiring jurisdiction-specific verification
Any publication that adds specific assertions about these should verify the precise jurisdiction:
Who must undergo KYB
Which entity details are legally required
Beneficial-owner definition
UBO percentage threshold
Control test
Director verification
Authorized-representative evidence
Accepted corporate documents
Document certification
Document age
Registry sufficiency
Address evidence
Bank-account ownership requirements
Ongoing review
Record retention
Do not publish universal rules for these.
KYB scope
Which business details are collected
Business-activity verification
Ownership requirements
UBO requirements
Director requirements
Authorized-representative requirements
Evidence
Registry usage
Accepted corporate documents
Ownership documents
Address documents
Banking documents
Electronic verification
Geography
Country-specific requirements
Registry coverage
Translation/certification requirements
Operations
Automated versus manual verification
KYB workflow
Merchant-facing status
Additional-information workflow
Ongoing merchant re-verification
Timing
Do not publish:
Internal thresholds
Risk models
Exact approval logic
Unverified country coverage
Guaranteed verification speed
Amber-flag claims
Require direct current evidence before saying that:
Every PSP performs KYB in the same way.
Every company requires UBO verification under the same threshold.
25% is the universal UBO threshold.
Every director must complete KYC.
Every authorized representative needs the same documents.
A registry lookup completes entity verification.
A certificate of incorporation is sufficient for KYB.
A bank account must always be in the incorporation country.
A provider must accept a parent-company bank account.
Exact name mismatch means fraud.
Complex ownership means higher risk.
KYB always takes a specified number of days.
Human review recommendation
Proposed author
Merchant KYB/onboarding specialist or payments compliance strategist
The author should be comfortable explaining:
Legal entities
Corporate registries
Ownership structures
Payment-provider onboarding
Merchant verification
Do not invent a named author.
Primary reviewer
KYC/KYB or AML compliance specialist
Review:
Definition of KYB
FATF framing
Beneficial ownership/control language
Relationship to KYC
Regulatory scope
Secondary reviewer
Merchant onboarding operations lead
Review:
Real-world delay mechanisms
Request quality
Relationship mapping
Merchant preparation advice
Regional reviewer
Required before adding substantial country-specific examples.
Cluster sameness audit
Article: KYB Explained
Verification subject: Legal entity and surrounding business relationships
Opening: A company can exist in a registry and still have incomplete verification
Primary intellectual center: Entity existence is the bottom layer, not the completion point
Framework: KYB Verification Stack
Primary distinction: Registry verification vs complete KYB
Secondary distinction: KYB vs KYC
Other distinctions: shareholder vs UBO; director vs owner; ownership vs control; identity vs representation authority
Primary merchant question: Which facts remain unresolved after entity existence is confirmed?
Primary merchant action: Map business facts and relationships before mapping documents to them
Conclusion: Move from “company exists” to “business relationship understood”
Boundary: Does not own deep UBO thresholds, director procedures, ownership-chain mechanics, address verification, bank verification, or country-specific KYB rules
That makes this article meaningfully different from KYC Explained and KYC vs KYB: KYC Explained starts with the person, KYC vs KYB explains how the two processes interact, and KYB Explained starts with the legal entity and builds outward until the provider understands the business relationship around it.
Need help narrowing down payment options?
Answer a few questions about your business and compare the capabilities that matter to you.
Explore matching options ↗