Skip to main content
POST
Create customer

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

Optional fields

Identity documents

Each entry in the documents 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 document
  • front_doc — Base64-encoded image of the front
  • back_doc — Base64-encoded image of the back when applicable
For 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 the documents array. The tax ID value is always passed in id_number; the id_type depends on the customer’s country: For any country not listed above, use id_type: "tin".

Authorizations

X-API-KEY
string
header
required

API key for authentication.

Body

application/json
email
string<email>
required

Customer email

first_name
string
required

Customer first name

last_name
string
required

Customer last name

phone
string
required

Customer phone number

date_of_birth
string<date>
required

Date of birth (YYYY-MM-DD)

country_code
string
required

ISO country code

gender
string

Customer gender

documents
object[]

Identity documents (see DocumentInput). Preferred way to send one or more IDs on create.

document
object

Legacy single primary identity document. Same shape and id_type values as each item in documents. Prefer documents when starting new integrations.

additional_documents
object[]

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.

address
object
proof_of_funds
object

Proof-of-funds / source-of-wealth fields. Use allowed field values from Proof of funds options in the Customers guides.

Response

Customer created successfully

status
boolean
data
object
error
any[]
message
string