Getting Started with MXaccess

  • Updated

This article outlines the system and work requirements necessary for you to successfully implement MXaccess. MX is committed to helping you get the most out of the product. You’ll find details about how MX will support you below. 

Client System Requirements

  • You must have a data API in place and documentation necessary to facilitate secure access from MXaccess to fetch customer financial data.

    This may not be required if you already have a data-sharing integration with MX.

  • Your systems must be prepared for the large volume of API calls and responses that will be made and received by intermediaries and data recipients.
  • You must have access to make changes to your online banking and/or mobile user interfaces (For example, embed the consent management widget). 
  • Your identity providers for both admin and customer must support OIDC.
  • Your data API must be able to fulfill MXaccess requests for financial data using customer idP-issued access tokens.
  • You must be able to provide access to the required core API/online banking endpoints needed to facilitate the desired FDX API standard adherence for data recipients. 

Client Work Requirements

In order for MX to fulfill its obligations to your organization, you must fulfill the following requirements:

  • Enter into and execute an MX master services agreement and accompanying order form for applicable products and/or services.
  • Provide environment variables and other information needed to create the test and production environments.
  • Provide OIDC configuration information as outlined in the implementation documentation.
  • Configure backend requests to MXaccess to generate customer JSON Web Tokens (JWTs) for embedding the authorizations widget as outlined in the implementation documentation.
  • Provide MX with a list of the desired FDX resources/endpoints/query parameters to be available to data recipients.
  • Add MX as an intermediary and ensure that MX remains authorized along with all of its apps. This includes but is not limited to: 
    • Whitelisting MX IP addresses in both test and production environments
    • Providing an API key for MX to register its applications
    • Providing MX with the client_id and secret for each app it registers, and
    • Providing information needed by MX to connect to the system
  • Contact, integrate with, and coordinate with non-MX intermediaries and data recipients
  • Embed the authorizations widget into your online banking and mobile app user interfaces
  • Configure DNS records to point to hosted MXaccess instances as needed
  • Provide accounts, credentials, and data for testing purposes, and
  • Conduct all production-level testing and final certification

MX work requirements

MX will perform the following for Clients:

  • Provide necessary technical documentation
    • Implementation guide
      • Overview of stack
      • Prerequisites
      • Configuration information
        • On-premises (environment variables)
        • MX-hosted (OIDC configuration)
  • Provide the resources to manage the production environment including redundancy, load balancing, and backups
  • Provide an adapter as defined in the SOW
  • Register MX as an intermediary, including
    • Provide a test data recipient for integration testing and POC as needed for non-production environments
    • Register MoneyDesktop as the first production data recipient for testing
    • Register MX applications
    • Conduct regular cadence meetings until product is successfully implemented, and
  • Provide technical support

Was this article helpful?