---
title: "Update a virtual account"
method: PUT
path: "/v1/accounts/virtual/{identifier}"
tags: ["Virtual Accounts"]
---

# Update a virtual account

`PUT /v1/accounts/virtual/{identifier}`

You can use this endpoint to update a virtual account.

## Path parameters

- `identifier` string, required

## Headers

- `accountId` string, uuid, required

## Request body

- UpdateVirtualAccountRequest
  - `newAccountRef` string — The new accountReference you want to issue to the Virtual account. This will be the value advised in webhook post update
  - `accountName` string — Account holder's name you want to update to
  - `expectedAmount` string — If provided, the virtual account will only accept payments that exactly match the specified amount. Once expectedAmount is set, the virtual account will no longer accept arbitrary payment amounts. You can, however, update the expectedAmount value at any time to change the accepted amount.

## Response `200`

OK - your request was successful.

- object
  - `code` string, required — Response Code
  - `description` string, required — Response description
  - `data` UpdateVirtualAccountResponse, required
    - `updated` boolean, required — Successfully updated

## Other responses

- `400` — The request body sent by merchant did not pass the validation checks
- `401` — The access_token provided to access the resource is missing or invalid.
- `403` — The client does not have the permissions to access this resource
- `404` — The record that the client is trying to access does not exist.
- `429` — The client has maxed out the number of calls within a time period on this resource.
- `500` — Downstream system error.

---

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