Risk
R.16
Payments must carry who sent and who receives
FATF Recommendation 16 requires originator and beneficiary information on wire transfers. All of that data has to be screened, not only the account holder.
Transaction ScreeningBefore settlement · Analyst decides
Screen payments against sanctions lists in real time, before they settle
Payments are checked against sanctions lists as they're processed. Where you allow it, the agent releases false hits on common names. It holds only the payments that need a human decision, with the match reasoning attached. Every release and every hold is logged.
Payment screening
Wires, SWIFT and instant
PAYMENTS SCREENED TODAY
1284310
HELD FOR ANALYST
2140
SWIFT wire
Dubai to Mumbai · trade
RISK 12··
ReleasedScanning
SWIFT wire
Kuwait to Istanbul
RISK 83··
HeldScanning
Domestic transfer
Payroll batch
RISK 6··
ReleasedScanning
Wire transfer
London to Nairobi
RISK 61··
ReviewScanning
Instant payment
Wallet top-up
RISK 9··
ReleasedScanning
SWIFT wire
Port Louis to Hong Kong
RISK 77··
HeldScanning
AI REASONING · SWIFT wireReleased · Risk 12
Checking parties, banks, vessels and free-text fields…
Beneficiary name similarDifferent countryKnown counterparty
Beneficiary shares a common name with a listed person but is a known counterparty in another country. Released under your false-hit rule.
Pre-settlement
Screened in the payment flow
Every
Hold comes with its reasoning
Logged
Every release and hold
Why payment screening slows everything down
Every false hit holds a payment someone is waiting for
Payment messages carry names, banks, addresses, vessels and free text. Screening all of it creates hits on common names, and each one sits in a queue while the customer waits.
Risk
ISO 20022
More data per payment
Cross-border messages on SWIFT have moved to ISO 20022, which carries richer, structured party data. More fields mean more potential hits.
Risk
Seconds
Instant rails leave no room to wait
Instant payments settle in seconds. A screening process built around a morning review queue doesn't fit them.
What FluxForce delivers
Screening that keeps payments moving
The agent screens each payment as it's processed, resolves the easy hits under your rules and holds the rest with the reasoning ready.
CAPABILITY 01 / 06
In-flight screening
Screens wires, SWIFT and ISO 20022 messages, and instant payments.
Checks parties, banks, countries, vessels and free text.
Runs before settlement.
Uses the same list set as your customer screening.
CAPABILITY 02 / 06
False-hit resolution
Compares each hit with what you know about the party.
Uses past decisions on the same counterparty.
Releases clear false hits only where your rules allow.
Records the reason for every release.
CAPABILITY 03 / 06
Holds with reasoning
Holds payments that need a person.
Shows the matched field and the listed entry side by side.
Gives the analyst a release or escalate decision in one screen.
Escalates true matches to your MLRO.
CAPABILITY 04 / 06
Ownership and control checks
Checks whether a beneficiary is owned or controlled by a listed person.
Uses ownership data from KYB onboarding.
Flags ownership thresholds your policy sets.
Attaches the ownership chart to the hold.
CAPABILITY 05 / 06
Trade and vessel context
Reads vessel names and ports in remittance information.
Flags trade routes your policy marks as high risk.
Links the payment to the trade it claims to fund.
Feeds trade finance cases with the evidence.
CAPABILITY 06 / 06
Complete record
Logs the list version used for every payment.
Logs every release, hold and analyst decision.
Stores evidence in tamper-evident form.
Lets an examiner replay any decision.
What changes for your team
Fewer payments waiting on false hits
We measure the change on your own payment traffic in shadow mode, with your list set and your current match settings as the baseline.
Pre-settlement
Screening
Every payment checked before funds move.
1 screen
Per hold
The matched field, the list entry and the evidence together.
Your
Release rules
You decide which false hits, if any, the agent may release.
Logged
Every release
Each release has its reason and list version on record.
Replay
For your examiner
Any hold or release, replayed with the evidence as it stood.
The agents on this work
Three AI agents in the payment flow
Payment screening needs the payment view and the customer view at once.
Director AI Payment Security
Leo Payden
Screens payments in flight, before they settle.
Wire, SWIFT and instant payments
Free-text field checks
Hold and release logging
Senior AI KYC/AML Compliance Director
Rhea Ledger
Resolves name matches using what you know about each party.
Sanctions list matching
Look-alike name resolution
MLRO escalation notes
Senior AI Audit Trail Specialist
Arin Narrate
Links every hold and release to its evidence.
List version logging
Decision history
Examiner-ready records
Where it fits
Screening for the payment flows you run
A correspondent wire, a wallet top-up and a trade payment carry different risks. The agents screen each in its own context.
WIRES AND CORRESPONDENT
Banking
Focus
SWIFT and ISO 20022
Scope
Cross-border
Shadow mode to go-live90 DAYS
Results
Fewer payments held on common names
True matches escalated with evidence
Every release logged with its reason
INSTANT AND WALLET
Fintechs
Focus
Real-time rails
Scope
High volume
Shadow mode to go-live90 DAYS
Results
Screening fits instant settlement
Clean payments flow without a queue
Evidence your sponsor bank can review
TRADE PAYMENTS
Trade Finance
Focus
Vessels and ports
Scope
Ownership checks
Shadow mode to go-live90 DAYS
Results
Vessel and port names screened in free text
Payments linked to the trade behind them
Holds sent with the trade evidence
Questions? We Have Answers
Frequently Asked Questions
Wires, SWIFT and ISO 20022 messages, domestic transfers and instant payments. We connect to your payment hub or switch through APIs.
Only for false-hit types you've approved. Real potential matches are always held for a person, and every release is logged with its reason.
It runs inside the payment flow before settlement. We'll measure the time it adds on your own traffic during the technical assessment.
Yes. Remittance information, addresses and other free text are checked, including vessel and port names.
Customer screening checks who you onboard. Transaction screening checks every party in every payment, including people who aren't your customers.
The payment, the matched field, the list version, the agent's reasoning and the decision taken, each timestamped.
Take the first step
See how an investigation file is built
Pick one alert type. We'll run the agents in shadow mode on your own data and show you the cases they prepare. Your team decides what happens next.
DeploymentDAY 90
Discovery
Shadow mode
Integration
Controlled go-liveDAY 76–90+
Security and governance