Skip to content
Sub-Accounts Onboarding/
/
Person
Last updated

Person

Overview

For Business entities, at least one Ultimate Beneficial Owner (UBO) must be verified, in addition to the business verification itself.

Once a Sub-Account for a Business entity has been created and you’ve received the Sub-Account ID in the response, you can use the Person API (if using the Non-Hosted onboarding flow) to add one or more individuals associated with the business.

The roles required for the Business are listed in the persons.required array, as shown in the example below.

subAccountGetById - Response Example
{
  ...,
  "persons": {
      "status": "Required",
      "required": [
          {
              "role": "BusinessContact",
              "minQuantity": 1
          },
          {
              "role": "Director",
              "minQuantity": 1
          },
          {
              "role": "UltimateBeneficialOwner",
              "minQuantity": 1
          }
      ]
  }
}

Please note: If a single individual fulfils all roles listed in the persons.required array, that is sufficient. However, in most cases, you will create one person with the BusinessContact role, and one or more persons with the Director and UltimateBeneficialOwner roles.

The following constraints apply:

  • Maximum of 1 person with the BusinessContact role
  • Maximum of 5 Directors
  • Maximum of 4 Ultimate Beneficial Owners
  • Maximum of 9 persons in total
  • Email addresses must be unique across all Person records (a 409 Conflict error will be returned if duplicates are submitted)

Create a Person

In order to create a Person entity for a Business, you can use the personCreate endpoint.

Request Example:

personCreate - Payload Example
{
    "firstName": "Fred",
    "middleNames": "David",
    "lastName": "Jones",
    "email": "fred.jones@example.com",
    "dateOfBirth": "1990-01-20",
    "countryOfBirth": "GB",
    "gender": "Male",
    "nationalities": ["GB"],
    "address": {
        "lineOne": "string",
        "lineTwo": "string",
        "city": "string",
        "country": "GB",
        "postalCode": "string",
        "region": "string",
    },
    "phoneNumber": "string",
    "businessRoles": ["UltimateBeneficialOwner", "Director"],
}

If a Person with the given email does not already exist under the specified Sub-Account, a 200 response containing the created resource will be returned.

Response Example:

personCreate - Response Example
{
    "id": "per_XXXXXXXX",
    "firstName": "Fred",
    "middleNames": "David",
    "lastName": "Jones",
    "email": "fred.jones@example.com",
    "dateOfBirth": "1990-01-20",
    "countryOfBirth": "GB",
    "gender": "Male",
    "nationalities": ["GB"],
    "address": {
        "lineOne": "string",
        "lineTwo": "string",
        "city": "string",
        "country": "GB",
        "postalCode": "string",
        "region": "string",
    },
    "phoneNumber": "+447900000000",
    "businessRoles": ["UltimateBeneficialOwner", "Director"],
    "verification": {
        "status": "Required",
        "requiredDocuments": [
            {
                "category": "ProofOfIdentity",
                "types": ["BankStatement", "DriversLicense", "Passport"],
                "quantity": 1,
                "state": "Invalid",
            }
        ],
    },
    "createdTimestamp": 1470989538,
    "lastUpdatedTimestamp": 1470989538,
}

The verification field is essential for identifying the documents required to verify a Person.

Next Steps

Once the Business entity and its associated Persons have been created, you can proceed to upload the necessary documents and provide any remaining information - see here.

Previous page
Next page