Frequently Asked Questions

CheckSanction is an Sanction/KYC screening and compliance operations platform that helps organizations screen individuals, companies, and beneficial owners against selected compliance lists, manage review cases, integrate screening by API, and maintain audit-ready records.

No. CheckSanction includes sanctions and watchlist screening, list control, API integration, case management, approval workflow, audit logs, and reporting. It is designed as a compliance operations platform, not only a search screen.

CheckSanction is designed for banks, exchange houses, fintechs, real estate companies, corporate service providers, auditors, compliance consultants, DNFBPs, and businesses that need Sanction screening or API-based compliance checks.

Yes. CheckSanction can support screening for individuals, companies, customers, vendors, directors, shareholders, and beneficial owners depending on the customer’s configuration and plan.

Yes. Alongside the screening engine score, an AI assistant independently reviews the case — including checker-uploaded documents and adverse media — and provides a separate, explainable risk score and recommendation to help your checkers. The human always makes the final decision.

No. AI is advisory only. It never makes the final decision; it provides a recommendation, reasoning and confidence that the checker can accept or override. Every AI run is logged and auditable.

Yes. AI can run on a hosted provider, on-premise, or your own AI API configured per organization. You can also disable AI entirely (no-AI mode) and use only the screening engine and human workflow.

Yes. Each organization can use the CheckSanction screening engine, its own external screening provider, or both — results are normalized and shown together.

CheckSanction can be configured to screen against sanctions lists, watchlists, PEP lists, adverse media sources, internal watchlists, local lists, and global compliance lists depending on the customer’s plan and enabled configuration.

Yes. Organizations can self-manage which screening lists are used for their checks. The same list configuration can be applied to both portal users and API screening, helping maintain a consistent screening policy.

Yes. CheckSanction is designed to support Arabic and English names, spelling differences, aliases, and regional naming patterns. This helps organizations screen names more effectively across different markets.

CheckSanction is designed to provide clearer match information, match scores, risk indicators, source details, and supporting evidence so compliance teams can review possible matches more efficiently.

Yes. CheckSanction can support tenant-specific internal watchlists so organizations can screen against their own internal risk lists in addition to external compliance lists.

Yes. When a possible match is found, users can create a review case and move it through a compliance workflow.

Yes. CheckSanction can support maker-checker workflows where one user creates or requests a decision and another user reviews, approves, rejects, escalates, or asks for clarification.

Yes. Cases can be designed with Level 1, Level 2, and Level 3 review stages depending on the organization’s approval workflow.

Final approved, rejected, or closed cases should remain read-only to preserve audit integrity.

Yes. CheckSanction provides API endpoints for screening and tenant list access management. This allows external systems to perform screening and manage list configuration through secure API calls.

CheckSanction can integrate with onboarding portals, CRM systems, ERP systems, compliance workflow tools, internal business applications, and other systems that can call REST APIs.

API calls use an API key in the request header. The API key identifies the client or organization and controls what actions are allowed.

Yes. API screening can include a client_reference so the external system can link the screening result back to its own customer, case, or transaction record.

Yes. Screening responses can include a screening_id, which can be used for audit, reference, and follow-up review.

Yes. CheckSanction is designed to keep audit logs for screenings, API calls, list access changes, user actions, and case decisions where configured.

List access changes can log the old enabled lists, new enabled lists, user or API key details, IP address, user agent, timestamp, and success or failure status where available.

Yes. CheckSanction helps maintain screening evidence, case history, and audit records that can support internal reviews, compliance checks, and regulatory reporting needs.

No software can guarantee regulatory compliance by itself. CheckSanction helps organizations implement and evidence Sanction screening controls, but each organization remains responsible for its own compliance program, policies, and regulatory obligations.

Yes. CheckSanction can be offered as a SaaS platform where users access the system through a web portal and API.

Yes. For banks, regulated entities, and larger organizations, CheckSanction can be deployed in a private environment or on-premise model, subject to commercial and technical agreement.

Yes. CheckSanction can support a local country SaaS partner model where a local partner operates a country-specific Sanction screening platform powered by CheckSanction.

CheckSanction is configurable for local and global screening policies. It can support country-specific list selection and audit requirements depending on the enabled lists, deployment model, and customer configuration.

A Free Forever plan can be offered for small users with limited monthly checks, basic screening, and limited report/history features.

The Starter plan is suitable for small businesses that need individual and company screening, standard reports, and basic user access.

API access is typically available from the Business plan and above, depending on the commercial configuration.

Yes. Enterprise pricing is available for banks, large corporates, regulated institutions, country partners, API-heavy users, and on-premise/private deployments.