Skip to main content

Microdeposits Overview

Microdeposits is an additional verification method that allows you to verify account details and navigate the process of using microdeposits and the automated clearing house (ACH) system.

Make two, small ACH deposits into a consumer's account using the provided account and routing number. You can then require that the end user confirm the exact amount of each deposit to verify that they own the account and meet NACHA’s account verification.

For more info, including process flows, setting block lists, and more, see Microdeposits.

Microdeposit Fields

Field NameData TypeDefinition
account_nameStringThe name of the account associated with the verification.
account_numberStringThe account number of the account associated with the microdeposit.
account_typeStringThe name of the account type. Possible values are CHECKING and SAVINGS.
created_atStringThe date and time the microdeposit was created, given in ISO 8601 format.
emailStringThe end user's email address.
error_codeStringThe code for the error.
error_messageStringA message explaining the error.
first_nameStringThe end user's first name.
guidStringThe unique identifier for the microdeposit. Defined by MX.
institution_codeStringThe code for an institution associated with the microdeposit, e.g., “chase-bank” or “wells-fargo-bank.” May be null for institutions which are not in the MX system.
institution_nameStringAn easy-to-read name for an institution, e.g., “Chase Bank” or “Wells Fargo Bank.” May be null for institutions which are not in the MX system.
last_nameStringThe end user's last name.
routing_numberStringThe routing number for the account associated with the microdeposit.
statusStringThe name of the current status.
updated_atStringThe date and time at which the microdeposit was last updated, given in ISO 8601 format.
verified_atStringThe date and time at which the microdeposit status changed from DEPOSITED to VERIFIED.

Microdeposit Statuses

StatusStatus nameDefiniton
0INITIATEDThe verification process has started.
1REQUESTEDMicrodeposits have been requested from the microdeposit provider.
2DEPOSITEDMicrodeposits have been deposited into the specified account and are ready to be verified by the end user.
3VERIFIEDThe microdeposit amounts have been successfully verified by the end user.
4ERROREDThe microdeposit could not take place due to an ACH error. This may indicate an incorrect account or routing number.
5DENIEDThe microdeposit amounts provided by the end user were incorrect.
6PREVENTEDThe microdeposit amounts provided by the end user were incorrect too many times and the verification cannot proceed.
7CONFLICTEDThe account and routing numbers have already been verified or are in the process of being verified, and a new microdeposit verification cannot be created. If the Connect UI encounters this status, it will load the view for the status of the already-existing verification.
8REJECTEDThe verification was rejected either because validation failed on our side or due to a problem with the provider.
9PREINITIATEDThe microdeposit was created with client-provided first_name, last_name, and email.

Verification Fields

Field nameData typeDefinition
account_nameStringThe name of the account associated with the verification.
account_numberStringThe account number of the account associated with the verification.
account_number_guidStringThe unique identifier for the account associate with the verification. Defined by MX.
account_typeStringThe name of the account type. Possible values are CHECKING and SAVINGS.
created_atStringThe date and time the verification was created, given in ISO 8601 format.
institution_codeStringThe code for an institution associated with the verification, e.g., “chase-bank” or “wells-fargo-bank.” May be null for institutions which are not in the MX system.
institution_nameStringAn easy-to-read name for an institution, e.g., “Chase Bank” or “Wells Fargo Bank.” May be null for institutions which are not in the MX system.
micro_deposit_guidStringThe unique identifier for the microdeposit associated with this verification. Defined by MX.
routing_numberStringThe routing number for the account associated with the verification.
updated_atStringThe date and time at which the verification was last updated, given in ISO 8601 format.
verification_methodStringThe name of the verification method.
verified_atStringWhen "verification_method": "CREDENTIALS": The date and time at which the associated account was created.

When "verification_method": "MICRO_DESPOSIT": The date and time at which the associated microdeposit status changed from DEPOSITED to VERIFIED.

Verification Methods

MethodMethod name
0CREDENTIALS
1MICRO_DEPOSIT