> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monxa.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Virtual Accounts
## Overview
Virtual Accounts (VAs) allow customers to complete payments by making a **bank transfer** into a unique account number issued for their transaction.\
This method is widely used across Asia because it is **familiar, trusted, and supports large-value payments**.
Monxa simplifies VA payments by:
* **Issuing dynamic or static VA numbers** through integrated banks and providers.
* **Returning ready-to-display VA details** (bank code, account number, expiry, instructions).
* **Listening for provider notifications** when funds are credited.
* **Sending webhook events** so your system always knows the real-time status.
Create a **charge** with virtual account channel code. Monxa requests a VA from the provider.
Show the customer the **bank name, VA number, and expiry** along with transfer instructions.
The customer transfers the exact (or open) amount to the VA via mobile banking or ATM.
Monxa confirms via **webhook** when funds are received and updates your system.
## Supported Channels
| Channel | Code | **Currency** | **Refund** | **Settlement** | Min Amount | Max Amount |
| :------- | ------------- | :----------- | :--------- | :------------- | ---------- | :---------- |
| BCA | `va_bca` | IDR | N/A | T+1 | 1 | 50,000,000 |
| BJB | `va_bjb` | IDR | N/A | T+1 | 1 | 500,000,000 |
| BNC | `va_bnc` | IDR | N/A | T+1 | 1 | 500,000,000 |
| BNI | `va_bni` | IDR | N/A | T+1 | 1 | 50,000,000 |
| BRI | `va_bri` | IDR | N/A | T+1 | 1 | 500,000,000 |
| BSI | `va_bsi` | IDR | N/A | T+1 | 1 | 500,000,000 |
| BSS | `va_bss` | IDR | N/A | T+1 | 1 | 500,000,000 |
| CIMB | `va_cimb` | IDR | N/A | T+1 | 1 | 500,000,000 |
| MANDIRI | `va_mandiri` | IDR | N/A | T+1 | 1 | 500,000,000 |
| MUALAMAT | `va_mualamat` | IDR | N/A | T+1 | 1 | 500,000,000 |
| PERMATA | `va_permata` | IDR | N/A | T+1 | 1 | 500,000,000 |
| **Channel** | Code | **Currency** | **Refund** | **Settlement** | Min Amount | Max Amount |
| :---------- | -------- | :----------- | :--------- | :------------- | :--------- | ---------- |
| SCB | `va_scb` | THB | N/A | T+1 | 20 | 700,000 |
## Payment Flow
```mermaid theme={null}
sequenceDiagram
participant Customer
participant Merchant
participant Monxa
participant VA as VA Provider (Bank)
autonumber
Customer ->> Merchant: Select Virtual Account
Merchant ->> Monxa: Create VA charge (amount, expiry)
Monxa ->> VA: Request VA issuance
VA ->> Monxa: Return VA details (account no, bank, expiry)
Monxa ->> Merchant: Return VA info + instructions
Merchant ->> Customer: Show VA account number & payment instructions
Customer ->> VA: Transfers funds via ATM / mobile banking
VA ->> Monxa: Notify credit received
Monxa ->> Merchant: Webhook: charge.succeeded
Monxa ->> Merchant: Settle funds into balance
Merchant ->> Customer: Show success confirmation
```
### Step 1: Create a Charge
**Endpoint: POST v1/charges**
```bash theme={null}
curl -X POST https://api.monxa.co/v1/charges \
-H "Authorization: Bearer sk_test_***" \
-H "Content-Type: application/json" \
-d '{
"amount": 250000,
"currency": "IDR",
"payment_method": "virtual_account",
"va": {
"bank_code": "BCA",
"account_type": "dynamic",
"amount_type": "exact",
"expires_at": "2025-10-15T23:59:59Z"
},
"metadata": { "invoice_id": "INV-10092" }
}'
```
```json theme={null}
{
"id": "ch_001",
"object": "charge",
"status": "PENDING",
"amount": 250000,
"currency": "IDR",
"payment_method": "virtual_account",
"va": {
"bank_code": "BCA",
"account_number": "1234567890123",
"account_name": "MONXA COLLECTION",
"expires_at": "2025-10-15T23:59:59Z",
"instructions": [
"Open BCA mobile app or ATM.",
"Choose Virtual Account transfer.",
"Enter account number: 1234567890123",
"Confirm amount: 250,000 IDR"
]
}
}
```
### Step 2: Display VA Information
Once the charge is created, show the returned **bank name, account number, expiry date, and instructions** to the customer.
This allows the customer to transfer funds using their preferred channel:
* ATM
* Mobile banking app
* Internet banking
Make sure to clearly show the **exact amount** if you are using a **closed/exact VA**.
### Step 3: Customer Transfers Funds
The customer proceeds to their banking channel and makes a transfer to the VA account number provided.
* For **dynamic/exact VAs**, the amount must match exactly.
* For **static/open VAs**, any incoming payment is accepted and must be reconciled against the customer/order.
The bank / VA provider will notify Monxa once funds are received.
### Step 4: Handle Webhooks & Update Payment Status
When the VA provider confirms the credit, Monxa updates the charge status and sends a **webhook notification** to your server.
* Typical webhook events:
* `charge.succeeded` → funds received successfully
* `charge.expired` → VA expired without payment
Your system should always rely on Monxa webhooks for final confirmation, then update the order / payment status shown to the customer.
| **Parameter** | **Description** | **Example Value** |
| :------------------- | :------------------------------------------------------------------------------- | :----------------------------- |
| `payment_id` | Unique identifier of the payment. | `pay_1234567890` |
| `payment_request_id` | Unique identifier of the payment request. | `req_0987654321` |
| `phone` | Buyer’s phone number. | `+6591234567` |
| `amount` | Amount related to the payment. | `100.00` |
| `currency` | Currency of the payment. | `SGD` |
| `status` | Payment status (`completed` / `failed`). | `completed` |
| `reference_number` | Custom reference number mapped during payment request creation. | `ORDER12345` |
| `hmac` | Message Authentication Code (MAC) of this webhook request (used for validation). | `a1b2c3d4e5f67890abcdef123456` |
## Refunds / Reversal
Unlike cards or wallets, **Virtual Account payments are bank transfers**. Because they are **push-based payments** initiated by the customer, **refunds or reversals cannot be processed automatically through Monxa**.
* Once a customer transfers funds into the VA, the transaction is **final and irreversible** via the API.
* If a refund is required (e.g., order cancellation, overpayment), the merchant must arrange a **manual bank transfer** back to the customer’s account outside of Monxa’s system.
* Monxa will still provide full **reporting, settlement, and reconciliation data** to help you identify the payment, but **no automated payout or refund request** is available.
**Important**: Always inform customers clearly that payments made via Virtual Accounts are non-reversible. If you wish to offer refunds, set up an offline/manual refund policy (e.g., customer provides bank details and you process a transfer).