Snowdrop MRS API
Snowdrop HomeTry our demo
  • Snowdrop Enrichment MRS
  • OpenAPI Docs
    • Enrich one transaction - GET
    • Enrich multiple transactions - POST
  • Implementation Guides
    • Quick Start
    • Data. How to get the best results
    • Examples
    • Recommended UX
    • Additional UX Considerations
  • Basic Concepts
    • List request
    • Restrictive vs Extended
    • Merchant Category Codes
  • Advanced Use Cases
    • Categorization
      • Categorization Overview
      • Transaction Category
      • Category Icons
    • Crowdsourcing
      • Overview
      • Crowdsourcing Example
    • Payment Intermediaries
      • Payment Intermediaries Example
    • Clear Response Enrichment
    • Google Maps
      • About Google Maps IDs
  • Legal & Compliance
    • Security / Compliance FAQ
      • Data Encryption
      • Penetration Testing
    • Terms of Service
      • MRS Terms of Service
      • Google Maps Terms of Service
  • Troubleshooting
  • FAQ
Powered by GitBook
On this page
  • Restrictive
  • Extended
  • Data Flow Diagram: Restrictive vs Extended

Was this helpful?

  1. Basic Concepts

Restrictive vs Extended

Exploring MRS request types.

PreviousList requestNextMerchant Category Codes

Last updated 3 months ago

Was this helpful?

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:

Information returned by a Restrictive call:

name

The merchant name.

website

The website for the merchant (if appropriate).

Img (logo)

logoImg (string):

categoryImg (string):

A logo for the merchant, if one is found. If a logo is not found a general category icon is returned.

A logo for the merchant, if one is found. (Does not return a category icon).

A category icon for the merchant. These can be customised by the bank.

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:

Information returned by the Extended call:

Includes the address, map coordinates, categorisation and more.

See the API specification for more details.

Data Flow Diagram: Restrictive vs Extended

Includes .

everything provided by the Restrictive call