Microdeposits Overview - MX Documentation

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	Data Type	Definition
`account_name`	String	The name of the account associated with the verification.
`account_number`	String	The account number of the account associated with the microdeposit.
`account_type`	String	The name of the account type. Possible values are `CHECKING` and `SAVINGS`.
`created_at`	String	The date and time the microdeposit was created, given in ISO 8601 format.
`email`	String	The end user’s email address.
`error_code`	String	The code for the error.
`error_message`	String	A message explaining the error.
`first_name`	String	The end user’s first name.
`guid`	String	The unique identifier for the microdeposit. Defined by MX.
`institution_code`	String	The 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_name`	String	An 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_name`	String	The end user’s last name.
`routing_number`	String	The routing number for the account associated with the microdeposit.
`status`	String	The name of the current status.
`updated_at`	String	The date and time at which the microdeposit was last updated, given in ISO 8601 format.
`verified_at`	String	The date and time at which the microdeposit status changed from `DEPOSITED` to `VERIFIED`.

Microdeposit Statuses

Status	Status name	Definition
`0`	`INITIATED`	The verification process has started.
`1`	`REQUESTED`	Microdeposits have been requested from the microdeposit provider.
`2`	`DEPOSITED`	Microdeposits have been deposited into the specified account and are ready to be verified by the end user.
`3`	`VERIFIED`	The microdeposit amounts have been successfully verified by the end user.
`4`	`ERRORED`	The microdeposit could not take place due to an ACH error. This may indicate an incorrect account or routing number.
`5`	`DENIED`	The microdeposit amounts provided by the end user were incorrect.
`6`	`PREVENTED`	The microdeposit amounts provided by the end user were incorrect too many times and the verification cannot proceed.
`7`	`CONFLICTED`	The 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.
`8`	`REJECTED`	The verification was rejected either because validation failed on our side or due to a problem with the provider.
`9`	`PREINITIATED`	The microdeposit was created with client-provided `first_name`, `last_name`, and `email`.

Verification Fields

Field	Data Type	Definition
`account_name`	String	The name of the account associated with the verification.
`account_number`	String	The account number of the account associated with the verification.
`account_number_guid`	String	The unique identifier for the account associate with the verification. Defined by MX.
`account_type`	String	The name of the account type. Possible values are `CHECKING` and `SAVINGS`.
`created_at`	String	The date and time the verification was created, given in ISO 8601 format.
`institution_code`	String	The 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_name`	String	An 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_guid`	String	The unique identifier for the microdeposit associated with this verification. Defined by MX.
`routing_number`	String	The routing number for the account associated with the verification.
`updated_at`	String	The date and time at which the verification was last updated, given in ISO 8601 format.
`verification_method`	String	The name of the verification method.
`verified_at`	String	When `"verification_method": "CREDENTIALS"`: The date and time at which the associated `account` was created. When `"verification_method": "MICRO_DEPOSIT"`: The date and time at which the associated microdeposit status changed from `DEPOSITED` to `VERIFIED`.

Verification Methods

Method	Method name
`0`	`CREDENTIALS`
`1`	`MICRO_DEPOSIT`

​Microdeposit Fields

​Microdeposit Statuses

​Verification Fields

​Verification Methods

Microdeposit Fields

Microdeposit Statuses

Verification Fields

Verification Methods