Testing
How to test your VerifiMe integration using the staging environment
Use the staging environment to test your integration end-to-end before going live. The staging environment mirrors production with a few differences to make testing easier.
See Environments for staging URLs.
Staging Differences
PEP / Sanctions Screening
Real PEP and sanctions screening is not performed in staging. See PEP and Sanctions Screening for how screening works in production. Instead, the outcome is controlled by the customer's middle name entered during data entry. Matching is case-insensitive.
| Middle name contains | Result |
|---|---|
pep | Customer flagged as a Politically Exposed Person |
sanction | Customer flagged as sanctioned |
| Neither | Clean, no flags raised |
For example, Jane Pep Smith produces a PEP flag; Jane Smith raises no flags. A middle name containing both pep and sanction raises both flags simultaneously.
Phase 2 Processing
The staging environment is integrated with an external DVS testing infrastructure that is operated independently of VerifiMe. Because test data is unlikely to match real identity records, verifications in staging are routinely flagged for manual review rather than completing automatically.
The Force Verify endpoint bypasses this review process, allowing your integration testing to proceed without waiting for manual intervention. If the RISK_ASSESSMENT_UPDATED webhook has not arrived after 5 minutes, use the endpoint to advance the verification manually.
This mechanism is available in staging only. Production does not provide an equivalent.