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

Recommended UX

Recommended User Experience for your app.

PreviousExamplesNextAdditional UX Considerations

Last updated 10 months ago

Was this helpful?

Recommendations for a typical banking application to optimize cost and efficiency:

  1. Use a List request (type restrictive) to fill the initial list of transactions using the cleaned up name and logo, and optionally also include categorisation and category icon in this view.

  2. When a user wants more information about a transaction then they can press/click on it. At this point a individual call (see Quick Start) of type extended is made and the user will navigate to the Detail View.

See also Restrictive vs Extended.

See also Additional UX Considerations.