> 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/adding-business-logo-and-custom-images.md).

# Adding Business Logos and Custom Images

By default, the payment page contains the Hyp Enterprise logo in the header, but you can change it to show your business logo instead.

You can also provide additional images to be used on the payment page, such as a background image.

## Uploading images

In order to be able to use custom images as the logo or refer to them in your CSS, you need to upload them to Hyp's servers first:

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. In the list of MIDs, click the three-dot menu and select **Manage Logo**:

   ![Locating logo management settings](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-c381e71db85fae9e76021beb79bd744b6ba08cbb%2Flogos-manage-logo.png?alt=media)
7. Click **New** to open a form that lets you upload a new image (up to 1 MB).
8. Once the image has been uploaded, keep **Set as default** checked to make this image display as your logo by default on all payment pages. Disable this option if you want to only use the image as a logo when explicitly requested or if you want to use it for CSS customization.

   ![Image preview](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-d2e77c450011a80656f8779749ed6fa7a15d2e2c%2Flogos-preview.png?alt=media)
9. Click **Save**.
10. After verifying the image file, Hyp Console will display a success message along with a pre-generated code snippet where `businessLogoUrl` set to the new filename of the uploaded image.

    ![Image has been uploaded](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-ececea05389c9f3b741aced9d8623734cf5ad207%2Flogos-success.png?alt=media)
11. Click **Close**.

You will now get back to the list of images that indicates the filename of each, as well as which of the images is set as the default logo.

![List of images](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-74695a12ae4c6ac39dc2a3593a315ad1c78b26c9%2Flogos-list.png?alt=media)

Using the three-dot menu in each images's row, you can set it as the default logo or copy the code snippet to use in your payment page configuration.

<img src="https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-982c10baae5d2e2f4bb0030d882b48144660b6f2%2Flogos-context-menu.png?alt=media" alt="Commands in a context menu for an image" width="75%">

## Setting business logos

The image that you set as the default logo will be displayed on all your payment pages without additional configuration.

To override the default logo, set the `businessLogoUrl` property of the `uiCustomData` object to a file name of an uploaded non-default image file:

```json
<paymentPageData>
    <ppsJSONConfig>
    {
      "uiCustomData": {
        "businessLogoUrl": "non-default-logo.png"
      }
    }
</ppsJSONConfig>
</paymentPageData>
```

A logo overridden like this always takes precedence over the default logo configured in Hyp Console.

## Using uploaded images for CSS customization

You can reference uploaded images in your custom CSS to style other parts of the payment page.

To do this, add CSS directives that reference uploaded images inside the `customStyle` property of the `uiCustomData` object:

```json
<paymentPageData>
    <ppsJSONConfig>
    {
      "uiCustomData": {
        "customStyle": "#cg-tx-container{background-color: #f7f5fb; background-image:url(18195625.svg);}"
      }
    }
    </ppsJSONConfig>
</paymentPageData>
```

For more details on CSS customization, see [Modifying the Default Styles](https://developers.hyp.co.il/enterprise/changing-the-default-payment-page-appearance/modifying-the-default-styles.md).


---

# 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/adding-business-logo-and-custom-images.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.
