Skip to main content
The Static QR Code Amount Configuration API lets integration partners control which payment amounts a customer sees after scanning a static QR code on the Mizaniya Pay platform. All amounts are in Algerian Dinars (DZD). You can attach a list of preset amounts to a QR code, make it expire at a specific time, and optionally clear the configuration after the first successful payment. Two simple POST endpoints manage the lifecycle of these configurations.

Attach configuration

Set amounts, expiration, and single-use behavior on a QR code.

Remove configuration

Clear the entire configuration from a QR code.

​
How it works

When a customer scans a QR code you configured, they are taken to the Mizaniya Pay payment platform. What they see next depends on how many amounts you attached.
  • Multiple amounts: the customer is presented with a list of preset DZD amounts and must choose one.
  • Single amount: no selection step appears. The platform shows the single preset amount directly.

​
Configuration modes

You can tailor each QR code to your business flow using three configuration modes. Calling /set-qr-config again for the same QR code token replaces the previous configuration entirely.

​
Endpoints

Both endpoints expect JSON request bodies and require the same authentication header.

​
Prerequisites

Before making API calls, retrieve the following values from the Mizaniya Partner Platform.
  • api_base_url: the root URL for all API requests in your environment
  • api_key: used in the x-api-key request header
  • token: the unique identifier of the static QR code you want to configure
Store your API key securely. Do not commit it to source control or expose it in client-side code.

​
Authentication

Every request must include the x-api-key header. A missing or invalid key returns 401 Unauthorized with a structured error body.
If you receive a 401 response, verify that the header name is exactly x-api-key and the value matches the key shown in the Partner Platform.

​
Response model overview

Responses follow one of several consistent envelope shapes. When handling errors, branch on the errorCode field instead of parsing message text.

​
Error code reference