Skip to main content
Before Nmbr can process payroll for a company, Nmbr needs information about the company to meet regulatory obligations, determine processing periods, and surface onboarding flows. As a partner, you submit this information through the Nmbr API before the customer’s first payroll. This guide walks through the API calls to create the company, create at least one business entity, and send the customer through business verification (KYB).

1. Create a company

A Company is the top-level container for one customer. Create it with your partner secret. The response includes a company-scoped access_token for future API calls for that customer. Request
Response

2. Create a business entity

A business entity is the legal employer that runs payroll. Tax agency accounts, such as CRA payroll accounts, are configured separately as remittance accounts. Required information includes:
  • Business number
  • Legal business name
  • Legal registration number
  • Address on file
  • Primary business contact
A company can have more than one business entity. Use the company-scoped access_token returned when you created the company. Request
Response
Outcome: Nmbr creates the business entity and starts business verification automatically. You do not need to create a separate verification record.

3. Send the customer to business verification

KYB stands for “Know Your Business.” It is the due diligence process financial companies use to verify a business’s identity and assess risk. Nmbr checks the business against corporate registries, sanctions and watchlists, and other AML sources. Nmbr creates a business entity verification when the business entity is created. When verification needs information directly from the business, Nmbr stores a hosted verification link on the business entity verification record. Retrieve the verification record after you create the business entity. Send the customer to the returned link so they can complete verification. Request
Response
Outcome: the customer completes verification from the hosted link. Nmbr receives the result from the verification provider and updates the verification status. Note: the verification link is provider-hosted and may expire. If a link no longer works, contact Nmbr support for a refreshed link.

4. Check verification status

Use GET /business_entities/<business_entity_id>/verification to check the current status. The status field is the verification decision. The link_status field only tracks how far the business has gotten through the hosted link:
  • not_started: the link has been shared, but the business has not completed it.
  • in_progress: the business submitted their information and it is being processed.
  • complete: the information is in and has been picked up for review.
link_status never carries the decision. Read the outcome from status.

Business verification warnings

Business verification can block onboarding while the status is incomplete, requested, or failed. When the status is approved, Nmbr clears the business verification warning. You can then continue with the rest of the company setup flow.

If verification needs review

Automated KYB can fail when business information cannot be validated against registry data, sanctions lists, or other AML checks. If that happens, Nmbr may ask the customer for an identification document so Nmbr can complete manual KYC/KYB review. Nmbr accepts any of the following documents for a business:
  • Certificate of incorporation/registration
  • Memorandum/articles of incorporation/association/registration
  • Directors registry
  • Shareholder registry
  • Trust agreement
  • Proof of address. For example, a utility bill, rent contract, or electricity bill.
  • Certificate of incumbency
  • Statement of information
  • Certificate of good standing
Manual review can often take 24 hours after Nmbr has the required information. Partners should not build a separate document-upload step for this guide. Nmbr does not expose an API for partners to upload these documents for business verification. The verification response also does not include a machine-readable failure reason or manual review payload.