Overview

Test and try out various scenarios using Truv. These features require no code for you to run. Get started with these sample integration solutions.

The emulator lets you view the Truv experience as a user. Each sandbox scenario offers a user context and situation for specific workflows. Simulate Truv integrations and use cases with the information from the sections below.

Truv Emulator

Access the Truv Emulator through the Truv Dashboard. This is a simulation of the Truv workflow. Experience Truv as a user and navigate different workflows and situations.

At the top, you can toggle Sandbox mode for testing various user scenarios. View the Sandbox scenarios section for additional details.

Learn more about the Truv Dashboard in the guides below.

Sandbox scenarios

Truv offers testing with our products with different user scenarios. The credentials below let you preview various user journeys. Use these values as login information to proceed with the scenario. In case you want to provide a SSN for an applicant, you have to use the SSN attached to the particular credentials scenario.

Supported scenarios and credentials

Test unique user scenarios with the appropriate credentials. View the available scenarios for the Truv products below. Each section describes the eligible credentials for the supported products.

All

Every Truv product is eligible for testing the scenarios in this section. Use the table below for the appropriate credentials for testing each scenario.

Username	Password	SSN	Scenario
`any`	`any`		Login Error
`goodlogin`	`goodpassword`	`991-91-9991`	Successful login with complete data returned
`goodlogin`	`mfa`	`991-91-9991`	Multi-factor authentication login, use code `12345` NOTE: Using any other code results in an MFA error.
`goodlogin`	`longcheck`	`991-91-9991`	Successful login with additional wait time for completion, about 30 seconds
`error.user`	`login_error`		Incorrect login and password
`error.user`	`mfa_error`		Issue with multi-factor authentication
`error.user`	`account_locked`		Locked account, requires provider unlock
`error.user`	`no_data`		No data found in the provider account
`error.user`	`unavailable`		Provider is going through maintenance and isn't available
`error.user`	`error`		Generic login error

Additional login fields

Providers may also use specific fields for login information. The points below cover these credentials for testing successful scenarios in Truv. These are the same scenarios as the good login credentials from the table above.

Phone number - (111)111-1111
Email - [email protected]

VOIE, VOE, DDS, PLL

These four products are available for testing the credentials below. Insurance Verification isn’t supported at this time for these scenarios. Use the values in this table for the products, VOIE, VOE, DDS, and PLL.

Username	Password	SSN	Scenario
`wronglogin`	`wrongpwd`		Page under construction
`fulltime`	`goodpassword`	`2211`	Full time salesperson
`hourly.part-time`	`goodpassword`	`666382548`	Hourly part-time worker
`partial.data`	`goodpassword`	`2222`	Partial data returned, payroll provider incomplete
`military`	`goodpassword`	`9988`	Military MyPay data
`error.user`	`config_error`		Incorrect organization ID, failed data import
`multiple.employments`	`goodpassword`		Multiple employments with different employers
`multiple.employments2`	`goodpassword`	`7740`	Multiple employments with the same employer
`nonactive`	`goodpassword`	`1890`	Employment with an `end_date` value
`unemployment`	`goodpassword`	`9988`	Unemployment benefits with weekly pay frequency

VOIE and VOE

The credentials below are eligible for both VOIE and VOE products. The values below are for the supported scenarios.

Username	Password	Scenario
`goodlogin.shift`	`goodpassword`	Gig worker, including earned wage access (EWA)

Insurance Verification

The credentials below are eligible for Insurance Verification product.

Username	Password	Scenario
`goodlogin`	`optionless_mfa`	Multi-factor authentication login without option selection, submit code `12345` for successful scenario
`goodlogin`	`good_commercial`	Successful login with commercial policies
`goodlogin`	`good_flood`	Successful login with flood and home policies
`goodlogin`	`good_expensive`	Successful login with dwelling coverage premiums more than 2.45x of `goodpassword`
`goodlogin`	`good_underinsured`	Successful login with higher home Coverage A limit
`goodlogin`	`good_home`	Successful login with home policy only
`goodlogin`	`good_auto`	Successful login with auto policy only
`goodlogin`	`good_partial_auto`	Successful login with auto and home policies, auto policy is partial
`goodlogin`	`good_landlord`	Successful login with landlord policy
`goodlogin`	`good_no_policies`	Successful login with no policies or policy-related data, returns profile-related data
`goodlogin`	`good_complete`	Successful login with different combinations of policies, vehicles, dwellings, coverages, and endorsements
`goodlogin`	`adams`	Successful login with realistic flood and home policies, static data matches PDF dec pages
`error.user`	`account_unactivated`	Error case with locked account. Requires provider account activation.

Native reset for authentication

Truv Sandbox supports authentication reset workflows in supported implementations. Follow the process below.

Enter values in requested fields
Use goodlogin credentials for verification during MFA

Multi-factor authentication and re-verification

For Tasks and Orders, MFA and re-verification are connected to the original configuration. Data refreshes use the original configuration for MFA and re-verification and cannot proceed with the additional prompt. When testing, these configurations aren't compatible with data refresh updates. For additional troubleshooting, view the Data Refresh guide for more information.

Payroll data source testing

The Truv products below collecting payroll data have their own supported testing connections. View the Supported companies for testing section when using payroll as a data source in the supported sandbox environments.

Supported companies for testing

The list below contains the available information for Mapping. These companies return a company_mapping_id value for integration.

Facebook - Workday
Bank of America - Company with single sign on
Kroger - Custom integration
Fannie Mae - ADP
Freddie Mac - Workday

📘
Note
In the emulator, only sandbox companies have the correct company_mapping_id value. Production environments have all valid mapping information values for many large US-based organizations and data providers.

Document processing testing

When testing for Integrating Document Processing, the PDF downloads in the list below cover different scenarios for sandbox use.

Upload the documents for testing different sandbox response results. Pay statements and tax documents return data when successful. Unsuccessful uploads respond with status updates. Users and applicants require both first_name and last_name values for testing.

Successful documents - Most recent paystub, Next recent paystub, First paystub, W2
1099 tax forms - 1099-DIV, 1099-G, 1099-INT, 1099-MISC, 1099-NEC, 1099-R, SSA-1099

📘
Note
For 1099 tax documents, Truv supports parsing for formatting from any year after 2021. This includes the following 1099 forms.

1099-DIV, 1099-G, 1099-INT, 1099-MISC, 1099-NEC, 1099-R

Suspicious document detection

Documents from uploads may have fraudulent, consistent, or unacceptable data. When encountering these issues, mark specific instances for review. Prevent malicious activity with additional analysis and attention.

View the table below for various scenarios and PDF examples.

Scenario	Description	Downloads
Tampered documents	Information is falsified or manipulated	Tampered 1, Tampered 2, Tampered 3
Different Social Security Numbers	Personal information is inconsistent	SSN 1, SSN 2, SSN 3
Different company names	Company information is inconsistent	Company 1, Company 2, Company 3
Different applicant names	Personal information is inconsistent	Applicant 1, Applicant 2, Applicant 3
Documents without data, or with invalid data	Information is missing or unable to be parsed	No data 1, No data 2, No data 3

📘
Note
Test scenarios use the file name to return results. Testing ignores the file contents when in the sandbox.