> For the complete documentation index, see [llms.txt](https://devs.snowdropsolutions.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devs.snowdropsolutions.com/advanced-use-cases/co-emissions.md).

# CO₂ Emissions

MRS can enrich each brand match with an estimated carbon footprint for the transaction. When enabled, the response includes a spend-based emission rate, a qualitative impact band, and a human-readable

### Response fields

The following fields are added to the brand object:

| Field                   | Type   | Description                                                                                                          |
| ----------------------- | ------ | -------------------------------------------------------------------------------------------------------------------- |
| `co2EmissionsRate`      | number | Spend-based emission factor for the matched category, expressed in **kg CO₂e per € spent**.                          |
| `co2EmissionsImpact`    | string | Qualitative impact band indicating the relative emissions intensity. One of `low`, `medium`, `high` and `very high`. |
| `co2EmissionsReasoning` | string | Human-readable explanation of the main sources of emissions for the category.                                        |

### Example

```json
{
  "brand": {
    "name": "Example Merchant",
    "brandCategoryType": "beauty_salon",
    "co2EmissionsRate": 0.12,
    "co2EmissionsImpact": "low",
    "co2EmissionsReasoning": "Treatment rooms require continuous heating. Single-use needles, oils, and consumables used carry their own manufacturing and disposal footprint."
  }
}
```

A high-impact category, such as an airline, returns a higher rate:

```json
{
  "brand": {
    "name": "Example Airways",
    "brandCategoryType": "airline",
    "co2EmissionsRate": 2.5,
    "co2EmissionsImpact": "high",
    "co2EmissionsReasoning": "Flying burns large amounts of jet fuel on every journey. Onboard heating, lighting, catering, and entertainment add further energy consumption throughout."
  }
}
```

> The surrounding brand structure above is illustrative; the CO₂ fields are appended to the brand object your integration already receives.

### Behaviour

CO₂ data is returned according to the matched category:

| Scenario                                     | CO₂ fields returned                                      |
| -------------------------------------------- | -------------------------------------------------------- |
| A `brandCategoryType` is matched             | Yes - the rate, impact, and reasoning for that category. |
| No `brandCategoryType` is matched            | No CO₂ fields are returned.                              |
| A virtual brand is matched with an MCC       | Yes - the CO₂ fields mapped to that MCC.                 |
| The `brandCategoryType` is an `other …` type | No CO₂ fields are returned.                              |

### Localisation

`co2EmissionsReasoning` is returned in **English** by default.

If a localised version is configured for your account, the reasoning is returned in the language supplied on the request when that language is one of:

| Code | Language |
| ---- | -------- |
| `fr` | French   |
| `it` | Italian  |
| `es` | Spanish  |
| `de` | German   |