Payments Compliance

WIDTH screens sender, beneficiary and ISO 20022 payment data against sanctions, fraud and Travel Rule requirements before the payment clears the rail, and returns one scored decision with a single audit trail.

Under 100 msOne Scored DecisionSingle Audit Trail

Three Checks, One Decision

Payment teams should not have to assemble a decision from separate screening results. WIDTH combines sanctions screening, fraud signals and FATF R.16 data into one scored decision with a single audit trail.

Sanctions Fraud signals Travel Rule Payee check Case review
The sanctions result arrives without the fraud signalTravel Rule data is checked outside the payment flowReviewers assemble the decision from separate results

One Scored Payment Decision

Sanctions, fraud and Travel Rule in one call, on one audit trail

Separate results One decision

Reviewers see the payment, the parties involved and the signals that contributed to the decision in one view.

Real-Time Payment Decisions

Screening has to run at the speed of the transaction without losing the context compliance review needs. WIDTH screens payment data before settlement, so sanctions exposure, fraud signals and Travel Rule issues surface within the payment flow.

<100 ms
Screening latency
Median end-to-end latency on SWIFT GPI and UK Faster Payments rails, with p99 under 250 ms.
180
Corridors supported
Per-corridor overlays for PSD2/PSD3 SCA, FinCEN 31 CFR 1010.410(f) and the Wolfsberg Principles.
FATF R.16
Travel Rule built in
Originator and beneficiary information carried, validated and re-screened through the payment workflow.
60–80%
Fewer false positives
Fuzzy-name resolution, PEP context and beneficiary disambiguation cut exact-match watchlist noise.

Sanctions and PEP Screening

WIDTH screens payment data against OFAC, UN and EU sanctions sources as part of the payment decision. More than 1,400 sanctions lists are fuzzy-matched and deduplicated, and PEP context is resolved against available registry data.

Screen Inside the Decision

Sender, beneficiary and ISO 20022 fields are screened as part of the payment call itself.

1,400+ Lists, Deduplicated

OFAC, UN, EU and more than 1,400 sanctions lists, fuzzy-matched and deduplicated.

PEP Context Resolved

Politically exposed persons resolved against available registry data, with their context.

Less Exact-Match Noise

Fuzzy-name resolution and beneficiary disambiguation separate real matches from noise.

A Focused Review Queue

Reviewers see the matches that matter, with the parties and the signals behind each one.

APP Fraud and Mule Signals

Authorised push payment fraud often involves a legitimate account holder sending funds to a fraudulent or mule-controlled beneficiary. WIDTH applies APP fraud and mule-risk signals during the payment flow, before settlement.

APP Fraud
Signals

Score the transfer for authorised push payment fraud patterns while it is still in flight.

Explore
Fraud Detection
→

Mule-Risk
Beneficiaries

Identify beneficiary accounts that show the indicators of receiving or moving fraudulent funds.

Explore
Fraud Detection
→

Confirmation
of Payee

Treat a payee-name mismatch as a signal that holds the payment for review before it completes.

Explore
Case Management
→

Travel Rule in the Flow

WIDTH supports FATF Recommendation 16 workflows for originator and beneficiary information. Payloads are structured to FinCEN 31 CFR 1010.410(f) or MAS PSN02 and re-screened through the transfer, so the data stays with the payment decision.

Stage 01

Originate

Capture the originator and beneficiary information the transfer has to carry.

Stage 02

Structure

Shape the payload to FinCEN 31 CFR 1010.410(f) or MAS PSN02 for the corridor.

Stage 03

Validate

Check the payload is complete and consistent before the payment moves on.

Stage 04

Carry

Keep the Travel Rule data with the payment through the transfer, not beside it.

Stage 05

Re-screen

Screen the named parties again as the data moves through the workflow.

Stage 06

Record

Keep the payload, the checks and the outcome on the payment’s audit trail.

Every Payment Traceable

A payment decision is more useful when compliance teams can see how it was reached. WIDTH brings the screening result, the fraud signal, the Travel Rule data and the review activity into one audit trail.

What Was Screened

The sender, the beneficiary and the ISO 20022 data checked, and the sources used.

Which Signals Were Found

The sanctions, PEP, fraud and mule-risk signals identified on the payment.

Which Policy Applied

The corridor overlay, rule or threshold that shaped the decision.

Whether It Needed Review

Whether the payment was held, who reviewed it and what they concluded.

How the Decision Progressed

Each step from screening to release, hold or escalation, in order.

What Was Recorded

The outcome and the evidence behind it, kept for later review.

Payment PY-58231 · SG to UK corridor Released
CorridorSingapore to United Kingdom, UK Faster Payments · PSD2 SCA overlay
ScreenedSender, beneficiary and ISO 20022 fields, 1,400+ lists · 71 ms
SignalsOne fuzzy PEP match, resolved to a different person · no mule indicators
Travel RuleOriginator and beneficiary payload validated to MAS PSN02 · re-screened
ReviewHeld for Tier 1 under the PEP-context rule · cleared in four minutes
OutcomeReleased after review, decision and evidence recorded · screened in 86 ms

Illustrative record. Screening, signals, Travel Rule data and review history stay attached to the payment.

Connected to the Platform

Payment screening is one part of compliance operations. WIDTH connects payment decisions with onboarding, screening, risk assessment and investigations, so payment teams manage the compliance lifecycle on one platform.

Onboard the
Customer

Run KYC, KYB and beneficial ownership verification before the first payment moves.

Explore
Onboarding
→

Screen
Every Party

Screen customers, businesses and payees against sanctions, PEP and adverse media.

Explore
AML Monitoring
→

Investigate
With Context

Move alerts and escalations into case management, investigation and reporting workflows.

Explore
Case Management
→
Real-time payment screening Sanctions and PEP screening APP fraud and mule-risk signals Travel Rule workflows Customer and business onboarding Risk assessment Compliance review Alerts and escalation Case management Investigation records Audit trails

The result is a more connected operating model for the teams responsible for payment risk and compliance decisions.

Frequently Asked Questions

What is real-time payment screening?

Real-time payment screening checks payment data before or during transaction processing to identify sanctions, fraud or other compliance risks before settlement. WIDTH screens sender, beneficiary and ISO 20022 payment data within the payment flow.

How fast does WIDTH screen payments?

WIDTH’s median end-to-end screening latency is under 100 milliseconds on SWIFT GPI and UK Faster Payments rails, with p99 under 250 milliseconds.

What payment information does WIDTH screen?

WIDTH screens sender, beneficiary and ISO 20022 metadata as part of the payment decision. The platform can combine this information with sanctions, PEP, fraud and Travel Rule signals.

Which sanctions sources does WIDTH use for payment screening?

The WIDTH Payments solution screens against OFAC, UN and EU sanctions sources. More than 1,400 sanctions lists are fuzzy-matched and deduplicated.

Does WIDTH support PEP screening for payments?

Yes. PEP context forms part of the payment screening process, resolved against available registry data.

How does WIDTH reduce payment-screening false positives?

WIDTH uses fuzzy-name resolution, PEP context and beneficiary disambiguation to reduce exact-match watchlist noise. This reduces reviewer queues by 60–80% compared with legacy screening.

Does WIDTH support APP fraud detection?

Yes. The WIDTH Payments solution includes APP fraud and mule-risk detection. Confirmation of Payee mismatch signals can be used to trigger a hold-and-review process before settlement.

What is mule detection in payments?

Mule detection looks for indicators that a beneficiary account may be used to receive or move fraudulent funds. WIDTH includes mule-risk signals within its payment fraud decisioning workflow.

Does WIDTH support the FATF Travel Rule?

Yes. The WIDTH Payments solution supports FATF Recommendation 16 Travel Rule workflows involving originator and beneficiary information.

How does WIDTH handle Travel Rule information?

WIDTH carries, validates and re-screens relevant originator and beneficiary data as part of the payment workflow. Travel Rule payloads can be structured against FinCEN 31 CFR 1010.410(f) and MAS PSN02 specifications.

Does WIDTH support ISO 20022 payment data?

Yes. ISO 20022 metadata is specifically included in the payment information screened by WIDTH.

Does WIDTH support cross-border payment compliance?

Yes. WIDTH supports 180 corridors with per-corridor policy overlays, covering PSD2 and PSD3 SCA, FinCEN 31 CFR 1010.410(f) and the Wolfsberg Cross-Border Principles.

Can WIDTH combine sanctions, fraud and Travel Rule checks?

Yes. WIDTH combines sanctions, APP fraud signals and FATF R.16 data into one scored payment decision with a single audit trail.

Does WIDTH provide an audit trail for payment decisions?

Yes. The Payments solution is designed to keep payment screening and decision information within a single audit trail.

How does WIDTH Payments connect to the wider compliance platform?

Payment screening can connect with WIDTH workflows for KYC, KYB, beneficial ownership verification, AML and sanctions screening, risk assessment, alerts, investigations and case management. This allows payment teams to manage more of the compliance lifecycle within one platform instead of separate operational systems.

Can I see WIDTH screen a live payment workflow?

Yes. WIDTH offers a live demonstration of the Payments solution, assessing a payment corridor against the relevant policy overlays and following the resulting decision into the wider compliance process.

See a Live Payment Workflow

See how WIDTH screens a payment corridor against sanctions, fraud and Travel Rule signals before settlement, and where the decision goes next.

One Platform. One Workflow. One Source of Truth.