Payment screening: real-time sanctions checks
Payment screening stops a transfer from reaching a sanctioned party before the transaction is completed. TruvaLI embeds screening directly into the payment flow: a match suspends the payment, while confirmation signals reduce unnecessary stops.
Payment screening is the checking of transfer parties against sanctions lists before a transaction is completed. It differs from customer screening in its timing: here, the check must be performed before money moves, and it must operate without disrupting the flow.
Who is screened in a payment?
The customer is not the only party screened in a transfer. Senders, beneficiaries, the beneficiary's bank, and any intermediary institutions are evaluated together. Name and address information in free-text fields is also covered by screening: a sanctioned party often appears in a description line rather than a structured field.
Country and currency also serve as signals. Sanctions regimes target countries and sectors as much as individuals; the route a transfer takes may require verification even if all parties involved are clear.
How does it work without disrupting the flow?
Payment screening operates within a latency budget. The check must return results in a fraction of a second within the payment flow; otherwise, screening is effectively disabled. This is why screening is embedded directly into the transaction pipeline, and its outcome becomes part of the decision.
When a match occurs, the payment is not rejected; it is suspended. The suspended transaction is linked to a case and routed to a human reviewer. The cost of a missed match is not the same as the cost of a false stop: the former is a sanctions violation, while the latter is a delayed customer payment, and both must be measured.
How are false stops reduced?
Confirmation signals are decisive here as well: aliases and transliterations, date of birth, ID and passport numbers, nationality, and city. Because these are stored in the record, a common name alone will not stop a payment. The effective date of the record is also checked; a lifted decision will not suspend a transaction.
Where to set the threshold is the institution's decision. How many transactions a new threshold would stop in historical payment traffic can be seen before going live using rule simulation. The rule itself is written in the rule and scenario engine.
Where do screening lists come from?
Sanctions records are maintained along with the issuing authority and country, preserving the source link. In countries not covered by off-the-shelf lists, the official source itself is monitored; regulatory bulletins are uploaded and converted into structured records. The institution can also add its own restricted party list. Details are available on the sanctions, PEP, and adverse media screening and custom screening lists pages.
What happens to a suspended payment?
A suspension opens a case. The case brings together the transaction parties, the matching record, confirmation signals, and the reviewer's justification. Both releasing and stopping are decisions, and both are written to the audit trail with their justification. Due to segregation of duties, the person who releases the transaction and the one who approves it may not be the same; this is explained on the maker/checker, authorization, and audit trail page.
Payment screening is part of sanctions compliance; the complete picture is on the sanctions compliance page, and continuous monitoring of transaction behavior is on the ongoing monitoring page.
Common questions
- Who is screened in payment screening?
- Senders, beneficiaries, the beneficiary's bank, and any intermediary institutions. Name and address information in free-text fields is also covered, as a sanctioned party often appears in the description line.
- Does screening slow down the payment flow?
- Screening is embedded directly into the transaction pipeline and operates within a latency budget. The result must return fast enough to be part of the decision; otherwise, screening is effectively disabled.
- Is the payment rejected when a match occurs?
- It is not rejected; it is suspended. The suspended transaction is linked to a case, and a human makes the decision.
- How are false stops reduced?
- Confirmation signals such as aliases, date of birth, ID and passport numbers, nationality, and city are stored in the record, so a common name alone does not stop a payment. The effective date of the record is also checked.
- Are country and currency covered by screening?
- Yes. Sanctions regimes target countries and sectors as much as individuals; the route of the transfer may require verification even if all parties are clear.
- Can the impact of a new rule be seen in advance?
- Yes. How many transactions the new threshold would stop in historical payment traffic is measured via simulation before the rule goes live.
- Is the release decision logged?
- Yes. Both releasing and stopping are decisions; both are written to the immutable audit trail with their justification and are subject to segregation of duties.
- Can an institution add its own restricted party list?
- Yes. The institution's own lists enter the same screening flow via official source definition, feed, or document upload.