Evidence-first screening

Screening that proves what you checked.

Screening does not end at match / no-match. Compliance teams need to prove what was checked, when it was checked, which sources were used, why a result appeared, and how the decision can be reviewed later. Verifex preserves that evidence for every screening.

Start in the dashboard. Integrate the API when the workflow is proven.

Decision record

Evidence, not a black box

Reviewable
Coverage
Successful, unavailable, and stale sources remain explicit
Evidence
Publisher context and match reasoning travel with the result
Decision
Actionable, review, or clear semantics stay distinguishable
Audit
The screening state can be reconstructed later

Built around the reviewer

The right workflow starts with the decision you need to defend.

01

Compliance and AML teams

Teams that must defend onboarding and monitoring decisions to auditors and regulators.

02

Fintechs and payment companies

Businesses that screen customers and recipients and need a retrievable record for each check.

03

Auditors and reviewers

People who need to reconstruct a past decision: which source version matched and why.

Clear scope

What the workflow does

  • Returns the evidence behind a result, not just pass/fail.
  • Records input, normalized query, source context, timestamp, matches, confidence, and request ID.
  • Lets you export a screening record for an AML file or case review.
  • Distinguishes risk records (sanctions, PEP, watchlists, debarment) from company/KYB and ownership data.

Honest boundaries

What it does not claim

  • Does not say a person is 'clean'. A no-hit alone is not a clearance. Treat a result as clear only when Standard Screening is clearance-eligible, source coverage is complete, the candidate set is complete, and the result has zero matches. Otherwise the result remains unresolved and needs your policy or review.
  • Does not replace your compliance team's judgment or policy.
  • Does not provide legal advice or guarantee regulatory outcomes.

One workflow, two entry points

Prove the operation before you automate it.

The dashboard and API share the same screening semantics, so an operational pilot can become a production integration without redefining the decision.

No-code dashboard

Run a screening in the dashboard and save or export the resulting evidence record — no code required.

REST API

Call the API and store the returned request ID; retrieve the full evidence record later for audit or case review.

curl -X POST https://api.verifex.dev/v1/screen \
  -H "Authorization: Bearer vfx_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"name": "Rosneft", "type": "entity"}'
Evidence by design

The result is useful now. The evidence makes it defensible later.

Each result can include the original input, normalized query, source context, timestamp, matches, confidence, request ID, and exportable evidence. Months later, you can retrieve the record and show exactly what was checked and why a result was returned.

Explore the evidence record

Questions before integration

Read the boundary conditions, not just the feature list.

What does 'evidence-based screening' mean?

It means a screening response exposes the candidate, coverage, source, decision, and evidence state needed for review. A durable Evidence Capsule is separately reported as available, pending, or unavailable.

What is an Evidence Capsule?

An Evidence Capsule is a structured, point-in-time record of a screening decision: input, normalized query, match rationale, source metadata, engine version, and a request ID, stored and retrievable by ID. It supports audit review and decision reproducibility.

Does a clear result mean the person is safe?

No. A no-hit alone is not a clearance. Treat a result as clear only when Standard Screening is clearance-eligible, source coverage is complete, the candidate set is complete, and the result has zero matches. Otherwise the result remains unresolved and needs your policy or review. Verifex provides screening infrastructure and data-derived results, not legal or compliance advice.

How long are records retained?

Screening and canonical decision records use the current ten-year default retention policy. This describes the service implementation, not a universal legal requirement or a substitute for a customer's retention policy.

Move from reading to evidence

Run a real workflow and inspect what comes back.

Verifex provides screening infrastructure and data-derived results, not legal or compliance advice. A no-hit alone is not a clearance. Treat a result as clear only when Standard Screening is clearance-eligible, source coverage is complete, the candidate set is complete, and the result has zero matches. Otherwise the result remains unresolved and needs your policy or review.