Skip to main content
PUT
/
virtual-accounts
/
{id}
Update a virtual account
curl --request PUT \
  --url https://developersandbox-api.flutterwave.com/virtual-accounts/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "action_type": "update_bvn",
  "status": "inactive",
  "bvn": "12345678912",
  "meta": {}
}
'
{
  "message": "<string>",
  "data": {
    "id": "",
    "amount": 1000,
    "account_number": "7824822527",
    "reference": "htuy68787hvhyff454",
    "account_bank_name": "WEMA BANK",
    "account_type": "static",
    "account_expiration_datetime": "2025-12-03T13:54:21.546559974Z",
    "note": "Please make a bank transfer to James Burgers",
    "customer_id": "cus_J0PvwvJB2n",
    "created_datetime": "2024-12-03T13:54:21.546559974Z",
    "meta": {},
    "customer_reference": "AEGP2345",
    "currency": "NGN"
  }
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
X-Trace-Id
string

A unique identifier to track this operation. It must be between 12 and 255 characters in length.

Required string length: 12 - 255
​
X-Scenario-Key
string

An optional scenario key that can be used to simulate specific behaviors or test different scenarios within the API. Providing this header allows you to trigger predefined responses or alter data based on the key's value, which can be useful for testing, development, or demonstrating specific functionalities. The key should be a string of 1 to 1000 characters.

Path Parameters

​
id
string
required

ID of the virtual account.

Example:

"va_EFAHCzELJb"

Body

application/json
​
action_type
enum<string>
required

The supported virtual account update actions.

Available options:
update_bvn,
update_status
Example:

"update_bvn"

​
status
enum<string>

The status of the virtual account.

Available options:
inactive
Example:

"inactive"

​
bvn
string

This is the customer's Bank Verification Number.

Pattern: ^[1-9][0-9]{10}$
Example:

"12345678912"

​
meta
object

Response

OK

​
status
enum<string>
Available options:
success,
failed
​
message
string
​
data
object