> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/merchant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payrexx.com/merchant/english/account/settings/general-settings/multilingual-frontend.md). # Multilingual Frontend In this article, you will learn how to offer payment pages and all other content seen by your customers in different languages. Payment forms and all other content your customers see can be configured in multiple languages in Payrexx. You can offer them in the following 13 languages:


German 🇨🇭	Dutch 🇳🇱
German 🇦🇹 🇩🇪	Polish 🇵🇱
English 🇬🇧 🇺🇸	Turkish 🇹🇷
French 🇫🇷	Danish 🇩🇰
Italian 🇮🇹	Swedish 🇸🇪
Spanish 🇪🇸	Norwegian 🇳🇴
Portuguese 🇵🇹

{% hint style="info" %} Two versions of the German language are available in Payrexx: * German (CH): Written with double-S (ss) * German (DE): Written with the sharp S (ß)" {% endhint %} ## Default Settings To display the various payment pages in different languages, the multilingual frontend must first be activated. Navigate to your Payrexx account, go to **Settings > General Settings**, and scroll down to the "Languages" section. Check the box labeled "Enable multilingual frontend":

Activating the multilingual frontend in Payrexx

On the left side of the window, you will see the list of available languages. By clicking on a language, you can move it to the right side of the window to activate it:

1. In the example shown above, German (CH) and English are activated. 2. One of the activated languages can be set as the default language; in the example above, it is German (CH). ## Configuring the Tools Once the multilingual frontend is set up in Payrexx, the [e-commerce tools](/merchant/english/account/tools.md) and payment pages can be created in various languages. {% hint style="info" %} The following instructions describe how to set up a multilingual frontend using the [Pages](/merchant/english/account/tools/pages.md) tool as an example. The multilingual setup for other tools, such as [Paylink](/merchant/english/account/tools/paylink.md) or [Donation](/merchant/english/account/tools/donation.md), follows the same pattern. {% endhint %} * Navigate to the **Pages > Overview** in the main menu of Payrexx. * Click "Edit" on the desired page.

* Select the first tab, "Title and description", and click on "Multilingual" next to "Page title":

Creating a multilingual Pages shop in Payrexx

* You now have the option to enter the title of the payment page in the languages you defined in the [Default Settings](#default-settings) step:

Entering the page title in German (CH) and English

* If you want to enter the page content in various languages, simply click on "Multilingual" next to "Description." {% hint style="info" %} If the desired language is not visible in the Pages shop, you need to add it first under **Settings > General Settings > Languages**. Refer to the [Default Settings](#default-settings) section for instructions on how to do this. {% endhint %} * To test if the multilingual Pages shop meets your expectations, simply click the "View" button:

Previewing the multilingual Pages shop in Payrexx

--- # 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.payrexx.com/merchant/english/account/settings/general-settings/multilingual-frontend.md?ask=&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.