Callback Ewallet Payment

Use this callback to update the matching transaction in your system, mark the payment as paid when appropriate, and trigger the next business process such as order fulfillment or balance update.

Callback Handling

• Match the callback to your transaction using referenceId and the Brick payment id.
• Store the callback payload before returning a successful response.
• 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 status update can be retried.
• Use the Ewallet status API if your callback endpoint was unavailable or your internal status is unclear.

Status Fields

Sample Callback for Ewallet 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": "WA_faef38eef5ce4178ad6508057b95f572",
    "type": "ewallet",
    "referenceId": "ref1234",
    "amount": 10000,
    "feeAmount": 44,
    "status": "COMPLETED",
    "createdAt": "2026-06-30T16:06:43.000+07:00",
    "paidAt": "2026-06-30T16:09:00.874+07:00",
    "metadata": {
      "orderId": "ORD-123",
      "customerId": "CUS-999"
    }
  }
}