Skip to main content
Update a Customer by ID
Use this endpoint to update mutable fields on an existing individual customer. You can update the customer’s address, personal information, and metadata at any time before KYC submission. Once a KYC review has been submitted, identity fields such as name, date of birth, and tax identification number are locked and cannot be changed — only contact details and metadata remain editable. Use this endpoint to backfill EEA+ fields (accountPurpose, countryOfBirth, nationality) on existing individual customers. Validation runs on the merged customer state — send only the fields you are adding or changing. See EEA+ residents.
This endpoint currently supports updates for individual customers only. Business customer fields must be managed through the KYC link flow.

Authorizations

Authorization
string
header
required

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

Path Parameters

id
string
required

Customer ID

Example:

"customer_f31121c389624d3697cbf3ea8830b7a4"

Body

application/json
address
object

The address of the customer. Required if personalInformation is provided.

Example:
meta
object

The customer metadata

Example:
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