The DEV (sandbox) environment runs against Equifax UAT — real Equifax services using non-production data. Specific SSN and mobile combinations route to hardcoded scenarios so you can exercise happy paths and every failure mode deterministically — DIT failures, SMFA timeouts, thin-file rejections, enrollment errors, and more — using Equifax UAT's synthetic identity catalog.
The sections below cover all four flows (Digital Identity Trust + Secure Multi-Factor Authentication, Digital Identity Trust + Customer OTP, Prefill + Onboarding, Offers IQ) plus a separate set of fully-mocked end-to-end test users that bypass Equifax entirely — identity verification, enrollment, and all subsequent credit-data retrievals (scores, reports, alerts) are served from pre-loaded fixtures on our side. Use the Equifax-backed scenarios to verify your error handling against real upstream behavior, and the mocked test users when you need a stable, repeatable path that works even if Equifax UAT is degraded.
- The cases below apply to every bureau setup — Equifax-only hosts, Equifax 3B hosts, and hosts enrolled with multiple bureaus (Equifax, TransUnion, Experian). The flow, endpoints and webhooks are the same; only the mocked end-to-end rows differ per setup.
- All demo SSNs start with
666— that's how the platform flags a request as a demo user (user.isDemo() = true). - Format SSNs as 9 digits without dashes (e.g.
666106116) and mobiles as 10 digits without dashes (e.g.5555551222). - The sandbox does not send real SMS. The SMFA link is returned directly in the
/users/smfa-send-linkresponse and shown in the response. - Use a unique number in
street2for each test run — the platform caches by an identity-data hash and reusing the same data may hit a previous run's cache.