Why SWIFT matters
SWIFT is the dominant messaging layer for cross-border bank-to-bank communication. When a US bank instructs a Spanish bank to credit a Spanish account, the instructions travel over SWIFT. The funds themselves move via correspondent-banking relationships (nostro/vostro accounts), not over SWIFT itself.
This distinction matters: SWIFT is messaging, not a settlement rail. The friction, cost, and time of a cross-border wire come mostly from the chain of correspondent banks involved, not from SWIFT itself.
When SWIFT matters most
- International wires — corporate B2B, international payroll, cross-border treasury
- Trade finance — letters of credit, documentary collections
- Securities messaging — DvP settlement instructions
The SWIFT gpi initiative and the network-wide ISO 20022 migration have substantially improved transparency and data richness for member institutions over the last decade.
Common pitfalls
- Confusing SWIFT with the rail. SWIFT can tell you a payment was instructed; the correspondent chain decides when it actually lands.
- Hidden fees. Each correspondent in the chain can deduct fees; advertised FX rates rarely reflect total cost.
- Sanctions exposure. Cross-border payments touch multiple jurisdictions; sanctions screening at every hop is non-optional.
For corridors that SWIFT serves badly, stablecoin rails and fintech corridor networks are increasingly viable alternatives — but SWIFT remains the global default.