Every decision. Held together.

Evidence Capsule packages the input, match reasoning, source freshness, request ID, reviewer state, and exportable JSON behind a screening decision.

Start screening free View API docs

Decision-support evidence only. Verifex does not provide legal advice or regulatory approval.

Evidence Capsule

illustrative preview

Request ID: 9f2a4c7e1b3d5a8c
Capsule ID: 9f2a4c7e1b3d5a8c
Verdict: possible_match
Coverage: complete
Hash version: 2
Screened at: 2026-05-12 14:32 UTC

OFAC

healthy

Illustrative values, not a live source-health display.

Input

Name, type, country

Screen

Lists, sources, mode

Explain

Match reasoning

Preserve

Capsule ID + hash

The decision trail in one artifact.

A screening result is useful in the moment. An Evidence Capsule keeps the decision explainable after the alert moves through review, audit, and partner diligence.

Original input

Name, entity type, jurisdiction hints, mode, normalized query, and the timestamp of the screening request.

Match reasoning

Candidate names, source list, match type, confidence, score breakdown, risk level, and recommended action.

Source snapshot

The exact list families checked, sync timestamps, source freshness, source health, and version context.

Decision lineage

Reviewer action, notes, capsule hash, request ID, and fields your case or CRM system can store.

Readable for analysts. Structured for systems.

The capsule is designed to be reviewed by a human and stored by software. Keep the full JSON and any retained content-integrity hash in your own case system.

Request and capsule identifiers

Point-in-time source freshness

Structured match rationale

Reviewer timeline fields

Content-integrity hash

JSON export for downstream storage

FieldValueWhy it matters

InputAlejandro Garcia LopezPerson, MX, broad mode

Normalized queryalejandro garcia lopezLatin script, accents removed

CandidateGARCIA LOPEZ, AlejandroIllustrative candidate, identity review required

DecisionPossible matchHuman review required

Source stateRecorded per sourceCoverage and warnings stay explicit

Integritysha256:a1b2c3d4...Content-integrity checksum, not independent attestation

json

{
  "illustrative": true,
  "capsule_schema_version": "1.0",
  "capsule_id": "9f2a4c7e1b3d5a8c",
  "screened_at": "2026-05-12T14:32:18.000Z",
  "input": {
    "name": "Alejandro Garcia Lopez",
    "entity_type": "person",
    "country": "MX",
    "date_of_birth": null
  },
  "verdict": "possible_match",
  "human_review_required": true,
  "recommended_action": "manual_review",
  "screening_contract": {
    "screening_mode": "standard",
    "clearance_eligible": false,
    "coverage_status": "complete",
    "candidate_set_complete": true,
    "sources_withheld_unavailable": []
  },
  "matched_candidates": [{
    "name": "GARCIA LOPEZ, Alejandro",
    "source": "OFAC",
    "matched_name": "GARCIA LOPEZ, Alejandro",
    "identity_evidence": [{ "field": "date_of_birth", "status": "not_available" }]
  }],
  "audit_log_available": true,
  "capsule_hash_version": "2",
  "capsule_hash": "sha256:a1b2c3d4...",
  "disclaimer": "Evidence Capsules support audit review; they are not legal advice."
}

The export is explicit, not mysterious.

Capsules expose the information your team needs to reconstruct what happened at screening time. This is an illustrative shape, not a literal response or a live screening record.

Integrity

Content-integrity hash

Freshness

Source sync time

Lineage

Candidate and list family

Storage

JSON export

Works in the dashboard and the API.

Evidence Capsules move with your decision workflow instead of sitting as a detached export.

Dashboard review

Open a screening from History and export the capsule when an analyst or partner asks for evidence.

Open history

API retrieval

Fetch a screening export or capsule by ID from your own workflow using a bearer token.

View docs

Case handoff

Attach capsule IDs to alert queues, case systems, CRM notes, Slack alerts, or data warehouse rows.

See integrations

Decision-support, not certification.

Evidence Capsules preserve structured screening context for audit review and internal controls. They do not certify counterparties, approve transactions, or replace a regulated business's risk-based compliance program.

Operational reality

Use the capsule to preserve what Verifex knew at screening time. Your compliance team still owns policy thresholds, review outcomes, escalation rules, and final decisions.

Frequently asked questions

What is an Evidence Capsule?

An Evidence Capsule is a structured JSON record that preserves the context behind a screening decision: input, candidates, identity evidence, source and coverage context, decision fields, timestamps and a content-integrity hash.

When is an Evidence Capsule created?

A completed screen receives an evidence-persistence state. A capsule can be available immediately, pending while a durable record is written, unavailable when there is an audit gap, or historical-unknown for a pre-capsule record. The API makes those states explicit.

How do I retrieve one?

From the dashboard, open a screening from History and download the JSON. From the API, use the screening export or evidence capsule endpoints with your bearer token.

Can it be tampered with?

The capsule includes a deterministic SHA-256 content-integrity hash. A recipient can compare a retained hash with a copy to detect changed content. It is not an external timestamp, independent attestation or a guarantee of immutability.

Does it replace compliance documentation?

No. Evidence Capsules are decision-support records for audit review and internal controls. Final policy decisions and regulatory obligations remain with your compliance team.

Preserve evidence with every screening.

Start in the dashboard, then pull capsule IDs and JSON exports into your own systems when you are ready.

Start screening free Explore API docs