Screening that reads the whole payment, not just the name.
Sender, beneficiary, bank code, intermediary and narration — checked against sanctions, PEP and adverse media, plus your own lists, before the payment settles.
Risk hides in the fields nobody screens.
Most tools screen the sender and beneficiary name and stop. Fintegrity screens all five fields a payment carries.
Not just a name match
Screens the payer's name and identifiers against sanctions and PEP lists, and flags spoofed or inconsistent originator details.
Reads through transliteration
Matches beneficiary names, aliases and common transliterations — the step most screening tools skip.
Screens the institution too
Checks the receiving bank's BIC and name against sanctioned-entity lists, not just the account holder.
Every hop in the chain
Screens every intermediary bank a payment passes through, catching sanctioned correspondents used to obscure the route.
Where the risk hides
Screens free-text reference and narration fields for geographic and keyword risk terms that name-only screening never reads.
Pick a payment. Watch every field get screened.
The score, the hit, the matched field and the action all change together — watch what happens when only the narration triggers a hold.
No field matched. The payment settles.
All five fields were screened against every enabled list. The clear result is written to the evidence trail with the list versions used.
Clean payment: score 0.00, RELEASE, no case opened.
A held payment is a customer waiting.
How long a hold lasts
Held payments are reviewed same-day by default; the SLA is configurable per corridor and per list.
Three dispositions
An analyst releases, rejects or escalates every held payment — there is no fourth option.
What gets recorded
The analyst, the reason, the timestamp and the evidence considered are written to the case.
Who can act
Disposition is restricted by role; escalation routes to a senior reviewer automatically.
Your screening policy, your thresholds.
Tune sensitivity per list and per field. Keep your own blocklists beside the global ones. Every configuration change is recorded with the user, the timestamp and the version it replaced.
- Nigerian name variants and transliterations handled by default
- Client-managed blocklists, editable without an engineering release
- Per-field thresholds, so narration noise doesn’t hold real payments
Screening and monitoring, one risk profile.
Payment Screening and Transaction Monitoring share the same customer risk state and the same evidence trail. One integration, one audit story.