# Brands

The `brand` object provides detailed metadata about the overarching brand associated with the merchant. This data is useful for categorization, UI representation (e.g. showing brand logos), aggregation and understanding corporate relationships. 

**Response Object:**

<figure><img src="/files/4yJ451gU2hxopbJXRNb6" alt=""><figcaption></figcaption></figure>

#### Field Overview

| Field                  | Type           | Description                                                                                                                                                          |
| ---------------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id`                   | `string`       | Unique identifier for the brand.                                                                                                                                     |
| `name`                 | `string`       | The official name of the brand (e.g., “Carrefour Express”).                                                                                                          |
| `img`                  | `string (URL)` | Main image associated with the brand. Typically used for brand visualization (e.g., banners, highlights).                                                            |
| `website`              | `string (URL)` | Official website of the brand.                                                                                                                                       |
| `esg`                  | `object`       | ESG (Environmental, Social, and Governance) data. Excluded from this section; refer to [ESG Documentation](/advanced-use-cases/esg.md) for full details.             |
| `brandCategory`        | `object`       | Hierarchical classification of the brand. Excluded from this section. See [Categorization](/advanced-use-cases/categorization/categorization-overview.md) reference. |
| brandParentCategoryImg | `object`       | Icon representing the **brand’s parent category**, used when no brand logo is available                                                                              |
| brandCategoryGroupImg  | `object`       | Icon representing the **brand category group**, used when no brand logo is available                                                                                 |

### Virtual Brands:

The API supports virtual brands to allow temporary representation of merchants that are not yet linked to a recognized brand. The virtual brand response essentially returns the merchant information inside the brand information as a placeholder. The way you can identify a virtual brand is by the missing id field inside the brand response. Once the proper brand is assigned, the virtual placeholder will be replaced accordingly.

If an MCC is included in the request, the response will also contain detailed categorisation regardless of whether a brand is found or not based on our MCC mapping techniques.

### Brand Category Icons:

Brands support category icons for brand parent categories and brand category groups (not category types). These icons are always returned and are also used as the brand image when a brand logo is unavailable.\
Using brand category icons helps maintain a consistent visual experience and makes transactions easier for users to recognise. While default icons are provided, we recommend supplying your own so they better align with your product’s look and feel.

#### Supported image sizes

* PNG images at **96 × 96 pixels**
* PNG images at **192 × 192 pixels**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://devs.snowdropsolutions.co.uk/advanced-use-cases/brands.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.