APP Fraud
Signals
Score the transfer for authorised push payment fraud patterns while it is still in flight.
ExploreFraud Detection →
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.
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 and Travel Rule in one call, on one audit trail
Reviewers see the payment, the parties involved and the signals that contributed to the decision in one view.
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.
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.
Sender, beneficiary and ISO 20022 fields are screened as part of the payment call itself.
OFAC, UN, EU and more than 1,400 sanctions lists, fuzzy-matched and deduplicated.
Politically exposed persons resolved against available registry data, with their context.
Fuzzy-name resolution and beneficiary disambiguation separate real matches from noise.
Reviewers see the matches that matter, with the parties and the signals behind each one.
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.
Score the transfer for authorised push payment fraud patterns while it is still in flight.
ExploreIdentify beneficiary accounts that show the indicators of receiving or moving fraudulent funds.
ExploreTreat a payee-name mismatch as a signal that holds the payment for review before it completes.
ExploreWIDTH 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.
Capture the originator and beneficiary information the transfer has to carry.
Shape the payload to FinCEN 31 CFR 1010.410(f) or MAS PSN02 for the corridor.
Check the payload is complete and consistent before the payment moves on.
Keep the Travel Rule data with the payment through the transfer, not beside it.
Screen the named parties again as the data moves through the workflow.
Keep the payload, the checks and the outcome on the payment’s audit trail.
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.
The sender, the beneficiary and the ISO 20022 data checked, and the sources used.
The sanctions, PEP, fraud and mule-risk signals identified on the payment.
The corridor overlay, rule or threshold that shaped the decision.
Whether the payment was held, who reviewed it and what they concluded.
Each step from screening to release, hold or escalation, in order.
The outcome and the evidence behind it, kept for later review.
Illustrative record. Screening, signals, Travel Rule data and review history stay attached to the payment.
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.
Run KYC, KYB and beneficial ownership verification before the first payment moves.
ExploreScreen customers, businesses and payees against sanctions, PEP and adverse media.
ExploreApply risk scoring, decision rules and compliance reviews on the same customer record.
Explore theMove alerts and escalations into case management, investigation and reporting workflows.
ExploreThe result is a more connected operating model for the teams responsible for payment risk and compliance decisions.
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.
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.
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.
The WIDTH Payments solution screens against OFAC, UN and EU sanctions sources. More than 1,400 sanctions lists are fuzzy-matched and deduplicated.
Yes. PEP context forms part of the payment screening process, resolved against available registry data.
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.
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.
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.
Yes. The WIDTH Payments solution supports FATF Recommendation 16 Travel Rule workflows involving originator and beneficiary 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.
Yes. ISO 20022 metadata is specifically included in the payment information screened by WIDTH.
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.
Yes. WIDTH combines sanctions, APP fraud signals and FATF R.16 data into one scored payment decision with a single audit trail.
Yes. The Payments solution is designed to keep payment screening and decision information within a single audit trail.
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.
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 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.