Understanding SWIFT for Remittance Operators: How International Wires Actually Work

SWIFT is not a payment system — it is a secure messaging network that tells banks to move money on your behalf. When you send an international wire for a customer, SWIFT transmits standardised instructions (like an MT103 message) between your bank and the beneficiary's bank, often passing through one or more correspondent banks along the way. The actual funds move through settlement accounts held between those banks, not through SWIFT itself.

This distinction matters because it explains almost every payment delay your customers complain about. If you have ever had to tell a customer their AUD 3,000 transfer to a relative is "still processing" three days later, the answer usually lies somewhere in the correspondent banking chain — and understanding that chain gives you the language to explain, investigate, and set realistic expectations.

Key Takeaways

• SWIFT is a messaging network, not a money mover — it carries payment instructions between banks, while settlement happens through correspondent account relationships.
• The MT103 is the customer credit transfer message that carries your remittance; the MT202 is the bank-to-bank cover payment that moves the funds behind it.
• BIC codes (also called SWIFT codes) identify each institution in the chain; an incorrect BIC is a leading cause of returned or delayed payments.
• Payments slow down at correspondent banks, cut-off times, and compliance screening — not usually at your own bank.
• SWIFT gpi and the mandatory move to ISO 20022 are reshaping transparency and data quality for cross-border payments through 2025 and beyond.

What SWIFT Actually Is (and Isn't)

SWIFT stands for the Society for Worldwide Interbank Financial Telecommunication. It is a member-owned cooperative headquartered in Belgium that operates a secure network connecting more than 11,000 financial institutions across 200+ countries, according to SWIFT's own network statistics.

The most common misconception is that SWIFT holds or transfers money. It does not. SWIFT sends encrypted, standardised messages instructing banks to debit and credit accounts. Think of it as a highly secure email system built exclusively for financial institutions — the message says "pay this beneficiary", but the money itself moves through pre-existing account relationships between banks.

For you as a remittance operator, this means the speed and success of a wire depends less on SWIFT and more on the banking relationships between the institutions in the payment chain. When you understand who those institutions are, you can diagnose problems your customers face.

The Correspondent Banking Chain Explained

Most banks do not hold accounts with every other bank in the world. Instead, they rely on correspondent banks — larger institutions that maintain settlement accounts (called nostro and vostro accounts) and act as intermediaries.

A nostro account is "our account with them" from the sending bank's perspective. A vostro account is "your account with us" from the correspondent's perspective. When money moves internationally, it hops through these accounts.

Here is a typical chain for a remittance from Australia to a smaller economy:

1. Your ordering bank (in Australia) sends an MT103 instruction and debits your account.
2. The funds pass to an Australian correspondent bank with strong international relationships.
3. That correspondent routes to an intermediary bank in a major currency hub (often USD-clearing in New York or EUR-clearing in Frankfurt).
4. The intermediary passes to the beneficiary's bank in the destination country.
5. The beneficiary's bank credits the recipient's account.

Each hop introduces potential for delay, an intermediary fee, and a compliance check. A three-hop chain is common; corridors to less-connected countries can involve four or more institutions.

Why Longer Chains Cost More and Take Longer

Every intermediary in the chain can deduct a correspondent banking fee — typically AUD 15 to AUD 50 per hop — from the transferred amount unless you specify OUR charges (sender pays all fees). Each intermediary also runs its own sanctions and AML screening, and any match or near-match can freeze the payment for manual review.

This is why the same AUD 1,000 transfer might arrive next-day in a well-connected corridor and take five days in a corridor with a thin correspondent network. The chain length, not your effort, drives the timeline.

SWIFT Message Types: MT103 vs MT202

SWIFT messages follow a standardised format identified by an "MT" (Message Type) number. Two dominate cross-border remittance flows, and understanding the difference helps you read confirmations and investigate delays.

Message	Purpose	Who it credits	Contains customer detail?
MT103	Single customer credit transfer	Ultimately the beneficiary	Yes — ordering customer and beneficiary names, amount, purpose
MT202	General financial institution transfer (cover payment)	A bank	No — bank-to-bank only
MT202 COV	Cover payment linked to an MT103	A bank, with underlying customer data	Yes — carries the related MT103 details

The MT103 is the workhorse of remittance. It carries the instruction to pay a named beneficiary, including the ordering customer, the amount, the currency, and the payment reference. When your customer asks for "proof of payment", the MT103 confirmation is what they mean.

The MT202 moves the actual funds between banks to "cover" the MT103 instruction. In a cover payment method, the MT103 tells the beneficiary bank "pay your customer", while a parallel MT202 COV moves the settlement funds through the correspondent chain to reimburse them.

Why MT202 COV Matters for Compliance

Before 2009, plain MT202 cover payments stripped out the underlying customer information, creating a transparency gap that concerned the FATF. The MT202 COV was introduced to carry the originator and beneficiary details through the correspondent chain, satisfying FATF Recommendation 16 (the "travel rule") on originator and beneficiary information.

As an MTO, you are subject to the same travel rule obligations under the AML/CTF Act 2006 and AUSTRAC's rules. Complete, accurate payer and payee data in your instructions reduces the risk of your payments being held for information requests at an intermediary bank.

BIC Codes: The Address System of SWIFT

A BIC (Bank Identifier Code) — commonly called a SWIFT code — is the unique address for each institution on the network. Getting it wrong is one of the most common causes of returned payments.

A BIC is 8 or 11 characters:

• Characters 1–4: Bank code (e.g. CTBA for Commonwealth Bank)
• Characters 5–6: Country code (AU for Australia)
• Characters 7–8: Location code (city/region)
• Characters 9–11: Branch code (optional; XXX denotes head office)

For example, Commonwealth Bank of Australia's BIC is CTBAAU2S. The 8-character version routes to the head office; the 11-character version specifies a particular branch.

Common BIC Errors That Delay Payments

• Wrong branch code — the payment routes to the wrong location and requires manual rerouting.
• BIC and IBAN mismatch — in IBAN countries (most of Europe), the account number's embedded bank identifier must match the BIC.
• Outdated BIC after a bank merger — decommissioned codes bounce the payment.

Always verify the beneficiary BIC against the beneficiary's own bank details, not a lookup tool alone. A validated BIC at onboarding prevents returns that erode both your margin and your customer's trust.

Cut-Off Times: The Hidden Cause of "Next-Day" Delays

Every bank in the chain operates a cut-off time — the deadline after which a payment is processed the next business day. Miss a cut-off, and a payment your customer submitted on Monday afternoon may not enter the chain until Tuesday.

Cut-offs compound across time zones. A payment sent from Australia in the afternoon may already be past the cut-off at a European correspondent because of the time difference, adding a full day before that leg even begins.

Currency clearing systems add their own constraints:

Currency	Clearing system	Typical AEST cut-off consideration
USD	Fedwire / CHIPS (US)	US business hours lag Australia by ~14–16 hours
EUR	TARGET2 (Europe)	European day begins in the Australian evening
GBP	CHAPS (UK)	UK business hours lag by ~9–11 hours
AUD	RITS (Australia)	Domestic leg only

Weekends and public holidays in any country in the chain halt processing. A payment routed through a US correspondent will not settle on the US Thanksgiving holiday even if it is a normal business day in Australia. Setting customer expectations around these realities prevents complaint calls.

Why Payments Take Longer Than Customers Expect

When a customer complains their transfer is "stuck", the delay almost always sits at one of five points. Knowing them lets you investigate quickly and communicate credibly.

1. Correspondent processing — the payment is queued at an intermediary awaiting its own cut-off or settlement window.
2. Compliance screening hold — a name matches or nearly matches a sanctions list, triggering manual review at an intermediary or beneficiary bank.
3. Incomplete payment data — a missing beneficiary address or purpose code prompts a request for information (RFI) that pauses the payment until answered.
4. Currency conversion at an intermediary — an unexpected conversion step adds a hop and a spread.
5. Beneficiary bank processing — the destination bank has slow internal crediting, especially in corridors with limited automation.

SWIFT gpi (see below) now lets you trace exactly where a payment sits, turning "we're checking" into "your payment cleared the Australian leg and is with the New York correspondent, expected to credit tomorrow".

SWIFT gpi: Real-Time Tracking for Cross-Border Payments

SWIFT gpi (global payments innovation) launched in 2017 to address the transparency and speed problems that plague correspondent banking. It assigns each payment a Unique End-to-end Transaction Reference (UETR) — a 36-character identifier that lets any party in the chain track the payment's status and location.

According to SWIFT, the majority of gpi payments are credited to the end beneficiary within minutes to a few hours, and nearly all within 24 hours. gpi also provides:

• End-to-end tracking via the UETR, similar to a parcel tracking number.
• Transparency on fees deducted at each hop.
• Confirmation of credit to the beneficiary account.

If your banking partner offers gpi tracking, use the UETR in your customer communications. It is the single most powerful tool for reducing "where is my money" enquiries.

ISO 20022: The New Standard Replacing MT Messages

The MT message format is being replaced by ISO 20022 — a richer, structured data standard using MX messages (e.g. pacs.008 replaces MT103, pacs.009 replaces MT202). The coexistence period for cross-border payments and reporting ended in November 2025, making ISO 20022 the mandatory standard on the SWIFT network for these flows.

ISO 20022 matters for remittance operators because it carries structured, granular data — separate fields for beneficiary name, street, city, and country rather than free-text blocks. This improves sanctions screening accuracy and reduces false-positive holds, but it also means your systems and data capture must produce clean, structured information at onboarding.

If your platform still generates free-text address blocks or truncates beneficiary detail, you risk payments being rejected by downstream banks enforcing the new standard. Confirm your PSP or banking partner has fully migrated and that your onboarding captures the structured fields ISO 20022 requires.

Practical Example: Tracing an Australia-to-Philippines Wire

Consider a customer sending AUD 2,000 to a family member in Manila. Here is how the wire moves and where time is spent:

1. Monday 2pm AEST — Customer submits. Your bank generates an MT103 (or pacs.008) and debits AUD 2,000. Cut-off met.
2. Monday evening — Funds convert to USD and route to a US correspondent bank via the sending bank's nostro account. A parallel MT202 COV carries the settlement.
3. Monday night AEST / Monday morning US — US correspondent screens the payment. A clean payment clears; a name match holds it for review.
4. Tuesday — Funds reach the beneficiary bank in the Philippines. The bank converts USD to PHP and credits the recipient.
5. Tuesday–Wednesday — Recipient sees funds, depending on the destination bank's crediting speed.

Total: one to three business days for a clean payment. If the US correspondent flags a screening hit or the beneficiary detail is incomplete, add one to three days for the RFI cycle. Communicating this range up front prevents disappointment.

How This Shapes Your Operations

Understanding SWIFT mechanics translates directly into better operations:

• Set realistic delivery expectations by corridor — publish a range, not a single day, and note that holidays and screening can extend it.
• Capture clean, structured beneficiary data at onboarding to satisfy ISO 20022 and reduce RFI holds.
• Validate BICs against the beneficiary's actual bank details before sending.
• Use UETR tracking where your partner offers gpi, and give customers a reference they can follow.
• Choose banking partners with strong correspondent networks in your priority corridors — fewer hops means faster, cheaper, more reliable delivery.

Many operators reduce their reliance on traditional SWIFT chains for high-volume corridors by using alternative rails — local payout partners, mobile money integrations, or platform providers that pre-fund destination accounts. SWIFT remains the backbone for many currencies, but knowing when a faster rail exists is a competitive advantage.

Frequently Asked Questions

Is SWIFT the same as a bank transfer?

No. SWIFT is the messaging network that carries the instruction to make a transfer between banks internationally. The actual money moves through correspondent banking relationships and clearing systems, not through SWIFT itself. A domestic bank transfer in Australia uses systems like the New Payments Platform or RITS, not SWIFT.

What is the difference between an MT103 and an MT202?

An MT103 is a customer credit transfer that instructs a bank to pay a named beneficiary and carries customer details. An MT202 is a bank-to-bank transfer that moves settlement funds between financial institutions. The MT202 COV variant links to an MT103 and carries the underlying customer information to satisfy FATF travel rule requirements.

Why do international wires sometimes lose money along the way?

Each correspondent bank in the chain can deduct a processing fee — typically AUD 15 to AUD 50 — unless the sender specifies OUR charges to pay all fees upfront. Intermediary currency conversions can also apply an FX spread. Longer correspondent chains mean more potential deductions.

How can I track where a SWIFT payment is?

If your banking or payment partner supports SWIFT gpi, each payment has a Unique End-to-end Transaction Reference (UETR) that lets you see its status and location in the chain, along with fees deducted and confirmation of credit. Ask your partner whether gpi tracking is available for your corridors.

Has ISO 20022 replaced SWIFT MT messages?

The coexistence period for cross-border payments and reporting ended in November 2025, making ISO 20022 (MX messages such as pacs.008) the mandatory standard for these flows on the SWIFT network. ISO 20022 uses richer, structured data fields, which improves screening accuracy and requires operators to capture clean beneficiary information.

What causes a SWIFT payment to be returned?

Common causes include an incorrect or outdated BIC, a BIC and IBAN mismatch, incomplete beneficiary details, a closed beneficiary account, or a compliance rejection at an intermediary bank. Validating beneficiary details and BICs at onboarding prevents most returns.

---

This information is general in nature and does not constitute legal advice. Consult AUSTRAC or a qualified legal professional for advice specific to your situation.

Want to sharpen your corridor operations and pricing? Explore our corridor guides for country-specific payout insights, or use the rate board tool to benchmark your FX pricing. Join our newsletter for practical updates on payments infrastructure and AUSTRAC compliance.