Anatomy of a Cross-Border Payout

Why It’s Worth Tracing Step by Step

The cost of a cross-border payment is hidden by design in the legacy system. A wire transfer’s published fee covers the sending bank’s part. The correspondent banks each take their own cut. The receiving bank may charge an inbound fee. The FX rate baked into the quote is a retail rate that includes the bank’s margin. The customer sees one number on the form and one number on the receipt; the gap between them is “the rest of the system.”

On the stablecoin side, the costs are mostly visible: a network fee, a provider fee, and the mid-market FX rate. There is still a leg where the recipient’s local currency lands in their bank account — and that leg can be priced more or less aggressively. But the structural difference is that the on-chain settlement removes the entire correspondent-banking layer.

A $5,000 SWIFT Wire from London to Mumbai

Scenario: a UK-based design studio paying a $5,000 invoice to an Indian contractor. The studio’s bank is a major UK high-street bank. The contractor’s bank is a major Indian private bank with a savings account.

1. 1

   Sender bank — debits GBP, applies FX, sends MT103

   The studio initiates a SWIFT wire from their UK business account in GBP. The bank converts GBP to USD at its retail FX rate (typically 1.5%–3% over mid-market on this size), debits the equivalent in GBP, and adds an explicit transfer fee (typically £15–£25 / approx $20–$32). The bank generates an MT103 message and sends it to its USD correspondent.

   Visible cost: approx $20–$32 transfer fee.
   Hidden cost (FX margin): 1.5%–3% on $5,000 = $75–$150.

2. 2

   USD correspondent — routes via Fedwire/CHIPS, takes “lifting fee”

   The UK bank’s USD correspondent (a US-based money-centre bank) receives the message, debits the UK bank’s USD nostro account, and prepares to forward the payment toward an Indian correspondent that has an INR settlement relationship. The correspondent typically takes a “lifting fee” of $10–$25 from the payment in transit.

   Hidden cost (lifting fee): $10–$25 deducted from the amount.

3. 3

   Indian correspondent — converts USD to INR, takes spread, forwards via NEFT/RTGS

   The Indian correspondent receives the USD, applies its own retail INR conversion (which the recipient will see as the “rate at which the credit was made”), and forwards the INR to the recipient’s bank via NEFT or RTGS. The spread on this leg is typically another 0.5%–1.5% — sometimes the dominant cost.

   Hidden cost (correspondent FX spread): 0.5%–1.5% = $25–$75.
   Hidden cost (potential second lifting fee): $5–$15 if a second correspondent is involved.

4. 4

   Receiving bank — credits the recipient’s account

   The recipient’s bank receives the INR via NEFT or RTGS, posts it to the savings account, and notifies the recipient. Some Indian banks charge an inbound foreign remittance fee (typically ₹100–₹500); others don’t. Form 15CA/15CB compliance handling sits with the recipient’s bank or the recipient.

   Possible visible cost: ₹100–₹500 inbound fee.

5. 5

   Total time: 1 to 5 business days

   From the studio clicking send to the contractor seeing the credit, the typical end-to-end time is 1–3 business days within main banking hours; 3–5 business days if any leg falls outside operating windows or triggers a manual review.

The Same $5,000 via USDC Stablecoin Payout

Same scenario, same studio, same contractor. The studio holds USDC; the contractor receives INR via UPI or bank transfer.

1. 1

   Studio initiates payout — selects India + UPI

   The studio opens the payout provider’s app, selects India as the destination, the contractor’s UPI ID as the recipient, and $5,000 in USDC as the source. The app shows the locked quote: mid-market USDC/INR rate, the provider fee (e.g., 0.3%), and the network fee for the chosen chain.

   Visible cost: $15 provider fee (0.3%).
   FX margin: Mid-market — no spread.

2. 2

   USDC moves on-chain to the settlement wallet

   On confirm, USDC is debited from the studio’s balance and moved on-chain to the provider’s settlement wallet. On Solana or Base, the network fee is sub-cent. On Ethereum mainnet, $1–$5. The transaction is final once confirmed.

   Visible cost: $0.01–$5 network fee.

3. 3

   Off-ramp partner converts USDC to INR at locked rate

   The provider’s licensed Indian PA-CB partner sells USDC for INR at the locked mid-market rate. The provider’s fee was already deducted at quote time; no additional spread is applied.

   Hidden cost: None on a transparent provider — the visible fee already covers this leg.

4. 4

   UPI push — INR credited to contractor’s account

   The PA-CB partner initiates the UPI credit. NPCI routes it to the contractor’s bank, which posts the INR and pushes a notification. End-to-end time from studio confirm to contractor credit: typically a few minutes.

   Visible cost: Zero.

5. 5

   Total time: minutes

   Most of the elapsed time is the on-chain confirmation window. UPI itself is sub-minute.

Side by Side

The numbers are illustrative — exact spreads, fees, and FX rates fluctuate by bank, currency pair, day of week, and amount. The structural pattern, though, is consistent across major corridors: the SWIFT cost is ~3%–4% on small amounts and improves marginally with scale; the USDC cost stays flat at the provider’s quoted percentage regardless of size.

When SWIFT Still Wins

The case for SWIFT is not zero. There are scenarios where it still beats stablecoin rails.

• Very large institutional flows. On $1M+ wires between major banks, the FX margin is negotiable, the correspondent fees are absorbed by the relationship, and the operational maturity of SWIFT (compliance, sanctions screening, audit trail) is what corporate treasury teams know how to defend.
• Currency pairs without a stablecoin off-ramp. Stablecoin rails depend on a partner being licensed in the receiving jurisdiction. For currency pairs where no stablecoin off-ramp exists, SWIFT is the rail.
• Highly regulated industries with specific compliance requirements. Some payment types (government, defence, certain financial-services flows) have specific MT103 field requirements or sanctions-screening expectations that the legacy rail handles by default.
• Recurring high-value B2B with established relationships. A monthly $500k payment between two corporations with negotiated banking spreads can be cheaper on bank rails than on a rate-card stablecoin provider.

For small-to-mid amounts ($100–$50,000) on common currency pairs, the stablecoin rail wins on cost and time consistently. The crossover point depends on the specific corridor and the negotiated bank rate.

The Other Hidden Cost — Time

Cost gets the headlines; time gets felt by the recipient. A SWIFT wire that takes three days isn’t just slower — it ties up working capital. For a freelancer earning $5,000 monthly, the difference between “credited tonight” and “credited Tuesday” can mean missing a rent date or paying credit-card interest while waiting. For a B2B supplier extending net-30 terms, the SWIFT delay effectively pushes the actual payment date further out.

Stablecoin rails settle in minutes including weekends and holidays. SWIFT settles within bank operating hours, which excludes weekends and major holidays in either jurisdiction. Over a year of recurring cross-border payments, the time difference compounds into a real cash-flow advantage for the recipient.

Frequently Asked Questions

Why does SWIFT have so many fees?

SWIFT itself is a messaging network, not a settlement system. The actual money movement happens through correspondent-banking relationships — each correspondent that touches the payment is a counterparty taking a cut for handling the FX, sanctions screening, and credit risk. The visible “$25 fee” covers only the sending bank; the rest of the system extracts its share along the way.

Is the FX margin really 1.5%–3% on a SWIFT wire?

For retail and SME-size transfers (under $50K) at major banks, yes. The published FX rate on a transfer form is typically 1.5%–3% worse than the interbank mid-market rate, because the bank takes a margin to cover its currency risk and operational cost. Larger transfers often negotiate better rates; small transfers see the highest spreads.

Are stablecoin payouts always cheaper than SWIFT?

Almost always for amounts under $50,000 on common currency pairs. The crossover depends on the specific corridor and the bank’s negotiated rate for the sender. For most freelancers, contractors, SMEs, and remittance flows, stablecoin rails are materially cheaper.

What about regulated compliance — is SWIFT safer for that reason?

Both rails operate under regulated frameworks. SWIFT messages go through banks subject to AML, sanctions screening, and reporting. Stablecoin payout providers operate under VASP/CASP licensing in their jurisdictions and apply the same screening. Neither bypasses compliance; the stablecoin provider’s job is to maintain it without the multi-correspondent overhead.

How does the recipient know the payment is real?

On the stablecoin side, the receipt is an inbound credit from a regulated banking partner — looking exactly like any other inbound transfer the recipient receives. On the SWIFT side, the inbound credit is similar but with longer-form remittance information including the sender’s bank reference. Both are auditable.

Can I keep using SWIFT for some payouts and stablecoin rails for others?

Yes — many businesses do. A common pattern is SWIFT for very large transfers between established banking relationships, stablecoin rails for the long tail of small-to-mid payments to contractors, suppliers, and remote workers. The two rails coexist; choosing the right one per transfer is a treasury question, not an all-or-nothing one.