QRIS Dynamic Callback (SNAP)

Brick sends this callback to your configured QRIS SNAP callback URL when the transaction status changes.

Brick sends this callback to your configured QRIS SNAP callback URL when the transaction status changes.

Use the callback as the primary real-time notification for QRIS payment updates. Your system should persist the identifiers in the callback, update the matching order or transaction, and optionally confirm the latest status with the QRIS status API when reconciliation is needed.

Callback Handling

• Match the callback to your transaction using originalPartnerReferenceNo, originalReferenceNo, or the identifiers stored when the QRIS was generated.
• Treat duplicate callbacks as possible and make your handler idempotent.
• Return a successful response only after your system has stored the status update.
• Use the QRIS status endpoint if the callback is delayed or your internal state is unclear.

Sample Callback Payloads

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

Callback Response - Paid

{
   "originalReferenceNo":"",
   "originalPartnerReferenceNo":"",
   "transactionStatusDesc":"PAID",
   "amount":{
      "value":"10000.00",
      "currency":"IDR"
   },
   "latestTransactionStatus":"00",
   "additionalInfo":{
      "issuerName":"GOPAY",
      "paymentDate":"2024-11-15T14:28:41+07:00",
      "buyerReff":"",
      "terminalId":"A01",
      "username":"customer-name",
      "rrn":"123456789012"
   }
}

Callback Response - Expired

{
   "originalReferenceNo":"",
   "originalPartnerReferenceNo":"",
   "transactionStatusDesc":"EXPIRED",
   "amount":{
      "value":"10000.00",
      "currency":"IDR"
   },
   "latestTransactionStatus":"06"
}