Verifex

OFAC Screening API for SDN and Sanctions Checks

Screen names, entities, and aliases against configured OFAC and sanctions sources. Preserve match evidence, source context, and decision records for later review.

Screening evidence needs policy context

A candidate is not a confirmed identity, and a no-hit alone is not a clearance. Review the returned evidence, coverage, and candidate-set status under your own applicable policy.

OFAC Programs Covered

Configured OFAC source coverage
Publisher provenance and freshness
Candidate and source evidence
Coverage-aware screening records

Inspect current configured source coverage.

Integrate OFAC screening through the documented API.

Use the current API reference for request fields, response schemas, and decision boundaries.

Frequently Asked Questions

Something else? Talk to us.
What is OFAC screening?

OFAC screening checks a person or entity against configured sources published by the U.S. Treasury's Office of Foreign Assets Control. It returns screening evidence for your review and policy. Verifex does not determine your legal obligations or make a legal compliance decision.

How often is the OFAC SDN list updated?

Verifex syncs the OFAC SDN list regularly directly from treasury.gov. The OFAC Non-SDN Consolidated list, Sectoral Sanctions (SSI), and other OFAC programs are also synced regularly. You screen against regularly synchronized source data.

Does Verifex support candidate matching for OFAC?

Yes. Verifex retrieves candidates using matching and identity evidence. A date-of-birth, country, or identifier conflict is evidence for identity assessment. It must not silently clear or confirm a candidate.

What OFAC programs does Verifex cover?

Source coverage is configuration- and plan-dependent. Inspect the coverage returned with a screen and the current source catalog rather than assuming a fixed list is complete.

Is OFAC sanctions screening free or paid?

Plans, quotas, and source access are shown on the current pricing page. Review them before relying on a workflow in production.

How do I reduce false positives in OFAC screening?

Provide available context such as entity type, country, date of birth, or identifiers. A date-of-birth, country, or identifier conflict is evidence for identity assessment. It must not silently clear or confirm a candidate.

Does a no-hit result mean the party is clear?

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.

Start OFAC screening

Review current plans, quotas, and source coverage before production use.