Skip to main content
Use updates to correct mistakes, respond to compliance requests, or refresh expired documents.
Some changes can trigger re-verification. Design your UX so the user understands why they may need to upload new documents again.

​
What can be updated

You typically update:
  • Name
  • Date of birth
  • Nationality
  • Address
  • Phone number
  • Email

​
What users should expect after an update

Example: phone number or email updates.The customer may remain active.
Example: name, date of birth, nationality, or address corrections.The customer may move to update_requested or pending while the update is reviewed.

​
Operational guidance

  • If the customer is blocked from product usage during re-verification, show a clear message and expected next step.
  • If the update was requested by compliance, keep the request and updated documents together in your UI to reduce back-and-forth.

​
Implementation details

For what fields are writable and how to submit an update, use the Customers API reference.

​
FAQ

Can I update a customer’s nationality? Yes, but this may trigger a full re-verification and compliance review, as nationality changes can affect regulatory requirements. What happens to active cards during re-verification? Existing cards remain functional. However, new card issuance is paused until the customer returns to active status. Can I update multiple customers in bulk? Bulk updates are not currently supported via the API. Each customer must be updated individually.