Testing in Sandbox
Test values and options for Identity Verification
Identity Verification is not supported in Plaid's Development environment. Only Production and Sandbox are supported environments. To request access to Identity Verification in Sandbox, Request product access.
Sandbox user for Identity Verification
In Sandbox mode, Identity Verification accepts a fixed set of inputs in order to result in a successful verification.
|123 Main St.
Identity verification behavior in Sandbox
Lightning checks in Sandbox will be compared against the information above. To simulate different test cases and results, you can adjust your Lightning input at the attribute level (e.g. an incorrect birthdate), and set up different Identity Rules to simulate different verification results.
Documents uploaded in Sandbox will always be interpreted as genuine (not fake) documents reflecting the name and date of birth above. Document check will pass if the data provided in the Lightning check matches this name and date of birth, and will fail otherwise.
Selfie checks will not be run in Sandbox mode, even if they are enabled in your template.
In Sandbox, Monitor screens against a real-world dataset, so the Sandbox user will not return any screening hits. For more information, including example data you can use to trigger screening hits, see Testing Monitor.
The risk check is fully functional in Sandbox. It’s common to trigger high risk scores when testing. For more information and advice, see Risk rules for testing.
Auto-fill behavior is fully functional in Sandbox.
Financial Account Matching
Financial Account Matching is fully functional in Sandbox. If you want to change the Identity data that is being compared to the Identity Verification session, see how to create Sandbox test data.
Risk rules for testing
Many common testing behaviors (e.g. attempting to enter the Identity Verification flow repeatedly on the same device using different credentials) may be flagged as risky behavior and cause your verification attempt to fail. For testing purposes, you can temporarily set the Acceptable Risk Level for any checks you are failing to High, under the Rulesets -> Risk Rules section of the template editor. Make sure to set the Acceptable Risk Level back to your desired setting before launching in Production.