Pular para o conteúdo principal
Create a Customer
Antes de iniciar qualquer transferência, você deve criar um registro de cliente (customer) no SpherePay. Este endpoint registra um cliente individual ou empresarial e retorna um objeto customer com um ID único e um array verificationProfiles que rastreia o status de conclusão do KYC/KYB. Você deve especificar type antecipadamente — ele não pode ser alterado após a criação. Clientes pessoas físicas residentes na região EEA+ e empresas constituídas na EEA+ têm campos adicionais que devem estar presentes antes da verificação. Esses campos são opcionais na criação. Consulte Residentes EEA+ e Empresas EEA+.

Autorizações

Authorization
string
header
obrigatório

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

Corpo

application/json
email
string<email>
obrigatório

The customer email address

Maximum string length: 254
Exemplo:

"jane.smith@example.com"

phone
string
obrigatório

The customer phone number in E.164 format

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

"+14155550123"

type
enum<string>
obrigatório
Opções disponíveis:
individual
address
object

The customer's address. Deprecated — prefer addresses.

addresses
object[]

The customer's addresses. Individual customers support exactly one residential address. Provide either this field or the deprecated address field, not both.

Exemplo:
dateOfBirth
string

The date string in YYYY-MM-DD format

Exemplo:

"2026-01-01"

enabledVerificationProfiles
enum<string>[]

Restricts which verification profile families this customer may onboard through. Must be a subset of the families enabled on your application; supplying one that is not enabled is rejected with a 422. Omit the field to inherit the application's setting.

Minimum array length: 1
Opções disponíveis:
a,
b,
c,
d
Exemplo:
firstName
string

The customer's legal first name.

Required string length: 1 - 100
Exemplo:

"Jane"

ipAddress
string

The IP address the customer used to sign up. Required by some verification providers.

Exemplo:

"203.0.113.4"

lastName
string

The customer's legal last name.

Required string length: 1 - 100
Exemplo:

"Smith"

meta
object

Additional metadata associated with the customer

middleName
string

The customer's legal middle name.

Required string length: 1 - 100
Exemplo:

"Anne"

personalExpectedActivity
Personal Expected Activity · object

The individual customer's expected transaction activity. Only accepted on individual customers.

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.

Resposta

Response containing information about an individual customer.

createdAt
string
obrigatório

ISO 8601 formatted customer creation timestamp

Exemplo:

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

enabledVerificationProfiles
enum<string>[] | null
obrigatório

Which verification profile families this customer may onboard through. Set explicitly at creation — from the request when supplied, otherwise a snapshot of the application's families at that moment — and thereafter changed only by an explicit update, so it does not follow later changes to the application. Always a subset of the application's families. Distinct from verificationProfiles, which reports the evaluated profiles and their statuses.

Opções disponíveis:
a,
b,
c,
d
Exemplo:
id
string
obrigatório

Customer ID

Exemplo:

"customer_f31121c389624d3697cbf3ea8830b7a4"

tosStatus
enum<string>
obrigatório

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

Opções disponíveis:
incomplete,
pending,
approved
Exemplo:

"incomplete"

type
enum<string>
obrigatório

Customer type

Opções disponíveis:
individual
Exemplo:

"individual"

updatedAt
string
obrigatório

ISO 8601 formatted customer update timestamp

Exemplo:

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

verificationProfiles
object[]
obrigatório

The evaluated verification profiles for this customer and their statuses — what the customer is being assessed against right now, as opposed to enabledVerificationProfiles, which says which families they are permitted to use. 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.

Exemplo:
dateOfBirth
string

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

Exemplo:

"1990-01-15"

email
string

Customer email address

Exemplo:

"jane.smith@example.com"

firstName
string

Customer first name (individual customers only)

Exemplo:

"Jane"

lastName
string

Customer last name (individual customers only)

Exemplo:

"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

Exemplo:

"+14155550123"

statusDetails
object

Additional context on why the customer's verification reached its current status.

Exemplo:
Última modificação em 27 de agosto de 2026