How Many Users Have Tracked My SWIFT Payment?

Under every tracking result Ohmyfin shows a small counter: how many separate parties have looked up this exact payment. Most of the time that number is boring. When it is not boring, it is one of the earliest warnings you will get that something about the payment is wrong.

Where you see it

Track a payment on Ohmyfin and the line appears with the result:

This payment has been tracked by 1 registered user, searching by UETR

The ordinary picture: one or two parties.

That is what you would expect. You tracked the payment, and so did the sender or their finance team. People who are genuinely part of a payment follow it. Nobody else has a reason to.

When the number stops being ordinary

This payment has been tracked by multiple parties: 54 registered and 119 unregistered users, searching by UETR

173 separate parties chasing one payment.

This is not ordinary. A hundred and seventy three separate people looked up one payment, and they are not all the sender's accountants. In the cases we have examined, a number like this means one payment reference has been shown to a long queue of strangers, each of them told the money was on its way to them.

How the counter is built

It counts on the UETR alone. A UETR identifies one payment globally and is never reused, so the number is about your payment and nothing else.
The same party counts once, however many times they track. Registered users are counted by account, visitors who are not signed in by browser session.
You are included in the count, and unregistered visitors are shown only when there are any.

This page used to show a second count, by payment reference. It was removed. A SWIFT field 20 reference is at most 16 characters and unique only inside one sender's own numbering, so a reference such as INV-1001 matched strangers' unrelated payments and inflated the figure for no reason.

Advance payment fraud, which is usually what a high number means

The pattern is old and it still works:

Someone offers goods, a contract, a loan, an investment or a released inheritance.
They send a payment confirmation: an MT103, a pacs.008, a screenshot, or a bare UETR. It looks genuine. It may even be a genuine document, issued once for some payment somewhere.
They ask for something before the money lands: release the goods, ship the container, pay a transfer fee, a tax, a compliance charge, an anti money laundering deposit, or send part of the amount back to a different account.
The money never arrives. Or it arrives and is recalled.

The same document is then reused. Every new target is given the same UETR and told to check it, and every one of them tracks it. That is why the counter climbs into the dozens or the hundreds. A high tracking count is the shape of one document being shown to many people.

The number is a signal, not a verdict. A payment can legitimately be tracked by several parties: an intermediary bank, a broker, a freight forwarder, a treasury team where everyone has their own login. Treat a high count as a reason to verify, never as proof of fraud.

What to do when you see a high count

Release nothing. No goods, no services, no refund, no fee.
Ask your own bank. Only your bank can tell you whether the funds are credited and cleared. A confirmation document, a tracker result and a screenshot are none of them your bank.
Check who is asking. Have the sender obtain the confirmation from their own bank, and check that the sending institution exists and matches the BIC on the document.
Never pay to receive money. No legitimate bank asks a beneficiary for a fee before an incoming wire can be credited.
Slow down. Urgency is the tool. Being pushed to act today is itself the reason to wait.

The rule that never fails: the money is yours when your own bank shows it credited and cleared in your balance. Until then a cross border payment can be delayed, returned or recalled by the sender, whatever any document says.