Testing Auth flows

To test in the Sandbox environment, you need to set the Link configuration environment to "sandbox":

1Plaid.create({
2  // ...
3  env: 'sandbox',
4});

You will also want to direct any backend API requests to the sandbox URL:

1https://sandbox.plaid.com

• Search for “Houndstooth Bank” in Link.
• Use the input data in the table above to simulate the desired outcome.

You can also test this flow in Sandbox with no code by using the Link Demo.

• Search for "Windowpane Bank" in Link.
• When prompted, use the input data in the table above to simulate the desired outcome.
• For all other fields, you can use any values.

• If you have enabled Same Day Micro-deposits, enter gibberish into the search bar to ensure no institutions will be found, then click on Link with account numbers.
• If you have configured Same Day Micro-deposits with Auth Type Select, choose "Manually" from the menu.
• When prompted, enter the input data in the table above. For all other fields, you can use any values.
• Note that, unlike the primary Instant Micro-deposits flow, the routing and account number entries will be on separate panes.

You can also test this flow in Sandbox with no code by using the Link Demo.

To simulate a database_matched result:

Any other input will simulate no match and proceed with Same Day Micro-deposits, e.g.:

• If you have enabled Database Match, enter gibberish into the search bar to ensure no institutions will be found, then click on Link with account numbers.
• If you have configured Database Match with Auth Type Select, choose "Manually" from the menu.
• Use the input data in the table above to simulate different outcomes.

You can also test this flow in Sandbox with no code by using the Link Demo.

To simulate a database_insights_pass result:

To simulate a database_insights_pass_with_caution result:

Any other input will simulate a database_insights_fail result, e.g.:

• If you have configured Database Insights with Auth Type Select, choose "Manually" from the menu.
• If you have configured Database Insights with Embedded Search, choose "Connect Manually".
• If you have enabled Database Insights without either of the above options, enter gibberish into the search bar to ensure no institutions will be found, then click on "Link with account numbers".
• Use input data from the table above to simulate various outcomes.

You can also test this flow in Sandbox with no code by using the Link Demo.

• Search for “Houndstooth Bank” in Link.
• Use the input data in the table above to simulate the desired outcome.

The micro-deposit verification will automatically succeed after twenty-four hours. To test a failed micro-deposit, or to skip the twenty-four hour waiting period, use the /sandbox/item/set_verification_status endpoint to manually control the Item's micro-deposit verification status.

You can also test this flow with no code by using the Link Demo.

• If you have configured Same Day Micro-deposits with Auth Type Select, choose "Manually" from the menu
• If you have enabled Same Day Micro-deposits without Auto Type Select, enter gibberish into the search bar to ensure no institutions will be found, then click on "Link with account numbers".
• Use the input data in the table above to simulate the desired outcome.

• Call /item/public_token/exchange with your public_token from the Link session in previous step to receive an access_token.
• Call /link/token/create and provide the access_token from the previous step to receive a link_token.
• Open Link with your link_token.
• In the deposit code field, enter ABC

Micro-deposits that are generated in Sandbox will never be posted by default. In order to generate a posted event that you can see when you query /bank_transfer/event/sync, you can use the /sandbox/bank_transfer/simulate endpoint.

Simulating a posted event in Sandbox does not generate a webhook. You will need to call /sandbox/bank_transfer/fire_webhook each time you want a webhook to be published for testing.

• Complete the Same Day Micro-deposits flow as detailed above
• Call /identity/match using any variation of data in order to test the matching algorithm
• The identity data of the test user is as follows: