Skip to main content
A Test Persona is a pre-configured individual or business profile available in our sandbox environment for testing purposes.

​
Successful Match Testing

To verify a successful match:
  1. Select a Test Persona from the test data spreadsheet
  2. Enter the information exactly as shown in the spreadsheet
  3. The required information depends on your Recipe configuration
A Recipe defines the set of verification checks applied to a customer’s profile. See Entity Profiles/Recipes for available configurations.

​
Failed Match Testing

To simulate a failed match:
  1. Select a Test Persona
  2. Modify one or more values from their original data
// Example: Modifying first name
originalName: "Bobby"
modifiedName: "Bobble" // This will cause a match failure
Avoid modifying the Family Name field as it’s used as a primary key for Test Personas and may cause unexpected behavior.

​
Dynamic Test Personas

Unlike static Test Data, Dynamic Personas allow you to simulate outcomes with custom information.

​
Force Successful Matches

Use any of these methods to ensure a successful match:
middleName: "passall"  // Forces all checks to pass
middleName: "onepass"  // Forces one data source to pass

​
Specialized Testing Cases

Non-ID Check Failures

Set otherName: "FailNonID" to pass document checks but fail other verifications.
Ensure document-related details (name, DoB, ID) match the Test Data exactly.

Credit Header Failures

To simulate provider-specific failures:
streetName: "77 Equifax Street"   // Equifax failure
streetName: "123 Experian Street" // Experian failure

​
PEP, Fraud, and Sanctions Testing

1
  1. Select a Test Persona marked with PEP, Sanctions, or Fraud flags
  2. Ensure your Recipe includes PEP checks
  3. Execute the verification process
PEP/Sanctions matches are pre-configured and static. Use Test Personas marked as SKIP to bypass these checks and test with external services instead.