KYC vs KYB

KYC vs KYB: What's the Difference in Merchant Onboarding? A payment provider asks a merchant for three things: Company registration. Ownership chart. Director's passport. Which requests are KYC? Which are KYB? The company-registration evidence is principally about the business. The ownership chart helps establish the company's ownership and control structure. The passport is about the identity of a natural person. But the useful distinction is not really between three documents. It is between three facts the provider is trying to establish. That leads to the simplest way to understand KYC vs KYB in merchant onboarding: KYC asks who a person is. KYB asks what a business is and how the relevant people relate to it. The two processes are therefore not competitors and one does not automatically replace the other. A merchant company may undergo KYB, while beneficial owners, directors, controllers, or authorized representatives associated with it may simultaneously or subsequently undergo KYC or another relevant personal verification process, depending on the applicable legal, regulatory, provider, acquiring, and risk requirements. That relationship is the important part. KYC and KYB are operational labels inside a broader due-diligence framework There is a terminology complication worth resolving early.

In payment and compliance operations, KYC and KYB are convenient ways to distinguish individual verification from business verification. Primary legal and regulatory frameworks do not necessarily organize their rules under those exact two labels. FATF, for example, frames the broader obligation in terms of customer due diligence and beneficial ownership. Its current glossary defines the beneficial owner of a legal person as the natural person or persons who ultimately own or control the customer, including through ultimate effective control. Current UK supervisory guidance provides a jurisdiction-specific illustration of the same architecture: a customer may be an individual or an entity, and due-diligence measures can include verifying the customer, beneficial owners, and—where relevant—people acting for that customer. So this article uses KYC and KYB as practical merchant-onboarding categories. They should not be read as a claim that every jurisdiction's law uses those terms identically. The difference starts with the verification subject Before asking which document is required, ask: Who or what is being verified? If the subject is a natural person, you are generally in KYC territory. If the subject is the merchant legal entity, you are generally in KYB territory. That sounds simple, but it resolves much of the confusion merchants encounter. KYC: the subject is a person Conceptually, KYC can seek to establish information such as: * the person's identity;

* relevant identifying information; * the person's relationship with the merchant; * and, where applicable, authority or control. Potential subjects can include an individual merchant, beneficial owner, director, controller, or authorized representative, depending on the relevant onboarding requirements. KYC is therefore broader than: “Upload a passport.” The document is evidence. The objective is establishing the underlying fact about the person. KYB: the subject is a business KYB generally concerns the legal entity or business relationship. Relevant questions can include: * What is the legal name? * Does the entity exist? * Where is it incorporated? * What legal form does it have? * What business does it conduct? * Who owns or controls it? * Who directs or represents it? The brief correctly warns against reducing this to “KYC for companies.” KYB needs to establish the business itself while also mapping the relationships that can lead back to relevant natural persons. KYC vs KYB Decision Matrix Question KYC KYB Primary subject Natural person Legal entity/business Core question Who is this person? What is this business? Typical information Personal identity information and relationship to merchant Legal name, registration, legal form, activity, ownership/control structure Typical evidence Appropriate personal identity or other personal evidence Corporate, registry, business, ownership, or organizational evidence Common subjects Beneficial owner, director, controller, representative where applicable

Merchant entity Main relationship question Is this the person they claim to be, and what is their relevant role? Does this entity exist, operate as described, and how is it owned, controlled, and represented? Dependency May begin after KYB identifies the relevant person Can identify people who then require KYC Does it replace the other? No No The matrix is conceptual. Exact verification requirements depend on jurisdiction, regulated context, provider, acquirer or bank relationships, merchant structure, and risk. Why a company can need KYB and its owners can need KYC This is the central misconception. A merchant might reasonably think: “You already verified our company. Why do you need information about the owners?” Because those checks answer different questions. Suppose the merchant is: Example Commerce Ltd. KYB may help establish: Does Example Commerce Ltd legally exist? Where is it registered? What business does it conduct? What is its ownership and control structure? During that work, the provider establishes that a natural person ultimately owns or controls the company under the applicable framework. Now there is another subject: the natural person. That person's identity may then require verification. FATF's beneficial-ownership standards make the conceptual relationship explicit: the ultimate beneficial owner of a legal person is always one or more natural persons, and ownership or control can be exercised through chains rather than only through direct shareholding. So: Merchant company

→ business/entity verification Ownership structure → identifies relevant natural person Relevant natural person → personal identity verification where required This is KYC inside a wider KYB/onboarding relationship, not necessarily duplicate compliance work. One company registration document does not verify the people behind the company Company-registration evidence can help answer a business-level question. Depending on the evidence and jurisdiction, it may support facts such as: * company name; * registration; * legal existence; * registered office; * directors or other recorded company information. But even if a corporate record names a person, that does not mean the person's identity has been independently verified. A registry could tell the provider: “Person A is recorded as director.” A personal identity check asks: “Is the individual presenting as Person A actually Person A?” Those are related facts. They are not the same fact. This is why document collection is not verification. The operating chain is better understood as: information declared → evidence supplied → evidence checked → information compared → independent source checked where appropriate → discrepancies resolved → verification outcome. An ownership chart belongs primarily to the business-verification problem Now consider the second requested item: ownership chart. That is principally evidence about the business relationship and corporate structure. It can help answer: Who owns or controls the merchant, through which entities?

A simple structure might be: Merchant Ltd ↓ Holding Co ↓ Person A A more complicated one could involve several intermediate companies across jurisdictions. Mapping those relationships belongs to the wider business/ownership verification problem. But the chart may ultimately identify Person A as someone whose natural-person identity needs separate verification. That creates the dependency: KYB ownership mapping → identification of relevant natural person → KYC where required The ownership chart itself should also not be treated automatically as conclusive proof merely because the merchant supplied it. Depending on the process, corporate or beneficial-ownership information may be compared with registries, corporate records, or other reliable sources. FATF's beneficial-ownership guidance emphasizes adequate, accurate, and up-to-date beneficial-ownership information and recognizes the importance of multiple information sources. The ownership question is not always solved by direct share percentage The comparison article should not become the full Beneficial Ownership Verification or UBO Requirements article, but one principle is necessary to understand the KYC/KYB boundary. Ownership and control can extend beyond the first shareholder listed against the merchant. FATF defines beneficial ownership in terms of the natural persons who ultimately own or control a legal-person customer and expressly recognizes ownership/control through chains or other forms of control.

That means KYB may have to travel through several legal entities before it identifies the natural-person subject of a KYC check. The full methodology belongs in Beneficial Ownership Verification and Ultimate Beneficial Owner Requirements. A director's passport verifies the person, not the company Now take the third item: director passport. If the provider is using it to establish the director's identity, the verification subject is a natural person. That places the identity check in KYC territory. But another distinction matters: Identity ≠ corporate role or authority. A passport can help establish that the person is who they claim to be. It does not by itself prove that the person: * is currently a director; * owns the company; * is a beneficial owner; * has authority to bind the merchant. Those facts may require corporate, registry, authorization, or other evidence. Current UK CDD guidance provides a useful jurisdiction-specific example: where someone acts for a legal-entity customer, the relevant process can need to establish both the individual's identity and that person's authority to act. This gives merchants a useful diagnostic: Passport requested does not automatically mean everything associated with the person has been verified. A single natural person can also occupy several roles. They might be: director + beneficial owner + authorized representative or only one of them. The article on Director Verification should own the deeper role distinction.

A director is not automatically a beneficial owner This mistake causes confusion because merchants often think the list of “people being checked” is one category. It is not. A director concerns the company's management or representation. A beneficial owner concerns ultimate ownership or control under the applicable framework. The same person can be both. But a person can also be: director only beneficial owner only both or: neither. The merchant should therefore ask: Why is this particular person in the verification flow? rather than: Why are you doing KYC again? The full legal tests and jurisdiction-specific thresholds belong in UBO Requirements, not this comparison article. The brief explicitly prohibits turning a particular ownership percentage into a universal UBO definition. KYC can depend on KYB before it can even start This is where the two processes become operationally interdependent. Consider a merchant with three corporate shareholders. Before the provider knows which natural persons are relevant, it may first need to understand the ownership chain. Conceptually: Verify merchant entity → map corporate ownership → identify natural persons at the end of the relevant ownership/control analysis → verify those people where required That means an incomplete KYB issue can prevent a KYC dependency from being defined. If the ownership chart stops at: Foreign Holding Co the provider may still not know whose natural-person information should be requested. So it cannot always solve the problem by saying:

“Just send us all the passports now.” The missing fact is not yet identity. It is who the relevant people actually are. This is why the cluster's conceptual verification model places legal-entity verification, business activity, and ownership/control mapping before identification of relevant natural persons, while recognizing that real providers may run some checks in parallel. But KYC and KYB do not always happen in a strict sequence Dependencies should not be confused with one universal workflow. If the relevant directors or owners are already known from the merchant's application, a provider may be able to begin some personal verification while corporate verification continues. Other cases cannot progress that way because KYB uncovers: * another parent company; * another ownership layer; * another controlling person; * an inconsistency requiring resolution. So the appropriate operating model is: Parallelize independent checks where the actual workflow permits it; preserve dependencies where one check determines the subject of another. The brief uses ownership mapping → UBO identification → UBO KYC as its clearest example of a true dependency. Why KYC and KYB can feel duplicative to merchants From the merchant's point of view, several requests may contain the same name. The application lists: Jane Smith — Director and shareholder The corporate register lists: Jane Smith — Director The ownership chart lists: Jane Smith — ultimate owner The provider then asks Jane for personal identity information.

The merchant sees Jane Smith four times and concludes: “You've already got this information.” But four appearances of the same name can answer four separate verification questions: Application: What is the merchant declaring? Corporate evidence: What does a business record say? Ownership analysis: What relationship does Jane have to the merchant? Personal verification: Is the individual being presented as Jane actually that person? The problem is not always duplicate data collection. It can be the distinction between claim, relationship, evidence, and verified identity. KYC vs KYB request classification A practical merchant can classify common onboarding requests like this: Request Primary verification subject KYC/KYB interpretation What it does not necessarily establish Company registration Legal entity KYB Identity of every person connected to company Registry extract Legal entity KYB Independent identity verification of named individuals Business description Legal entity/activity KYB Beneficial ownership Ownership chart Entity structure/ownership KYB Conclusive identity of the natural persons shown Beneficial owner's identity evidence Natural person KYC Entire ownership chain Director's identity evidence Natural person KYC where personal identity is being established That person is necessarily a beneficial owner Director/appointment record Company's relationship to person KYB / role verification Personal identity by itself Authorized representative's ID Natural person KYC where identity is required

Authority to bind the company Authority/mandate evidence Merchant-to-person relationship KYB/authority context Natural-person identity by itself This is an explanatory framework, not a universal provider document policy. Exact evidence and classifications vary. Not every onboarding check is neatly “KYC or KYB” Another reason not to overuse the labels is that merchant onboarding can contain additional verification questions. For example: Address verification may concern a person's residential address or a company's registered/operating address. Bank-account verification may concern the existence and ownership of a settlement account and its relationship to the merchant. Source-of-funds or source-of-wealth checks, where applicable, answer other financial-origin questions. The useful method remains: Identify the subject and objective before naming the process. Calling everything “KYC” makes the merchant's request list harder, not easier, to understand. The brief explicitly requires requests to specify who or what is being verified instead of relying on vague phrases such as “the KYC information.” Where KYC/KYB mismatches create avoidable delays Necessary verification can take time. But some verification delay is operationally preventable. The company name and personal role disagree The application says: Alex Morgan — Director but the current corporate source does not show Alex in that role. That does not automatically establish wrongdoing.

The company may recently have changed directors, an external record may still be updating, or the merchant may have submitted outdated information. But the relationship needs resolving before the provider can comfortably rely on it. The ownership chain stops at another company The merchant submits: Merchant → Holding Company but does not explain who ultimately owns or controls the holding company. The missing material is not necessarily another passport. The first problem is an incomplete KYB ownership map. Legal and trading names are confused The merchant uses a brand name in one place and the legal entity in another without explaining their relationship. Again, that is not automatically fraud. It is an unresolved entity relationship. Personal identity evidence is supplied for the wrong verification objective An identity document may establish identity. It does not necessarily establish: * ownership; * corporate role; * business address; * bank-account ownership; * source of funds. Sending additional copies of the same ID cannot solve a different evidentiary problem. The best clarification question is about the unresolved fact When a merchant receives another compliance request, an operationally useful question is: Which person or entity is being verified, and what fact is still unresolved? That question tends to produce more actionable information than: “Why do you need more KYC?” A high-quality request should, where possible, make clear: what is missing whose information is missing

what fact needs to be established what discrepancy requires resolution and: what happens next. That improves merchant response quality without weakening the underlying verification. A mismatch should trigger resolution, not an automatic fraud conclusion KYC and KYB information will not always match perfectly on the first comparison. Legitimate causes can include: * a recent corporate change; * pending registry updates; * trading names; * international transliteration; * bank abbreviations; * changes in directors or addresses. The correct operational response is to establish why the mismatch exists and whether reliable evidence resolves it. The brief explicitly makes this distinction: mismatch is an investigation prompt, not automatically evidence of fraud. Merchant preparation should follow the person/entity split Before onboarding, create two related evidence maps. Business side — KYB readiness Know: * exact legal entity; * registration information; * incorporation jurisdiction; * business activity; * ownership structure; * directors; * authorized representatives; * relevant business addresses. Person side — KYC readiness For each relevant natural person, know: * who they are; * what role connects them to the merchant; * whether they are an owner, director, controller, representative, or combination; * who internally can coordinate the appropriate requested information securely. Do not gather every imaginable sensitive personal document “just in case.”

Compliance quality is not proportional to the number of documents collected. Collecting unnecessary identity, residential, banking, or financial data can itself create privacy, security, operational, and merchant-friction costs. KYC and KYB ultimately describe one merchant relationship from two directions KYB without the relevant people can leave a company with no understandable human ownership, control, or representation. KYC without the company can verify a person's identity while leaving unanswered what that person has to do with the merchant. That is why the two processes coexist. The relationship can be summarized as: KYB establishes the business → KYB maps ownership, control, and representation → those relationships identify relevant natural persons → KYC establishes the identities of those persons where required → the combined evidence helps the relevant provider or financial institution understand the merchant relationship. A current U.S. example makes the connection especially explicit: FinCEN's CDD framework for covered financial institutions deals separately with legal-entity customers and identification and verification of their natural-person beneficial owners. FinCEN modified part of that process through exceptive relief in February 2026, which is also a useful reminder that exact requirements can change and must be checked in the relevant jurisdiction and regulated context. The merchant therefore does not need to ask whether KYC or KYB is more important.

It needs to ask what each request is trying to establish. For company registration, the subject is the business. For an ownership chart, the subject is the relationship between the business and its owners. For a director's identity document, the subject is the person. Once those subjects are separated, what initially looks like repeated compliance work becomes a set of distinct verification questions about the same merchant relationship. That is the practical difference between KYC and KYB: KYB tells the provider which business it is dealing with and how relevant people connect to it. KYC establishes who those people are where their identities need to be verified. One does not make the other redundant. They complete different parts of the same picture. 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. 🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂

END OF ARTICLE A. Brief interpretation Article-owned question: How should a merchant distinguish KYC from KYB when both appear inside the same onboarding flow? Verification subject: KYC centers on a natural person; KYB centers on the legal entity/business, while KYB work can identify owners, directors, controllers, or representatives whose identities may then require separate verification. Verification objective: Determine whether an information request is trying to establish who a person is or what a business is and how relevant people relate to it. Key distinction: Company verification does not automatically verify the people behind the company, and verifying a person's identity does not establish the existence, ownership, or activity of the company. Editorial position: Merchant onboarding becomes much easier to understand when every request is classified first by subject: person or business. Unique evidence anchor: One merchant application can involve KYB of the merchant company while multiple owners, directors, controllers, or representatives undergo KYC or related personal/authority checks. Current international AML/CFT standards likewise distinguish legal-person customers from the natural persons who ultimately own or control them. Final merchant decision: Is this request trying to verify the company or a person connected to it?

Everything below is SEO, editorial, sourcing, visual, verification, and production guidance and is not part of the publication article.

C. Original article asset — KYC vs KYB Decision Matrix The article's signature asset should remain the subject-first comparison, not a document checklist. Recommended production version Decision question KYC KYB What is being verified? Natural person Legal entity/business Core fact Person's identity Entity's existence, identity, activity, ownership/control relationships Typical merchant subjects UBO, director, controller, authorized representative where applicable Merchant company Evidence orientation Personal/identity evidence Corporate, registry, ownership, business evidence What can trigger it? A relevant person has been identified Merchant application/business relationship Key dependency May depend on KYB identifying the person first Can identify people who require KYC Common merchant misunderstanding “You already saw their name in the company records.” “You verified the people, so the company is verified.” Merchant diagnostic question Who is this person? What is this business and how is it owned/controlled/represented? Visual footer Classify the subject before classifying the document. This directly supports the article's primary merchant decision and avoids reproducing the independent definitions owned by KYC Explained and KYB Explained.

D. SEO package SEO title: KYC vs KYB: What's the Difference in Merchant Onboarding? H1: KYC vs KYB: What's the Difference in Merchant Onboarding? Meta description: Learn the difference between KYC and KYB in merchant onboarding, why a company may undergo KYB while owners or directors undergo KYC, and how to identify what each verification request is trying to establish. Suggested URL slug: /kyc-kyb/kyc-vs-kyb/ Primary keyword: KYC vs KYB Secondary keywords: KYC and KYB difference; KYB vs KYC; KYC vs business verification; KYC KYB merchant onboarding; KYC requirements for companies; know your customer vs know your business. Related entities Customer due diligence, CDD, natural person, legal person, legal entity, business verification, merchant verification, beneficial owner, ultimate beneficial owner, UBO, director, controller, authorized representative, beneficial ownership, corporate ownership, entity verification, identity verification, merchant onboarding. Recommended excerpt KYC and KYB answer different questions about the same merchant relationship. KYB establishes the business and maps relevant ownership, control, and representation relationships; KYC establishes the identities of natural persons such as beneficial owners or directors where required. A company passing KYB therefore does not automatically eliminate personal KYC requirements. Internal links KYC Explained Recommended anchor: how KYC verifies a natural person Use after the first natural-person definition. KYB Explained

Recommended anchor: how KYB verifies a legal entity and its business relationships Use after the business definition. Ultimate Beneficial Owner Requirements Recommended anchor: who qualifies as a UBO under the applicable requirements Use where the article deliberately declines to provide one universal threshold. Director Verification Recommended anchor: why director verification differs from beneficial ownership verification Use after director ≠ UBO. These are the article's assigned internal-link targets. Structured-data recommendation Use Article structured data with the actual published headline, author, publication/modification dates, and supporting image. A conventional FAQ section is not necessary. The KYC vs KYB Decision Matrix answers the comparison intent more directly and is a better information-gain asset. Supporting visual KYC vs KYB: One Merchant, Two Verification Subjects Center: MERCHANT APPLICATION Split into two branches. BUSINESS — KYB Merchant legal entity → registration → business activity → ownership/control mapping → directors/representatives identified Then show an arrow from identified people across to: PEOPLE — KYC Natural persons → beneficial owner → director where required → controller where required → authorized representative where required At the bottom: KYB can identify who needs KYC. KYC does not replace verification of the business. Recommended alt text

KYC vs KYB decision diagram showing a merchant company undergoing KYB to establish its legal entity, business, ownership and control relationships, while relevant natural persons such as beneficial owners or directors may undergo separate KYC identity verification.

E. Source and verification plan Recommended authoritative sources FATF — current conceptual foundation Use the FATF Recommendations, current glossary, and beneficial-ownership guidance for the internationally relevant conceptual distinction among legal-person customers, natural persons, beneficial ownership, and ultimate control. FATF states that an ultimate beneficial owner is always a natural person and recognizes ownership/control through chains or other forms of control. This is the strongest source for the article's global conceptual architecture, not a basis for claiming that every country's merchant-onboarding procedure is identical. UK HMRC — useful current jurisdictional illustration Current UK CDD guidance distinguishes individual and entity customers, understanding ownership/control of legal persons, beneficial-owner verification, and the identity/authority of people acting for companies. Keep every such statement explicitly UK-specific if detailed requirements are introduced. FinCEN — useful U.S. illustration FinCEN's current CDD material illustrates the relationship between legal-entity customers and their natural-person beneficial owners. In February 2026, FinCEN granted covered financial institutions exceptive relief from identifying and verifying beneficial owners at each new account opening, while retaining requirements in defined circumstances.

That recent change is exactly why the publication should avoid turning one jurisdiction's procedure into a universal KYB/KYC rule. Claims requiring primary-source verification before adding specificity Any final publication edit that introduces the following needs fresh jurisdiction-specific sourcing: * which persons must undergo KYC; * director-verification requirements; * UBO ownership/control thresholds; * required identity information; * accepted identity documents; * accepted corporate evidence; * proof-of-address requirements; * document age; * certification/notarization; * electronic-verification rules; * required registry checks; * whether particular checks can occur after relationship establishment; * periodic re-verification; * source-of-funds or source-of-wealth requirements; * bank-account ownership requirements. The brief explicitly treats these as time-sensitive and prohibits universal requirements. Jurisdiction-specific checks For every numerical threshold or mandatory requirement, record internally: jurisdiction → regulated activity → affected party → requirement → primary legal/regulatory source → effective date → exceptions. Do not use a FATF recommendation as though it were directly operative national law. Do not use U.S., UK, or EU requirements interchangeably. Provider-policy checks Distinguish whether each request comes from: law/regulation regulator guidance acquirer/bank requirement payment-network requirement provider policy risk-based enhanced diligence

merchant-specific circumstances. The brief requires this distinction explicitly.

That safely supports only a limited public statement about merchant-associated personal information and KYC.

2. Which legal entities undergo business verification. 3. Which merchant information is verified against independent sources. 4. Which corporate registries or data sources may be used. 5. Which associated natural persons can require KYC. 6. Whether directors are verified universally or only in defined circumstances. 7. Which beneficial owners can require verification. 8. Current jurisdiction/provider/acquirer-specific UBO criteria. 9. Whether controllers are a separate verification subject. 10. How authorized representatives are verified. 11. How identity is separated from authority to act. 12. Current Business Profile information collected. 13. Current corporate-document requirements. 14. Current personal-document requirements. 15. Whether document requirements vary dynamically by merchant. 16. Whether KYB mapping identifies people who then enter KYC workflows. 17. Which entity/person checks can run in parallel. 18. Which checks have true dependencies. 19. How ownership discrepancies are handled. 20. How director discrepancies are handled. 21. Whether merchant-supplied ownership charts are independently validated. 22. Whether registry data is used automatically or manually. 23. Whether verification evidence can be reused. 24. Current secure document-upload methods. 25. Data-retention/access policies relevant to merchant verification. 26. Ongoing merchant re-verification procedures. 27. Whether changes of ownership/directors trigger additional checks.

28. Which onboarding/KYC terminology is approved for public publication. 29. Which workflow details are proprietary. 30. Whether any approved merchant example or aggregate onboarding data exists.

F. Human review recommendation Recommended author: Merchant compliance/onboarding specialist with practical KYC/KYB operations experience. Primary compliance reviewer: AML/KYC/KYB specialist who can validate the distinction among legal-entity verification, beneficial ownership, director verification, and natural-person identity checks. Legal reviewer: Payments/financial-services legal counsel if jurisdiction-specific regulatory claims are added. Regional specialist: Needed only when the publication introduces country-specific KYC/KYB requirements; a general comparison article should avoid unnecessary geographic detail. Recommended last-reviewed field: Use a visible last-reviewed date because KYC, beneficial-ownership, and provider requirements change. The brief identifies these types of compliance, onboarding, legal, and regional expertise as appropriate publication reviewers and explicitly prohibits inventing named reviewers or implying that review has already occurred. Best first-hand contribution An approved merchant-operations example where an applicant initially believed a personal verification request duplicated completed company verification, but the unresolved fact was the identity or authority of a natural person identified during the company's ownership or director mapping. The contribution should explain: company fact already verified → new person/relationship identified → different verification objective

Final differentiation check Dimension KYC vs KYB Intellectual center Relationship between two verification subjects Subject Person versus business Primary merchant confusion Why both checks appear in one application Core evidence anchor Company undergoes KYB while relevant people may undergo KYC Framework KYC vs KYB Decision Matrix Main decision Is this request verifying the company or a person? Important dependency KYB can identify natural persons who need KYC Primary misconception Company KYB makes personal KYC redundant Not owned here Complete KYC definition, complete KYB definition, UBO threshold analysis, director-verification procedure Conclusion Different checks complete different parts of the same merchant relationship That keeps Article 3 in exactly the territory assigned by the cluster map: direct comparison, overlap, person versus business, and why KYB of a company can coexist with KYC of the people connected to it.