Skip to main content

​
Overview

MX’s instant account verification allows partners to access account and routing numbers for demand deposit accounts in just a few simple steps. Functionally, this means that only CHECKING and SAVINGS accounts are likely to be verified. Verification requires requests to several APIs. Partners may optionally use the Connect widget to simplify their workflow. The Connect widget simplifies creating members and answering multi-factor authentication while providing a ready-made user interface for these verification steps. The general workflow for verification is very similar to standard aggregation. The workflow you’ll follow depends on whether you decide to use the Connect widget or build your own UI that relies on our API.
INFOFor detailed information on requirements, errors, standards, and conventions for the various APIs and products involved in verification, please see the documentation for Nexus , Real Time, SSO, and Personal Finance Management.

​
Workflow With the Connect Widget:

  1. Creating a user with a request to the MDX Real Time API
  2. Loading the Connect widget in verification mode on your website or within a WebView
  3. End users create a member, launch a verification job, and respond to MFA within the Connect widget
  4. Getting an API token with the SSO API
  5. Getting a session token with the Nexus API
  6. Polling the member’s verification status with the Nexus API
  7. A member with a complete, successful verification will have "connection_status":"CONNECTED" and "is_being_aggregated":false
  8. Once verification has completed, getting the verification data with another request to the Nexus API

​
Workflow with APIs Only

  1. Creating a user (MDX Real Time API)
  2. Getting an API token for that user (SSO API)
  3. Getting a session token for that user (Nexus API)
  4. Getting institution information (Nexus API)
  5. Get institution-required credentials (Nexus API)
  6. Creating a member with the correct institution code and credentials required by that institution (Nexus API)
  7. Calling the verify endpoint (Nexus API)
  8. Polling the member’s verification status (Nexus API)
  9. Answering MFA if necessary (Nexus API)
  10. Reading the member’s account_numbers (Nexus API)

​
A Note on Virtual Account Numbers

OAuth connections for the Chase institution do not return end users’ actual account numbers for deposit accounts. Instead, they return a Virtual Account Number (VAN) and an associated routing number (ABA). The VAN will not have any similarity to the actual account number; the ABA will be an ABA for the institution, but may or may not be the ABA associated with the actual account number, as some institutions have multiple ABAs. The VAN and associated ABA returned through the verification endpoint are valid for money movement on the ACH system, but only when used together; for instance, using the VAN with a different ABA also associated with the institution will not work for money movement. Nevertheless, these numbers will not match end users’ actual account numbers for verification purposes. While Chase is currently the only institution on the MX platform which returns VANs on OAuth connections, other institutions may do so in the future. Non-OAuth connections will return real account and routing numbers.