Skip to content

Reach the receiving bank in minutes, not days

Cross-bank fraud investigations and stolen fund recovery with Salv Bridge. Send a structured request to the other bank's fraud team while the money can still be stopped.

How it works

Trusted by 130+ financial institutions across 30 jurisdictions

A cross-bank fraud investigation begins when your customer has been tricked into paying an account at another institution. The money has left your bank, and whether any of it comes back depends on someone at the receiving institution acting quickly.

Get your request straight to the receiving bank's fraud team with Salv Bridge, so they can check the account and freeze the funds. The median response is 17 minutes.

Bridge carries the request and the answer between members, conformant with the EPC's FRIDA rulebook. It doesn't move money, and the decision to freeze or return it stays with the bank that holds it.

Why cross-bank fraud cases stall

Today the request goes out as an email, a SWIFT message or a call to whoever your team last spoke to at that bank. It lands in one person's inbox, and that person is in a meeting, on leave, or was never the right person. Meanwhile the account is emptied and the balance split across two more banks. By the time an answer comes back, a day or sometimes three later, your analyst is working a case they can't see into, and your customer is asking every morning whether anything has happened.

Open an interbank fraud investigation the other bank can act on

When an account-to-account, instant or card payment ends in an account at another institution on the network, open an investigation addressed to that institution.

Pick a fraud category and a template: the receiving account, why you suspect it, and what you need back, such as whether the account is still open and the funds still there. Only the fields the template asks for are sent. Mark a request urgent while the money is still moving. If the balance was split across several banks, send one request to all of them and track it as a single case, with a separate conversation for each.

Start in the web interface, then use the API to raise requests from your own systems. That's how it works at volume and on instant payments. Everyone on your side sees the same case: who owns it, what's been asked and answered, and the files attached, so nothing stalls because one person is away.

Stop the same account being used again

Recovery is one outcome. The other is stopping the same account being used on someone else next week. Report a confirmed mule IBAN to the network, and any member who queries it, at onboarding or from a payment flow, will see it was reported. It surfaces at the moment someone is about to deal with that account.

Bridge carries the case once the payment has gone. To stop the payment before it leaves, see scam and mule detection.

Before, during and after the payment

Checking an applicant is the first of three moments around a payment. The earlier the question is asked, the less there is to recover.

  1. 01Before: onboardingJoint screening of persons.
  2. 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.
  3. 03After: investigationJoint investigation is a structured RFI exchange, so two institutions resolve, freeze and recover together.

See it on your own data

Fraud tools that work together

  • Intelligence sharing
    The 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.
  • Monitoring
    Scenarios you can read, test on your own data and change yourself. Watch payments, customers and counterparties, for AML and fraud.
  • Alert and case management
    When an investigation grows, it becomes a case. Bring the related alerts, customers and payments together and work it from one place as a team.
Trust and security What we hold, where your data sits, and how every decision is recorded.
Explore

Questions fraud teams ask

By reaching the institution that received it. Your fraud team raises a request naming the account and the reason for suspicion, and the receiving bank checks it and, under its own obligations, freezes or returns what's left. Speed decides recovery in authorised push payment (APP) fraud, because the funds are usually moved on within hours.

Faster than email, because the request doesn't depend on one person happening to see it. Requests can be marked urgent, and each network agrees response expectations its members have committed to.

Only the fields the request template asks for: the receiving account, why you suspect it, and what you've asked for back. Messages are encrypted in the user's browser, and only the institutions in that conversation can read them.

Yes. Report a confirmed mule IBAN to the network, and any member querying that IBAN, at onboarding or from a payment flow, sees that it was reported, at the moment they're about to deal with it.