---
title: "Update customer account"
method: PATCH
path: "/accounts/{zrn}"
tags: ["Customer Accounts (MTA)"]
---

# Update customer account

`PATCH /accounts/{zrn}`

Updates prefunded and tier values for an existing customer account.

## Path parameters

- `zrn` string, required

## Headers

- `X-SCX-SIGNED` string, required
- `X-SCX-TIMESTAMP` string, required

## Request body

- UpdateCustomerAccountBody
  - `prefunded` boolean, required — Indicates whether the participant is using a prefunded model, or using the plaform float funding model to fund buy trades. - If `true`, the participant is prefunding their account and will be responsible for ensuring they have sufficient balance in their account to cover trades. - If `false`, the platform will fund trades from their float balance at zerohash, on behalf of the participant and settle at the end of the day.
  - `tier` 'lite' | 'pro' | 'bronze' | 'silver' | 'gold', required — The account `tier` associated with the account with regards to the commission structure defined by the platform. The specific tier values available depend on the platform configuration.

## Response `202`

Customer account updated successfully. Updating an existing customer account is an asynchronous process that does several operations in the background after the response is returned. 
 Customers are advised to listen to the `customer_account_status_changed` webhook event to be notified when the account is active and ready to use.

- CustomerAccountResponse
  - `message` object
    - `zrn` string — The unique zerohash Account Identifier.
    - `participant_code` string — The `participant_code` is the primary account holder.
    - `platform_code` string — The code of the platform associated with the newly created account.
    - `prefunded` boolean — Indicates whether the participant is using a prefunded model, or using the plaform float funding model to fund buy trades. - If `true`, the participant is prefunding their account and will be responsible for ensuring they have sufficient balance in their account to cover trades. - If `false`, the platform will fund trades from their float balance at zerohash, on behalf of the participant and settle at the end of the day.
    - `account_label` string — The platform-dictated account label for the participants account. Accounts labels created for the same participant must have a different `account_label` value, and all maintain an individual balance.
    - `account_group` string — The group that the account is a part of
    - `type` 'individual' | 'business' | 'jtic' | 'jtwros' | 'trust' | 'utma' — The account type associated with the account
    - `tier` 'lite' | 'pro' | 'bronze' | 'silver' | 'gold' — The account `tier` associated with the account with regards to the commission structure defined by the platform. The specific tier values available depend on the platform configuration.
    - `status` 'open' | 'locked' | 'withdraw_locked' | 'divesting' | 'closed' — The status of the customer account
    - `tenants` string[] — Tenants are the second owners of the account and have the same permissions as the primary account holder. Each tenant must be an onboarded participant to zerohash and not the same as the primary account holder.
    - `financial_advisors` string[] — The Financial Advisors of the participant which must be an onboarded participant to zerohash and not the same as the primary account holder.

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `404` — Not Found
- `500` — Internal Server Error
- `503` — Service Unavailable

---

[API](https://skmtc.net/zerohash/apis/zerohash-api.md) · [All operations](https://skmtc.net/zerohash/apis/zerohash-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zerohash/zerohash-api/revisions/8b647d934363/schema)