LogoLogo
  • Introduction
  • Terms and Definitions
    • Terms And Definitions
  • Integration And Certification
    • Third-Party Provider Integration
    • Account Provider Certification
      • Pre-production Setup
      • Production Ready
      • Sandbox Testing
  • Developer Center
    • Open Banking API
    • API Architecture
    • Messaging Standard
    • Performance Monitoring
    • Hashmaps and Lookups
  • Open Banking Standard
    • Standard
  • Operational Guideline
    • Overview
    • Service Management
    • Front-Office
    • Back-Office
    • Operations-Readiness Checklist
  • Customer Experience
    • Overview
    • Authorization
    • Mobile App Interface Guidelines
  • Security Framework
    • Overview
    • Security-Readiness Checklist
    • Data Management and Exchange
    • Securing Consumer Information
  • References
    • References
Powered by GitBook
On this page
  1. Developer Center

Hashmaps and Lookups

Hashmaps and Lookups contain relatively static content throughout the API lifetime. This content is however crucial for processing such as a map of response codes to response descriptions. Relevant mappings are provided within the API specifications under the META Directory collection.

Developers are advised to store this information in persisted format e.g. within a database, a database table or system file in a way that they can be dynamically updated and reloaded within their applications. For instance, a mapping reference called response_code_descriptions can be created with response code to response description mapping as columns in a database table. This table can be called up at intervals and loaded into the application memory or upon an application restart. New definitions of response code and descriptions can simply be updated in this table if/when any updates arise. This structure is especially useful for self-defined mappings for which allowances have been provided in the specifications.

PreviousPerformance MonitoringNextStandard

Last updated 3 years ago