Brick API Documentation
Brick
Brick API

Open VA

Server

Generate and monitor reusable Open VA payments. Use these endpoints when customers can transfer flexible amounts to the same virtual account identifier and your system needs Open VA status reconciliation.


Status of Open VA

GET
https://sandbox.onebrick.io
/v2/payments/gs/va/open
publicAccessToken (header)

Check the latest payment status for an Open Virtual Account. Use this endpoint when callbacks are delayed, when support teams need to verify a payment, or when your reconciliation job needs to confirm the current VA state. Pass the required VA identifiers and use the response to update internal payment records.

Status of Open VA › query Parameters

vaId
​string · required

Unique id of virtual account ex: OP_xxxx

Status of Open VA › Responses

200

status
​integer
Default: 0
​object
​object
error
​

Generate Open VA

POST
https://sandbox.onebrick.io
/v2/payments/gs/va/open
publicAccessToken (header)

Generate an Open Virtual Account that can receive flexible payment amounts from a customer. Use Open VA when the payer can transfer varying amounts to the same VA identifier, such as wallet top-up or reusable account funding flows. Store the VA details returned by Brick and reconcile payments through callbacks or the Open VA status endpoint.

Generate Open VA › Request Body

bankShortCode
​string · required

Institution short code of the bank

Default: MANDIRI
referenceId
​string · required

Unique ID that is being generated by the client to track each VA generation (maximum 255 characters)

Default: test-VA-1
displayName
​string · required

Display name shown in the customer's payment platform (maximum 24 characters).

Default: PRODONLY

Generate Open VA › Responses

200

status
​integer
Default: 0
​object
​object
error
​