> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/guides/merchant-portal/accept-payments-without-integration/payment-links-and-qr-codes.md).

# Payment Links and QR Codes

**Payment Links** allow you to accept payments directly from the SEB Merchant Portal without building your own checkout integration.

Create a payment request for a selected shop and provide it to your customer as a:

* **Payment link** – copy and share a secure payment URL.
* **QR code** – generate a QR code that customers can scan.
* **Payment button** – generate customizable HTML for a payment button.

All three options represent the **same Payment Link** and direct the customer to **Hosted Checkout**, where they can complete the payment using the payment methods available for the selected shop.

Payment Links are useful for individual payment requests, email or messaging-based sales, customer service-assisted payments, physical locations, QR code payments, and other cases where a dedicated checkout integration is not required.

The functionality available to you depends on your Merchant Agreement, shop configuration, enabled services, and user permissions.

***

### Access Payment Links

In the Merchant Portal, use the left navigation panel:

1. Expand **Pay by link**.
2. Select **Payment links / QR codes**.

The **Payment links** page displays your existing Payment Links and provides access to saved templates and the option to create a new Payment Link.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FP5HNoCi0WZUwy1UKiZoh%2FScreenshot%202026-08-18%20at%2017.33.21.png?alt=media&amp;token=14de2f69-b8da-4c96-af10-ce935aafe9fc" alt=""><figcaption></figcaption></figure>

From this page you can:

* Create a Payment Link.
* Search and filter existing Payment Links.
* Review link status and expiration.
* Open Payment Link details.
* Copy and share payment links.
* Generate QR codes and payment buttons.
* Save and use templates.
* Duplicate, deactivate, or delete existing Payment Links.
* Download Payment Link information, where available.

***

## Create a Payment Link

Select **Create payment link** and choose the shop that will process the payment.

Configure the payment request using the options applicable to your payment scenario.

### Payment Details

Configure the basic payment information:

* **Shop** – Select the shop that will process the payment. The selected shop determines the payment methods and services available to the customer.
* **Payment description** – Enter a clear description that helps the customer understand what the payment is for.
* **Pre-authorize payment** – Where applicable, authorize an eligible Card payment first and capture it separately later.
* **Tax payer ID** – Where required, request a Tax payer ID from the customer during checkout.

{% hint style="info" %}
If you manage multiple shops, verify that the correct shop is selected before creating the Payment Link.
{% endhint %}

***

### Amount and Currency

Select the payment currency and choose how the amount is determined.

#### Fixed Amount

Select **Amount** and enter the amount the customer must pay.

This is normally suitable for a specific order or payment request where the amount is already known.

#### Customer-Defined Amount

Select **Allow client to set amount** when the customer should enter the payment amount during checkout.

Where applicable, you can define a:

* Minimum amount.
* Maximum amount.

***

### Link Type and Validity

Choose how the Payment Link can be used.

#### One-Time Link

A **one-time link** is intended for a single successful payment.

Use this option for individual orders or customer-specific payment requests.

#### Reusable Link

A **reusable link** can accept multiple payments.

Use this option only when multiple payments through the same Payment Link are intentionally required.

#### Validity

Set the date until which the Payment Link should remain available or, where appropriate, select **No expiration**.

{% hint style="warning" %}
For individual customer orders, use a one-time link where appropriate. Use reusable or non-expiring links only where there is a clear business need.
{% endhint %}

***

### References

Use the available reference fields to associate payments with your own business records.

* **Order Nr** – Your order number or another order-related reference.
* **Merchant Reference Nr** – Your internal reference for identifying or reconciling the payment.

Use references consistently to make it easier to match Payment Link transactions with your own records.

***

### Customer Details

Choose how customer information should be handled.

#### Enter Customer Details

Use this option when you already know the customer's information.

Depending on the available fields, you can provide:

* Full name.
* Email address.
* Phone number.

Where available, select **Notify customer** to send the payment request using the provided customer contact information.

#### Customer Details Required at Checkout

Use this option when the customer should provide the required information during Hosted Checkout.

#### No Customer Details

Use this option when customer information is not required for the payment request.

You can also select the **Language** used for the customer-facing payment journey.

***

### Additional Fields

Where enabled, you can add [**Additional Fields**](/guides/merchant-portal/accept-payments-without-integration/additional-fields.md) to collect information specific to your business process.

Depending on the field configuration, a value can be:

* Provided when you create the Payment Link.
* Requested from the customer during checkout.
* Optional or mandatory.

See [**Additional Fields**](/guides/merchant-portal/accept-payments-without-integration/additional-fields.md) for detailed configuration instructions.

***

### Preview the Payment Request

A preview is displayed while you configure the Payment Link.

Use the **mobile** and **desktop** preview controls to review how the payment request will appear to the customer, including:

* Shop information.
* Amount and currency.
* Requested customer information.
* Additional Fields.
* Available payment methods.
* Hosted Checkout presentation.

The payment methods displayed depend on the configuration of the selected shop.

***

### Use a Saved Template

If you frequently create similar Payment Links, you can save the configuration as a template.

Select **Save as template** when creating a Payment Link, or save an existing Payment Link as a template from the Payment Links list.

When creating another Payment Link, select **Prefill from template** to reuse the saved configuration.

{% hint style="info" %}
Always review prefilled values before creating a new Payment Link. Amounts, references, customer information, validity, and other details may need to be updated.
{% endhint %}

***

### Create the Payment Link

When the configuration is complete:

1. Review the selected shop and payment information.
2. Review the customer preview.
3. Select **Create Payment link**.

The Payment Link is created and becomes available in the **Payment links** list.

***

## Share a Payment Link

Open the created Payment Link to choose how you want to provide the payment request to your customer.

The Payment Link details provide three options:

* **Details**
* **QR code**
* **Button**

{% hint style="info" %}
The URL, QR code, and payment button are different ways of providing the **same Payment Link**. They do not create separate payment requests.
{% endhint %}

***

### Share the URL

Select **Copy payment link** to copy the generated secure payment URL.

You can share the URL through an appropriate customer communication channel, such as email, SMS, messaging applications, or your own website.

Do not manually modify the generated payment URL.

***

### QR Code

Open the **QR code** tab to generate a QR code for the Payment Link.

Customers can scan the QR code with a compatible mobile device and continue to Hosted Checkout.

Where available, you can customize elements such as:

* Text.
* Font.
* Text colour.
* Frame colour and shape.
* Shop logo or branding.

Use the preview to review the QR code and select **Save and copy or Save and Download** when ready.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2Fd1xtikA9i2OMAoyNB3xJ%2Fblured%202.jpg?alt=media&amp;token=f2caf36f-07ca-4fbe-a3b1-7385ffb24b11" alt=""><figcaption></figcaption></figure>

***

### Payment Button

Open the **Button** tab to generate a payment button linked to the Payment Link.

Depending on the available options, you can customize:

* Button text.
* Font.
* Text capitalization.
* Text colour.
* Button colour.
* Button size.
* Button shape.

Select **Save and copy as HTML** to copy the generated button code.

{% hint style="info" %}
The Merchant Portal preview shows the configured button. Its exact appearance may vary depending on the environment where the generated HTML is placed.
{% endhint %}

***

## Track Payments

Open an existing Payment Link and select **Details** to review its configuration and associated payments.

Depending on the configuration, you can review information such as:

* Amount and currency.
* Payment description.
* Authorization type.
* Link type and validity.
* Order and merchant references.
* Customer details.
* Checkout language.

The **Orders paid with this link** section displays payments associated with the Payment Link.

For each payment, available information may include:

* Date and time.
* Customer.
* Amount.
* Currency.
* Payment status.

Where available, select **Open orders** to review the corresponding transactions in **Orders**.

For reusable Payment Links, multiple payments may be associated with the same link.

{% hint style="warning" %}
**Payment Link status and payment status are different.**

An **Active** Payment Link means that the link is available for use. It does not mean that the customer has completed a payment.

Always verify the associated **payment status** before delivering goods or services.
{% endhint %}

***

## Manage Payment Links

Existing Payment Links can be managed directly from the **Payment links** list.

Open the **More actions** menu for the required Payment Link.

Available actions include:

#### Open Details

Review the Payment Link configuration, generated URL, QR code, payment button, and associated payments.

#### Save as Template

Save the existing configuration as a reusable template for future Payment Links.

#### Deactivate

Make an active Payment Link unavailable for new payments.

Deactivating the link does not change payments that have already been completed through it.

#### Duplicate Payment Link

Create a new Payment Link based on the configuration of an existing one.

Review and update the amount, references, customer information, validity, and other applicable settings before creating the new link.

The duplicated Payment Link receives its own payment URL.

#### Delete

Remove a Payment Link that is no longer required.

{% hint style="warning" %}
Review the Payment Link and any associated payment activity before deleting it.

Deleting a Payment Link does not cancel, refund, or otherwise change payments that have already been processed through the link.
{% endhint %}

***

## Best Practices

When using Payment Links:

* Select the correct shop before creating a payment request.
* Use clear payment descriptions.
* Keep Order Nr and Merchant Reference Nr aligned with your own records.
* Use fixed amounts for specific orders where appropriate.
* Use one-time links for individual payment requests.
* Use reusable links only when multiple payments are intentionally expected.
* Set an appropriate expiration date.
* Use **No expiration** only where there is a clear business need.
* Collect only the customer information required for your business process.
* Review templates before reusing them.
* Share Payment Links through trusted communication channels.
* Do not manually modify generated URLs.
* Deactivate links that should no longer be available.
* Verify the final payment status before fulfilling an order.
* Use **Orders** to investigate individual transactions.

{% hint style="info" %}
Payments initiated through Payment Links are completed through **Hosted Checkout** and processed by the SEB Ecommerce Payment Gateway.

Payment Links provide a way to accept payments without requiring you to build your own checkout integration.
{% endhint %}

### Frequently Asked Questions

<details>

<summary>Do I need a website integration to use Payment Links?</summary>

No. Payment Links are created and managed in the Merchant Portal, and the customer pays on the Hosted Checkout page.

</details>

<details>

<summary>Can the same link be paid more than once?</summary>

Yes, if the link is configured as reusable and that option is enabled for your account. A single-use link closes after one successful payment.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ecommerce.seb.ee/guides/merchant-portal/accept-payments-without-integration/payment-links-and-qr-codes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
