The sandbox environment is your safe space to test and validate API integrations before going live. All operations performed here are isolated from production data.
Accessing the Sandbox
Receive Credentials
You’ll get a welcome pack containing:
- API access keys
- Code examples
- Test data sets
Testing Guidelines
Test Data Matching Rules
Test Data Matching Rules
- Family name matching is the primary identifier
- Matching is case-insensitive
- Use middle name “
passall” to force a successful match
Special Test Cases
Special Test Cases
The test data includes special markers that trigger specific responses:
Available Entity Profiles
Entity profiles determine the combination of checks performed during verification. Choose based on your regulatory requirements and jurisdiction.
- Basic Profiles
- Safe Harbor Profiles
- KYB Profiles
- International Profiles
| Profile | Check Types | Description |
|---|---|---|
default | two_plus,id,pep_media,idvalidate | Standard verification suite |
gov_id | blacklist,id_only,pep,idvalidate | Government ID focused checks |
gov_id_media | blacklist,id_only,pep_media,idvalidate | Enhanced government ID checks with media screening |
Profile Selection
- KYC profiles are designed for individual verification
- KYB profiles are specifically for business-related verifications
- Safe Harbor Plus profiles are required for jurisdictions with mandatory address verification (e.g., New Zealand)
Testing Error Scenarios
Credit Header Failures
Set street address to either:
- “Equifax”
- “Experian”
Non-ID Check Failures
Set middle name to “FailNonID” to:
- Force fail all non-ID checks
- Only evaluate ID verification
Ensure ID-related details (name, DoB, ID numbers) are correct for proper testing.
All data sources in the sandbox environment are stubbed and may return randomized source information for testing purposes.