GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
PAYMENTSSIGNAL

The interactive academy for the standards, messages, and rails that move money.

GET IN TOUCH
LEARNING PATH / 16 STOPS

SWIFT specialist

This path covers the SWIFT network and the full MT payments set: message structure, the customer credit transfer, bank-to-bank transfers, and the confirmations and statements that close the loop. Serial and cover routing gets standards-level attention because it shapes everything from fees to sanctions exposure. The path closes with the ISO 20022 cross-border guidelines and MT-to-MX translation, because the migration is now part of the job.

FOR: Practitioners who work with SWIFT messaging daily — building, validating, or investigating MT messages and the correspondent flows they ride on.

AFTER THIS PATH YOU CAN

  • You can parse an MT message block by block and explain what each field tag carries.
  • You can construct the message chain for a cross-border customer payment, including the correspondent accounts involved.
  • You can choose between serial and cover routing for a given scenario and explain the trade-offs.
  • You can use confirmations and statements to prove what happened to a payment.
  • You can anticipate what changes — and what breaks — when an MT flow moves to ISO 20022.

THE LINE

Learning path as a transit lineEach station is a stop on the path; filled stations are mastered, the ringed station is where you are, and the rest are ahead. The full list follows this map as text.
  1. 01GO TO L2 — PRACTITIONER VIEW
    The SWIFT network and BICsWhat the SWIFT network actually is, what FIN does, and how a BIC identifies a bank — the addressing layer behind cross-border payments.The network, its identifiers, and its relationship controls are the ground your messages travel over. Knowing what a bank identifier code actually addresses prevents basic routing mistakes.
  2. 02GO TO L3 — TECHNICAL DETAILS
    MT message structureHow an MT message is put together: five blocks, numbered field tags, and the references that let banks track one payment across many systems.Blocks, tags, and field formats are the syntax of your daily work. Fluency here is what lets you spot a malformed message before the network or the counterparty does.
  3. 03GO TO L3 — TECHNICAL DETAILS
    Correspondent banking, nostro & vostroHow banks pay across borders with no shared system: accounts held at each other, chains of correspondents, and what nostro and vostro mean.MT payment messages only make sense against the nostro and vostro accounts they instruct. The account relationships explain why the same payment can be routed in more than one way.
  4. 04GO TO L4 — STANDARDS & SOURCES
    MT103: the customer credit transferThe MT103 carries one customer credit transfer between banks — who pays, who gets paid, how much, and who bears the charges along the way.The MT103 is the message you will handle most and be questioned on hardest. Field-level depth — parties, charges, routing — is the core of the specialty.
  5. 05GO TO L3 — TECHNICAL DETAILS
    MT202 and MT202 COVMT202 moves money between banks; MT202 COV is the variant that funds a customer payment and must show whose payment it is.Bank-to-bank transfers and the cover variant move the actual funds behind customer payments. Knowing when a cover message is required, and what it must mirror, is essential to routing work.
  6. 06GO TO L3 — TECHNICAL DETAILS
    MT101: the request for transferThe MT101 lets a customer ask a bank to move money from its own account — a request for transfer, not the interbank payment itself.Corporate customers initiate payments with the request for transfer, so it is the message where relationship, mandate, and execution questions meet. Knowing it rounds out the initiation side of the MT set.
  7. 07GO TO L3 — TECHNICAL DETAILS
    MT9xx: confirmations and statementsMT910 confirmations and MT940 statements tell a bank what happened on its accounts at other banks — the raw material of reconciliation.Confirmations and statements are your evidence when investigating what happened to a payment. Reading them fluently makes you the person who can close a case with proof rather than opinion.
  8. 08GO TO L4 — STANDARDS & SOURCES
    Serial versus cover routingTwo ways to route the same payment: pass the MT103 bank to bank, or send it direct and move the money separately with an MT202 COV.The serial-versus-cover choice determines which banks see payment details, how fast funds move, and where screening happens. It is the routing decision a SWIFT specialist must be able to defend at full depth.
  9. 09GO TO L3 — TECHNICAL DETAILS · OPTIONAL
    The pacs family: interbank messagesThe interbank workhorses: pacs.008 and pacs.009 move value, pacs.002 reports status, and pacs.004 brings money back.The pacs messages are the ISO 20022 counterparts of the MT messages you know. Learning the family makes the cross-border and translation topics that follow far easier.
  10. 10GO TO L4 — STANDARDS & SOURCES
    CBPR+: ISO 20022 for cross-border paymentsCBPR+ profiles ISO 20022 for correspondent banking over SWIFT; HVPS+ does the same for high-value payment systems.Cross-border payments are moving to ISO 20022 under agreed usage guidelines, and MT expertise is expected to extend there. This is where your serial-and-cover knowledge maps onto the new messages.
  11. 11GO TO L4 — STANDARDS & SOURCES
    MT-to-MX translation and truncationWhat happens when rich ISO 20022 data must fit MT fields and back — truncation, address handling, and one-to-many mappings.During coexistence, translated messages are a daily reality, and truncated or dropped data creates the investigations you will be asked to resolve. Deep translation knowledge is what distinguishes an MT specialist who made the transition.
  12. 12GO TO L4 — STANDARDS & SOURCES
    SWIFT gpi and payment trackingSWIFT gpi adds speed and transparency rules on top of the network and gives one reference, the UETR, that follows a payment end to end so banks can track it.gpi and the UETR are how modern cross-border payments are tracked and recalled. A SWIFT specialist is expected to explain end-to-end tracking and stop-and-recall, not just the message formats underneath them.
  13. 13GO TO L3 — TECHNICAL DETAILS
    The annual Standards Release (MSR)SWIFT updates its message standards once a year, and every connected institution moves to the new version on the same November weekend — the annual Standards Release.Every message you handle changes on the annual Standards Release cycle. Knowing the timeline and how to read a Standards Release Guide is what keeps your validation and back-office work current year to year.
  14. 14GO TO L3 — TECHNICAL DETAILS
    SWIFT connectivity, messaging services, and the CSPThe Swift messaging services FIN, InterAct, and FileAct, the validation that guards them, and the Customer Security Programme that hardens every user's environment.The messages only matter if the connection is safe. FIN, InterAct, and FileAct, plus the Customer Security Programme and its annual attestations, are what a SWIFT specialist is expected to know about running on the network securely.
  15. 15GO TO L2 — PRACTITIONER VIEW
    SWIFTRef and reference data directoriesTrusted directories of codes, identifiers, and settlement instructions keep payments routed correctly and out of manual repair.Clean routing depends on good reference data. SWIFTRef and its directories — BIC Directory, Bank Directory Plus, IBAN Plus, and the SSI directory — are where a specialist confirms who to pay and how to reach them.
  16. 16GO TO L3 — TECHNICAL DETAILS
    The Swift services portfolio and platformSwift is more than messaging: connectivity, gpi, low-value payments, hosted compliance, and a central transaction platform sit around the network.Swift is now a platform, not just a message. gpi variants, SWIFT Go, the Transaction Manager, and the hosted compliance services are the wider portfolio a SWIFT specialist is increasingly expected to place and use.