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

Was this helpful?

  1. Implementation Guides

Additional UX Considerations

PreviousRecommended UXNextBasic Concepts

Last updated 10 months ago

Was this helpful?

  • Consider providing the original merchant description and perhaps other transaction info at the bottom of the Detail View page. This can be useful for your customer service function, should they be contacted about a transaction and they do not have access to the enriched information.

  • The transaction categories can be used to present summarised spending to your users (see Additional UX Considerations).

  • Consider allowing your users the ability to re-categorise specific transactions themselves.

  • You may also wish to summarise transaction info in other ways:

    • List the merchants that your users spend the most money with.

    • You can summarise recent spending on a map.

Examples

Transaction Categorization

Top Merchant
Recent spends map