QRIS

QRIS (Quick Response Code Indonesian Standard) is a unified QR code system regulated by Bank Indonesia, enabling merchants to accept payments through a single QR code from all supported Indonesian payment providers.

Transaction Limits & Settlement Time

QRIS supports payments ranging from IDR 1,000 to IDR 10,000,000 per transaction.

Minimum Amount	Maximum Amount	Settlement
IDR 1.000	IDR 10.000.000	D+1, excluding weekends (Saturday–Sunday) and public holidays

Settlement Time: Refers to the time it takes for funds to appear in your Brick account balance after the customer completes a QRIS payment.

QRIS Types

Brick supports two types of QRIS, each tailored to different business needs:

1. Dynamic QR Code

• Contains a predefined amount set at the time of generation.
• Ideal for point-of-sale systems, e-commerce checkout, and real-time billing.
• Can only be used once—QR code expires after payment or timeout.
• Requires API integration to generate in real time.

Benefits:

• Reduces manual errors
• Enables seamless order-based payment tracking

🚧

Dynamic QRIS is generated via API only.

2. Static QR Codes

• A reusable QR code that allows multiple payments with variable amounts.
• Users scan the same code and enter their desired payment amount.
• Generated once via the Brick dashboard.
• Static QR codes never expire.

Use Cases:

• Donations
• Physical store counters
• General-purpose or open-ended payments

QRIS Transaction Statuses

QRIS transactions go through several statuses throughout their lifecycle:

Status	Description
PROCESSING	The QRIS has been created and is awaiting payment.
PAID	The customer has completed the payment.
COMPLETED	Funds have been successfully settled into your Brick account.
EXPIRED	The QR code expired before payment was made.
CANCELLED	Once any transactions / QRIS gets canceled.

---

Customer Information Parameter

Brick now supports an optional customerInformation object in the QRIS request payload. This parameter allows clients to attach payer identification details to a QRIS transaction, making it easier to trace and verify who made a specific payment.

Parameter Structure

JSON

"customerInformation": {
  "customerName": "Customer QRIS",
  "issuerName": "OTTOCASH"
}

Field Descriptions

Field	Type	Description
customerName	string	The name of the customer who made the QRIS payment.
issuerName	string	The name of the issuer or payment provider associated with the customer

Use Case

This feature is useful for clients who need to match and verify which payer a QRIS transaction originated from. By including customerInformation in the request, you can:

• Cross-reference incoming QRIS payments with your own customer database.
• Identify the issuer/wallet provider used during payment.
• Improve reconciliation accuracy in multi-customer or high-volume environments.

Example Scenario

A platform processes QRIS payments on behalf of multiple end-users. By passing customerInformation, the platform can link each incoming payment to the specific customer who initiated it — even before the callback is received — and reconcile records more reliably.

How to Enable This Feature

🔔

This is an optional add-on feature and is not enabled by default.

If you are interested in using the customerInformation parameter, please contact the Brick Business Team for further information and activation.