Swift services and platform checkpoint
Check that you can separate the things Swift actually provides from the things people assume it provides: a messaging network rather than a settlement account, a tracked reference that follows a payment end to end, a yearly release cycle that changes message versions on a fixed date, reference data you look up rather than guess, and a security programme every user has to attest against.
QUESTIONS AS TEXT
Q1. A colleague says "we'll just send the money over Swift." What is actually happening?
Answer: A: Swift carries the instruction between the banks; the money moves through accounts the banks hold with each other or at a central bank.
Swift is a messaging network, not a settlement system. Keeping that separation straight is the single most useful thing to know about it: when a payment is late, the question is which bank is holding it and why, not what Swift is doing with the money — because Swift never has the money.
Q2. What does the UETR give an operations team that a plain transaction reference does not?
Answer: A: One identifier that stays with the payment across every bank in the chain, so each leg can be located without asking each bank in turn.
A Unique End-to-end Transaction Reference is generated once, at the start, and every bank quotes the same value. That is what makes end-to-end tracking possible: before it existed, tracing a payment meant a chain of individual enquiries, each one a phone call or an MT199.
Q3. Why does the annual Standards Release matter to a project plan rather than only to a developer?
Answer: A: Message versions change on a fixed published date network-wide, so testing and deployment have to be finished before it, not around it.
The Standards Release is a fixed, network-wide event: on the published date, the new message versions are live for everyone. Because the date is not negotiable, it works backwards through a plan — a bank that discovers an incompatibility in the week before has run out of options.
Q4. A payment file has a beneficiary bank name and city but no BIC. What is the correct first move?
Answer: A: Look the institution up in the published reference-data directories and use the BIC recorded there.
Reference data is looked up, never inferred. Directories exist precisely because identifiers, standing settlement instructions and national clearing codes are assigned facts, and guessing them produces payments that fail late, in another institution's queue.
Q5. What is the Customer Security Programme asking of an institution connected to Swift?
Answer: A: That it meets a defined set of security controls for its own local environment, and attests to that annually.
The attacks that have moved real money did not break the network — they took over a bank's own terminals and operators and sent perfectly valid instructions. That is why the controls and the annual attestation focus on the user's local environment, access control and detection.