What is the full form of SWIFT? All you need to know

A US customer owes an Indian exporter $10,000.

The customer opens their bank account, enters the beneficiary details and sends the payment. Somewhere in that process, the word SWIFT appears.

What exactly did SWIFT do?

The easiest way to understand it is to follow that $10,000 payment from the sender's bank to the beneficiary.

The customer clicks Send: what does SWIFT actually do?

The sending bank now needs to tell the Indian bank:

Who is paying? → Who should receive the money? → How much? → In which currency? → Which institutions are involved? → What is the payment for?

SWIFT provides the network and common financial language used to communicate those instructions securely.

Its full form is Society for Worldwide Interbank Financial Telecommunication.

Swift began in 1973 with 239 banks across 15 countries. Today, it connects 11,500+ institutions across more than 200 countries and territories.

SWIFT sends financial messages. It does not itself hold customer money or settle the transaction.

The actual funds move through banking accounts, correspondent relationships and payment or settlement systems.

The bank asks for a SWIFT code: what is it identifying?

To send the instruction to the right financial institution, the payment needs a BIC, commonly called a SWIFT code.

Under ISO 9362, the core BIC contains 8 characters, with an optional 3-character branch identifier.

A simplified structure is:

AAAA BB CC DDD

Where:

• AAAA = business-party identifier
• BB = country code
• CC = additional party/location identifier
• DDD = optional branch identifier

So a BIC identifies the financial institution or business party involved in the payment. It does not identify the beneficiary's individual bank account.

The banks do not have a direct relationship: what happens now?

This is where correspondent banking enters the picture.

Suppose the US bank does not maintain the required direct account relationship with the Indian beneficiary bank. Another bank may sit between them.

The payment path could look like:

US bank → correspondent bank → Indian bank → exporter

The correspondent helps bridge the financial relationship and settlement path.

SWIFT carries the instructions; participating institutions handle settlement.

Swift says 86% of messages are direct or involve only one intermediary, even though more than 40,000 payment routes are available across its network.

The payment leaves the sender: can anyone see where it is?

Every payment instruction carried over Swift contains a Unique End-to-end Transaction Reference (UETR).

A UETR is a 36-character reference based on the UUID v4 standard. The same reference follows the payment throughout its journey.

Think of it as: BIC = institution; account/IBAN = beneficiary account; UETR = payment.

Swift tracking services can use the UETR to show information such as payment status, timestamps, instructed amount and credited amount.

Where does MT103 fit now?

MT103 is a SWIFT message format used for customer credit transfers. It can contain valuable payment information, but MT103 is not the same thing as a tracking number.

The coexistence period for legacy MT and ISO 20022 cross-border payment messaging ended in November 2025. The newer ISO 20022 environment uses richer, more structured payment data that can improve automated processing, compliance screening and reconciliation.

How long is our $10,000 payment actually inside the network?

Swift currently reports:

• 75% of payments reach the beneficiary bank within 10 minutes
• more than 90% reach it within one hour

Once the message reaches the beneficiary institution, local processing can still include:

• sanctions or AML checks
• foreign-exchange processing
• regulatory reporting
• beneficiary verification
• local operating-hour constraints
• manual exception handling

The customer's banking app can therefore say completed while the exporter still cannot see the funds.

The exporter receives less than $10,000: where did the difference go?

SWIFT itself is not one universal consumer transfer fee.

Costs can arise across the banking chain:

• sender-bank fee
• intermediary/correspondent charges
• beneficiary-bank fee
• FX spread or conversion charge
• amendment or investigation charges

Payment instructions can also use OUR, BEN and SHA to indicate whether charges are borne by the sender, beneficiary or shared.

The useful question is: how much did the sender pay, and how much finally reached the beneficiary?

Does every international business payment need SWIFT?

No.

SWIFT remains important for global bank-to-bank reach, but repeat collections can also use local payment rails.

An Indian exporter collecting GBP from a UK buyer, for example, can use UK-local collection details. The buyer pays domestically rather than initiating a SWIFT wire to India.

PayGlocal's Multi-Currency Accounts use this model across supported markets. Indian businesses can collect in 33+ currencies from 180+ countries, with local receiving details in currencies including USD, GBP, EUR, CAD and AUD.

The funds are then converted and settled into the business's Indian bank account in INR, with settlement within 24 hours and automated FIRA.

This means SWIFT is not the only architecture for cross-border collection.

Five SWIFT terms worth remembering