Callback E-wallet Payment

Brick sends this callback to your configured URL when an e-wallet payment status changes.

Brick sends this callback to your configured URL when an e-wallet payment status changes.

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.
• Make your handler idempotent because the same status update can be retried.
• Use the e-wallet status API if your callback endpoint was unavailable or your internal status is unclear.

Status Fields

Field	Description
id	Brick payment identifier.
referenceId	Your transaction reference.
amount	Payment amount.
feeAmount	Fee amount applied to the payment.
status	Latest e-wallet payment status.
paidAt	Timestamp when the payment was paid, when available.

Sample Callback for E-wallet 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:

Callback Response - Paid

{
  "data": {
    "id": "WA_7d6f21d3e170424ea1ac1a79996f27c7",
    "referenceId": "Test-Kevin-67",
    "amount": 10000,
		"feeAmount": 1000,
    "status": "PAID",
    "createdAt": "2024-09-13T10:16:03.000+07:00",
    "paidAt": "2024-09-13T10:47:34.557+07:00"
  }
}