Skip to main content

Data Provider Implementation Reference

What is Data Access and What Can It Do For You?

Data Access is an open finance API platform designed to make it as easy as possible for you to share your institution's financial data and access the data of other institutions using the latest FDX and OAuth standards.

In other words, you can stand up and manage your own financial data API in a fraction of the time it would take to build your own.

Data Access includes ready-made user interfaces for administration and authorization, as well as third-party management.

Data Access enables you to monitor and manage where customers are sharing your financial data and provides the tools to implement a more secure data-sharing experience with modern, token-based connectivity. It also empowers consumers to better understand, leverage, and benefit from their own financial data in a secure, reliable, and user-centric manner. Consumers gain visibility and control over which apps and institutions access their data by giving them the power to them to grant, modify, and revoke access at any time.

Data Access uses the Ruby on Rails and React frameworks.

Features

API

  • OAuth 2.0
  • OIDC
  • FDX 4.6-compliant endpoints for customers, accounts, and transactions.
    • Also includes capabilities endpoint for API information.
  • Dynamic data-recipient registration.
    • Quickly register and manage multiple apps at once with a streamlined endpoint rather than a UI.

User Interfaces

  • Data provider branding for all UIs.
  • Data provider administration dashboard.
    • Ability to manage intermediaries and apps.
    • Searchable logs.
    • Analytics reports.
    • Security.
  • Customer consent-granting widget.
  • Customer consent-management dashboard.
    • Embeddable in a data provider's experience.
    • Ability to grant and revoke consent at any time.
  • Data recipient self-registration widget.
  • Data recipient administration dashboard.

Hosting

  • Hosted by MX.

Application Adapter

Data Access delivers FDX-compliant data to third parties. It does this by translating data from your backend systems into FDX data. Because all backend systems are a little bit different, this requires building an adapter specific to your systems to do the translation.

MX generally performs the work of building an adapter, but partners are welcome to do this themselves as well.

In order for MX to build this adapter, we need a few of things.

  1. Your existing backend API must be accessible from the outside and access must be given to MX so that Data Access can get your data and translate it with the adapter.
  2. Your existing backend API must be able to return the correct data for a given customer based on that customer's OIDC token.
  3. You must provide documentation on your existing backend API.

Application Architecture

A system architecture diagram for data access

Data Flow

A data flow diagram for data access