> For the complete documentation index, see [llms.txt](https://docs.maibmerchants.md/mia-qr-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maibmerchants.md/mia-qr-api/en/overview/mia-qr-types.md).

# MIA QR Types

Within the QR MIA API, QR codes can be generated in several formats, depending on the usage context and the required level of transaction detail.

* **Static QR** – A predefined QR code with fixed data (no amount or personalized details). It is suitable for recurring payments where the amount is manually entered by the customer (e.g., donations, flexible contributions).
* **Dynamic QR** – A one-time generated code that includes specific transaction details such as the amount, merchant ID, and optionally customer information. It is ideal for cases where accurate and secure payment tracking is required.
* **Hybrid QR** – Combines features of both static and dynamic codes. It may be used for both one-time and recurring payments, where some data remains constant and other data is transaction-specific.

The choice of QR code type should be based on the operational purpose and expected user behavior.

<table><thead><tr><th width="164">Feature</th><th>Static QR</th><th>Dynamic QR</th><th>Hybrid QR</th></tr></thead><tbody><tr><td><strong>Reusable</strong></td><td>Yes</td><td>No</td><td>Yes</td></tr><tr><td><strong>Can be modified later</strong></td><td>Yes</td><td>No</td><td>Yes – via the extension endpoint</td></tr><tr><td><strong>Placement on static media</strong></td><td>Yes (stickers, posters)</td><td>No (one-time use)</td><td>Yes</td></tr><tr><td><strong>Amount type</strong></td><td>Fixed, Controlled, Free</td><td>Fixed, Controlled</td><td>Fixed, Controlled</td></tr><tr><td><strong>Allows variable amounts</strong></td><td>Yes,  <code>Controlled</code> or <code>Free</code></td><td>Yes,  <code>Controlled</code> or <code>Free</code></td><td>Yes,  <code>Controlled</code> or <code>Free</code></td></tr><tr><td><strong>Configurable validity</strong></td><td>No</td><td>Yes</td><td>Yes (possibility via extension)</td></tr><tr><td><strong>Callback URL</strong></td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td><strong>Suitable for</strong></td><td>Universal QR codes with open payment</td><td>One-time orders or fixed payments</td><td>One-time orders or fixed payments with QR code placed on a static media</td></tr></tbody></table>

{% hint style="info" %}
The MIA API supports callback URLs for receiving payment status notifications.&#x20;

Redirect URLs *are not supported* in the current version of the MIA API and must not be sent in API requests.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.maibmerchants.md/mia-qr-api/en/overview/mia-qr-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.