Screen at your chosen checkpoint
Call the screening API from customer onboarding or a party-review workflow. Keep screening outcomes and technical failures separate in your application logic.
Sanctions screening API for fintech and payment teams
Screen customers as part of your onboarding flow.
Bring sanctions screening into customer onboarding and payment-party review. Give engineers a practical API and operations teams the evidence behind a potential match.
API and compliance dashboard included in every plan.
SanctionsKitIllustrative workflow
Customer onboarding
Known identity
Selected lists
Review path
Completed screeningContinue your policy workflow
Potential matchInvestigate in the dashboard
Identity verification and transaction monitoring remain separate.
Built around your work
Connect the integration to the investigation.
A potential match can travel from an onboarding system to an operations queue in seconds, but a reviewer still needs the right context. SanctionsKit carries the selected coverage, match explanations, and source references with the result so teams can investigate the same evidence.
Make exceptions reviewable
Route potential matches with the supporting fields and conflicts. Let reviewers record their reasons without changing the underlying screening outcome.
Understand repeat-screening costs
Use idempotency keys for safe retries and plan for completed subject screenings. Monthly caps avoid automatic overages as your workflow expands.
A practical use case
A new customer reaches the sanctions checkpoint.
For a wallet, payments platform, or fintech onboarding flow, screening belongs at the point where your policy requires it. Your system already has the identity details to submit.
The review challenge
An ambiguous response creates an ambiguous next step for the customer-facing application and the operations team.
How SanctionsKit helps
Keep potential matches, completed no-match results, and incomplete checks separate. Give operations the screening reference and evidence needed to investigate.
- 01
Define the party to screen
Map the customer or counterparty details your system actually knows to the subject contract. Keep identity verification as a separate step.
- 02
Choose coverage and handle outcomes
Select the sources your team needs, check availability, and create explicit paths for potential matches, no matches, and errors.
- 03
Preserve the handoff
Pass the screening reference into your operations workflow so reviewers can investigate and record a decision against the same result.
Evaluate the fit
Screening questions for fintech & payments.
Is this a transaction monitoring system?
SanctionsKit screens submitted subjects against selected sources. It does not evaluate transaction behavior, detect payment fraud, or replace a transaction monitoring system.
Can we use the same integration for customers and counterparties?
Yes. Model each person or organization as a subject and choose the relevant coverage for that screening. Your application determines where screening belongs in the payment journey.
See SanctionsKit in action
Explore sanctions screening for your onboarding flow.
Try the interactive demo with synthetic examples. Compare plans for your team’s screening volume.