SWIFT MTs / Learning brief
SWIFT System and Service Messages
Your notes
In simple terms / 01
What this means in plain language
SWIFT Category 0 system messages pass between a user and the network itself, not between banks. This guide covers acknowledgements, authentication responses, retrieval and delivery notifications, and why a valid payment can still fail at the network layer.
Most Society for Worldwide Interbank Financial Telecommunication (SWIFT) messages carry business content between banks, such as a payment instruction. Category 0, the MT0xx range, is different: these system messages pass between a user and the SWIFT network itself. They tell you whether the network accepted a message you sent, confirm authentication, let you retrieve or receive delivery notifications, and broadcast network news. Understanding them matters because a payment can be perfectly valid in its business content and still never reach its destination if it is rejected at the network layer. The evidence for what actually happened lives in these Category 0 exchanges. This guide explains them and separates them from service and business messages.
Complete lesson / 02
Understand the full idea, step by step
Maya has a payment that, by every business measure, is correct — right parties, right amount, right account — and yet Nordbank swears it never arrived. Before she reopens the payment itself, she reads a different set of messages: the quiet conversation each bank has with the network about whether its messages got through.
Messages to the network, not to a bank
Alongside the business messages banks send each other, SWIFT carries Category 0 (the MT0xx range): system messages exchanged between a user and the network itself. These are not instructions between two banks. They are the record of the network telling a member what happened to the messages it submitted and received — easy to overlook until a payment goes quiet.
ACK and NAK — positive acknowledgement / negative acknowledgement
When a member submits a message, the network answers. An ACK (acknowledgement) says the message was accepted for the network. A NAK (negative acknowledgement) says it was rejected — a syntax or validation fault at the network layer — and gives a reason. A NAK means the message never went forward: it did not reach the receiving bank.
The network-layer messages Maya can read
- ACK / NAK
- Accepted, or rejected with a reason, at submission
- UAK / UNAK
- Authentication acknowledged, or rejected
- Delivery notification
- Confirms a message reached the receiver
- Retrieval request
- Fetches an earlier message from the network
- Broadcast
- A network-wide announcement to members
You may be wondering: if my message got an ACK, does that mean the payment is done?
No — and the difference matters. An ACK is the network saying it accepted the message for transmission. It is not the receiving bank accepting the payment, and it is certainly not the beneficiary being credited. Business acceptance, or a rejection for a business reason, comes later in a separate message. The ACK only clears the first hurdle: the message is well-formed and on its way.
What the network tells Bank Alfa
- MESSAGE
Bank Alfa submits the MT103 to the network.
- VALIDATION
The network checks the message's structure and authentication and answers with an ACK — or a NAK if it is malformed or fails a check.
- NOTIFICATION
If accepted, a delivery notification later confirms the message reached Nordbank. A NAK, by contrast, means it never left the network for Nordbank at all.
COMMON CONFUSION
“A valid payment always reaches the receiving bank; if it did not arrive, the payment data must be wrong.”
A payment can be perfectly valid in its content and still fail at the network layer — a NAK, an authentication reject, a non-delivery. The business fields were fine; the message simply never got through. That is exactly why investigators read the Category 0 evidence first: it says whether the message was accepted and delivered before anyone re-examines the payment.
WHAT IF — The MT103 received a NAK
What happens: The message was rejected at submission and never reached Nordbank. No funds moved, even though the payment instruction itself was correct.
How it is handled: Maya reads the NAK reason, corrects the fault, and resubmits — no need to reopen the underlying payment logic. The acceptance-or-rejection and delivery-or-non-delivery trail is the operational evidence of what actually happened to the message.
STRICTLY SPEAKING
Strictly speaking, ACK/NAK and their siblings are FIN's network responses. Traffic sent over ISO 20022 and other SWIFT transports has its own transport-level acknowledgements, but the principle carries across: acceptance by the network is a distinct event from a bank's business acceptance of the payment. Always separate the two when you read a case.
FOR NOW, REMEMBER
- Category 0 (MT0xx) messages pass between a user and the network, not between two banks.
- ACK means the network accepted the message; NAK means it rejected it and it never reached the receiver.
- Network acceptance is not the same as the receiving bank accepting the payment or the beneficiary being paid.
- A valid payment can still fail at the network layer — which is why investigators read this trail first.
TRY IT YOURSELF
Maya sees an ACK for Bank Alfa's MT103, but the supplier has not been paid and Nordbank has raised no rejection. What is the most accurate reading?
So far the members on the network have been banks. But corporates like Asha Traders can join too — and connect once to reach many banks. Next: how they do it, through SCORE and MA-CUG.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
Society for Worldwide Interbank Financial Telecommunication (SWIFT) Category 0 system messages (MT0xx) are exchanged between a user and the network, not between two banks like the business payment messages they wrap.
- 02
Acknowledgement (ACK) and negative acknowledgement (NAK) tell the sender whether the network accepted a submitted message; user-header authentication acknowledgements (UAK and UNAK) confirm or reject authentication, and there are retrieval requests, delivery notifications, and broadcasts.
- 03
A payment can be valid in its business content yet still fail at the network layer, so the operational record of acceptance or rejection is found in these Category 0 exchanges.
Practical use cases / 04
Where you would use this
An operations analyst investigating a missing payment checks whether the original message received an ACK or a NAK before assuming the beneficiary bank is at fault.
A support engineer reconciling sent and delivered messages uses delivery notifications to confirm a message actually reached the receiving institution.
A payments team distinguishes a business message rejection from a network-layer NAK so that the right team, business or technical, takes the next action.
Worked example / 05
Put the idea into a real situation
Illustrative example: Meridian Bank sends an MT103 to pay a beneficiary at Cedar Bank. Meridian's operator expects an acknowledgement, but the network instead returns a negative acknowledgement (NAK) because a header field failed validation. The MT103 itself was well formed as a payment, yet it never left the network, so no funds moved. When the beneficiary later chases the payment, Meridian's investigation team finds the answer not in the MT103 but in the Category 0 NAK recorded at the network layer.
Evidence & review / 07
Evidence & review
SWIFT FIN Category 0 system messages and service notifications; concept generalises to other SWIFT transports
What this brief simplifies: Treats FIN ACK/NAK as the concrete example while noting other transports carry their own acknowledgements. Exact codes and message layouts are set by SWIFT.
Sources for this brief2
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Category 0 system and service messages; ACK/NAK/UAK/UNAK
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal · Maya investigation and network-versus-business acceptance
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.