Using the Sandbox
How to Run a Test Verification in the Sandbox
How do I create a test user?
Switch to the Sandbox environment, then create a user with the exact PII (name, SSN, date of birth) of one of the six test users from the reference table. The identity you choose determines the outcome you'll get.
How do I run a test verification?
After creating the test user, run the verification — via Medallion or the relevant check — the same way you would in production. Because vendor responses are mocked, the result matches the scenario mapped to that test user.
How do I read the verification result?
Results appear the same way as in production — in the portal and via your configured result method — carrying the sandbox environment badge. Match the result against the expected outcome for the test user you ran.
FAQs
Does testing in the sandbox affect my production billing?
No. The sandbox has its own fixed $100 credit balance and is separate from your production account. Test transactions don't touch production billing or production credits.
Is sandbox data isolated from production?
Yes. The sandbox is a separate company with its own data.
How long does sandbox data persist?
Sandbox data is purged periodically. Use the sandbox for testing flows, not for long-term storage.
What happens if I run out of sandbox credit?
The balance is fixed and there's no self-serve top-up. Contact the Authenticate team to add more sandbox credit.
Can I add my team members to the sandbox?
Yes. When you create a new member in the portal, you'll see an option to also add them to your sandbox company. If selected, the member is created in both environments automatically.
Can I test KYB, FAOV, Professional License, or STR checks in the sandbox?
Not currently. FAOV, Professional License, and KYB aren't supported in the sandbox yet, and STR-related checks can only be tested in the production environment.
Why are my sandbox results unexpected?
Most often because the PII doesn't exactly match a test user. The sandbox works reliably only with the pre-defined test identities — any other name, SSN, or date of birth produces unreliable output. Confirm the name, SSN, and date of birth match the reference table exactly.
Can I log in to the sandbox directly?
No. The sandbox is reachable only through the environment switch inside the production portal — there is no standalone sandbox login.