Compliance questions, answered clearly.

WIDTH is an all-in-one compliance and risk decision intelligence platform. It connects customer onboarding, screening, monitoring, investigations and case management within one operational environment.

This shared approach helps compliance teams work from connected customer records, apply consistent review processes and maintain clearer evidence across the customer lifecycle. Explore the WIDTH Platform.

All-in-one compliance means managing related compliance workflows through one connected platform instead of several disconnected tools. With WIDTH, onboarding information can support screening, monitoring, investigations and case decisions without repeatedly moving records between separate systems.

WIDTH is designed to address fragmented compliance workflows, repeated data entry, inconsistent reviews, disconnected alert queues and difficult audit preparation. It gives teams a clearer operational view across onboarding, screening, monitoring and investigations.

WIDTH is designed for regulated organisations and compliance teams managing customer due diligence, financial crime controls, risk reviews and investigations. Typical users include compliance analysts, operations teams, investigators, reviewers, managers and Money Laundering Reporting Officers.

No. AML monitoring is one part of the wider WIDTH platform. WIDTH also supports KYC and KYB onboarding, screening, fraud detection, risk intelligence, case management and audit-ready compliance workflows.

WIDTH supports compliance operations across banking, payments, insurance, fintech, digital assets, remittance, professional services and other regulated sectors. Each implementation can reflect the organisation’s customer types, risk policies and operating model. View WIDTH industry solutions.

The WIDTH Platform brings together onboarding, customer and entity screening, AML monitoring, fraud detection, risk intelligence, investigations and case management. Organisations can connect these capabilities through a shared compliance workflow rather than maintaining separate operational records.

Yes. Organisations can begin with the WIDTH capability that addresses their immediate requirement and expand into other modules as their compliance operations develop. The platform model allows connected modules to share relevant customer and case context.

WIDTH keeps relevant identity, business, screening, transaction and case information connected to the customer record. Therefore, a review does not need to begin with analysts manually reconstructing context from unrelated tools.

WIDTH supports configurable workflows for different customer types, review stages and risk outcomes. The specific configuration depends on the organisation’s policies, operating model, data sources and approval requirements.

Yes. WIDTH can bring together customer, entity, screening, transaction and relationship signals to support risk-based routing and review. Compliance teams remain responsible for defining the policies and governance applied to those decisions.

WIDTH maintains decision context, review activity and supporting evidence within connected compliance records. This helps teams retrieve the information behind an onboarding, monitoring or investigation decision without rebuilding the history manually.

KYC identifies and assesses individuals, KYB verifies businesses and ownership, while AML monitoring reviews activity after onboarding for risk that may require investigation. In WIDTH, these workflows can use connected customer and entity records so onboarding context can inform later monitoring and review. Explore the WIDTH Platform and WIDTH Onboarding.

Risk scoring is a structured way to assess the level of compliance risk associated with a customer, business, transaction or relationship. A score can use factors such as identity, ownership, geography, screening results, transaction behaviour and connected relationships. The organisation defines how those factors affect review or escalation. See WIDTH Platform capabilities.

A risk-based approach applies stronger or different controls where the assessed risk is higher, instead of treating every customer and transaction identically. This can influence onboarding checks, review depth, monitoring rules and escalation paths. WIDTH supports configurable workflows that organisations can align to their own policies and risk model. Explore WIDTH Onboarding.

Authoritative reference: FATF Recommendations

Know Your Customer onboarding is the process of collecting and assessing information about an individual before or during a business relationship. It commonly includes identity evidence, document checks, screening and a documented risk decision. Explore WIDTH KYC Onboarding.

Know Your Business onboarding is the process of verifying a business entity and understanding the people who own or control it. It can include registry information, directors, shareholders, beneficial owners, screening and business risk assessment. Explore WIDTH KYB Onboarding.

KYC focuses on identifying and assessing an individual. KYB focuses on a legal entity, including its registration, ownership and controlling parties. A corporate onboarding process may require both KYB for the entity and KYC for relevant directors or beneficial owners.

Yes. WIDTH supports onboarding workflows for individuals and businesses. This allows organisations to connect identity verification, business verification, screening, risk review and case escalation through the same compliance environment. See WIDTH Onboarding.

WIDTH can combine document capture, data extraction, authenticity checks, biometric liveness, face comparison and screening within an identity workflow. Available checks depend on the configured package, document, device, jurisdiction and deployment.

Yes. WIDTH supports optical character recognition and structured data extraction from supported identity documents. Extracted information can be cross-checked against available document zones and connected to the wider onboarding record.

Yes. WIDTH supports liveness and face-comparison capabilities within configured digital identity workflows. The exact journey and available checks depend on the selected deployment, device and risk requirements.

WIDTH supports KYB workflows that collect and connect company, director, shareholder and ultimate beneficial owner information. Graph-based views can help analysts understand layered ownership and control relationships.

An application can be routed into a review workflow with the relevant identity, entity, screening and risk information attached. The reviewer can assess the evidence, record a decision and preserve the review history for future reference.

Ongoing due diligence is the continued review of customer information, activity and relevant risk changes after initial onboarding. It can include re-screening, customer information updates, transaction review and reassessment when material risk events occur. WIDTH supports lifecycle workflows that connect onboarding information with later monitoring and review. See WIDTH lifecycle onboarding.

UBO verification is the process of identifying the natural person or people who ultimately own or control a business. The review may require tracing direct and indirect ownership through corporate layers, then verifying and screening relevant individuals. WIDTH KYB supports ownership mapping and connected KYC for relevant directors and beneficial owners. Explore WIDTH KYB.

Authoritative reference: FATF guidance on beneficial ownership

Customer Due Diligence (CDD) is the standard process of identifying a customer, understanding the relationship and assessing relevant risk, while Enhanced Due Diligence (EDD) applies additional measures where higher risk is identified. The scope of EDD depends on the risk and applicable regulatory requirements.

FATF standards describe CDD as including customer identification, beneficial ownership checks, understanding the purpose of the relationship and ongoing due diligence. Higher-risk situations may require enhanced measures. See the FATF Recommendations.

KYC commonly refers to identifying and verifying a customer, while CDD is the broader process of understanding the customer, beneficial ownership, purpose of the relationship and relevant risk over time. In practice, KYC is usually one component of customer due diligence.

The exact CDD measures depend on applicable law, regulation and the organisation's risk framework. Explore WIDTH KYC Onboarding.

WIDTH supports sanctions, politically exposed person and adverse media screening within onboarding and ongoing compliance workflows. Screening results can be connected to customer records, risk reviews and investigations.

Sanctions screening compares a person, business or counterparty against relevant sanctions and watchlist data. Potential matches require assessment because similar names or incomplete identifiers can create false positives. Learn more about sanctions screening.

Politically exposed person screening identifies individuals who hold, or have held, prominent public functions and may require enhanced risk assessment. A PEP match is a risk indicator for review; it is not automatically evidence of wrongdoing.

Authoritative reference: FATF guidance on PEPs

Adverse media screening searches relevant news and information sources for risk-related reporting about a person or organisation. Analysts should assess the source, subject match, recency and relevance before using the result in a decision.

Yes. WIDTH supports ongoing screening so material changes can be assessed after onboarding. This helps compliance teams manage customer risk as watchlists, profiles and other relevant information change.

AML transaction monitoring is the review of transactions and behavioural patterns for activity that may require further investigation. WIDTH supports connected monitoring, alert review and case escalation rather than treating each transaction as an isolated event. Explore Transaction Monitoring.

Customer screening assesses people and businesses against risk data such as sanctions, PEP and adverse media sources. Transaction monitoring assesses financial activity and behavioural patterns. Connected workflows allow both types of information to inform a wider customer risk view.

WIDTH supports real-time transaction risk assessment as part of configured monitoring workflows. The final architecture, response handling and action logic depend on the organisation’s integration, policies and operational requirements. See WIDTH AML Monitoring.

WIDTH can combine rules with customer, transaction, behavioural and relationship context. This gives analysts more information for prioritising alerts and helps organisations refine thresholds based on their risk policies and review outcomes.

Know Your Transaction (KYT) assesses the risk of a specific transaction using information about the parties, payment context and other available risk signals. Transaction monitoring looks more broadly for patterns and behaviour across activity over time. WIDTH supports both real-time transaction screening and ongoing monitoring workflows. Explore WIDTH KYT and Transaction Monitoring.

Continuous monitoring means reassessing relevant customer or transaction risk when new information or activity is received, rather than relying only on periodic reviews. Depending on the workflow, this can include screening updates, behavioural changes, transaction alerts or changes to customer information. See WIDTH Transaction Monitoring.

Transaction screening evaluates a transaction or its parties at or near the point of processing, while transaction monitoring analyses activity and behaviour across a wider period. Screening can support an immediate decision; monitoring can identify patterns that only become visible across multiple events. Explore transaction screening with WIDTH KYT and WIDTH Transaction Monitoring.

Sanctions screening checks whether a person or organisation may match a sanctions or watchlist record, while PEP screening identifies people who hold or have held prominent public functions and may require additional risk assessment. A PEP match is not evidence of wrongdoing.

Both controls can form part of customer screening, but they address different risk indicators and require different review logic. Learn more about sanctions screening.

AML monitoring focuses on activity that may indicate money laundering, terrorist financing or related financial crime, while fraud monitoring focuses on behaviour or transactions that may indicate deception, account misuse or unauthorised activity. The same transaction can create signals relevant to both workflows.

Connected customer, transaction and relationship context can help investigation teams assess those signals without treating each alert in isolation. Explore WIDTH AML Monitoring and Fraud Detection.

WIDTH uses AI to assist with activities such as information review, risk signal analysis, alert prioritisation, case summarisation and investigation support. AI output should operate within the organisation’s policies, controls and human-review model. Explore WIDTH AI.

The WIDTH AI Reviewer supports compliance teams by examining available information, identifying relevant issues and preparing review context. It is designed to reduce repetitive analysis while keeping evidence and reviewer accountability connected to the decision. Explore AI Reviewer.

No. WIDTH positions AI as part of a governed compliance workflow. Organisations define where automation may assist, where escalation is required and which decisions need human review or approval.

WIDTH is designed to connect recommendations and risk indicators to their supporting data, rules and evidence. This helps reviewers understand why an issue was surfaced instead of relying only on an unexplained score.

WIDTH Graph Intelligence connects customers, businesses, accounts, devices, transactions and risk events as relationships within a network. This helps analysts find risks that may not be visible when each record is reviewed separately. Explore Graph Intelligence.

Rules commonly assess a customer or transaction against defined conditions. Graph Intelligence examines the relationships between records. Used together, they can show both the individual trigger and the wider network context surrounding it.

Graph-based analysis can surface direct and indirect relationships across ownership, control, accounts, counterparties, devices and fund flows. Reviewers can then assess whether those connections change the risk understanding of a customer or case.

WIDTH supports fraud risk assessment using available identity, device, behavioural, transaction and network signals. Alerts can be prioritised and routed into connected investigation workflows. Explore Fraud Detection.

Explainable AI means a reviewer can understand the evidence, signals or policy context behind an AI-assisted recommendation instead of receiving only an unexplained result. WIDTH connects AI-assisted review with supporting context so organisations can keep human judgement and accountability visible. Explore WIDTH AI and AI Reviewer.

A compliance AI reviewer is an AI-assisted capability that assembles and analyses case information to support a human reviewer. It can organise context, surface relevant issues and prepare a draft rationale, while the authorised reviewer checks the evidence and owns the final decision. See WIDTH AI Reviewer.

Compliance case management organises alerts, evidence, review activity, decisions and approvals within a controlled investigation record. It helps teams manage ownership, consistency and traceability from initial escalation to closure. Explore Case Management.

A configured alert or review outcome can initiate a case with relevant customer, entity, transaction and screening context attached. This reduces the need for investigators to assemble the same evidence manually before beginning their assessment.

WIDTH supports structured case workflows, including assignment, status management, review stages and escalation. The operating model can reflect team responsibilities, risk levels and approval requirements.

WIDTH supports the preparation of investigation evidence and draft suspicious activity or transaction report narratives. A qualified reviewer remains responsible for checking the content and completing the organisation’s required approval and filing process.

WIDTH can record relevant actions, timestamps, reviewers, status changes, evidence and decision context across configured workflows. This gives compliance teams a clearer history for management review, audit preparation and regulatory enquiries.

A compliance audit trail is a chronological record of the actions, evidence, decisions, approvals and changes associated with a compliance process. A clear audit trail helps teams reconstruct what happened, who acted and what information supported a decision. WIDTH records workflow and case activity within connected records. Explore Case Management and WIDTH Audit Log guidance.

WIDTH supports server-to-server REST APIs and web or mobile SDK integration paths. Organisations can choose an approach based on whether they need backend control, a managed customer interface or a combination of both.

Yes. WIDTH provides REST APIs for supported compliance workflows, including identity, business and transaction-related processes. API access allows organisations to connect WIDTH with their own applications and backend services. View WIDTH Developer Documentation.

Yes. WIDTH provides integration paths for web, Android and iOS experiences. SDK availability and supported workflow steps should be checked in the current developer documentation before implementation.

An API is appropriate when an organisation wants greater backend control over data collection and workflow orchestration. An SDK is useful when the organisation wants a managed verification experience within a web or mobile interface. Many implementations use both.

Yes. WIDTH developer documentation describes separate staging and production environments. Teams can use staging to develop and test integrations before moving approved workflows into production.

Yes. WIDTH supports a modular adoption approach. An organisation can begin with a priority workflow, then connect additional capabilities as requirements expand and internal operating processes mature.

An API lets another system request or send compliance data, an SDK provides packaged components for embedding a workflow into an application, and a webhook sends an event notification when something changes. Organisations may use one or combine them depending on the required user experience and backend control. View WIDTH Developer Documentation.

Yes. WIDTH states that its information security management system is certified to ISO/IEC 27001:2022. Procurement teams can request relevant security documentation through WIDTH’s established review process. Visit the WIDTH Security Centre.

Authoritative reference: ISO/IEC 27001 standard overview

WIDTH states that it uses TLS 1.3 for data in transit and AES-256-GCM encryption for data at rest. The security architecture and deployment requirements should be reviewed during procurement and solution design.

WIDTH states that it supports SAML-based single sign-on, multi-factor authentication and role-based access control. These controls help organisations manage access according to user responsibilities.

WIDTH is designed to record relevant administrative, reviewer and workflow activity with supporting timestamps and context. This helps organisations maintain accountability across privileged and compliance-related actions.

WIDTH supports regional hosting and data-residency discussions as part of solution design. Availability depends on the required region, deployment model and contractual arrangement, so organisations should confirm their requirements during procurement.

Yes. Qualifying procurement teams can request WIDTH security materials, including available certification and assurance documentation. Some information may be provided under a non-disclosure agreement.

Banks can use WIDTH to connect retail and corporate onboarding, screening, monitoring, investigations and case records. The goal is to give teams a more consistent risk view across customer lifecycle activities. Explore WIDTH for Banks.

Payment institutions can use WIDTH for merchant or customer onboarding, screening, transaction risk assessment, alert review and case escalation. Connected workflows help compliance and operations teams work from the same risk context. Explore WIDTH for Payments.

Insurance teams can use WIDTH to support onboarding, screening, risk review, investigations and case documentation across relevant customers, counterparties and distribution relationships. Explore WIDTH for Insurance.

Corporate service providers can use WIDTH to manage client onboarding, KYC, KYB, screening, risk reviews and audit-ready records. This reduces dependence on spreadsheets, screenshots and disconnected email trails. Explore WIDTH for Professional Services.

WIDTH is designed for organisations managing compliance operations across markets. The required data sources, workflows, hosting arrangements and policy configurations should be confirmed for each deployment and jurisdiction.

Book a WIDTH demonstration and share the workflow you want to improve. The team can walk through relevant onboarding, monitoring, investigation or integration capabilities and discuss the next evaluation steps. Book a Demo.

The Travel Rule requires certain originator and beneficiary information to accompany qualifying virtual-asset transfers under applicable regulatory requirements. Requirements vary by jurisdiction and transaction context. WIDTH provides a Travel Rule workflow for data exchange, counterparty handling and audit records within digital-asset operations. Explore WIDTH Travel Rule and WIDTH for Digital Assets.

Authoritative reference: FATF Recommendations