---
title: "Withdraw lock customer account"
method: POST
path: "/accounts/{zrn}/withdraw_lock"
tags: ["Customer Accounts (MTA)"]
---

# Withdraw lock customer account

`POST /accounts/{zrn}/withdraw_lock`

Locks withdrawals for an existing customer account

## Path parameters

- `zrn` string, required

## Headers

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

## Request body

- WithdrawLockCustomerAccountBody — Request body for withdraw-locking a customer account. Withdraw-locking an account prevents any new withdrawal requests from being created on the account, but does not impact the ability to create trades or deposits. This is typically used as a precautionary measure when suspicious activity is detected on an account, in order to prevent potential funds outflows while an investigation is conducted.

## Response `202`

Request to withdraw-lock the customer account accepted. The withdraw lock is applied asynchronously; clients should listen for the `customer_account_status_changed` webhook event to observe the new state.

- object — Empty JSON object.

## 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)