QRIS Callback - Static QRIS

Brick sends this callback to your configured URL when a Static QRIS transaction status changes.

Brick sends this callback to your configured URL when a Static QRIS transaction status changes.

Use this callback as the primary real-time payment notification for Static QRIS. Static QRIS can be reused, so your system should rely on the callback data to identify the payment and reconcile it to the correct merchant or customer flow.

Callback Handling

• Match the callback using referenceId, QRIS id, and merchant information.
• Treat callbacks as idempotent because retries can happen.
• Store paidAt, amount, feeAmount, merchant, and merchantNmid for reconciliation.
• If customerInformation is enabled, store buyer and issuer details according to your own data handling policy.

This is a sample of the status update we send to your callback URL:

Callback Response - Paid

{
  "data": {
    "id": "QR_XXXX",
    "referenceId": "XXXX",
    "amount": 10000,
    "feeAmount": 70,
    "status": "PAID",
    "createdAt": "2024-03-13T14:12:25.000+07:00",
    "paidAt": "2024-03-13T14:12:26.212+07:00",
    "qrisType": "STATIC",
    "merchant": "merchant_name",
    "merchantNmid": "merchant_Nmid"
  }
}

This is a sample of the status update we send to your callback URL if customerInformation is enabled:

Callback Response - CustomerInformation

{
  "data": {
    "id": "QR_0a50018350f34cd4901c97e22cb1cfde",
    "referenceId": "1710323916255",
    "amount": 11000,
    "feeAmount": 77,
    "status": "PAID",
    "createdAt": "2024-03-13T16:58:37.000+07:00",
    "paidAt": "2024-03-13T23:58:58.000+07:00",
    "qrisType": "STATIC",
    "merchant": null,
    "merchantNmid": null,
    "customerInformation": {
      "customerName": "Customer QRIS",
      "issuerName": "issuerName"
    }
  }
}

Note: To get customerInformation, refer to the QRIS Overview docs or contact our Sales team.