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.

• Dashboard
• Basics

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.

• Income and Employment (VOIE)
• Employment History (VOE)
• Direct Deposit Switch (DDS)
• Paycheck Linked Loans (PLL)
• Insurance Verification

Refreshes

Data refreshes will automatically succeed if the goodlogin/goodpassword credential combination is used. To test for a failed refresh, use the goodlogin/mfa credential combination from the initial verification. This will result in the refresh having the mfa_error status.

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 goodlogin 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.

VOIE and VOE

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

VOIE (Retirement, Disability and Veterans Benefits)

Retirement Benefits, Disability Benefits and Veterans Benefits test scenarios for the VOIE product are available. Retirement and Disability Benefits scenarios will return a sample Social Security Administration Benefits Verification Letter instead of a paystub. Veteran Benefits will return a VA Benefit Summary Letter if Veteran Affairs provider is selected or a retirement paystub if DFAS myPay provider is selected.

Once the Truv bridge opens, search for the desired benefit type, select a login method and use the successful login goodlogin and goodpassword credentials.

Insurance Verification

The credentials below are eligible for Insurance Verification product.

Native reset for authentication

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

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

Multi-factor authentication and re-verification

For the embedded Truv flow and Orders, borrowers may be required to go through MFA during authentication. The re-verification during an automated refresh could also require MFA and could fail as a result. For Orders, the borrower would receive a notification to re-verify. For the embedded flow, you would need to implement the appropriate steps to contact the end-user.

In order to test this scenario, please use MFA credentials in the original verification and trigger a data refresh via Truv's API.

For additional troubleshooting, view the Data Refresh guide for more information. For Orders, please use the Data Refresh endpoint within Orders.

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.

• Income and Employment (VOIE)
• Employment History (VOE)
• Direct Deposit Switch (DDS)
• Paycheck Linked Loans (PLL)

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.

📘

Note

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