Instant Account Verification

Get account and routing numbers for demand deposit accounts

New to MX Connectivity?

See the Connectivity Overview to learn about our Connectivity products and integration options.

Integrate using the Connect Widget

Use the Connect Widget and Platform API to let end users connect to their accounts.

Go to Guide

Integrate using the Platform API

Use the Platform API to power a non-MX UI connection experience.

Go to Guide

With Instant Account Verification, you can connect to an end user's financial institution and retrieve account and routing numbers for their demand deposit accounts. You can use this data for any number of solutions such as moving money or account opening. In many cases, Instant Account Verification must be used in conjunction with Account Owner Identification and Balance Checks to prevent problems like ACH returns.

Diagram flow of the steps to get account and routing numbers

Tokenized Account Numbers

Tokenized Account Numbers (TANs) are substitute account numbers used for secure ACH money movement. When an end user connects an account via an OAuth connection, certain financial institutions provide a TAN instead of the user's actual account number.

This practice enhances security and provides users with greater control. Because each application receives a unique TAN for the same bank account, users or their financial institutions can manage access on a per-application basis without exposing the underlying account details.

The MX platform currently supports TANs from Chase and U.S. Bank.

Using TANs for ACH Payments

The TAN and associated routing number are valid for money movement on the ACH network but only when used together. This combination won't work for other purposes, such as wire transfers, and third-party verification services may not recognize them. Using the TAN with a different routing number—even one from the same institution—will cause the transfer to fail.

Best Practice

To avoid confusing the end user, don't display the TAN in your application's UI. The user won't recognize this number. Instead, display the masked account number provided in the account_number field from the /users/{user_guid}/accounts endpoint.

Connection Types

OAuth: For supported institutions like Chase and U.S. Bank, a call to /users/{user_guid}/members/{member_guid}/account_numbers will return a TAN in the account_number field.
Non-OAuth Connections: These connections return traditional (non-tokenized) account and routing numbers.

Institution-Specific Behavior

The lifecycle and behavior of a TAN can vary by financial institution.

Chase

TANs issued by Chase will become invalid and ACH transfers will fail under the following conditions:

MX revokes consent.
The end user revokes consent directly with Chase.
Chase flags the account for fraudulent activity.

U.S. Bank

TANs issued by U.S. Bank won't become invalid if the end user revokes consent or deletes the connection. They remain active for money movement even after the associated MX connection is no longer active.

For more information, reference the U.S. Bank Developer Portal.

Quick Links

API Reference

Learn about the full features of the Platform API.

Go to Reference

Connect Widget

Learn about the Connect Widget.

Go to Docs

Demo App

View the demo app on GitHub.

Go to GitHub

Account Number Sample Data

This sample response shows the data you can expect to get for account owners.


_20{
_20  "account_numbers": [
_20    {
_20      "account_guid": "ACT-82a93692-f756-534f-9b2e-ad10a0f38462",
_20      "account_number": "10001",
_20      "institution_number": null,
_20      "member_guid": "MBR-3bdc7d6b-efd4-1497-a0af-b23501cf9bd0",
_20      "routing_number": "091000019",
_20      "passed_validation": true,
_20      "transit_number": null,
_20      "user_guid": "USR-11141024-90b3-1bce-cac9-c06ced52ab4c"
_20    }
_20  ],
_20  "pagination": {
_20    "current_page": 1,
_20    "per_page": 25,
_20    "total_entries": 1,
_20    "total_pages": 1
_20  }
_20}