Skip to main content
MX Connectivity products serve as a bridge between your application and financial institutions. They allow you to:
  • Connect end users to thousands of financial institutions
  • Retrieve financial data such as account details, transactions, and more
  • Enhance and standardize data
  • Power financial use cases including account opening, payments, and more
To understand the core resources of our platform, see MX Data Architecture.

Integration Checklist

Complete steps for integrating MX Connectivity products

Connect Accounts

Follow our integration guides to connect user accounts

Connectivity Products

MX offers several connectivity products to address different use cases.
NOTEMost connectivity products focus on retrieving specific types of data from connected accounts (such as transactions, balances, or account numbers). Microdeposits is different—it provides an alternate method for verifying account ownership by making small test deposits to an account.

Aggregating & Enhancing Data

Our platform uses distributed services to aggregate, enhance, and deliver financial data to end users and institutions. The platform includes RESTful web APIs, embeddable digital money management tools, customer analytics and marketing software, and more. The following flow shows how MX aggregates and enriches data:
  1. End users provide their login credentials for a financial account, such as their bank or retirement account (you can also send your own customers’ data to MX using one or more of our APIs).
  2. Those credentials are supplied to the MX system.
  3. MX brings data from those accounts into its system, through a direct data-sharing connection or a third-party data provider.
  4. MX enhances account and transaction data:
    • Account types and subtypes like CHECKING or SAVINGS are assigned
    • Every transaction is categorized into one of more than 100 default categories
    • When possible, additional classifiers like is_bill_pay or is_direct_deposit are assigned
    • Transaction descriptions are made readable. For example, DBT CRD 1357 07/22/19 XXXX1357 JCWS RESTAU LEHI UT C#5144 becomes JCW's Burgers
    • Dates, locations, and merchant logos are added wherever possible
    • If two months of transaction data exists, user budgets are automatically calculated
  5. MX delivers this enhanced financial data through our APIs, UIs, or daily change files. Additionally, we identify when end users have financial accounts with competitors and provide analytics on product usage and money management.

Retrievable Data

The following examples show what data you can expect with our Connectivity products.
See Account Aggregation for more info. To learn more about individual fields, see Account Fields or Transaction Fields.
See Instant Account Verification for more info. For field descriptions, see Account Number Fields.
See Account Owner Identification for more info. For field descriptions, see Account Owner Fields.
Extended Transaction History shows up to 24 months of transactions, instead of only up to 90 days. For field descriptions, see Transaction Fields.
See Statements for more info. For field descriptions, see Statement Fields.

Next Steps

Integration Checklist

Complete steps for integrating MX Connectivity products

Connect Accounts

Follow our integration guides to connect user accounts