Skip to main content
PATCH
Update a customer

Authorizations

Authorization
string
header
required

Token from POST /auth/token

Path Parameters

customerId
string
required

Body

application/json

Partial update — only send the fields you want to change. All optional fields from CustomerRequest can be updated (including ipAddress). PII fields are write-only.

firstName
string
middleName
string
lastName
string
email
string
phone
string
birthDate
string
write-only
nationality
string
ipAddress
string
write-only
externalId
string
signedAgreement
boolean

One-way operation — cannot be set back to false.

residentialAddress
object

Customer's residential address.

identifyingInformation
object[]
write-only

Appends to existing array. To replace an entry, submit the same type with updated fields.

endorsements
enum<string>[]

Request additional endorsements. New endorsements are added; existing ones are not removed. Including endorsement names triggers re-evaluation.

Available options:
basic,
cryptoCustody,
usd
metadata
object

Response

Customer updated

Customer response object. PII fields (birthDate, residentialAddress, ipAddress, identifyingInformation) are write-only — accepted in POST/PATCH but never returned in responses.

id
string
Example:

"cst_01H9Xa8F5dN6mP3q"

object
string
Example:

"customer"

type
enum<string>

Customer type. Only individual is supported for MVP.

Available options:
individual
Example:

"individual"

firstName
string | null
Example:

"Jane"

middleName
string | null
Example:

null

lastName
string | null
Example:

"Smith"

email
string | null
Example:

"jane@example.com"

phone
string | null

Primary phone in E.164 format.

Example:

"+12125551234"

nationality
string | null

ISO 3166-1 alpha-2 country code.

Example:

"US"

externalId
string | null

Developer's own user ID for cross-referencing.

Example:

"usr_12345"

status
enum<string>

active or inactive. Inactive customers cannot create new transactions. No intermediate states — all granularity lives in endorsement statuses.

Available options:
active,
inactive
Example:

"active"

signedAgreement
boolean

Whether the customer has accepted OMS terms of service.

Example:

true

signedAgreementAt
string<date-time> | null

Timestamp when signedAgreement was set to true. Null if not yet signed.

Example:

"2026-03-20T14:15:22Z"

wallets
object[]

Simplified flat view: one entry per wallet-asset combination. Use GET /wallets/{id} for the full representation.

endorsements
object[]

Endorsements track KYC/compliance status. Types: basic, cryptoCustody, usd. Statuses use SCREAMING_CASE: INACTIVE, PENDING, ISSUES, ACTIVE, REJECTED, REVOKED_ISSUES, OFFBOARDED.

metadata
object | null
createdAt
string<date-time>
updatedAt
string<date-time>