Callback Virtual Account

Brick sends this callback to your configured URL when a Virtual Account payment status changes.

Use this callback to update the matching VA transaction, reconcile the paid amount, and trigger fulfillment or balance update workflows in your system.

Callback Handling

• Match the callback using the Brick payment id, referenceId, and VA account number.
• Store the payment method details, including bank short code, account number, and display name.
• Return HTTP 200 only after your system has accepted the callback. Dashboard Test URL / Save & Test also requires a JSON ACK with the exact Brick test referenceId.
• Make your handler idempotent because the same callback can be retried.
• Use the VA status endpoint if the callback is delayed or your internal state is unclear.

Key Fields

Sample Callback for VA Payment Status Update:

When a payment status changes, we will send a status update to your callback URL. Below is an example of the payload:

Code
{
 "data": {
  "id": "OP_10f7044129d44d1e8b3f5d7d8347466b",
  "type": "payment",
  "attributes": {
   "referenceId": "canopy-1768903058380",
   "amount": "29999.00",
   "feeAmount": "5617",
   "status": "paid",
   "createdAt": "2026-01-20T16:57:40.000+07:00",
   "paymentMethod": {
    "paymentId": "PAY_87d2e2b840df041938e3894eff0c5844",
    "type": "virtual_bank_account",
    "instructions": {
     "bankShortCode": "BRI",
     "accountNo": "13950108036973309",
     "displayName": "PTQamiAwesomeautomation"
    }
   }
  }
 }
}