Deactivate a customer
Stops new money movement for the customer. Card purchases are declined with account_inactive. New cards, transfers (POST /transfers), account payouts and wallet sends are refused with 403 CUSTOMER_DEACTIVATED; withdrawals through the custody API are refused with 403 USER_DEACTIVATED. Deposits sent to the customer's wallets and accounts still arrive and are credited, but cannot be spent until you reactivate. It applies to test keys too, so you can try it in the sandbox.
Operations created before the deactivation finish, except wallet sends still waiting for approval or a delay, which are refused when they would execute. Self-custody transaction intents are not affected: OZAV does not sign them.
Calling it again on a deactivated customer changes nothing and returns the date of the first deactivation. This is your own switch: it does not lift, and does not reveal, any restriction OZAV applies for compliance reasons. Your organization's own account cannot be deactivated (422 CUSTOMER_DEACTIVATION_NOT_ALLOWED).
Request
- Base URLhttps://developers.ozav.io/v2
- Auth
- API key in header X-API-Key
- or HTTP bearer
Path parameters
Response
The customer's deactivation state.
Changes
No recorded changes to this operation across all 1 revision of this API.