SWIFT connectivity, messaging services, and the CSP
The Swift messaging services FIN, InterAct, and FileAct, the validation that guards them, and the Customer Security Programme that hardens every user's environment.
IN ONE LINE
Think of Swift not as a bank or a place money is kept, but as a very careful postal service used by banks to send each other instructions.
Money does not travel through Swift; messages do, and those messages tell banks to move money that sits in their own accounts.
Because these messages are so consequential, the postal service offers different ways to send them, suited to different needs.
Some messages are single, urgent notes handed over one at a time and held safely until the receiver picks them up.
Some are quick back-and-forth exchanges, like a short conversation.
And some are large sacks of documents sent in bulk.
Just as importantly, a careful postal service does not only worry about the letters in transit; it also worries about whether each sender's own mailroom is locked and trustworthy.
Much of the effort, then, goes not just into carrying messages safely but into making sure every participant keeps their own doors secure.
WHAT IT ACTUALLY IS
Swift offers several messaging services, each suited to a different job.
FIN (Swift FIN messaging) is the classic store-and-forward service that carries structured MT (message type) messages, such as bank-to-bank funds transfers, one message at a time.
Swift accepts, validates, and holds each FIN message, then delivers it to the receiver, so neither party need be online at the same moment.
InterAct is a service for real-time, interactive exchange of individual messages, commonly the newer ISO 20022 MX messages used in modern market infrastructures.
FileAct is for moving files and bulk data, and it is largely format-agnostic, so it can carry batches of instructions, statements, or reports that do not fit a single structured message.
Choosing among them depends on whether the traffic is a single instruction, a live exchange, or a large file, and on which message standard is in use.
Together they let Swift serve both older MT flows and newer structured ones.
HOW IT WORKS
A key strength of the FIN (Swift FIN messaging) service is that it does not simply carry whatever it is given; it validates messages before accepting them.
Each field in an MT (message type) message has a defined format, and the network checks that the content fits.
Beyond single fields, FIN applies network-validated rules: cross-field checks that confirm combinations of fields are consistent with each other, for instance that a code word matches the presence or absence of another field it governs.
Fields are also marked as mandatory or optional, so the network can reject a message that omits something it must contain.
A message that fails validation is rejected at the network rather than passed on, which stops many malformed instructions before they ever reach a receiver.
This up-front discipline is one reason MT messages have been dependable for decades: the format is strict, the rules are published, and the network enforces them evenly for everyone, so a receiver can trust the shape of what arrives.
THE WORDS
- Swift Customer Security Programme (CSP)
- A Swift programme setting mandatory and advisory security controls for users, with annual self-attestation against the controls framework.
- SwiftNet FileAct
- A SwiftNet service for transferring files and bulk data, format-agnostic, used for batches such as bulk payments and reports.
READ FIRST
CONNECTED TO
SOURCES
Derived from SWIFT connectivity, messaging services, and the CSP. Every claim on this card is sourced on that page.