SWIFT — Cross-Border Payments
Overview
SWIFT (Society for Worldwide Interbank Financial Telecommunication) is a member-owned cooperative providing a global secure messaging network for financial institutions. SWIFT itself does not hold or transfer funds — it transmits standardized payment messages between correspondent banks, which then execute the actual fund movements through their respective accounts.
SWIFT connects over 11,000 financial institutions in 200+ countries and is the dominant rail for international (cross-border) US dollar payments. All international wire transfers from US banks to foreign beneficiaries — or US beneficiary accounts receiving funds from abroad — travel over SWIFT or through SWIFT-connected correspondent banks.
Correspondent Banking
Because most banks do not have direct accounts with every bank in every country, they use correspondent banks — intermediaries that hold accounts on behalf of other banks in a given currency and jurisdiction.
Nostro and Vostro Accounts
| Term | From Whose Perspective | Definition | Example |
|---|---|---|---|
| Nostro ("our money, with you") |
Bank A | An account held by Bank A at Bank B, in Bank B's currency | US Bank A holds a EUR account at Deutsche Bank (Bank B) to facilitate EUR payments |
| Vostro ("your money, with us") |
Bank B | An account held by Bank A at Bank B, from Bank B's perspective | Same account — Deutsche Bank calls it Bank A's "vostro" account |
Correspondent Chain
A SWIFT payment may travel through multiple correspondent banks before reaching the final beneficiary bank. Each hop in the chain adds processing time and may deduct correspondent fees from the payment amount. SWIFT gpi (see below) was introduced to address transparency and speed in multi-hop chains.
A typical correspondent chain for a US-to-India payment:
(Sending)
of Indian Bank
(Receiving)
Beneficiary
SWIFT Message Types — MT and MX
SWIFT has historically used MT (Message Type) format — proprietary, fixed-field, alphanumeric messages. SWIFT is currently migrating to MX messages (ISO 20022 XML) as part of the global ISO 20022 initiative. Both formats co-exist during the migration period.
Key MT Message Types for Payments
| MT Code | Name | Direction | Use Case |
|---|---|---|---|
MT 103 |
Single Customer Credit Transfer | ODFI → Correspondent / Beneficiary Bank | Standard international customer wire transfer. The most common cross-border payment message. Contains ordering customer, beneficiary, amount, value date, and remittance fields. |
MT 103 STP |
MT 103 Straight-Through Processing | ODFI → Beneficiary Bank | Enhanced MT 103 for automated processing without manual intervention. Requires strict field completion standards. |
MT 202 |
General Financial Institution Transfer | Bank → Correspondent Bank | Bank-to-bank transfer with no underlying customer transaction. Used for nostro funding and interbank settlements. |
MT 202 COV |
Cover Payment | ODFI → Correspondent | Interbank cover message sent alongside MT 103. The MT 103 carries payment details to the beneficiary bank; the MT 202 COV moves the actual funds. Must include originator information from the underlying MT 103. |
MT 199 |
Free Format Message | Bilateral | Used for queries, recalls, and free-form bilateral communications between correspondent banks. |
MT 192 |
Request for Cancellation | Sending Bank → Correspondent | Formal recall request for a previously sent MT 103 payment. |
MT 299 |
Free Format Confirmation | Bilateral | Confirmation of payment or status update. |
ISO 20022 MX Equivalents
| Legacy MT | ISO 20022 MX Equivalent | Description |
|---|---|---|
| MT 103 | pacs.008 | Customer Credit Transfer (FI to FI) |
| MT 202 | pacs.009 | Financial Institution Credit Transfer |
| MT 202 COV | pacs.009 ADV | Advice of Payment (cover payment) |
| MT 192 (recall) | camt.056 | Payment Cancellation Request |
| MT 196 (recall response) | camt.029 | Resolution of Investigation |
| MT 910 (credit confirmation) | camt.054 | Bank-to-Customer Debit/Credit Notification |
SWIFT gpi (Global Payments Innovation)
SWIFT gpi was launched in 2017 to address the core complaints about cross-border payments: lack of transparency, multi-day settlement, fee deductions without notice, and no end-to-end tracking. gpi is now mandatory for SWIFT member banks on cross-border payments.
Key gpi Features
| Feature | Description | Ops Benefit |
|---|---|---|
| UETR Tracking | Every gpi payment carries a Unique End-to-end Transaction Reference (UETR) — a UUID assigned at initiation and passed through every hop. | Enables real-time status tracking via SWIFT Tracker. Customer inquiries can be answered in minutes instead of days. |
| Same-Day Settlement SLA | gpi banks commit to crediting beneficiary accounts within the business day — or faster. The SWIFT Tracker shows confirmation timestamps at each hop. | Dramatically reduces "where is my payment?" queries from customers. |
| Fee Transparency | Each bank in the correspondent chain must report fees deducted from the payment amount. | Customers can see exactly how much was deducted at each hop and why the beneficiary received a different amount. |
| gSRP (Stop and Recall) | SWIFT's global payment recall mechanism. Allows the Sending Bank to request recall of a payment from any point in the chain. | Standard recall mechanism for erroneous payments. Replaces ad-hoc phone/email recalls. |
Processing Flow
- Customer Initiates International Wire: Customer submits the wire instruction with SWIFT BIC (Bank Identifier Code) of the beneficiary bank, IBAN (or local account number), beneficiary name/address, amount, value date, and payment purpose.
- OFAC and Sanctions Screening: Mandatory pre-submission screening of all parties (sender, beneficiary, all correspondent banks identified in the routing) against OFAC SDN, EU Consolidated List, UN Sanctions, and any other applicable lists. Any match triggers a hold.
- Correspondent Bank Selection: The Sending Bank's payment system determines the optimal correspondent chain based on the destination country, currency, and cost. The SWIFT BIC determines routing.
- MT 103 / pacs.008 Construction: The payment message is constructed with all required fields. The UETR is assigned at this point. In a cover payment structure, a separate MT 202 COV / pacs.009 is generated to move the interbank funds.
- Transmission via SWIFT Network: Messages are transmitted to the next hop in the correspondent chain via SWIFT FIN (for MT) or SWIFT MX.
- Correspondent Bank Processing: Each correspondent bank in the chain validates, screens, deducts fees (if applicable), and forwards the message to the next bank. gpi Tracker is updated at each hop.
- Beneficiary Bank Credits Account: The final beneficiary bank receives the payment, validates the beneficiary account, and credits the account. gpi confirmation (SWIFT camt.054) is sent back to the originating chain.
Settlement Timeline
Unlike Fedwire (immediate) or ACH (defined batch cycle), SWIFT cross-border payment settlement timing depends on the correspondent chain length, currency, and destination country banking hours.
| Payment Type | Typical Timeline | Factors Affecting Speed |
|---|---|---|
| USD to USD (US correspondent chain) | Same day to T+1 | Submission time, Fedwire cut-off, correspondent availability |
| USD to EUR (US to Europe) | T+1 to T+2 | TARGET2 operating hours, cut-off times in both time zones, correspondent hops |
| USD to INR, USD to emerging markets | T+2 to T+5 | Regulatory holds, local clearing systems, correspondent chain depth, local banking holidays |
| gpi Same-Day commitment (Major currencies) | Same business day | Applies to gpi-member banks; subject to cut-off and bank operating hours |
Compliance and Sanctions Requirements
OFAC — Mandatory for All International Wires
- Screen all parties in the payment (ordering customer, beneficiary, all named banks in the SWIFT message) against the OFAC SDN List.
- For MT 103, screen fields: :50K (Ordering Customer), :57A (Account with Institution), :59 (Beneficiary Customer), and any :70 (Remittance Information) content.
- A confirmed match requires immediate hold. Do not process or forward the wire. Escalate to Compliance within 1 business hour.
Travel Rule (31 CFR 103.33) — Bank Secrecy Act
- For international wire transfers of $3,000 or more: Full originator information (name, address, account number) and beneficiary information must be included in the SWIFT message and passed to all subsequent correspondent banks.
- The ISO 20022 pacs.008 structured format fully supports Travel Rule compliance. Ensure the
<Dbtr>(Debtor) and<Cdtr>(Creditor) elements are completely populated. - For payments below $3,000: At minimum, include originator account number in the message.
AML Program Requirements
- Monitor international wire volume for patterns consistent with money laundering: structuring below threshold, rapid movement through multiple accounts, payments to high-risk jurisdictions, round-number amounts.
- Maintain a documented Risk-Based Approach (RBA) for correspondent banking relationships — Know Your Correspondent (KYC) due diligence must be performed and refreshed periodically.
- De-risking (exiting correspondent relationships) without documented due diligence may itself trigger regulatory scrutiny — maintain records of all KYC assessments.
Exception Handling and Recalls
Payment Query — SWIFT Tracker
For gpi payments, use the SWIFT Tracker (accessible via SWIFT gpi portal or integrated payment hub) to view real-time status. The UETR provides the tracking reference. Status codes:
| gpi Status | Meaning | Action |
|---|---|---|
| ACSP — Accepted, Settlement In Progress | Payment is being processed in the correspondent chain | No action — monitor |
| ACCC — Accepted, Credit Completed | Beneficiary account has been credited | Confirm with customer; close inquiry |
| RJCT — Rejected | Payment was rejected by a bank in the chain | Review rejection reason; resubmit with corrections or return funds to customer |
| PDNG — Pending | Payment is held at a bank (e.g., compliance review) | Contact the holding bank; may require additional documentation |
SWIFT gSRP — Recall Process
- Obtain the UETR from the original payment.
- Submit a
camt.056(Payment Cancellation Request) via SWIFT Tracker / gSRP portal. Include the UETR, reason for recall (DUPL = duplicate, FRAD = fraud, TECH = technical error, CUST = customer request), and UETR of the original payment. - The receiving bank must respond within 1 business day with a
camt.029(Resolution of Investigation) — either confirming the recall or rejecting it (e.g., funds already paid to beneficiary). - If the beneficiary bank cannot recover the funds (beneficiary account drained), escalate to Legal. Cross-border fund recovery is complex and jurisdiction-dependent.
Reconciliation Procedures
Nostro Account Reconciliation
SWIFT nostro account reconciliation is one of the most critical — and complex — reconciliation tasks in international operations. Each nostro account (USD account held at a correspondent bank abroad, or foreign currency account held domestically) must be reconciled daily.
- Obtain the correspondent bank's nostro account statement (MT 940/950 or camt.053) for the prior business day.
- Match each debit and credit on the statement against internal SWIFT payment records (outgoing MT 103 debits, incoming MT 103 credits).
- Identify any unmatched items — break items — and categorize: timing difference (expected to match next day), fee deduction, correspondent error, or unexplained.
- Escalate unexplained break items over $10,000 (or institutionally-defined threshold) to the Operations Supervisor immediately.
- Send queries via SWIFT MT 195/MT 199 or email to the correspondent bank for all unresolved items within 24 hours.
- Confirm that nostro balances are sufficient for next-day outgoing wire commitments. Pre-fund nostro accounts ahead of high-volume periods (month-end, quarter-end).