> 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/additional-fields.md).

# Additional Fields

[**Additional Fields**](/features/additional-fields.md) allow you to collect additional information required for your business as part of a Payment Link and Hosted Checkout payment journey.

Create reusable Additional Fields in the Merchant Portal and then add them to Payment Links when the information is required.

For example, an Additional Field can be used when you need information related to the customer's order or your internal business process that is not included in the standard payment request.

Depending on the field configuration, the value can be provided when creating the Payment Link or requested from the customer during checkout.

***

### Access Additional Fields

In the Merchant Portal, use the left navigation panel:

1. Expand **Pay by link**.
2. Select **Additional fields**.

The **Additional fields** page displays the reusable fields available for your merchant account.

From this page you can:

* Create a new Additional Field.
* Search and filter existing fields.
* Review field configuration and status.
* Edit existing fields.
* Delete fields that are no longer required.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FvWWx2qYBP0OsAOgloUgt%2FScreenshot%202026-08-19%20at%2015.57.18.png?alt=media&amp;token=cf3abc32-3c12-408c-b42f-4cf4187cf521" alt=""><figcaption></figcaption></figure>

***

### How Additional Fields Work

Additional Fields are created and managed separately from individual Payment Links.

A typical flow is:

1. Create an Additional Field in the Merchant Portal.
2. Configure the field and its customer-facing presentation.
3. Save the field for future use.
4. Create a Payment Link.
5. Select the required Additional Field.
6. Provide the value or request it from the customer, depending on the applicable configuration.
7. The information is included in the Hosted Checkout payment journey.

Because Additional Fields are reusable, you do not need to create the same field separately for every Payment Link.

***

### Create an Additional Field

Select **Create new field** to create a reusable Additional Field.

Depending on the field configuration available in the Merchant Portal, Additional Fields support:

* Field name.
* Field type.
* Customer-facing display name.
* Text fields with minimum and maximum character validation.
* Customer-facing translations.
* Preview of the field presentation.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2Fw5UFD05hkxGBydV7CwDH%2Fimage.png?alt=media&amp;token=3a5371af-2b48-4cf8-86df-e0dc34a28a95" alt=""><figcaption></figcaption></figure>

Configure the field so that its purpose is clear both for your own administration and for customers when the field is displayed during checkout.

{% hint style="info" %}
Use a clear **Display name** because this information may be presented to customers as part of their payment journey.
{% endhint %}

***

### Customer-Facing Labels and Languages

Additional Fields support multilingual customer-facing labels.

Select **Languages and translations** to:

* Set the **default language**.
* Add translations for the languages available in Hosted Checkout.

The appropriate field name is displayed according to the customer's checkout language.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FFyuS02ppUPsXP9qx1nxy%2FScreenshot%202026-08-19%20at%2016.12.32.png?alt=media&amp;token=84f822b3-a1f9-4afd-b404-c031422afa19" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If a translation is not provided, the field name in the **default language** is displayed.

You are responsible for providing the required translations for your Additional Fields.
{% endhint %}

***

### Field Validation

For supported text fields, minimum and maximum character limits can be used to validate the information entered.

Configure validation according to the expected value and avoid unnecessarily restrictive rules that could prevent customers from completing checkout.

The applicable validation is applied when customer input is requested during the payment journey.

***

### Find an Additional Field

Use the filters on the **Additional fields** page to locate an existing field.

You can filter by:

* **Field name**
* **Field type**
* **Display name**
* **Status**

Select **Apply** to update the results.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2F3iRZhD8DtRvhRzOdtWrO%2FScreenshot%202026-08-19%20at%2016.17.24.png?alt=media&amp;token=1576558c-4243-48f6-8a1d-20827137fcb8" alt=""><figcaption></figcaption></figure>

Select **Clear** to remove the applied filters.

The list displays information about each field, including:

* Field name.
* Field type.
* Display name.
* Creation date.
* Current status.

***

### Use Additional Fields with Payment Links

After an Additional Field has been created, it can be associated with a Payment Link.

When creating a Payment Link, use the **Additional fields** section to select the required field.

One or more Additional Fields can be associated with a Payment Link where supported.

Depending on the applicable configuration, you can:

#### Provide the Value

Provide the value when creating the Payment Link.

Use this option when the information is already known and should be associated with the payment request.

#### Request the Value from the Customer

Request the customer to provide the value during Hosted Checkout.

Depending on the configuration, customer input can be optional or mandatory.

The configured customer-facing display name is shown to help the customer understand what information is required.

For information about creating the payment request, see [**Payment Links & QR Codes**](/guides/merchant-portal/accept-payments-without-integration/payment-links-and-qr-codes.md).

***

### Hosted Checkout

When customer input is requested, the Additional Field is presented as part of the **Hosted Checkout** payment journey.

The customer sees the configured display name and provides the requested value.

Where validation rules are configured, the entered value must satisfy those rules before the customer can continue.

Use the available preview when configuring the payment journey to verify how the field will appear to customers.

***

### Manage Additional Fields

Existing Additional Fields can be managed from the **Additional fields** page.

Open the **More actions** menu for the required field.

Available actions include:

#### Open Details

Select **Open details** to review the current field configuration.

#### Edit

Select **Edit** to update an existing field.

Before changing a reusable field, consider whether it is already used by existing Payment Links.

Changes to field definitions apply to future use and do not modify information already associated with historical transactions.

#### Delete

Select **Delete** when an Additional Field is no longer required.

{% hint style="warning" %}
Before deleting an Additional Field, verify that it is no longer required for new Payment Links or other payment requests.

Deleting or changing a field does not modify information already associated with completed transactions.
{% endhint %}

***

### Reuse Additional Fields

Additional Fields are designed to be reusable.

For example, if the same information is required for multiple Payment Links, create the field once and select it whenever you create the applicable payment request.

Reusing fields helps maintain consistent:

* Field definitions.
* Customer-facing labels.
* Validation rules.
* Translations.
* Checkout presentation.

***

### Best Practices

When using Additional Fields:

* Request only information required for your business process.
* Use clear customer-facing display names.
* Provide translations for the checkout languages you support.
* Configure validation appropriate to the expected information.
* Reuse existing fields instead of creating duplicate definitions.
* Preview customer-facing fields before using them.
* Review the impact before editing or deleting a reusable field.
* Do not use Additional Fields to collect payment-card data, authentication credentials, or other sensitive payment information.

{% hint style="warning" %}
**Do not use Additional Fields to collect card numbers, CVV/CVC values, passwords, authentication credentials, or other sensitive payment information.**

Additional Fields are intended for merchant-specific information required as part of your business and payment journey.
{% 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 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/additional-fields.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.