Skip to main content
Create a Customer
Before you can initiate any transfer, you must create a customer record in SpherePay. This endpoint registers either an individual or a business customer and returns a customer object with a unique ID and a verificationProfiles array that tracks KYC/KYB completion status. You must specify type upfront — it cannot be changed after creation. Individual customers resident in the EEA+ region and EEA+ incorporated businesses have additional fields that must be present before verification. Those fields are optional at creation. See EEA+ residents and EEA+ businesses.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
address
object
required

The customer's address.

email
string<email>
required

The customer email address

Maximum string length: 254
Example:

"jane.smith@example.com"

phone
string
required

The customer phone number in E.164 format

Pattern: ^\+(?:[0-9]){6,14}[0-9]$
Example:

"+14155550123"

type
enum<string>
required
Available options:
individual
dateOfBirth
string

The date string in YYYY-MM-DD format

Example:

"2026-01-01"

firstName
string

The customer's legal first name.

Required string length: 1 - 100
Example:

"Jane"

lastName
string

The customer's legal last name.

Required string length: 1 - 100
Example:

"Smith"

meta
object

Additional metadata associated with the customer

middleName
string

The customer's legal middle name.

Required string length: 1 - 100
Example:

"Anne"

personalInformation
object

Personal information including tax identification details for individual customers. When any tax identification field is provided, all tax identification fields (number, type, country) and address are required. Please refer to the Individual Verification Criteria for the full list of reference.

Response

Response containing information about an individual customer.

createdAt
string
required

ISO 8601 formatted customer creation timestamp

Example:

"2026-03-09T20:46:31.305Z"

id
string
required

Customer ID

Example:

"customer_f31121c389624d3697cbf3ea8830b7a4"

tosStatus
enum<string>
required

Customer Terms of Service acceptance status (incomplete | pending | approved).

Available options:
incomplete,
pending,
approved
Example:

"incomplete"

type
enum<string>
required

Customer type

Available options:
individual
Example:

"individual"

updatedAt
string
required

ISO 8601 formatted customer update timestamp

Example:

"2026-03-09T20:46:31.305Z"

verificationProfiles
object[]
required

Array of verification profiles. For individual customers, this will include kyc_profile_a. For business customers, this will include kyb_profile_a. See KYC Flow for individuals or KYB Flow for businesses. See Verification Profile for individual status definitions and criteria breakdown or Verification Profile for business status definitions and criteria breakdown.

Example:
dateOfBirth
string

The customer's date of birth in YYYY-MM-DD format (individual customers only).

Example:

"1990-01-15"

email
string

Customer email address

Example:

"jane.smith@example.com"

firstName
string

Customer first name (individual customers only)

Example:

"Jane"

lastName
string

Customer last name (individual customers only)

Example:

"Smith"

meta
object
personalInformation
object

Personal information for an individual customer, echoed back from the most recent submission. The tax identification number is omitted from responses for privacy.

phone
string

Customer phone number

Example:

"+14155550123"

Last modified on August 24, 2026