Find out about known fraudsters at onboarding, before they become your customers
Screen each new customer at onboarding, before the first payment, against bad actors and mule accounts that other institutions in your network have already confirmed. Powered by Salv Bridge.
Trusted by 130+ financial institutions across 30 jurisdictions
Three banks already know the risk. The fourth onboards the applicant, because it had no way of knowing.
A fraud consortium onboarding check tests an account applicant against what other institutions have already offboarded.
Salv Bridge lets a bank run that check against mule accounts and offboarded customers in its network, before a new account makes a payment. A match returns only for an identical identifier, and the bank decides. Customers offboarded for serious financial crime risk are not all fraudsters, but many are. Each match comes with the offence category and a case description, so your team can see why and decide. More than 200,000 joint screening queries have been run between institutions using Salv Bridge.
How banks warn each other about known fraudsters today
Banks already tell each other about people like this, by email, calls and former colleagues. None of it is structured, and none of it is logged. Salv Bridge makes that exchange structured and logged, and institutions in a live network have been using it to check applicants since 2024.
How offboarded customer screening works at onboarding
Institutions in your network report mule accounts and customers they have offboarded for serious financial crime risk. Reporting is a person's decision, and the network's rulebook sets which offence categories can be reported and the minimum data each report carries.
At onboarding you query the shared pool with the applicant's identifier, by API or in the web interface, next to your sanctions check. An IBAN, a device or an account number can all be queried. A match comes back only when you already hold the same identifier, and matching is exact. It returns the offence category and a case description, and you approve, decline or escalate in your own workflow.
Banks typically begin with manual lookups or batch exports, then move to an API. An institution that wants full local control can run matching without a shared central store.
Before, during and after the payment
Checking an applicant is the first of three moments around a payment. It does not replace what protects the payment itself.
- 01Before: onboardingJoint screening of persons, the check on this page.
- 02During: the paymentJoint screening of IBANs checks the beneficiary IBAN against a shared pool of confirmed fraudulent IBANs inside the instant-payment window, and on the answer your own system holds, releases or rejects.
- 03After: investigationJoint investigation is a structured RFI exchange, so two institutions resolve, freeze and recover together.
Fraud tools that work together
-
Intelligence sharingThe secure network where fraud, AML and sanctions teams settle a case directly with other institutions. Send structured requests, answered in minutes, under rules your network agrees.
-
ScreeningScreen customers and payments against sanctions, PEP and adverse-media lists, with matching you configure and lists Salv keeps current.
-
Risk scoringCustomer risk rating on weighted rules built around your framework. Kept current as the facts change, feeding the monitoring and screening that act on it.
-
MonitoringScenarios you can read, test on your own data and change yourself. Watch payments, customers and counterparties, for AML and fraud.
-
Alert and case managementWhen an investigation grows, it becomes a case. Bring the related alerts, customers and payments together and work it from one place as a team.
Questions about fraud consortiums for onboarding
A bank queries the shared pool with the applicant's identifier during onboarding, by API or in a web interface, next to its sanctions check. Most banks begin with manual lookups or batch exports.
The offence category and a case description. Customers offboarded for serious financial crime risk are not all fraudsters, but many are, so your team sees why the person was reported before it decides.
A person at the reporting institution. Querying is automated, reporting is not, by design, and the network's rulebook sets which offence categories can be reported and the minimum data each report carries.
No. A match is a prompt for your team's decision, not a verdict. You approve, decline or escalate in your own onboarding workflow.

