Modern Treasury API Documentation

Welcome to Modern Treasury. You'll find comprehensive guides and documentation to help you start working with Modern Treasury APIs as quickly as possible, as well as support if you get stuck.

Verifying with Microdeposits

Modern Treasury supports micro-deposit verification for its customers. This is a form of authenticating bank account ownership. There are two steps to using Modern Treasury micro-deposits.

  1. The first API call will initiate the verification by depositing two small sums in the external account via ACH. The verification status will be pending_verification until #2 is completed.

  2. The second API call completes the verification by certifying that the amounts provided to you by your counterparty are correct. This transitions the verification status to verified.

These micro-deposits occur via payment orders. The payment orders will be created by Modern Treasury automatically. Fields that are used for internal usage, such as the internal description and metadata, may be edited on these payment orders. The fields that dictate the mechanics of the payment itself, such as the amount, counterparty, and payment type, may not be changed. The payment orders will also adhere to the rules system, which means a user may have to approve the micro-deposits before they are sent. If you want to bypass this, add into your rule that the amount must be greater than $1, as all micro-deposits are less than $1.

Rule condition that will bypass micro-deposits.Rule condition that will bypass micro-deposits.

Rule condition that will bypass micro-deposits.

Updated about a year ago


Verifying with Microdeposits


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.