All [External Accounts](🔗) in Modern Treasury have an attribute called `
verification_status`. This attribute tracks whether the external account's banking information has been verified through the Modern Treasury platform. There are three possible states that this can be in: `
pending_verification`, or `
verified`. All API responses and webhook payloads will include this field.
The verification status of an external account has no impact on your ability to use the account for payment orders. It is purely for informational purposes so that you can track whether an account has been verified through Modern Treasury. This is different than what you might be familiar with from other platforms, where some form of verification is required prior to initiating payments.
By default, all external accounts are unverified. If you do not plan to use our platform's verification tools, the accounts will remain unverified. You may choose to do this if you handle verification in your own platform and do not want to use our tools.
If you do want to use our verification tools, there are currently three ways that we support verifying external accounts.
Microdeposit verification is a way to verify bank accounts by testing small payments to the account. Modern Treasury will send two payments that are under $1 to the account. The counterparty can verify that they own the account by passing back the amounts that were deposited to them.
The benefit of microdeposits is that they work with any bank account. All you need is an account and routing number to send funds to someone.
The disadvantage is that it will take 1-2 days until the counterparty can view the microdeposits and verify their account.
Modern Treasury partners with Plaid to perform account validation. Plaid verifies accounts through end users providing account credentials. Once the connection has been made and the account information has been pulled, the external account will be verified.
The benefit of this type of verification is that it is instant. You can also prevent banking information from passing through your infrastructure, and simply pass Modern Treasury a tokenized string when creating a counterparty rather than bank account details.
The main disadvantage is that this approach requires your user to grant access to their bank account, which some users may be reluctant to do. Additionally, some banks do not support Plaid.
## Bank Consortium Data
With Modern Treasury's Compliance product, you can verify bank accounts using bank consortium data. The checks verify account status (e.g. is the account open and valid) and ownership (e.g. does the owner match the user).
The benefit of this type of verification method is that it is instant, unlike microdeposits. Additionally, users are not required to provide their bank account credentials, just their name, account number, and routing number.
The data covers over two thirds of bank accounts in the United States, with particularly strong coverage at large financial institutions.