Sandbox Testing

To help you test different outcomes reliably, use these applicant names. They'll always return the same result.

Deterministic Test Scenarios

Applicant name	Result
Jacfirst Beclast	Failed
James Alexander	Insufficient (shown as "Undetermined" on the backend)
Taylor Curtis	Passed
Robert Jones (with attached bank statements)	Passed, also returns an asset figure, from our asset verification feature (if enabled on your account)
Suzie Johnson	Income error (3005)
Test Incomeerror	Income error (3004)
Bob Jones connected payroll credentials: username: `test_1`, password: `passgood`, MFA: `8081`	For testing connected payroll
Sue Wealthy bank linking credentials: username: `sue_wealthy`, password: `profile_700`, bank: FinBank Profiles - A	For testing bank linking
Joseph Burnam connected payroll credentials: username: `test_3`, password: `passgood`, MFA: `8083`	Name mismatch warning code

Any other applicant name will receive a randomly assigned outcome, weighted toward Clean/Passed, but any result is possible, so these shouldn't be used for deterministic testing.

Testing Override Codes (4000 Series)

To test the 4000-series override codes, use any first name paired with the last name Override. This will produce a REPORT_UPDATED webhook, if one is registered for your company API key.

Reach out to your technical contact at Snappt for sample testing documents, or if you run into any issues getting set up or have questions along the way.