> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/interfaces/backoffice/secure-paygate/multiuse-links-qr-codes.md).
# Multiuse Links/QR codes
This section allows you to create payment links, alongside a QR code, that are valid for multiple payments, where the payer can choose the amount he/she wants to pay.
This can be helpful for simple donation sites or other use cases, where a full-blown webshop is too much, where the usage of single links for each order would not outweigh the effort necessary to create them, and/or where the payer proactively should engage in a payment without the merchant having to act beforehand.
### Overview
Similar to the regular Secure PayGate offers, you'll first see the overview, which'll provide you with a list of all links you have created so far. You can either decide to remove the link by clicking on Remove, edit an existing link, search for a link, or apply search filters to the selection, like the terminal, if you have multiple.
After removing a link, it is marked with the status "deleted". After 6 months, the link is permanently deleted and disappears from the list. Until then, a deleted link can be restored.
### Creating a new Link/QR code
By clicking on "Create" in the top right of the overview, you will open up the creation mask.
#### Creation Mask
While similar to the normal creation mask, multiuse links offer a reduced feature set of a normal Secure PayGate offer, due to some not being necessary in this scenario.
The mask is divided into two sections:
#### Offer Details
This section covers the details of the offer itself.
**(1) Sales description:** Here you can leave a short description, which will be displayed inside the [transaction details](/home/interfaces/backoffice/transactions/journal-details.md) once a transaction is made, but also on the Saferpay Payment Page for your customer. This text can be anything, like an order number or a short description of what the customer is buying.
**(2) Terminal:** A terminal is where all your payment methods and their attributes (currencies, account number, other features, like 3D Secure) are connected to. Usually, only one Secure PayGate terminal is activated, but you can have more if you wish. This can be useful if you want to split offers between countries and/or the revenue to other bank accounts, as there usually can only be one bank account per payment method and only one type of payment method per terminal.
You will be presented with a full list of terminals. However, you may also search for a given terminal and its description/name, which you can set under [Settings => Terminals](/home/interfaces/backoffice/settings.md#payment-means-terminals), making it easier to keep track of your terminals.
**(3) Currency:** Here you can set the desired currency.
{% hint style="warning" %}
Note that the currency dropdown will only display the currencies that are activated on that terminal.
Furthermore, while a payment method may be generally available, it will not be displayed to your customer if the selected currency is not activated. You can check this under [Settings => Terminals](/home/interfaces/backoffice/settings.md#payment-means-terminals).
{% endhint %}
**(4) Amount Type:** Set a fixed or variable payment amount. If this option is set to variable, the payer can set the payment amount by themselves. If set to fixed, the merchant will decide on the amount.
**(5) Authorization Type:** The authorization type dictates how Saferpay should proceed once the transaction itself has been successful. There are three different types to choose from:
* **Authorization:** The transaction will be authorized, but not captured. The transaction must then be reviewed and [captured manually](/home/interfaces/backoffice/transactions.md#capturing-or-cancelling) for the money to be transferred to the merchant's bank account.
* **Pre-authorization (Visa/Mastercard only):** Each authorization has a minimum time limit in which the payout of the authorized amount is guaranteed to be transferred upon capture. Usually, this time frame is 10 days; however, a pre-authorization will extend this to 30 days if desired.
* **Automatic capture:** The transaction is automatically captured, initiating the money flow right away.
**(6) Condition:** Controls the [3D Secure](/home/integration-guide/general-information/3d-secure.md) liability shift behavior. There are three settings to choose from:
* **No Condition:** The transaction is accepted, no matter the status of the liability shift. **This is generally not recommended.**
* **Only with liability shift:** The transaction is only accepted, if liability shift has been granted by the cardholder's bank.
* **Only with liability shift and 3-D Secure challenge:** The transaction is only accepted if liability shift has not only been granted, but the cardholder has also been fully authenticated. This may grant additional security for the merchant, but can have an impact on the conversion rate.
**(7) Merchant Notification:** Saferpay will send a confirmation e-mail to the provided merchant e-mail address(es) once a payment has been made.
**(8) Reference number prefix:** If the reference number of the transactions is to be used for reconciliation matching, a prefix can be specified here, which is added before the automatically generated reference number of each transaction.
**(9) Custom field:** This option can be used to display an additional input field to the cardholder during payment. It can be used to capture additional data for customer identification, like:
* Invoice number
* License plate
* Booking Reference
* etc.
Please [contact us](/home/integration-guide/support.md) if you are in need of other options.
**(10) QR code:** This is your QR code. Upon scanning, your customer is redirected to the Saferpay Payment Page to perform the payment.
{% hint style="info" %}
You can download the QR code as a .png, by simply clicking on it!
{% endhint %}
**(11) Flyer:** You can also download a prefabricated flyer and print it if you want to.
**(12) Payment link:** This is your payment link that the customer will be redirected to. You can either use the Saferpay provided mailing option or copy the link so you can insert it into your own email application.
#### Payment Page Configuration
This section concerns all the settings of the Payment Page itself during checkout:
**(1) Customer email configuration:** Determines whether the payer can/must enter his/her e-mail address on the payment page.
**(2) Payment Page configuration:** Select a[ Payment Page configuration](/home/interfaces/backoffice/settings/payment-page-configuration.md), if available, allowing you to adjust the Payment Page look and feel to your corporate design.
**(3) Billing/Delivery address needed:** Specify whether the payer must enter the billing/delivery address.
### On the Payment Page
While this also uses the Saferpay Payment Page, there is one major addition to the overall payment flow that needs attention.
As previously mentioned, the amount itself is defined by the payer itself, so before the payment method can be selected, the payment page will display a form that accepts the amount the payer wants to pay.
Additionally, the payer's e-mail is captured, which is used to send a payment confirmation e-mail to. It is also displayed in the [transaction details](/home/interfaces/backoffice/transactions/journal-details.md#customer-address) under **Billing Address**, so you may contact your customer.
## Journal
Due to the nature of them being able to be used multiple times, the Multiuse Links do have their own transaction journal, which lists all transactions that have been done through this particular link.
You can access the journal of a particular link by clicking on **`Transactions`** in the link overview.
This will lead you to the journal page of this specific link, showing you all transactions, that have been made through this MultiUse link.
There, you can click on **`Open in Journal`**, which will redirect you to the [details page of the main transaction journal](/home/interfaces/backoffice/transactions/journal-details.md), giving you more details on a specific transaction.
## Security concerns
Due to their nature, QR codes may be convenient, but they also are simple to misuse for fraud by simply replacing the code with a manipulated one that leads to a fake transaction page to gather customer or even payment details.
When using the Saferpay Multiuse links, please make sure that access to them is restricted and that they cannot be easily replaced or otherwise manipulated by fraudsters.
Hang them up in a way that they still can be scanned, but also that a potential customer can see that someone may have put a sticker over the real code, which is a very common practice.
One way could be to hang them up in a small box behind glass and far away enough so that a sticker would easily be noticed.
Also, please check on your flyers at regular intervals and remove any manipulation attempts that may have happened.
---
# 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.saferpay.com/home/interfaces/backoffice/secure-paygate/multiuse-links-qr-codes.md?ask=&goal=
```
`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.