Sandbox Testing

Testing in the Demo/Sandbox Environment

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

Deterministic Test Scenarios

Applicant nameResult
Jacfirst BeclastFailed
James AlexanderInsufficient (shown as "Undetermined" on the backend)
Taylor CurtisPassed
Robert Jones (with attached bank statements)Passed, also returns an asset figure, from our asset verification feature (if enabled on your account)
Suzie JohnsonIncome error (3005)
Test IncomeerrorIncome 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.


Identity Verification Testing

You can test the full Identity Verification flow in the demo environment without using your real information. Any name, email address, and phone number will work, and you can test both passing and failing results.

How to run a test

  1. Create an invite in the demo environment with POST /id-verification/generate-idv-link or POST /id-verification/send-idv-email. You can use any name and email address.
  2. Open the link and start the verification. Enter any phone number when asked.
  3. When you're asked for a verification code, enter 123456.
  4. Continue the flow on your phone. At this step, you can choose whether the verification passes or fails.
  5. Scan any ID document. In the demo environment, the document doesn't need to be valid or current.
  6. Receive the IDV_REPORT_READY webhook, then use the idVerificationId to retrieve the record and report.
📘

Testing a failed verification

When the flow moves to your phone, choose the fail option to receive a FAIL result on the IDV_REPORT_READY webhook. Otherwise, the verification returns a PASS result.

🚧

Use the demo environment only

These testing shortcuts only work in the demo environment (https://enterprise-api.demo.snappt.com). In production, applicants need a real phone number to receive their verification code and a valid ID document.



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.


Did this page help you?