Will transaction screening slow down my payment flow?

Measure the API in your own integration before setting a payment-flow latency target. For a time-sensitive flow, define a safe hold, retry, and manual-review path for unavailable or incomplete screening results.

Can I screen both sender and recipient?

Yes. You can make two sequential API calls or use the batch endpoint to screen multiple parties in one request. Both approaches return structured evidence for each screened entity.

What happens if a beneficiary is a confirmed match?

Use the served verdict, recommended action, human-review requirement, and clearance fields together. A candidate does not auto-confirm identity, and your system remains responsible for the action under its own policy.

Do you support batch file screening?

Yes. The POST /v1/screen/batch endpoint accepts up to 100 names per request, subject to plan and feature availability. Read each item's evidence-persistence state before treating a capsule as durably available.

Transaction screening before payment execution.

Screen beneficiaries and counterparties before payment execution. Structured results, monitoring notifications, and plan-gated batch support for payment workflows.

Start screening API docs

Decision contract

A zero-match result is not enough on its own.

The API returns the conditions a caller must check before treating a screening result as clear. A retrieved candidate is not a confirmed identity, and an unavailable, partial, or capped result is not complete coverage.

screening_mode: An `exact_only` result may never be read as a clearance. The mode deliberately skips fuzzy, phonetic, transliteration and typo recovery, so “no exact candidate” is not evidence the party is unlisted.
clearance_eligible: When false, no combination of other fields makes the result clean. Treat it as unresolved regardless of `risk_level`.
coverage_status: Partial or unavailable coverage cannot clear. Absence of a hit in the sources that answered says nothing about the ones that did not.
candidate_set_complete: A truncated set cannot clear. No-hit inside a capped set is not no-hit — it is no-hit in the part that was examined.

Built for payment velocity.

Payment initiation

Screen a beneficiary before payment execution, then route the served decision through your own policy. A retrieved candidate is not a confirmed identity.

Cross-border remittance

Screen sender and recipient before funds are released. Read the result's source scope and coverage status instead of assuming every list was available or included.

Crypto on/off-ramps

Integrate screening at transfer initiation for fiat-to-crypto and crypto-to-fiat flows. Keep sanctions decisions separate from any fraud or transaction-risk decision.

Payroll and treasury batch

Submit up to 100 beneficiaries per request, subject to plan and feature availability. Apply the clearance contract to every response before an automated route.

What the API delivers.

Payment-flow screening

Screen a beneficiary or counterparty before your system moves value. Measure latency against your own integration and operating requirements.

Batch screening

Submit up to 100 beneficiaries in a single request for file-based payment workflows. Ideal for payroll, remittance, and treasury batch files.

Monitoring notifications

Add entities to continuous monitoring and configure available notifications for changed screening results. Notification delivery depends on your plan and configuration.

Explainable decisions

Every match includes structured confidence scores, source attribution, and match rationale. Compliance teams can inspect — not just trust — the result.

Single and batch workflows

Use the single-screen endpoint for an individual party or the plan-gated batch endpoint for up to 100 entities per request.

Evidence status

The response exposes whether its evidence record is available, pending, or unavailable. Treat a pending or unavailable record as such, rather than assuming durable evidence exists.

Integrate in minutes.

One POST request per beneficiary. Route the structured response with its decision, review, coverage, and evidence-persistence fields.

bash

curl -X POST https://api.verifex.dev/v1/screen \
  -H "Authorization: Bearer vfx_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Beneficiary Name",
    "type": "person",
    "country": "US",
    "mode": "broad"
  }'

Start screening transactions today.

Start with the current plan allowance, then validate the screening and evidence contract in your payment flow.

Start screening View pricing