Brick API Documentation
Brick
Brick API

QR Code Dynamic

Server

Create, test, and check dynamic QRIS QR Codes for customer payments. Dynamic QR Codes are generated per transaction and should be reconciled through callbacks or status inquiry.


Generate Dynamic QR Code

POST
https://sandbox.onebrick.io
/v2/payments/gs/qris/dynamic
publicAccessToken (header)

Create a dynamic QRIS QR Code for a specific payment amount and reference ID. Use this endpoint when every customer transaction needs a unique QR payload for payment collection. The response includes QR data that can be rendered in your checkout flow, while final payment state should be confirmed through callbacks or the dynamic QR status endpoint.

Generate Dynamic QR Code › Request Body

referenceId
​string · required

Unique reference of Transactions from client side(Maximum length of 25 characters)

amount
​integer · int32 · required

Amount that clients wants to transfer

validityPeriod
​string

Minimum 600 seconds (10 minutes), maximum 86,400 seconds (24 hours) from the creation time. If not set, the default value will be 86,400 seconds (24 hours)

Generate Dynamic QR Code › Responses

200

status
​integer
Default: 0
​object
​object
error
​

Status for Dynamic QR Code

GET
https://sandbox.onebrick.io
/v2/payments/gs/qris/dynamic/{referenceId}
publicAccessToken (header)

Check the latest status of a dynamic QRIS transaction by reference ID. Use this endpoint when your system needs to confirm whether a QR payment is still processing, paid, expired, or unresolved. It complements callbacks and is useful for reconciliation jobs, customer support checks, and payment confirmation screens.

Status for Dynamic QR Code › path Parameters

referenceId
​string · required

Unique referenceId of Transactions

Status for Dynamic QR Code › Responses

200

status
​integer
Default: 0
​object
​object
error
​

QR Code Testing in Sandbox

POST
https://sandbox.onebrick.io
/v2/payments/gs/qris/update-status-sandbox
publicAccessToken (header)

Simulate QRIS payment status changes in the sandbox environment so your team can test callback handling and reconciliation before production. Use this endpoint after generating a sandbox dynamic QR Code to move the transaction into a desired test state. Do not use it for production payments or live customer transactions.

QR Code Testing in Sandbox › Request Body

referenceId
​string · required

Unique referenceId of Transactions

status
​string · required

The status that want to be achieved (PAID/COMPLETED)

Default: PAID/COMPLETED

QR Code Testing in Sandbox › Responses

200

status
​integer
Default: 0
data
​string
​object
error
​