Settings: Sandbox Profiles: Overview

The default behavior of the sandbox environment is to approve every application that it receives. Sandbox Personas allow you to coerce specific service responses out of the sandbox environment. By using Sandbox Entity Tokens to trigger flags in our workflow, we can trigger Manual Reviews and Denials. 

To visit the Sandbox Profiles settings page, follow the navigation path:

1. Click the Settings option on the left-side menu bar. 
2. Click Sandbox Profiles from the Settings menu.

From the Sandbox Profiles page, you can add new profiles, edit or delete existing ones, or create new profiles by duplicating an existing profile.

This article will cover the following topics:

• How profiles work
• Adding a new profile
• Managing profiles

How profiles work

In the below example, we're looking to trigger a "Fraud Warning" tag. The threshold rules for this tag are: set tag if the ID Analytics ID Score is 850 or higher.

However, a Sandbox API call will always return a hardcoded ID Analytics ID Score of 500.

Therefore, to coerce the "Fraud Warning" tag, a Sandbox Profile would need to be created that coerces a ID Analytics ID score of 850 or above. Here is a configuration of the profile that coerces an ID Analytics ID score of 900:

In this same example, the identifier is the SSN "000-00-0001." This would be passed in the body of the Sandbox API call, as shown in the example below.

{
    "name_first" : "John",
    "name_last" : "Smith",
    "document_ssn" : "000000001",
    "address_line_1" : "41 Elizabeth St."
    "address_line_2" : "St. 501",
    <...>
}

Adding a new profile

1. Click the Add Profile button to add a new persona. 
2. With the Add Sandbox Profile modal open, configure your profile by filling in the following information. 
   • Name - Required - The name of the profile as it appears on the Sandbox Profiles settings page to distinguish it from other profiles. The name does not affect the functionality of the profile.
   • Description - Optional - A brief summary of the profile's purpose or its intended use. This field can provide additional context for your team but does not affect functionality.
   • Identifier - Required - A unique value used to reference the profile and activate the sandbox profile during a Sandbox test. When running a Sandbox request, the identifier must be supplied in the body. Available identifiers are: Zip Code/Postal Code, SSN, Last Name, Business FEIN, National ID, Business Registry ID.
   • Associate with Workflows - Optional - Connect a profile with the Workflows it's intended to be used with. This helps maintain clarity on which Workflow a profile was created for, but does not affect functionality.
   • Attribute - Required - Choose the attribute you're looking to test and configure the specific attribute value that should be returned, which can drive a specific tag or outcome to be returned. More than one attribute can be selected per profile, and attributes across different Workflows can be selected.
3. Once the profile is configured, click Save to complete creating the profile.

Managing profiles

Once a profile has been created, it can be edited, deleted, or duplicated to easily create new profiles.

To access these options, click the ⋮ menu ("More Options" menu) to the right of a profile.