# Restrictive vs Extended

There are two different types of requests you can make to MRS:

* `restrictive`
* `extended`

You specify which type you want with the `type` parameter.

### Restrictive 

The Restrictive Call is used to populate a statement view of transactions.

Its main purpose is to return merchant names and logos.

Characteristics of the Restrictive call

* Does not rely on the Google Maps Platform APIs.
* The caching rules are determined by Snowdrop.
* Match rates will typically be lower as compared to the Extended call.
* Returns what is needed to populate a statement view of transactions.

#### Example UX for Restrictive calls:

![](https://lh7-us.googleusercontent.com/VtYAW9I3XRiYrvmyDmjcMRNVqJ5exk0qZgsH7z3jv-qSGiuFEsAvcU5QzJLzJsB9LPngIe4DTY2fcihETjf7FTV6JoF6IbsMv43UMhM1UF_pjCE_ElvbwVqTD63uD4wbLGE9DwUWhcMdjDqD9M5L06-K=s2048)

####  **Information returned by a Restrictive call:**

| name                                                                     | The merchant name.                                                                                                                                                                                                                                                           |
| ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| website                                                                  | The website for the merchant (if appropriate).                                                                                                                                                                                                                               |
| <p>Img (logo) </p><p>logoImg (string): </p><p>categoryImg (string): </p> | <p>A logo for the merchant, if one is found. If a logo is not found a general category icon is returned.</p><p>A logo for the merchant, if one is found. (Does not return a category icon).</p><p>A category icon for the merchant. These can be customised by the bank.</p> |
| cachePolicy                                                              | An indicator for the caching rules for the returned information.                                                                                                                                                                                                             |
| logoScore                                                                | An indicator as to the likelihood that the returned image is a logo.                                                                                                                                                                                                         |
| categorisation                                                           | Categorisation is returned when the merchant has been found in the Snowdrop Top Merchants database.                                                                                                                                                                          |
| ID                                                                       | This is an optional transaction identifier that can be sent to Snowdrop. If sent, it is returned. This is to allow for linking up the returned information with other systems.                                                                                               |

### Extended

The Extended call is used to populate a statement view of a single transaction with enriched GeoLocation data points.

Its main purpose is to return a map location (when appropriate) for the transaction. It also returns categorisation and other information.

The typical architecture is to present a statement view (list of transactions) first and then allow the user to press (or click) on a transaction to get more info. This is when the Extended call is used.

Characteristics of the Extended call

* Relies on the Google Maps Platform.
* The caching rules are determined by Google.
* Match rates will typically be higher as compared to the Restrictive call. This is because the Google Places database is very comprehensive.

#### Example UX for Extended call:

![](https://lh7-us.googleusercontent.com/KP0M_FRM8ZV3MTcdqky4vqMSiMQonxgxFVlRYlHNTWKkXevPGFxeNVcstxmN8g7Wks-SrsMaHZnW5sR4FRNF4NV8tt4uzXl_BQymzG4n5LWliSnWw9mnLZUm1dUpNWlsSyUtWM00zcPdpgb5YkGD6KJm=s2048)

#### Information returned by the Extended call:

Includes [everything provided by the Restrictive call](#information-returned-by-a-restrictive-call).

Includes the address, map coordinates, categorisation and more.

See the API specification for more details.

### &#x20;Data Flow Diagram: Restrictive vs Extended

<figure><img src="/files/mISm3BYtIEfF9fIwSNb1" alt=""><figcaption></figcaption></figure>


---

# 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/basic-concepts/restrictive-vs-extended.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.