Test Data
Pre-built payloads for testing every verification outcome in the staging environment. Each payload triggers a specific result from mock providers.
Always include external_reference in your test payloads. This enables idempotency testing and correlates requests with your internal records.
Company Verification
Clean company (Pass)
Expected result:
Company with screening hits (Refer)
Expected result:
The Refer verdict is triggered by the PEP match on the director. The company itself screens clean.
Company registry failure (Fail)
Expected result:
The mock registry returns “company not found” for INVALID999. Use this to test how your application handles verification failures.
Person Verification
Clean individual (Pass)
Expected result:
Individual with PEP match (Refer)
Expected result:
The PEP match triggers a Refer verdict. Your application should route this to a compliance reviewer.
Individual with sanctions hit (Fail)
Expected result:
Sanctions hits produce an immediate Fail verdict. Your application should halt onboarding and escalate to your compliance team.
Screening
Clean screening
Expected result:
Screening with matches
Expected result:
Important notes
- Staging results are mock data. The match scores, categories, and sources are synthetic. They test your integration logic, not real screening accuracy.
- Pattern matching is case-insensitive.
PEPMatch, pepmatch, and PEPMATCH all trigger the same PEP hit.
- Names that don’t match a pattern default to clean. Any name without a recognized trigger string returns a Pass with no screening hits.
Next steps