QR Code Callback - Static QR Code

Use this callback as the primary real-time payment notification for Static QR Code. Static QR Code 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, QR Code id, and merchant information.
• Treat callbacks as idempotent because retries can happen.
• Store paidAt, amount, feeAmount, merchant, and merchantNmid for reconciliation.
• 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.
• 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:

Code
{
  "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:

Code
{
  "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 QR Code",
      "issuerName": "issuerName"
    }
  }
}

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