> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/platform/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/platform/english/admin/settings/default-fronted-template.md).

# Default Fronted Template

This article explains how to define the default appearance of your new merchants’ payment pages and emails.

To access the settings for the look & feel of your merchants’ payment pages and emails, navigate to **Settings > Default Frontend Template** in the platform administration.

When a new merchant registers on your platform, the settings defined under **Default Frontend Template** are applied by default to the merchant’s [Look & Feel](https://docs.payrexx.com/merchant/english/account/settings/look-and-feel). Merchants can then make individual customizations if desired.

## Defining the Default Frontend Template

The following settings can be configured in the template:

<div align="left"><figure><img src="https://13947520-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McKWr2N1ZENCggMlAH5%2Fuploads%2FcNbODnYGyFycHhd4kToR%2Fimage.png?alt=media&amp;token=430d51d3-a026-4bf4-a9ca-2b8662741142" alt=""><figcaption><p>Setting the default logo, color, and font settings for new merchants</p></figcaption></figure></div>

#### 1. Logo shape

Define whether the logo should be square, rectangular, or round.

#### 2. Upload logo

Upload your desired logo.

#### 3. Logo background color

Specify if the logo should have a background and select the background color if needed.

#### 4. Logo border color

Specify if the logo should have a border and select the border color if needed.

#### 5. Background

Set the background for the payment pages. You can either define a color or upload an image to be used as the background.

#### 6. Background header

For the header section of the payment pages, you can also set a color or upload an image. Additionally, it is possible to opt for no background.

#### 7. Colors

In this section, you can define the colors for texts, links, and buttons on the payment pages. A separate text color can be selected for the [Terminal](https://docs.payrexx.com/merchant/english/account/tools/terminal).

#### 8. Font and size

Choose the font and font size in which texts should be displayed on the payment pages.

#### 9. Use individual email logo

If this checkbox is not selected, the logo uploaded under point 2 will be used in system-generated emails. If desired, you can select the checkbox and upload a different logo to be used exclusively in emails.

#### 10. Email background color header

Set a color for the header section of emails.

#### 11. Main background

For the Terminal, a separate background can be defined, different from the other payment pages. You can choose an image, a color, or a gradient. If two different colors are set in Gradient Color 1 and Gradient Color 2, they will be displayed as a gradient. To avoid a gradient, select the same color in both fields.


---

# 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/platform/english/admin/settings/default-fronted-template.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.
