ClearingPost
Cross-Border Payments

SWIFT & Correspondent Banking

The infrastructure powering international payments — SWIFT messaging, correspondent banking networks, CLS foreign exchange settlement, and the emerging alternatives challenging the status quo.

SWIFT & Global Messaging Infrastructure
SWIFT FIN
Financial messaging · 50M+ messages/day
SWIFT FINplus
Enhanced messaging (ISO 20022) · Growing (replacing FIN)
SWIFT gpi
Payment tracking overlay · 85%+ of cross-border SWIFT payments
CLS
FX settlement · $6.5T daily settled value
SWIFT Go
Low-value cross-border · Growing
How Cross-Border Payments Work

Cross-border payment flows via SWIFT. Toggle between the legacy MT103 format and the current pacs.008 (ISO 20022) standard.

SWIFT pacs.008 Cross-Border Payment (ISO 20022)
Message flow (purple) & money flow (green)
1
Ordering CustomerMSG
Instructs payment to bank
2
Ordering Bank (Debtor Agent)MSG
Creates pacs.008 with BAH (head.001), debits customer
3
SWIFT FINplusMSG
Validates XML, routes via Transaction Manager (gpi tracking, UETR assigned)
4
Intermediary Bank (if needed)$$$
Processes enriched data, forwards pacs.008 with UETR
5
Beneficiary Bank (Creditor Agent)$$$
Receives pacs.008, credits beneficiary. Richer data enables STP.
6
Beneficiary Customer$$$
Credited. gpi Tracker updated at each step.
In gpi, a UETR tracks each step. In legacy, status is opaque until settlement.
pacs.008 vs MT103: Key Differences
Data richness: Structured XML vs fixed-length fields
Addresses: Structured (street, city, country) vs unstructured text
Identifiers: Mandatory LEI/BIC vs optional
Purpose codes: ISO purpose codes vs free text
Tracking: UETR built-in end-to-end vs gpi overlay
Compliance: Richer screening data, fewer false positives
Key Cross-Border Concepts
Correspondent Banking
Nostro / Vostro
UETR
PvP (Payment vs Payment)
Herstatt Risk
MT103
MT202 / MT202COV
pacs.008
Intermediary Bank
SWIFT BIC
De-risking