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
  • Overview
  • API Specification
  • Data Flow

Was this helpful?

Snowdrop Enrichment MRS

Snowdrop Enrichment API (MRS - Merchant Reconciliation System) guide. Here you will find detailed explanations of how our API works, the required data, and best practices for optimal results.

NextOpenAPI Docs

Last updated 4 months ago

Was this helpful?

Overview

  • The Snowdrop MRS API enriches banking data with information about the merchants associated with each transaction. It helps to make “messy” transaction data clear and easily understood.

  • Send the raw transaction data to our API, and it will return the merchant name, logo, its postal address, website, category, and other information.

Take your Payment Data to the next level. Get in touch with our team.

API Specification

Want to skip the guides and go directly to the tech specs? See OpenAPI Docs.

Data Flow

Try our demo