Sandbox test credentials

Log on to Sandbox and simulate different flows using Sandbox credentials

Sandbox simple test credentials

The easiest approach to create Items in the Sandbox is by using the username user_good. This gives you some limited control over Sandbox Item creation flow. It is not as flexible as the custom Sandbox, as Item details such as accounts and transactions are hardcoded.

1
2
3
username: user_good
password: pass_good
pin: credential_good (when required)

Sandbox multi-factor credentials

You can trigger any type of multi-factor authentication (MFA) flow that Plaid supports when creating an Item. Do so by using username user_good and modifying the password.

Note: Bank of America and U.S. Bank cannot be used as test institutions when triggering MFA flows with modified passwords. Instead, these banks will always launch on Sandbox with an MFA flow.

Multi-factor device OTP
1
2
3
4
5
username: 'user_good'
password: 'mfa_device'
# Code for all devices: 1234
code: 1234
Multi-factor questions
1
2
3
4
5
6
# n-rounds of m-questions per round, where 0 <= i, j < 9
username: 'user_good'
password: 'mfa_questions_<n>_<m>'
# answer_<i>_<j>, for j-th question in i-th round.
answer: 'answer_<i>_<j>'
Multi-factor selections
1
2
3
4
username: 'user_good'
password: 'mfa_selections'
answer: 'Yes'
1
2
3
4
5
6
7
# n-rounds of m-questions with o-answers per question
# 0 < n, m < 10 and 2 <= o < 10
username: 'user_good'
password: 'mfa_selections_<n>_<m>_<o>'
# answer_<n>_<m>_0, for m-th question in n-th round.
answer: 'answer_1_1_0'

ReCAPTCHA testing credentials

You may trigger a reCAPTCHA in Plaid Link in the Sandbox environment by customizing the test account password. Possible values are good or bad. A value of good will result in successful Item creation and bad will result in a RECAPTCHA_BAD error to simulate a failed reCAPTCHA. Both values require the reCAPTCHA to be manually solved within Plaid Link.

1
2
username: user_good
password: {"recaptcha":"bad"}

Error testing credentials

You can trigger a number of ITEM_ERROR or INSTITUTION_ERROR errors that you could typically receive when creating an Item. Do so by using username user_good and modifying the password:

1
error_[ERROR_CODE]

For example, the password error_ITEM_LOCKED allows you to simulate an ITEM_LOCKED error.

The list of errors that can be simulated in this way is below:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
"COUNTRY_NOT_SUPPORTED"
"INSTITUTION_DOWN"
"INSTITUTION_NOT_RESPONDING"
"INSTITUTION_NO_LONGER_SUPPORTED"
"INSUFFICIENT_CREDENTIALS"
"INTERNAL_SERVER_ERROR"
"INVALID_CREDENTIALS"
"INVALID_MFA"
"INVALID_SEND_METHOD"
"ITEM_LOCKED"
"ITEM_LOGIN_REQUIRED"
"ITEM_NOT_SUPPORTED"
"MFA_NOT_SUPPORTED"
"NO_ACCOUNTS"
"PAYMENT_INVALID_RECIPIENT"
"PRODUCTS_NOT_SUPPORTED"
"USER_SETUP_REQUIRED"

Auth micro-deposit testing credentials

For automated micro-deposit testing, use the username user_good with the password microdeposits_good. For more details, see Institution details for Auth testing.