Skip to main content
We’ve provided ways to simulate some common scenarios you’ll encounter so you can effectively test your code. These test scenarios only work in our integrations environment, not in production. Producing the scenario is just a matter of using the given input.
Input fieldFormat
First nameMust be less than or equal to 50 characters and contain no special characters, e.g., Dave but not D#ve.
Last nameMust be less than or equal to 50 characters and contain no special characters, e.g., Smith but not Sm_th.
EmailMust be in standard email format, e.g., example@email.com.
Routing numberMust follow standard American Banking Association rules for routing numbers, e.g., 091000019 but not 222222226 or 021000021.
Account numberAny integer that begins with 3333 (e.g. 333312345) will be interpreted as a valid account number. Valid account numbers produce an INITIATED status for the microdeposit object that is created, followed by a REQUESTED status; REQUESTED will change to DEPOSITED after two minutes.
Microdeposit amountsSpecific amounts correspond to specific scenarios, described below.

​
A Successful Verification

Inputs:
  • First name
  • Last name
  • Email address
  • Routing number
  • Account number
Amounts:
  • 0.09 for both

​
A FailedVerification that Cannot Be Retried

Inputs:
  • First name
  • Last name
  • Email address
  • Routing number
  • Account number
Amounts:
  • 0.04 for the first
  • 0.01 for the second

​
A Failed Verification That Can Be Retried

Inputs:
  • First name
  • Last name
  • Email address
  • Routing number
  • Account number
Amounts:
  • 0.02 for both to cause a failure.