Logistics & trade compliance
Screen every party before you move freight.
Logistics teams transact with carriers, brokers, vendors, customers, and payment recipients — any of which can be sanctioned or owned by sanctioned parties. Verifex screens them against sanctions, PEP, and watchlist sources and keeps an audit-ready record of each check.
Start in the dashboard. Integrate the API when the workflow is proven.
Decision record
Evidence, not a black box
Built around the reviewer
The right workflow starts with the decision you need to defend.
Freight forwarders and 3PLs
Screening carriers, agents, and consignees across trade lanes.
Carriers and brokers
Checking counterparties and customers before accepting business.
Procurement and AP teams
Screening vendors and payment recipients before releasing funds.
Clear scope
What the workflow does
- Screens companies and people against sanctions, PEP, watchlist, and debarment sources.
- Covers carriers, brokers, vendors, customers, and payment recipients.
- Adds ownership (UBO) context to catch indirect sanctions exposure.
- Records each check as retrievable evidence with a request ID.
Honest boundaries
What it does not claim
- Does not classify goods, screen HS codes, or provide export-licensing determinations.
- Does not certify a counterparty as cleared for trade.
- Does not provide legal or compliance advice.
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
Screen a carrier, broker, vendor, or recipient by name in the dashboard and export the record for your trade-compliance file.
REST API
Screen counterparties via the REST API at onboarding or before payment, and store request IDs against your records. SDKs for Python, Node.js, Go, and Rust.
curl -X POST https://api.verifex.dev/v1/screen \
-H "Authorization: Bearer vfx_your_api_key" \
-H "Content-Type: application/json" \
-d '{"name": "Acme Logistics LLC", "type": "entity"}'The result is useful now. The evidence makes it defensible later.
Each counterparty check produces a record of what was screened, which sources matched, a timestamp, confidence, and a request ID — point-in-time evidence you can keep in a trade-compliance file and produce during an audit.
Explore the evidence recordQuestions before integration
Read the boundary conditions, not just the feature list.
Who should logistics teams screen?
Carriers, brokers, freight agents, consignees, vendors, customers, and payment recipients — anyone you transact with — plus, where relevant, their beneficial owners under the OFAC 50% rule.
Does Verifex handle export control classification?
No. Verifex screens parties against sanctions, PEP, and watchlist sources. It does not classify goods or provide export-licensing decisions; pair it with your trade-compliance process.
Can we screen before releasing a payment?
Yes. Many teams screen payment recipients via the API as a pre-payment check and store the request ID against the transaction.
Does a clear result mean the party is safe to use?
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.
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.