Wire transfers on the Isle of Man run under two separate duties: fiat information requirements deriving from Regulation (EU) 2015/847, and the virtual-asset Travel Rule under the Travel Rule (Transfer of Virtual Assets) Code 2024. Both require the sender to attach originator information to a transfer, and both apply to any relevant person carrying out the activity, not only banks.

We treat this as one question with two branches: wire transfers, in two forms. A firm can owe both duties on the same day, to different transfers, and each is tested separately. This sits alongside the wider framework health-check we set out in our review of the AML/CFT Handbook (April 2026) — the duties below are one procedural thread within that broader picture.

Does the wire-transfer rule apply to us if we aren't a bank?

Scope turns on function, not on the label "bank". The fiat regime applies to any payment service provider — a relevant person carrying out the activity of transferring funds by electronic means, whatever else the firm calls itself. The Isle of Man is required to comply with Financial Action Task Force Recommendation 16 on wire transfers. Before the UK left the EU, the Island — with the other Crown Dependencies — took advantage of a provision letting EU member states extend reduced information requirements to associated territories sharing a monetary union and payment clearing systems, covering the Isle of Man and the Channel Islands. With effect from 26 June 2017, Regulation (EU) 2015/847 repealed and replaced the earlier Regulation (EU) No 1781/2006, tightening the rules against wire transfers being abused for money laundering or terrorist financing. It was applied, with modifications, as Manx law by the European Union (Information Accompanying Transfers of Funds) Order 2016, as amended by the 2017 Amendment Order, with the Information Accompanying Transfers of Funds Regulations 2016 carrying its enforcement provisions from the same date. Despite the UK's withdrawal from the EU, the position between the UK and the Crown Dependencies has not needed to change.

None of that legal lineage asks whether your letterhead says "bank". A firm running international transfers over SWIFT, or domestic transfers over CHAPS or BACS, for customers is already in scope. The virtual-asset side is not theoretical either: the 2026 civil-penalty amendment covered below shows the Authority actively enforcing the Travel Rule right now, which catches firms in payments, e-money or virtual-asset-adjacent business who never thought of themselves as running a "wire transfer" service at all.

What information has to travel with a fiat wire transfer?

The Regulation covers funds transfers "by electronic means" — for a Manx payment service provider, that captures international transfers over SWIFT, including euro payment systems, and domestic transfers over CHAPS and BACS. Two categories sit outside it: transfers where both the Payer and the Payee are themselves payment service providers acting on their own behalf (MT 200-series SWIFT messages), and the MT 400- and 700-series messages banks use to settle trade-finance obligations between themselves. The UK credit clearing system falls outside the Regulation too, since it is paper-based rather than electronic, and a customer paying in cash or by cheque over the counter via a bank giro credit is unaffected.

Where a transfer is in scope, the ordering institution must ensure it carries specified Payer and Payee information. Payee information is short: name and account number. Payer information is name and account number, plus at least one of:

• the Payer's address
• an official personal document number, or a customer identification number
• the Payer's date and place of birth

Any intermediary payment service provider has its own obligations to preserve that information, with permitted variations set out in the Authority's guidance for cases where the full set cannot practically travel with the message. Two pre-conditions decide how much verification sits behind those fields. For an account-holding customer, Payer information must be accurate and verified — but that is deemed satisfied where identity has already been appropriately verified under the AML/CFT Code 2019 ("the Code"), so no further verification is required purely for the wire-transfer rule, though a firm may still choose to run one. For a one-off payment above €1,000 where identity has not already been verified under the Code, the relevant person must verify the Payer's identity plus either date of birth or address, per Article 4.4 of the Regulation, and keep evidence of it.

If your onboarding file cannot show which of those two pre-conditions applied to a given payment, that is worth finding out before a supervisor asks.

What is the virtual-asset Travel Rule, and how does it sit alongside the fiat rule?

The virtual-asset Travel Rule runs on the same logic as the fiat regime — information has to travel with the transfer — but it is a separate Code, with its own definitions, and a firm can owe both duties side by side rather than one displacing the other. Under Code 5 of the Travel Rule (Transfer of Virtual Assets) Code, the originator is the account holder who allows a virtual-asset transfer to be made from their account. The Authority's Travel Rule guidance requires originator information to accompany every transfer: the originator's name, unique account identifier, and — where the originator or beneficiary lacks a unique account identifier — one of the originator's address, a national identification number, or date and place of birth. An equivalent requirement identifies the beneficiary on the receiving side.

As with the fiat rule, the amount involved changes what has to travel. A transfer below EUR 1,000 attracts a reduced, specified set of information rather than the full requirement; above that threshold, the fuller set applies. A firm running both fiat wire transfers and virtual-asset transfers is running two related Codes, each with its own information set and threshold, on what its systems may treat as a single "payment" function.

Why does the 2026 civil-penalty amendment raise the stakes?

Until recently, a Travel Rule breach and an AML/CFT Code breach sat under different enforcement machinery. That changed with the Anti-Money Laundering and Countering the Financing of Terrorism (Civil Penalties) (Travel Rule) (Amendment) Regulations 2026 (SD No. 2026/0014), made by the Authority on 9 January 2026 under section 157 of the Proceeds of Crime Act 2008 and section 68 of the Terrorism and Other Crime (Financial Restrictions) Act 2014, coming into operation the day after Tynwald approval. It amends the definition of "contravention" in the Anti-Money Laundering and Countering the Financing of Terrorism (Civil Penalties) Regulations 2019 (SD 2019/0201) so that it now covers the Travel Rule (Transfer of Virtual Assets) Code 2024 (SD 2024/0137), alongside the AML/CFT Code 2019 (SD 2019/0202). The regulations' own Explanatory Note is direct: it brings "contraventions of the Travel Rule (Transfer of Virtual Assets) Code 2024 into scope of the AML/CFT civil penalty regime."

A firm that gets the virtual-asset originator information wrong can now face a civil penalty through the same regime as a firm that gets a due diligence step wrong under the AML/CFT Code — not a lesser, informal consequence. That is precisely why this matters to firms that do not think of themselves as running a wire-transfer business: if any part of your activity touches payments, e-money, or virtual assets, the Travel Rule now carries the same enforcement weight as the rest of your AML/CFT framework.

Firms that have never mapped which of their products fall under the fiat rule, the Travel Rule, or both, are the ones most exposed to that change.

Common mistakes we see

The most common mistake is treating this as one obligation rather than two. A firm maps its fiat wire-transfer procedure carefully, then assumes the same document covers virtual-asset transfers because both involve "sending money electronically" — it does not, and a supervisor reviewing virtual-asset activity will look for the Travel Rule Code specifically. A second, related error is applying the €1,000 threshold from one regime to the other — the fiat rule's Article 4.4 trigger and the Travel Rule's EUR 1,000 de minimis are separate thresholds in separate Codes, and conflating them produces a control built on the wrong number for at least one of the two.

We also see firms confuse the wire-transfer information duty with the sanctions check that runs on the same transaction. They are not the same control: our piece on sanctions screening on the Isle of Man covers the separate duty to check a name against the sanctions list, which a firm runs alongside — not instead of — carrying the correct originator and beneficiary information. A transfer can clear sanctions screening and still be a wire-transfer breach if the Payer information is missing, and vice versa. Finally, we find firms that verified Payer identity once under the Code years ago and never revisited whether that verification still supports the "already verified" pre-condition once a customer moves into virtual-asset activity.

Frequently asked questions

Is a domestic BACS payment in scope, or only international transfers?

Both, provided the transfer is "by electronic means". SWIFT transfers, including euro payment systems, and domestic CHAPS and BACS transfers are all covered. Paper-based routes are not — the UK credit clearing system falls outside the Regulation for that reason, as do cash or cheque deposits over the counter.

Do we need a separate procedure for the Travel Rule, or can we extend our fiat one?

A separate one. The Travel Rule (Transfer of Virtual Assets) Code has its own originator and beneficiary definitions and its own EUR 1,000 de minimis threshold, distinct from the fiat rule's Article 4.4 trigger. Adapting a fiat procedure risks carrying the wrong threshold or the wrong information fields into virtual-asset transfers.

Does a Travel Rule breach carry the same weight as an AML/CFT Code breach now?

Yes. Since the Anti-Money Laundering and Countering the Financing of Terrorism (Civil Penalties) (Travel Rule) (Amendment) Regulations 2026 (SD 2026/0014), a breach of the Travel Rule (Transfer of Virtual Assets) Code 2024 falls within the same civil-penalty regime as a breach of the AML/CFT Code 2019 — no longer a lesser or separate category of failing.

Whichever rail your firm runs, the fastest way to find the gaps before a supervisor does is to have someone map your actual transfer flows against both Codes.

A wire transfer is still a wire transfer whether it moves in sterling or in a virtual asset — the Authority has simply made sure both now answer to the same enforcement regime.