Onboard a Corporate Customer with KYB and UBO Verification

This guide covers business onboarding, creating a business entity, verifying it against official registries, and screening the company and its beneficial owners.

1

Complete authentication and connection check

Before creating any entity, authenticate your API session and confirm connectivity. Every request carries your API secret token in the header; a failed auth check here is the most common cause of downstream 401 errors that look like data problems but aren't.

2

Add the business entity

Tier 1 typically requires only a name and phone number. Choose the creation method that matches the data you hold.

• Add with incorporation number and country. The most reliable method resolves the company directly against the registry.

POST {{baseUrl}}/v2/api/entities
{
  "entityType": "business",
  "isSubjectConsent": true,
  "incorporationName": "Acme Payments Ltd",
  "incorporationNumber": "RC123456",
  "incorporationCountry": "NG",
  "incorporationDate": "2015-03-20",
  "businessType": "Fintech",
  "address": "12 Marina Street, Lagos"
}

References: Create Entity

3

Verify the business with a KYB check

Cross-reference the company against official registries. The response returns verified company details registration status, directors, and available ownership data.

POST {{baseUrl}}/v2/api/entities/:entityId/company
{
  "entityType": "business",
  "isSubjectConsent": true,
  "incorporationNumber": "RC123456",
  "incorporationCountry": "NG",
  "checkType": "standard"
}

References: Verify Entity (KYB)

4

Screen the business and its UBOs

Screen the company name and each Ultimate Beneficial Owner against sanctions lists, PEP databases, watchlists, and adverse media. Supply UBO details in a single call the platform runs individual checks on each.

POST {{baseUrl}}/v2/api/entities/:entityId/amlChecks
{
  "entityType": "business",
  "isSubjectConsent": true,
  "incorporationName": "Acme Payments Ltd",
  "incorporationCountry": "NG",
  "amlCheckType": "name",
  "amlChecks": [
    "pep",
    "sanctions",
    "adverseMedia"
  ],
  "ubos": {
    "uboList": [
      {
        "category": "individual",
        "firstName": "Michael",
        "lastName": "Okonkwo"
      }
    ],
    "amlChecks": [
      "pep",
    "sanctions",
    "adverseMedia"
    ]
  }
}

References: Verify Entity (AML)

5

What happens in the background?

The moment the entity is created, the platform automatically runs a full AML screen — Sanctions, PEP, Watchlist, and Adverse Media — against it. This always runs, on every plan, and produces the entity's initial risk score.

At this stage the score reflects AML data only. A newly created entity has no session or behavioral history yet, so Fraud Insight — which scores device and behavioral signals — has nothing to evaluate. As the customer transacts and generates signals, Fraud Insight enriches the profile into a fuller risk score on the same entity record. This enrichment happens over the customer's lifecycle, not at creation.