One payment, two journeys: how the message and the money travel separately over SWIFT.
When a bank sends an international payment, two things happen in parallel. A message travels over SWIFT telling each bank what to do. And value moves across a chain of accounts that banks hold with each other — debited here, credited there — until it reaches the beneficiary's bank. This second layer, called correspondent banking, is centuries older than SWIFT, and it's the part that determines how many banks touch your payment, how many fees get taken, and how long it takes.
The vocabulary comes from Latin, and it's all about perspective:
When the Bangkok bank sends USD 10,000 on a customer's behalf, it's really instructing its New York correspondent: "debit our account with you, and credit this other bank." No physical money crosses the ocean. Balances shift on ledgers.
Take a small design studio in Chiang Mai paying a USD invoice to a software vendor in Germany whose account is held in USD.
Every step is fast when automated. Every step can also pause — for a compliance query, a cut-off time, a public holiday, or a missing piece of information.
Regulators require cover messages to carry the underlying customer details, so intermediary banks can screen who is really paying whom.
| Role | Who it is | What it does | Can it deduct a fee? |
|---|---|---|---|
| Ordering (sending) bank | Your bank | Checks, debits you, sends the message | Yes — sending fee |
| Correspondent bank | A bank holding an account for another bank in a given currency | Settles the currency on the sending bank's behalf | Yes |
| Intermediary bank | Any bank in the chain between sender and receiver (often a correspondent) | Relays and screens the payment | Yes — "lifting" fees |
| Beneficiary bank | Recipient's bank | Final checks, credits the recipient | Yes — receiving fee |
| Settlement system | Fedwire, CHIPS, T2, CHATS, BAHTNET etc. | Final, irrevocable settlement of each currency | Built into bank pricing |
The number of banks between you and your payee is the single biggest driver of cost and delay in a SWIFT payment — and it's usually invisible to you. Two practical takeaways: send in the currency your payee's account is actually held in (so the receiving bank doesn't convert at its own rate), and ask your provider which route and charge option it will use before you send. Where both ends have strong local payment rails, a provider that collects and pays out locally can avoid the correspondent chain entirely.
DSGPay helps businesses get paid by overseas customers and pay suppliers abroad, as if they were local.
Use DSGPay through OneWeb, the DMA mobile app or our GraphQL API.
DollarSmart Global Pte. Ltd. holds a Money Service Operator licence in Hong Kong (No. 15-08-01682) and is registered with AUSTRAC in Australia. Bahtsmart Co., Ltd. is licensed by the Bank of Thailand (ง(3.3)003/2568).
DSGPay ช่วยร้านค้าไทยรับเงินจากนักท่องเที่ยวต่างชาติ ลูกค้าจ่ายผ่านธนาคารประเทศของตัวเองได้โดยตรง ร้านค้าได้รับเป็นเงินบาท
บริษัท บาทสมาร์ท จำกัด ได้รับใบอนุญาตให้บริการรับชำระเงินแทนจากธนาคารแห่งประเทศไทย (ง(3.3)003/2568)