Beneficial Ownership Verification for Nigerian Businesses: An Evidence Guide

Beneficial ownership verification for Nigerian businesses helps answer a question that a company registration certificate cannot settle alone: which natural persons ultimately own or control this business? For fintechs, marketplaces and other digital businesses embedding financial services, that answer should inform whether a customer can access accounts, payouts or cards.

This guide focuses on the evidence and decision controls behind ownership verification—not a general onboarding integration or an ongoing monitoring programme. The goal is to help product, compliance and engineering teams turn complicated ownership structures into reviewable cases before activating financial features.

Paddle is a banking-as-a-service platform by Pickpadi Global Ltd. It is not a bank; banking services are provided by CBN-licensed partner banks. Your verification process should reflect the requirements of the relevant partner, your product and applicable Nigerian obligations. This guide is not legal advice.

Why company registration is not enough

A company can be validly registered while its ultimate ownership remains unclear. Its direct shareholder might be another company. The person operating the account might be a director rather than an owner. Someone with a small shareholding might exercise control through voting rights or contractual arrangements.

Those distinctions matter when your product lets a business receive customer funds, pay vendors or issue employee cards.

Keep these roles separate in your data model:

• Legal entity: the registered business seeking access to your product.
• Direct shareholder: a person or entity holding shares in that business.
• Beneficial owner: a natural person who ultimately owns or controls it under the applicable criteria.
• Authorised representative: the person permitted to act for the business.

Verifying a representative’s identity does not establish beneficial ownership. Identifying the owners does not establish that the representative has authority to initiate transactions.

Beneficial ownership verification for Nigerian businesses: what to establish

In Nigeria, the Corporate Affairs Commission, or CAC, is a relevant source for company information and persons with significant control disclosures. Registry information can support verification, but it should not automatically replace the evidence or checks required by your banking partner.

Do not hard-code a single ownership threshold based on an article or a remembered rule. Applicable definitions, control tests and evidence requirements need to be confirmed against current requirements, including relevant CAC guidance, CBN materials and partner policies.

Your process should establish three things:

1. Who owns the entity: identify direct interests and follow corporate ownership chains to natural persons.
2. Who controls the entity: investigate relevant voting, appointment or other control rights, even where shareholding alone looks straightforward.
3. Whether the evidence supports the declaration: compare customer-supplied information with suitable records and resolve material discrepancies.

If the structure cannot be resolved, escalate it. Do not substitute the account operator as the beneficial owner simply to complete a required field.

Build an evidence pack, not just a form

An ownership declaration is a starting point. A defensible decision also needs evidence, provenance and a record of how discrepancies were handled.

Entity and ownership evidence

Depending on the entity and partner requirements, relevant material may include registration details, current company information, shareholder records, ownership declarations and documents explaining control arrangements.

For a corporate shareholder, collect enough information to continue tracing ownership. If an overseas entity appears in the chain, determine which registry records, translations or additional verification your partner accepts before promising fast activation.

Avoid treating every document as equally authoritative. A customer-created ownership chart is useful for navigation, but the underlying relationships still need support.

Identity and authority evidence

Once relevant natural persons are identified, complete the identity and screening checks required for them. Keep those results separate from the evidence establishing their ownership or control relationship.

Also verify the account operator’s authority through appropriate evidence, such as an accepted mandate or authorisation document. The exact evidence should follow the entity type and partner policy.

Evidence metadata

For each evidence item, record:

• The entity, person or relationship it supports.
• Its source and when it was obtained.
• The relevant issue or effective date, where available.
• The reviewer or verification process used.
• Any limitation, mismatch or unresolved question.

Store sensitive documents in controlled storage rather than application logs. Restrict access by role and apply a documented retention policy consistent with applicable requirements.

Model ownership as relationships

A flat list of names becomes unreliable when businesses have layered ownership. Use a relationship model that distinguishes entities, people, ownership interests and control rights.

For example, imagine a Nigerian operating company owned partly by an individual and partly by a holding company. That holding company has its own shareholders. Your review needs to connect each relevant natural person to the operating company through supported relationships.

For simple proportional structures, multiplying percentages along a chain can help calculate an indirect economic interest. It does not, by itself, resolve every legal ownership or control test.

Capture ownership percentages, voting rights and other control indicators separately. Where a relationship is unknown, mark it as unresolved rather than assigning a guessed percentage.

This model also makes review more efficient: an analyst can request evidence for one unclear relationship without asking the customer to repeat the entire submission.

Route discrepancies into explicit decisions

Discrepancies should produce a review task, not an invisible override. Common examples include a declaration that conflicts with registry information, a missing intermediate shareholder or documents that show different names for the same person.

Use defined outcomes:

• Request clarification: evidence is incomplete or an explanation is needed.
• Escalate for review: the structure, screening result or control arrangement needs specialist assessment.
• Approve: required checks are complete and the evidence supports activation.
• Decline: the case fails applicable acceptance criteria following the required review.

A name match in sanctions or politically exposed person screening requires assessment under the applicable policy; it is not automatically a confirmed match or an automatic rejection.

Record the decision reason, supporting evidence, reviewer and policy version. Customer-facing messages should explain what action is needed without disclosing sensitive screening logic or restricted information.

Gate financial capabilities separately

Do not let a completed form automatically unlock money movement. Separate submission, verification and product activation in your application.

Illustrative internal states might include evidence_pending, under_review, approved and declined. These are suggested application labels, not Paddle API statuses.

Keep capability permissions distinct from the review state. Approval for one product should not implicitly enable every other product. A business seeking domestic collections may face different requirements when requesting cross-border payouts or card issuing.

Enforce these permissions on the backend. A hidden dashboard button is not an access control. Before creating an account or initiating a payment, check the applicable approval and any partner-imposed restrictions.

If your integration consumes asynchronous verification updates, handle duplicates and delayed messages carefully. Preserve the decision history instead of allowing an older update to overwrite a newer review outcome.

Practical pre-activation checklist

Before releasing your ownership-verification workflow, confirm that your team can answer yes to each item:

1. Requirements: Have compliance and the banking partner confirmed the applicable ownership, control and evidence criteria?
2. Coverage: Can the model represent both direct individuals and layered corporate ownership?
3. Separation: Are ownership, identity, screening and representative authority recorded as distinct checks?
4. Exceptions: Can reviewers request clarification or escalate without inventing missing data?
5. Enforcement: Do backend capability checks prevent premature activation?
6. Traceability: Can you reconstruct why a case was approved using its evidence and policy version?
7. Privacy: Are collection, access and retention limited to a documented purpose?

Test with incomplete chains, conflicting records and late verification updates—not only a single-owner business with matching documents.

Build it with Paddle

Paddle offers KYB/AML verification alongside virtual accounts, NIP payouts, global payouts, card issuing through licensed partners and other embedded financial capabilities. Use those services within an ownership-review process that makes evidence, decisions and activation permissions explicit.

Before implementation, confirm supported checks, required documents, review responsibilities and product-specific requirements with Paddle and the relevant banking partner. Avoid assuming that one successful verification result satisfies every financial product’s requirements.

Ready to build? Create a free account and read the API docs to plan your verification and financial-service integration.