Partner asset

Sanctions-screening readiness checklist for client onboarding.

Use this one-pager when a fintech, payments, marketplace, or embedded finance client needs to evaluate whether an API-first screening layer is ready for onboarding, payouts, vendor review, or counterparty checks.

Create sandbox key

Best-fit clients

API-first teams that need a lightweight screening workflow before a heavyweight enterprise platform makes sense.

Referral trigger

The client asks how to add sanctions checks to onboarding, payouts, vendor review, KYB, or counterparty workflows.

Partner promise

Fast sandbox, readable docs, structured responses, and reviewer-friendly logs for internal compliance review.

Discovery checklist

☐ What workflow needs screening: onboarding, payouts, vendors, beneficiaries, counterparties, or periodic review?

☐ Which sources are required by the client’s policy? Verify current source status before production reliance.

☐ What should happen on CLEAR, REVIEW, and HIT outcomes?

☐ Who owns human review and false-positive handling?

☐ What evidence must be stored: call ID, decision, status, score, list metadata, reviewer notes?

☐ What volume and latency expectations matter during pilot?

☐ Is this a sandbox evaluation, production rollout, or replacement of manual lookups?

Recommended pilot plan

Create a sandbox API key.
Run 10-20 representative test cases, including clear, likely-review, and known-test-hit scenarios.
Validate response fields against the client’s policy and reviewer workflow.
Confirm list availability and freshness endpoints.
Define escalation routing, logging, and go/no-go criteria before production traffic.

Compliance note

Veridex provides screening technology and source-list data workflows. It does not provide legal advice, determine regulatory obligations, or replace a customer’s compliance program.