> For the complete documentation index, see [llms.txt](https://developers.hyp.co.il/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.hyp.co.il/enterprise/changing-the-default-payment-page-appearance/templates.md).

# Payment Page Templates

Hyp Enterprise supports two main payment page templates that define the overall layout, user experience, and behavior of the payment page:

* **Hyp Basic**: The current default template, providing the existing payment page look and behavior. Most UI examples and instructions in this documentation use this template.
* **Hyp Standard**: A new template option that provides a different layout. Unlike *Hyp Basic*, which navigates to a separate full-screen view when a payment method (e.g., Google Pay) is selected, *Hyp Standard* keeps the payment method selector visible at the top of the page. This template currently **does not support** [Pay By Link](https://developers.hyp.co.il/enterprise/available-payment-options/pay-by-link.md) or [PCP](https://developers.hyp.co.il/enterprise/available-payment-options/physical-pinpad-terminal.md).

## Configuring templates

You can configure which template to use by setting a default template in the Hyp Console or by choosing a template on a per-request basis.

### Configuring the default in the Hyp Console

To set a default template that will be used on all payment pages unless [overridden per request](#choosing-a-template-per-request):

1. Open your Hyp Console.
2. In the sidebar, click **Merchant details**.
3. Expand the **Merchant settings** section.
4. Click **Gateway management settings**.

   <img src="https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-562509f3e9901e0aae02e294ad737d0ec3a1837a%2Flogos-navigation.png?alt=media" alt="Navigating the Hyp Console" width="75%">
5. Under **Gateway management settings**, open the **Payment Account Payment Management (MID)** tab.
6. Click the name of a merchant ID (MID) in the table. The default template is configured per MID, so you may need to repeat this and the following steps for each MID that you have.
7. In the **MPI account information** form, use the **Default PPS template** dropdown to set a default template:

   ![Selecting a default template](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-dd2537a796ef58a202ff1a301a514a42609f5fa0%2Fselect-default-template.png?alt=media)
8. Optionally, you can set different default templates for:
   * [Pay By Link](https://developers.hyp.co.il/enterprise/available-payment-options/pay-by-link.md): Use the **PPS template - Payment link J206** dropdown.
   * [Payment requests](https://developers.hyp.co.il/enterprise/available-payment-options/payment-request.md): Use the **PPS template - Payment link J306** dropdown.

Currently, the default template for all new terminals is *Hyp Basic*.

### Choosing a template per request

You can specify the template for a specific transaction by including the `template` property inside the `uiCustomData` object within `ppsJSONConfig`:

```json
{
  "uiCustomData": {
    "template": "hypstandard"
  }
}
```

The template specified in `ppsJSONConfig` overrides the default template selected for the MID that your request uses.

## Customization and `ppsJSONConfig`

Most [customization options](https://developers.hyp.co.il/enterprise/changing-the-default-payment-page-appearance/overview.md) available via `ppsJSONConfig` (such as custom logos, styles, and text) are expected to apply to both *Hyp Basic* and *Hyp Standard* templates.


---

# 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://developers.hyp.co.il/enterprise/changing-the-default-payment-page-appearance/templates.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.
