Every week, platforms onboard businesses they have never met. Some are legitimate SMEs ready to transact. Others are fabrications — registered-looking entities with no real operations behind them. CAC verification is the first line of defence that separates one from the other.

CAC verification sits at the centre of business onboarding in Nigeria. Whether it's a fintech onboarding merchants, a lender verifying SMEs, or a marketplace approving new vendors, it is one of the first systems used to confirm that a business is actually real.

What makes it harder than it looks is not the lookup itself. It is the consistency problem: name formatting mismatches, outdated registration statuses, and isolated checks that are never revisited after onboarding. At scale, these gaps compound quickly.

This article breaks down what CAC verification is in Nigeria and how it actually works inside real onboarding systems.

What CAC Verification Actually Is in Nigeria

CAC verification is a structured lookup in Nigeria's Corporate Affairs Commission database to confirm whether a business is officially registered and whether the provided details match existing records.

At its simplest level, it allows platforms to validate a business using either an RC number or registered business name and compare it against official CAC records.

In most onboarding systems, the verification process returns key business information such as the registered name, RC number, incorporation date, and registration status. This status typically shows whether the business is active, inactive, or dormant.

What platforms actually rely on is not just the data itself, but consistency between what the user submits and what the registry returns. Even small mismatches in business name formatting or RC details can determine whether a business passes onboarding or gets flagged for review.

It is also worth noting what CAC verification does not cover on its own. Confirming registration is not the same as confirming legitimacy, active operations, or beneficial ownership. This is why CAC verification works best as one layer inside a broader KYB system rather than a standalone check.

How CAC Verification Works Step-by-Step

CAC verification is usually embedded inside onboarding or KYB systems. Here's a step-by-step process of how it works in practice:

Step 1: Business details are submitted

 The merchant provides business information such as business name, RC number, or registration details during signup. This becomes the system's first reference point for validation.

Step 2: System triggers a CAC lookup request 

The onboarding system sends a query to the CAC registry or an integrated verification provider. This request is used to search for a matching business record.

Step 3: Registry search and record matching 

The CAC database is searched using RC number or business name. At this stage, the system is trying to determine whether a valid, matching business exists in official records.

Step 4: Returned data is validated against input

 The system compares returned CAC data with what the merchant submitted. It checks for consistency in name structure, registration number, and business status.

Step 5: Onboarding decision is applied

 Based on match accuracy and registration status, the business is either approved, flagged for manual review, or rejected. This decision is passed directly into the onboarding flow.

Common Mistakes in CAC Verification Implementation

Even though CAC verification is widely adopted, many platforms still implement it in ways that weaken its reliability at scale.

1. Over-reliance on manual CAC checks 

Some platforms still depend on manual registry searches. This slows down onboarding and introduces inconsistency in how verification decisions are made across different reviewers.

2. Weak RC and business name matching logic

 Without proper matching rules, small variations in spelling, formatting, or abbreviations can cause incorrect verification outcomes. This leads to both false approvals and unnecessary rejections.

3. Poor input standardisation before verification 

When business data is not cleaned or standardised before lookup, the system struggles to match it correctly against CAC records. This creates avoidable mismatches during verification.

4. Treating CAC as a one-off onboarding check 

Many systems verify businesses only at signup and never revisit the verification status again. This limits CAC to a static checkpoint instead of a continuous trust signal.

5. Isolating CAC from broader identity and risk checks

 CAC verification is often run independently, without connection to identity verification, account ownership, or fraud risk systems. This creates gaps where a valid business registration does not guarantee a trusted merchant.

How to Automate CAC Verification in Nigeria

As onboarding scales, manual CAC verification quickly becomes a bottleneck. The question is no longer whether to automate, but how to embed it correctly.

1. Real-time CAC lookup via APIs

 Instead of manual registry searches, platforms can verify businesses instantly using CAC APIs that return structured business data in real time. This removes the single biggest source of onboarding delay.

2. Direct integration into onboarding workflows

 CAC verification can be embedded directly into signup and KYB flows, allowing checks to happen automatically as part of onboarding rather than as a separate process. When verification is woven into the flow rather than bolted on afterwards, fewer businesses fall through review queues.

3. Consistent, scalable verification decisions

 API-based verification removes the human variability that makes manual checks unreliable at volume. Whether a platform is onboarding ten merchants or ten thousand, the logic applied to each lookup stays the same.

This is where platforms like Dojah come in. Instead of building and maintaining CAC verification infrastructure internally, platforms integrate APIs that handle business lookup and validation as part of a unified onboarding system, connecting CAC data to identity verification, account validation, and risk scoring in a single flow.

Seamless CAC Verification with Dojah

Most CAC verification failures are not registry problems. They are implementation problems: checks that run too late, match logic that is too loose, and verification that stops at registration without asking whether the business behind the number is actually trustworthy.

Automation solves the first layer. Integration solves the rest.

With Dojah, platforms can embed CAC verification directly into their onboarding systems, turning it from a manual step into a real-time infrastructure layer. Here is what that looks like in practice:

• Real-time business lookup at the point of onboarding, so registration status is confirmed before a merchant moves further into the flow, not after.
• Immediate validation of registration and status, including whether the business is active, inactive, or dormant, surfaced in the same step rather than checked separately.
• Seamless connection to broader KYB checks, so CAC data does not sit in isolation. It feeds into identity verification, account ownership validation, and risk scoring as part of a single onboarding decision.
• Reduced manual review workload, because legitimate businesses clear the automated checks without needing human intervention, freeing operations teams to focus on the cases that actually need review.

By turning CAC verification into an automated workflow, platforms reduce friction while strengthening trust at the point of onboarding.

See how platforms are cutting merchant onboarding time while tightening business verification. Explore Dojah's KYB APIs.

Frequently Asked Questions About CAC Verification in Nigeria

What is an RC number?

An RC number, or Registration Code number, is the unique identifier assigned to a business by the Corporate Affairs Commission at the point of registration. It is the primary reference used during CAC lookups to match a business against official records.

What types of businesses need CAC registration in Nigeria?

Any business operating as a limited liability company, business name, or incorporated trustee in Nigeria is required to register with the CAC. Sole traders operating informally may not have RC numbers, which is why platforms should understand what entity types they are onboarding before designing their verification flow.

How long does CAC verification take with an API?

With an automated API integration, CAC verification typically returns results in seconds. The delay in most onboarding systems comes from manual review steps, not the lookup itself.

Does a valid CAC registration mean a business is trustworthy?

Not on its own. CAC verification confirms that a business is registered, not that it is actively operating, financially sound, or free from fraud risk. This is why CAC verification works best as one layer inside a full KYB system that also includes identity checks, account validation, and risk scoring.

Can CAC verification be used for continuous monitoring, not just onboarding?

Yes. Platforms that revisit CAC status periodically can detect businesses whose registration has lapsed or become dormant after onboarding. Treating CAC as a continuous signal rather than a one-time gate significantly improves ongoing merchant risk management.