Create Customer
Create a new individual customer profile with identification details, address information, and KYC compliance data.
Overview
Create a new individual customer profile. This endpoint allows you to onboard customers with identification details, address information, and KYC (Know Your Customer) compliance data. The response confirms successful creation or returns relevant validation errors.Required fields
| Field | Description |
|---|---|
email | Valid email address |
first_name | Customer first name |
last_name | Customer last name |
phone | Phone number |
date_of_birth | YYYY-MM-DD |
country_code | ISO country code |
Optional fields
| Field | Description |
|---|---|
gender | Customer gender |
documents | Array of identity documents (recommended; see Identity documents) |
address | Residential or mailing address: street, city, state, postal_code, country, optional document (base64-encoded proof-of-address file) |
proof_of_funds | Employment and source-of-funds object (employment_status, occupation, primary_purpose, source_of_funds, expected_monthly_pay). Allowed field values and meanings are in Proof of funds options. |
Identity documents
Each entry in thedocuments array uses the same shape:
id_type— Any of:passport,resident_id,drivers_license,national_id,voters_card,nin,bvn, or a tax ID type (see Tax ID document)id_number— The number on the documentfront_doc— Base64-encoded image of the frontback_doc— Base64-encoded image of the back when applicable
passport, resident_id, drivers_license, national_id, voters_card, and nin, you need at most front_doc (base64); back_doc is not required for those types.
To change documents or proof-of-funds after creation, use Update customer.
Tax ID document
A tax ID document is required when creating virtual accounts for a customer. Submit it as an entry in thedocuments array. The tax ID value is always passed in id_number; the id_type depends on the customer’s country:
| Country | Country Code | id_type |
|---|---|---|
| Algeria | DZ | nif |
| Angola | AO | nif |
| Canada | CA | sin |
| France | FR | spi |
| Indonesia | ID | npwp |
| Italy | IT | cf |
| Kenya | KE | pin |
| Mexico | MX | rfc |
| Nepal | NP | pan |
| Nigeria | NG | bvn |
| Pakistan | PK | ntn |
| Romania | RO | cnp |
| Tunisia | TN | mf |
| Turkey | TR | tckn |
| United Kingdom | GB | nino |
| United States | US | ssn |
| All other countries | — | tin |
id_type: "tin".Authorizations
API key for authentication.
Body
Customer email
Customer first name
Customer last name
Customer phone number
Date of birth (YYYY-MM-DD)
ISO country code
Customer gender
Identity documents (see DocumentInput). Preferred way to send one or more IDs on create.
Legacy single primary identity document. Same shape and id_type values as each item in documents. Prefer documents when starting new integrations.
Legacy extra identity documents. Same id_type options and front/back rules as documents. The API merges these with documents server-side; prefer a single documents array when possible.
Proof-of-funds / source-of-wealth fields. Use allowed field values from Proof of funds options in the Customers guides.

