QR Code Payments
A QR Code payment lets the customer scan a code — on a counter screen, invoice, poster or in a remote conversation — and pay with MULTICAIXA Express. You create a charge, GPO returns its QR Code as an image, and IZI Pay notifies your backend once the payment is accepted.
Building a mobile app?
Use a Deeplink instead: it is the same QR Code Payment, opened directly in MULTICAIXA Express without scanning.
QR Code types
STATICReusable or parametrised code, for example printed on a poster or invoice.Limit it with maxTransactions and endDate.DYNAMICA code for one specific charge, generated at checkout.maxTransactions and endDate are ignored.Integration flow
Create a QR Code
http
json
| Field | Required | Description |
|---|---|---|
amount | Yes | Charge amount, ≥ 1. |
posId | Yes | Terminal associated with the merchant. |
config.viewType | Yes | QR_CODE. |
config.type | Yes | STATIC or DYNAMIC. |
config.reference | Recommended | Your order or invoice reference — keep it to match the payment notification. |
config.size | No | Size of the QR image, for example MEDIUM. |
config.description | No | Description of the charge. |
config.maxTransactions | No | Maximum payments accepted by a STATIC code. |
config.endDate | No | Expiry of a STATIC code (ISO 8601). |
config.minAmount | No | Optional minimum amount. 0 is treated as not set. |
notify.mobile / notify.email | No | Optional customer notifications. |
GPO replaces any notify.callbackUrl you send with the callback configured by IZI Pay. Payment notifications are always delivered to the merchant callback set up with IZI Pay.
Response
On success the body is the QR Code itself, as image/png — not JSON. Show it to the customer as-is:
bash
Browser
Errors are returned as JSON with message and details (400 if the charge was rejected, 500 if the charge or image failed).
Call GPO from your backend
Never put the GPO access token in a browser or mobile app. Your backend creates the charge and streams the PNG to the client.
Show the QR Code again
If you know the chargeId (returned by deeplink charges), fetch the image again with Get QR Code image:
http
Payment confirmation
Displaying or scanning the QR Code does not confirm payment. After an accepted payment, IZI Pay forwards the transaction JSON to your merchant callback with the Access-Key you configured:
json
- Validate the
Access-Keyheader. - Use the transaction
idfor duplicate detection — store it, you need it for refunds. - Confirm
statusisACCEPTED. - Match the payment to your order and process it idempotently.
- Return a successful HTTP response.
The full notification format is described in Deeplink → Backend payment confirmation.
Refund a QR Code payment
http
paymentIdis the transactionidfrom the payment notification.amountmust be equal to or lower than the charge amount; otherwise400 Refund amount exceeds charge amount.- A payment can be refunded once; a second attempt returns
404. supervisorIdis the supervisor of the terminal — seesupervisorIdin Get terminal.- The response is
200with the refund transactionid. The refund was accepted whenerrorCodeanderrorTypeare empty.