SWIFT in 2026: how the system works, ISO 20022, gpi, and why stablecoins are catching up

SWIFT (Society for Worldwide Interbank Financial Telecommunication) is not a payment system, but a closed messaging network for 11,000+ banks and financial institutions in more than 200 countries. It handles around 50+ million messages per day, enabling global interbank transfers. In November 2025, SWIFT completed its biggest migration in 50 years: the outdated MT format (used since the 1970s) gave way to ISO 20022 (MX) — a structured standard with rich data. The SWIFT gpi service provides real-time payment tracking and guarantees crediting on the day of sending in 80% of cases. But a competitor is growing alongside it — stablecoins ($390 billion in volume, +733% year-over-year growth in B2B transactions, settlement in 0.4–15 seconds versus SWIFT’s 1–3 days). In this article — a complete breakdown: how SWIFT actually works, what a BIC code is, how gpi differs from a traditional transfer, the November 2026 deadlines, how to receive SWIFT transfers in KAST/Wise/N26, competition with stablecoins, and the hybrid future.

Disclaimer: This material is for informational purposes only. The specific timing, fees, and terms of SWIFT transfers depend on your bank and correspondent banks. Before making large transfers, confirm the details with your bank.

What You Need to Know About SWIFT in 2026

The 2026 context is essential. If you read guides 2–3 years ago, the situation has changed radically:

• November 22, 2025 — the MT/MX coexistence period ended. All SWIFT messages for cross-border payments are now required to use the ISO 20022 (MX) format
• November 2026 — the next key deadline: a ban on fully unstructured addresses; end of life for MT 101 (multiple)
• G20 Roadmap through 2027 — the goal is to make cross-border transfers cheaper and faster globally
• January 2026 — SWIFT successfully conducted a multi-bank experiment with tokenized bonds and stablecoins (BNP Paribas, Intesa Sanpaolo, Société Générale-FORGE with EURCV)
• SWIFT gpi in 2026 — real-time tracking, 80% of transfers are credited within an hour in major corridors
• Competition from stablecoins: volume of $390B, B2B transaction growth of +733% year over year, settlement in milliseconds vs. days with SWIFT
• For Ukrainians: SWIFT still works with Ukrainian banks (Privat, Mono, PUMB), but with sanctions screening specifics
• Russian banks — most have been disconnected from SWIFT since 2022, and operations through correspondent banks are extremely limited

Key point: In 2026, SWIFT is not an “outdated system”, as crypto enthusiasts often claim. It is an actively modernizing infrastructure adapting to stablecoins, ISO 20022, and tokenized assets. But stablecoins are no longer an “experiment” either—they are a real alternative for certain use cases.

What SWIFT Is in Simple Terms

SWIFT (pronounced “swift”) is not a bank and not a payment system. It is a global messaging network through which banks securely exchange standardized financial messages.

A Simple Analogy

Imagine that SWIFT is “email just for banks”. With three key differences from regular email:

• Military-grade security — every message is encrypted and signed
• Strict formatting standards — Bank A knows that Bank B will interpret the message unambiguously
• Closed network — ordinary users cannot access it, only licensed financial institutions can

What SWIFT Does and Does NOT Do

✅ What SWIFT does	❌ What SWIFT does NOT do
Transmits transfer instructions	Does NOT physically move money
Provides a message format	Does NOT hold customer funds
Tracks message status (gpi)	Does NOT control settlement
Supports trade finance, securities	Does NOT issue loans
Supports AML/sanctions screening	Does NOT make payment decisions

Key point: SWIFT is messaging, not money

When you make a SWIFT transfer:

1. Your bank sends a message to the recipient’s bank via the SWIFT network
2. Banks individually move money through their correspondent accounts (nostro/vostro)
3. The money is physically transferred through a chain of correspondent banks, not through SWIFT

This explains why a SWIFT transfer can take 1–5 days — not because the message itself takes a long time to arrive (it gets there in seconds), but because each bank in the chain must:

• Receive the message
• Conduct AML/sanctions checks
• Move money between your own accounts
• Forward the following message

Who Is Behind SWIFT

• Legally: a membership-based cooperative society, registered in Belgium (La Hulpe, near Brussels)
• Controlled by: 11,000+ member banks worldwide
• Regulated by: the National Bank of Belgium with the involvement of the ECB, the U.S. Federal Reserve, and other G10 central banks
• Legal status: not a bank, not a financial institution, but a messaging provider

Important nuance: precisely because SWIFT is a banking cooperative rather than a payment system, disconnection from SWIFT does not prohibit a bank from conducting international transactions. It simply becomes many times more expensive and slower (through alternative channels — telex, direct correspondent relationships, Russia’s SPFS, China’s CIPS).

History of SWIFT

SWIFT has existed for more than 50 years and has lived through several eras of the financial industry.

Brief timeline

Year	Event
1973	SWIFT was founded by 239 banks from 15 countries. The goal was to replace unreliable telex
1977	Network launch. The first message was sent between Bank of America and Australia and New Zealand Bank
1980s	Mass adoption by banks, with the MT format becoming the industry standard
2001	After 9/11 — stronger AML/CFT compliance, coordination with FATF
2012	Iranian banks disconnected from SWIFT (international sanctions)
2017	Launch of SWIFT gpi — real-time payment tracking
2018	SWIFT begins working with API for fintech integration
2022	7+ Russian banks disconnected after the start of the war in Ukraine
March 2023	Start of migration to ISO 20022 (MX) for cross-border payments
November 2025	End of MT/MX coexistence — all cross-border SWIFT messages in ISO 20022
2024-2026	Experiments with tokenization and stablecoins (CBDC, EURCV)
November 2026	Deadline: ban on unstructured addresses, end of MT 101 (multiple)

Why SWIFT emerged

Before 1973, international bank transfers were made via telex — an outdated system with major problems:

• ❌ Messages were often distorted
• ❌ There was no standard format
• ❌ Low security (easy to intercept)
• ❌ Manual processing at every stage

SWIFT solved all these problems: a unified message format, encryption, and automation. Over 50 years, this made international transfers possible on a mass scale.

How a SWIFT transfer works

This is the most interesting and often misunderstood part.

Scenario: you transfer $1000 from Ukraine to the USA

Suppose Anna in Kyiv transfers $1000 to her friend Michael in New York through her PrivatBank → JPMorgan Chase.

Step 1: Anna sends the instruction

Anna logs into Privat24, selects “International transfer,” and enters:

• Amount: $1000
• Recipient: Michael Smith
• Recipient’s bank: JPMorgan Chase
• SWIFT/BIC: CHASUS33
• Account number: 1234567890
• Recipient’s address (required from November 2025!)

Step 2: PrivatBank generates a SWIFT message

PrivatBank creates a message in the MX (ISO 20022) format — previously this was MT103. The message contains structured data: sender, recipient, amount, currency, payment purpose, AML information.

The message is assigned a UETR (Unique End-to-End Transaction Reference) — a unique ID for tracking via SWIFT gpi.

Step 3: Passing through correspondent banks

This is where the main magic of SWIFT begins — the correspondent network.

PrivatBank does not have a direct relationship with JPMorgan Chase. Therefore, the payment goes through correspondent banks:

PrivatBank (UA)
    ↓ (SWIFT message)
Intermediary bank #1 in the EU (for example, Raiffeisen Bank)
    ↓
Intermediary bank #2 in the USA (for example, Bank of New York Mellon)
    ↓
JPMorgan Chase
    ↓
Michael's Account

Each bank in the chain:

• ✅ Receives the message
• ✅ Checks AML/sanctions
• ✅ Moves the money through its correspondent account (nostro)
• ✅ Forwards the message

Step 4: Crediting the recipient

JPMorgan Chase receives the money from Bank of New York Mellon, performs a final compliance check, and credits $1000 to Michael’s account.

Step 5: Tracking via gpi

Anna can see in real time where her transfer is currently located — via the SWIFT gpi Tracker (if her bank supports it).

What is a correspondent account (nostro/vostro)

This is the most difficult part of SWIFT to understand.

• Nostro account — “our account with them” (bank A’s account with bank B)
• Vostro account — “their account with us” (bank B’s account with bank A)

These accounts are the “physical channel” through which money moves. SWIFT itself does not move any money — it only instructs banks on what to do with their nostro/vostro accounts.

Why intermediary banks charge fees

Each bank in the chain performs real work:

• Processes the message (employee FTE minutes)
• Conducts compliance checks
• Uses its own liquidity in nostro accounts
• Bears regulatory risks

Therefore, correspondent fees of $15–50 are standard practice. For large amounts, they become negligible as a percentage; for small amounts ($50–200), they consume a significant share.

What Is a BIC SWIFT Code

BIC (Bank Identifier Code) or SWIFT code is a bank identifier in the SWIFT network.

BIC Structure: 8 or 11 Characters

CHAS  US  33  XXX
 |    |   |   |
 |    |   |   └── Branch (optional, 3 characters)
 |    |   └── Location (2 characters — city)
 |    └── Country (2 characters — ISO 3166 country code)
 └── Bank code (4 characters — bank letter code)

Breakdown by position

Position	What it means	Example
1-4	Bank code	CHAS = JPMorgan Chase, DEUT = Deutsche Bank
5-6	Country code	US = USA, DE = Germany, UA = Ukraine
7-8	City code	33 = New York, FF = Frankfurt
9-11	Branch code (optional)	XXX = head office

Examples of popular BIC codes

Bank	BIC
JPMorgan Chase (USA)	CHASUS33
Bank of America (USA)	BOFAUS3N
Deutsche Bank (Germany)	DEUTDEFF
HSBC London	HBUKGB4B
PrivatBank (Ukraine)	PBANUA2X
Monobank (Universal Bank, Ukraine)	COMRUAUK
PUMB	FUIBUA2X
Raiffeisen Bank (Ukraine)	AVALUAUK
N26 Bank (Germany)	NTSBDEB1
Wise (Wise Payments)	TRWIBEB1
Lead Bank (Member FDIC)	LDDBUS44

How to find your bank’s BIC

• On the bank’s official website in the “Details for international transfers” section
• In the statement or mobile app
• Through the public SWIFT directory: https://www.swift.com/bsl/
• From the bank’s support team

Do not confuse BIC and SWIFT — they are the same thing. “SWIFT code” and “BIC code” are synonyms. Different banks may use different terms, but they refer to the same 8–11 character code.

ISO 20022

The most important part of the article for understanding modern SWIFT 2026. It is a revolution that happened quietly, but changed everything.

What ISO 20022 Is

ISO 20022 is a global financial messaging standard based on XML and supporting rich structured data.

Before ISO 20022, SWIFT used the MT (Message Type) format — an old text-based format with a limited set of fields.

MT vs MX (ISO 20022): a revolutionary difference

Parameter	MT (old)	MX / ISO 20022 (new)
Format	Text-based, fixed positions	XML, structured
Data size	Up to 2000 characters	Much larger, no rigid limits
Addresses	Free text (“unstructured”)	Structured (country, city, street in separate fields)
AML data	Limited	Rich — purpose codes, regulatory reporting
Compliance	Manual checks	Automation through structured fields
Customer experience	Poor (often incomplete data)	Detailed remittance information
Compatibility	Isolated	Compatible with SEPA, RTGS, instant payments

Main migration dates

Date	What happened / will happen
March 2023	Start of coexistence — banks can use both MT and MX
November 22, 2025	🚨 End of coexistence for cross-border payments — everyone must use MX
November 2026	🚨 Ban on fully unstructured addresses; end of MT 101 (multiple)
January 2026	Additional fees for contingency processing for those still using MT
2027	G20 Roadmap targets for cross-border payments

What this means for the user

Main point: now, when sending a SWIFT transfer, you must provide the recipient’s full structured address — not just “New York,” but: country, city, street, building number, postal code. Without this, from November 2025 payments may be rejected or delayed.

From November 2026, this will become even stricter: hybrid addresses (part structured, part not) will also be banned for cross-border payments.

Benefits of ISO 20022 for businesses and individuals

✅ Fewer rejections — structured data = fewer parsing errors
✅ Faster compliance — AML checks are automated
✅ Better reconciliation — corporate accounting becomes easier
✅ Fewer investigations — typical “where did my transfer go?” cases are reduced
✅ Better customer experience — the client sees details about every fee and step

Bonus: compatibility with stablecoins

ISO 20022 is the same standard used by CBDCs and regulated stablecoins. This means that in the future (and already today in experiments), SWIFT messages will be able to “understand” on-chain transactions and vice versa.

In January 2026, SWIFT successfully conducted an experiment with BNP Paribas, Intesa Sanpaolo, and Société Générale-FORGE on settlements for tokenized bonds via the EURCV stablecoin using ISO 20022 messaging. This is a direct bridge between SWIFT and blockchain.

SWIFT gpi

SWIFT gpi (Global Payments Innovation) is an upgrade of classic SWIFT, launched in 2017. By 2026, it is the de facto standard for most banks.

What gpi provides

Main improvements compared with classic SWIFT:

• Real-time tracking via UETR (Unique End-to-End Transaction Reference)
• Transparent fees — the client can see who charged what at each stage
• Guaranteed speed — service level agreements between banks
• 80% of transfers are credited within an hour in major corridors
• Same-day settlement in most G7 corridors

How UETR Works

When a payment is created, the sending bank assigns a unique UETR code — a “tracking number” for your payment, similar to a courier parcel.

Example UETR: eb6305c9-1f7f-49de-aed0-16487c66fcb1

With this UETR, your bank can see in real time in the SWIFT gpi Tracker:

• Where the payment is currently located (which correspondent bank)
• Which fees have already been charged
• How much time has passed at each stage
• When it was credited to the recipient

Types of gpi Services

Service	What it does	Who it is for
gpi for Corporates	Payment tracking for corporates	Businesses
gpi Stop and Recall	Recall of a sent payment	In case of an error
gpi for Cover Payments	Payment tracking through correspondent banks	Everyone
SWIFT Go	Simple, low-cost transfers for small businesses	SMBs and retail
gpi Pre-validation	Verification of payment details BEFORE sending	Reducing rejections

Actual SWIFT gpi Speed in 2026

According to SWIFT itself:

• 40% of gpi transfers arrive within 5 minutes
• 50% within 30 minutes
• 80% on the day of sending
• 97% within 24 hours

But these are average figures. In reality, the speed depends on:

• Corridor (US→EU is faster than US→Africa)
• Amount (large transfers are often slower due to compliance)
• Recipient bank (some operate only during banking hours)
• Time sent (payments made on Friday at 18:00 may be delayed until Monday)

When gpi is available to the user

Most major banks support gpi in 2026:

• ✅ JPMorgan Chase, Bank of America, Wells Fargo
• ✅ Deutsche Bank, HSBC, BNP Paribas
• ✅ PrivatBank, PUMB, Raiffeisen (Ukraine)
• ✅ N26, Wise (access via correspondent banks)
• ⚠️ Small regional banks may NOT provide gpi tracking directly to clients

Tip: for a large SWIFT transfer, be sure to ask your bank for the UETR code. It allows you to track the payment independently.

Cost of a SWIFT transfer

In 2026, the cost of a SWIFT transfer depends on three factors: your bank, correspondent fees, and the fee-sharing arrangement.

Fee structure

Fee 1: Your bank ($15-60)

This is what your bank charges for processing a SWIFT transfer:

Bank / Fintech	SWIFT withdrawal fee
PrivatBank	~0.5-1% of the amount, min. $25
Monobank	$20-30 fixed
PUMB	$25-50
Wise	from $5 (one of the cheapest)
Revolut	from $5-15 (on paid plans)
N26	$25-50
KAST	$25-50
Coinbase	free (for inbound SWIFT)

Fee 2: Correspondent banks ($15-50)

Each bank in the chain may charge a fee ($5-25). On the standard USA → EU route, there are usually 1-2 correspondents.

Fee 3: Receiving bank ($0-25)

Some banks charge a fee for inbound SWIFT. For example:

• 🇺🇸 JPMorgan Chase: $15 for incoming
• 🇪🇺 N26, Wise, KAST: $0 for incoming
• 🇺🇦 PrivatBank: $5-10 for incoming

SHA, OUR, BEN — who pays the fees

This is an essential point that many people ignore.

When sending a SWIFT transfer, you need to choose a fee-sharing scheme:

Option	What it means	Who pays
SHA (Shared)	Each party pays their own	The sender pays their bank; correspondent banks deduct from the amount; the recipient pays their bank
OUR	The sender pays everything	The sender pays ALL fees (their bank + correspondent banks + the recipient’s bank)
BEN (Beneficiary)	The recipient pays everything	Correspondent banks and the recipient are paid from the amount

Which option to choose

Scenario A: You are paying a freelancer’s salary

→ Choose OUR — the freelancer will receive the full amount with no deductions. Good etiquette.

Scenario B: You are receiving payment from a client

→ Ask the client to send with the OUR option — then you will receive the full amount. If it’s SHA, you may receive $30–50 less.

Scenario C: A family transfer

→ Usually, SHA is the cheapest for the sender, and the recipient will also understand (fees are normal).

A real calculation example

A $1000 transfer from the USA to Ukraine:

• Bank of America (sender): $45 (fixed fee)
• Correspondent bank in the EU: $20
• PrivatBank (recipient): $10

With the SHA option:

• The sender pays: $1000 + $45 = $1045
• The recipient receives: $1000 – $20 – $10 = $970

With the OUR option:

• The sender pays: $1000 + $45 + $20 + $10 = $1075
• The recipient receives: $1000 in full

Minimum amounts

Most banks have a minimum of $50–100 for a SWIFT transfer. For small amounts, fees “eat up” 10–30% — this is not cost-effective.

Rule: SWIFT makes sense for amounts of $500-1000 and above. For smaller amounts, use Wise, KAST, or stablecoins (USDT/USDC).

Transfer times

In 2026, actual SWIFT transfer times depend heavily on the corridor.

Actual timelines by corridor

Corridor	Standard SWIFT	Via SWIFT gpi
US ↔ EU (USD/EUR)	1-3 business days	5 minutes – 24 hours
US ↔ UK (USD/GBP)	1-2 business days	minutes – hours
EU ↔ EU (if not SEPA)	1-2 days	minutes – hours
US ↔ Japan	2-3 days	hours – day
EU ↔ Ukraine	1-3 days	hours – day
EU ↔ Africa	3-5 days	day – 2 days
EU ↔ Latin America	2-5 days	day – 3 days

Factors that speed up the payment

✅ Transfer during the sender bank’s business hours (9:00-17:00 local time)
✅ A single-correspondent corridor (US-EU, US-UK)
✅ Use of a gpi-certified bank
✅ Full structured addresses (ISO 20022)
✅ An amount that does not trigger AML flags ($5K-50K — sweet spot)

Factors that slow down the payment

⚠️ Friday evening or weekends — may delay it by 2-3 days
⚠️ Multiple correspondents (for example, Africa-Asia)
⚠️ Public holidays in any of the countries along the route
⚠️ AML flags (large amount, new client, high-risk country)
⚠️ Incomplete details (old address format)
⚠️ Sanctions screening for certain countries and names

What is cut-off time

Every bank has a cut-off time — the time after which a payment is processed on the next business day.

Typical cut-off times:

• 🇺🇸 USA: 15:00-17:00 EST
• 🇪🇺 EU: 15:00-17:00 CET
• 🇬🇧 UK: 15:00 GMT

Tip: send important payments before 14:00 local time at your bank.

Receiving details

This is a practical section for anyone who wants to receive SWIFT transfers from the US/EU/worldwide.

What should be included in the receiving details

So that a client/employer/family can send you a SWIFT transfer, provide them with:

Beneficiary Name: YOUR_NAME (exactly as in your passport, in Latin letters)
Beneficiary Address: STREET, CITY, ZIP CODE, COUNTRY (in full!)
Beneficiary Account Number / IBAN: ACCOUNT_NUMBER_OR_IBAN
Beneficiary Bank Name: BANK_NAME
Beneficiary Bank Address: FULL_BANK_ADDRESS
SWIFT/BIC: BIC_CODE (8-11 characters)
Intermediary Bank (optional): if required for routing
Purpose of Payment: Purpose (important!)

Especially important from November 2025

With the completion of the migration to ISO 20022, a full structured address is required:

❌ Old format (no longer works):

Beneficiary: John Doe
Address: New York

✅ New ISO 20022 format:

Beneficiary: John Doe
Street: 123 Main Street, Apt 4B
City: New York
Postal Code: 10001
Country: United States (US)

Bank details for popular services

🇺🇸 KAST USD Account (via Lead Bank):

• SWIFT/BIC: LDDBUS44
• Bank: Lead Bank, 1801 Main Street, Kansas City, MO, USA
• Account Number: your personal

🇪🇺 KAST EU Account:

• SWIFT/BIC: depends on the partner (EE, BE, IE)
• IBAN: your personal one
• Bank: partner European bank

🇬🇧 Wise:

• SWIFT/BIC: TRWIBEB1 (Wise Belgium)
• IBAN: your personal one (Belgium IBAN BE)
• Bank: Wise Payments Belgium SA/NV

🇩🇪 N26:

• SWIFT/BIC: NTSBDEB1
• IBAN: your personal (DE)
• Bank: N26 Bank AG, Berlin, Germany

🇺🇦 PrivatBank:

• SWIFT/BIC: PBANUA2X
• IBAN: your personal (UA)
• Bank: PrivatBank, Kyiv, Ukraine

Receiving scenarios for Ukrainians

Scenario 1: Salary from a U.S. company

The best option is a KAST USD Account (a virtual U.S. account):

• The client pays via ACH (free, fast) or SWIFT
• The funds are automatically converted into USDC
• Withdrawal to any wallet or via Visa card
• See our full KAST review

Scenario 2: Payment from a European client

The best option is N26 or KAST EU IBAN:

• If N26 is standard SEPA, fast and free
• If KAST is SEPA Instant + auto-conversion to USDC

Scenario 3: SWIFT from a Middle Eastern/Asian client

Use Wise or KAST:

• Wise: $5–15 fee, transparent exchange rate
• KAST: $25–50 fee, instant conversion to crypto

Scenario 4: Direct SWIFT to a Ukrainian bank

PrivatBank / Monobank / PUMB accept SWIFT, but:

• ⚠️ Incoming fee of $5–15
• ⚠️ Conversion to hryvnia at the bank’s exchange rate (worse than the market rate)
• ⚠️ AML check for large amounts

For large amounts, Ukrainians are advised to use the KAST → Wise → PrivatBank route or receive funds directly in KAST and withdraw them in parts.

SWIFT vs SEPA

The main practical comparison for EU residents and those who receive payments from there.

Key differences

Parameter	SWIFT	SEPA	SEPA Instant
Coverage	Global (200+ countries)	36 eurozone countries + EFTA	36 eurozone countries + EFTA
Currencies	Any	EUR only	EUR only
Speed	1-5 days	1 business day	10 seconds
Cost	$20-50+	Usually free	Usually free
Operating hours	Depends on the banks	Business hours	24/7
Amount limit	No limit	Up to €100K (by default)	Up to €100K (required from October 2025)
Identification	BIC + account / IBAN	IBAN (+ optional BIC)	IBAN (+ optional BIC)
Who pays	Correspondent fees	No one	No one

When to use each system

Use SWIFT if:

• Transfer between different currencies (USD↔EUR)
• The recipient is outside the SEPA zone (USA, Japan, China, the United Kingdom after Brexit)
• Corporate payment to a less common country
• The amount exceeds SEPA limits

Use SEPA if:

• Both accounts are in EUR
• Both accounts are in the SEPA zone (EU + Switzerland, Norway, Liechtenstein, Iceland)
• Ultra-fast speed is not required

Use SEPA Instant if:

• Need instant processing (10 seconds)
• Payment on weekends/holidays
• Standard SEPA transfer within the EU

Since October 2025, SEPA Instant has been required for all eurozone banks. If your bank is still charging for it, that is already an outdated practice. Learn more in our guide to SEPA in 2026.

The UK After Brexit

The UK is no longer in the SEPA zone for most purposes (although it technically remains in it). As a result, UK ↔ EU transfers now often go through SWIFT, which is more expensive and slower.

SWIFT vs Stablecoins

The main fintech battle of 2024-2026. Who is winning?

A Tough Fact-Based Comparison

Parameter	SWIFT (gpi)	Stablecoins (USDC/USDT)
Speed	5 minutes – 3 days	0.4-15 seconds
Operating hours	Depends on the banks	24/7/365
Cost for $1000	$30-80	$0.001 (Solana) — $5 (Ethereum)
Fee transparency	Via the gpi tracker	Fully transparent
Financial infrastructure	50 years, 11K banks	5 years, growing rapidly
Regulation	Regulated everywhere	Evolving (MiCA, etc)
Compliance / AML	High level	Depends on the platform
Reversibility	Stop & Recall	Impossible (irreversible)
Consumer protection	High	Low (if you make a mistake — you lose it)
Suitable for large $$	✅ Institutional standard	✅ Growing fast
Accessibility for retail users	Through a bank	Anyone with a smartphone

Stablecoin Growth Figures in 2026

• $390 billion — the current USDT + USDC circulation
• +733% year over year — growth in B2B transactions using stablecoins
• Solana — 400-millisecond finality
• TRON — 1–2 seconds
• Ethereum L2 (Arbitrum, Base) — 5–15 seconds
• Visa, Stripe, Shopify — all have integrated stablecoins

When to Choose SWIFT

✅ Institutional payments $1M+ — for now, SWIFT infrastructure is more reliable
✅ Regulated environment — where compliance is essential (banking, securities)
✅ Recall capability — if there is an error, funds can be returned
✅ The recipient does not use crypto — most companies and individuals
✅ Trade finance, securities settlement — where SWIFT dominates

When to Choose Stablecoins

✅ Speed — settlement in seconds, not days
✅ Micropayments — $0.001 fee vs $30
✅ 24/7 — weekends, holidays, nighttime
✅ Emerging markets — Argentina, Nigeria, Turkey, Venezuela
✅ Crypto-native business — paying freelancers in the crypto industry
✅ Privacy-conscious (with an understanding of on-chain tracking risks)

A Hybrid Future: KAST as an Example

In 2026, people no longer choose “either-or”. The best fintechs (like KAST) are building a bridge:

1. Accept SWIFT/ACH/SEPA like a regular bank transfer
2. Automatic conversion to USDC (stablecoin)
3. Withdrawal to blockchain networks (Solana, Ethereum, Tron)
4. Or spend with a Visa card

This is the best of both worlds — the reliability of SWIFT for receiving funds and the speed of crypto for further transactions. See the full KAST review.

SWIFT for Ukrainians

A separate important section for our audience.

Which Ukrainian banks are on SWIFT in 2026

Most major Ukrainian banks are fully functional on SWIFT:

Bank	SWIFT/BIC	Accepts inbound?	Sends outbound?
PrivatBank	PBANUA2X	✅	✅
Monobank (via Universal Bank)	COMRUAUK	✅	✅
PUMB	FUIBUA2X	✅	✅
Raiffeisen Bank	AVALUAUK	✅	✅
UkrSibbank (BNP Paribas)	KHABUA2K	✅	✅

SWIFT specifics for Ukrainians

Enhanced AML checks

After 2022, SWIFT transfers from/to Ukraine undergo additional checks for sanctions-related risks. Especially for:

• Amounts of $10K+
• Transfers from/to high-risk countries (Russia, Belarus, Iran)
• Connections to politically exposed persons (PEPs)

What to prepare:

• Contract or invoice (for business payments)
• Proof of source of funds (salary, sole proprietorship)
• Tax return (for large amounts)

Conversion to hryvnia

Incoming SWIFT transfers in USD/EUR are converted by the bank into hryvnia at the bank’s exchange rate, which is usually 1–3% worse than the interbank rate.

Tip: for large amounts, keep a foreign currency account and convert later via Wise/KAST.

NBU limits

When withdrawing from a sole proprietor account abroad, the limit is €400K/month for most types of business activity.

For regularly receiving payments from abroad, Ukrainians are better off using KAST or Wise rather than a direct SWIFT transfer to a Ukrainian bank. See our comparison guide.

Alternatives to direct SWIFT for Ukrainians

KAST USD Account — virtual US account + auto-conversion to USDC
Wise — the best exchange rate for international transfers
N26 — a European bank for those who moved to the EU
Paysera — a Lithuanian fintech for sole proprietors
Trustee Plus — a crypto card with IBAN for receiving SEPA

Learn more: comparison of all options.

Sanctions and SWIFT

This is an essential topic in 2026.

What happened since 2022

After the start of the war in Ukraine, 7 major Russian banks were disconnected from SWIFT:

• Sberbank (later added to a broader list)
• VTB
• Gazprombank (with a delay)
• Otkritie
• Sovcombank
• VEB
• Promsvyazbank

By 2026, most Russian banks have been disconnected from SWIFT for cross-border operations. Russia uses its own SPFS (System for Transfer of Financial Messages), but it operates only within Russia and with a limited number of foreign banks.

Other sanctions scenarios

🚫 Iran — disconnected since 2012, partially since 2019 (after the US withdrew from the nuclear deal)
🚫 North Korea — complete disconnection
⚠️ Syria, Venezuela, Cuba — severe restrictions
⚠️ Belarus — several banks disconnected since 2022

What this means for users

✅ Ukraine — fully connected to SWIFT, no restrictions
✅ EU, US, UK, Canada, Japan, Australia — no issues
⚠️ Russia — extremely difficult, only through alternative banks
⚠️ Belarus — most transfers are impossible
🚫 Iran, DPRK, Syria — most operations are blocked

Alternative systems

There are SWIFT competitors in the world, but they are much smaller:

• 🇷🇺 SPFS (Russia) — within Russia and with limited partners
• 🇨🇳 CIPS (China International Payments System) — China and partners
• 🇮🇳 SFMS (India) — within India
• 🌍 Experiments with CBDCs and stablecoins for cross-border payments

But SWIFT remains dominant for global operations.

SWIFT Security

SWIFT is one of the safest financial systems in the world, but not perfect.

Multi-layered protection

Encryption — all messages are encrypted between banks
Authentication — each bank has its own key and certificate
AML/CFT — all banks must conduct compliance checks
Sanctions screening — automatic screening against OFAC, EU, and UN lists
Fraud detection — monitoring of anomalous patterns

Famous incidents

⚠️ Bangladesh Bank Heist (2016) — hackers used compromised SWIFT access to steal $81 million from the account of Bangladesh’s central bank at the U.S. Federal Reserve. This led to a major strengthening of security.

⚠️ Various regional incidents — especially in 2017–2019. Since then, SWIFT has introduced the Customer Security Programme (CSP) — a required security program for all members.

What protects SWIFT in 2026

• ✅ Required CSP attestation annually
• ✅ End-to-end encryption
• ✅ Behavioral analytics on every message
• ✅ Pre-validation service — verification before sending
• ✅ Stop & Recall — the ability to cancel
• ✅ Penetration testing of member banks

AML/CFT compliance

Every SWIFT transfer undergoes at least 3–5 checks along the way:

1. Sanctions screening (sender, recipient, banks)
2. PEP screening (politically exposed persons)
3. Adverse media (negative information about clients)
4. Source of funds (for large amounts)
5. Pattern analysis (unusual transactions)

This explains why SWIFT is slower than stablecoins — compliance takes time.

How to Receive via Fintech

A practical section: how to actually use SWIFT in 2026 through modern fintech services.

Via KAST

KAST provides virtual SWIFT account details for receiving global transfers:

✅ Bank: Lead Bank (Member FDIC)
✅ SWIFT/BIC: LDDBUS44
✅ Account Number: your personal
✅ Routing Number: for ACH (within the USA)

Advantages:

• Funds are automatically converted to USDC
• Fast further processing
• You can immediately spend with a Visa card or withdraw to the blockchain

Learn more: full KAST review.

Via Wise

Wise is an excellent service for SWIFT transfers with the best exchange rate:

✅ Bank: Wise Payments Belgium SA/NV
✅ SWIFT/BIC: TRWIBEB1
✅ IBAN: your personal (BE)

Advantages:

• Real interbank exchange rate (with no hidden markups)
• 40+ currencies supported
• Wise card for spending

Cons:

• ⚠️ Not a bank, no FDIC insurance
• ⚠️ For large amounts, Wise may ask questions

Via N26

N26 is for those who live in the EU:

✅ Bank: N26 Bank AG, Berlin
✅ SWIFT/BIC: NTSBDEB1
✅ IBAN: your personal (DE)

Advantages:

• A fully licensed German bank regulated by BaFin
• €100K EDIS deposit insurance
• Visa Debit Card

Cons:

• ⚠️ For EU residents only
• ⚠️ Not all plans include free incoming SWIFT transfers

See the N26 guide for Ukrainians.

Via Trustee Plus

Trustee Plus is a crypto card with a European IBAN:

✅ IBAN: your personal (Lithuanian)
✅ Suitable for receiving SEPA (euro)
⚠️ For SWIFT in USD — it is better to use KAST

See the Trustee Plus review.

Comparison Table

Service	SWIFT inbound	Fee	Conversion	Best for
KAST	✅	$0-$15	to USDC automatically	Global incoming transfers
Wise	✅	$5-15	to any currency at the real exchange rate	Exchange rate / multicurrency
N26	✅	$0-25	EUR (you can hold USD)	Living in the EU
Trustee Plus	⚠️ SEPA is better	$0	to crypto	Receiving SEPA into crypto
PrivatBank	✅	$5-10	to UAH at the bank’s exchange rate	Direct receiving in Ukraine

The Future of SWIFT

By 2026-2030, SWIFT will be undergoing active transformation. Here’s what’s coming.

1. Full integration with CBDC

Central banks are actively working on CBDC (Central Bank Digital Currencies). SWIFT is already testing integration:

• 🇪🇺 ECB — digital euro (launch planned for 2027–2028)
• 🇨🇳 China — digital yuan (e-CNY)
• 🇧🇷 Brazil — Drex (2024–2025)
• 🇮🇳 India — digital rupee
• 🇺🇸 USA — currently in the research phase

SWIFT plans to ensure interoperability between all these CBDCs through ISO 20022 messaging.

2. Tokenized assets and stablecoins

As early as January 2026, SWIFT conducted a multi-bank experiment with EURCV (the Société Générale-FORGE stablecoin) for DvP (Delivery vs Payment) settlement of tokenized bonds.

There’s more to come:

• ✅ Settlements for tokenized assets via SWIFT messaging
• ✅ Atomic swaps between fiat and digital assets
• ✅ Standardization of stablecoin payments through ISO 20022

3. AI and automation

• AI-powered fraud detection — real-time fraud detection
• Predictive routing — the optimal payment route through AI
• Smart compliance — automatic resolution of AML flags
• Conversational interfaces — banks will be able to interact with SWIFT through natural language

4. G20 Roadmap through 2027

The G20 has set goals for cross-border payments:

• 75% of retail transfers must be credited within one hour (by 2027)
• The cost must fall to 1% of the amount
• Transparency of all fees
• 24/7 availability

SWIFT is the main channel for achieving these goals.

5. Competition and Partnership with Stablecoins

In 2024-2026, SWIFT shifted from the position of a “crypto competitor” to a “partner and integrator”. This is a smart move — stablecoins are not going away, so it is better to integrate them.

By 2030, a scenario is likely in which SWIFT messaging + blockchain settlement becomes the standard for certain types of transactions.

Common Problems

Frequent issues with SWIFT transfers and how to avoid them.

Problem 1: “The money hasn’t arrived after 3+ days”

Reasons:

• Error in the bank details (BIC, account number)
• The AML check got stuck at one of the banks
• Public holiday/weekend

What to do:

1. Obtain the UETR code from your bank
2. Ask the bank to check the status via the SWIFT gpi Tracker
3. If the transfer is stuck — use Stop & Recall through your bank
4. Contact the recipient bank directly

Problem 2: “The recipient received less than was sent”

Reason: the SHA or BEN option + correspondent bank fees

Solution: use OUR for the next transfer

Problem 3: “Transfer rejected”

Reasons:

• Incomplete address (from November 2025, structured addresses will be required)
• Sanctions match (even a false positive)
• AML flags (unusual pattern)
• Recipient’s closed account

What to do:

1. Check all recipient details
2. Use the full structured address
3. Prepare the documents (purpose of payment, invoice)
4. Repeat the transfer

Problem 4: “The conversion rate is worse than expected”

Cause: the bank uses its own rate (usually +1–3% above the interbank rate)

Solution:

• Use Wise for the best exchange rate
• Receive the currency and convert it later on an exchange
• Confirm the exchange rate before sending

Issue 5: “AML Request Message”

What to do:

• ✅ Don’t panic — this is a standard procedure
• ✅ Don’t ignore it — it may lead to account suspension
• ✅ Prepare: contract, invoice, source of funds
• ✅ Respond honestly and promptly
• ✅ Keep all correspondence

Tip: if you regularly receive large SWIFT transfers, provide the bank with documents about the source of funds in advance. This will reduce the number of requests.

Frequently Asked Questions FAQ

What is SWIFT in simple terms?

SWIFT (Society for Worldwide Interbank Financial Telecommunication) is a closed messaging network for banks and financial institutions. Through it, banks securely exchange standardized messages about transfers, trade, and securities. SWIFT itself does not transfer money — it only transmits instructions. The actual funds move through banks’ correspondent accounts. The network has been operating since 1973 and connects 11,000+ financial institutions in more than 200 countries.

How long does a SWIFT transfer take in 2026?

With SWIFT gpi, the actual speed in 2026 is: 40% of transfers arrive within 5 minutes, 50% within 30 minutes, 80% within one day, and 97% within 24 hours. Without gpi, it usually takes 1–3 business days. The speed depends on the corridor (US↔EU is faster than US↔Africa), participating banks, the time of sending, and whether there are AML flags. Payments sent on Friday evening are often delayed until Monday.

How much does a SWIFT transfer cost?

The cost consists of three parts: your bank’s fee ($15-60), correspondent banks ($15-50 for the chain), and the recipient bank ($0-25). Total — usually $30-130 per transfer. Wise is one of the cheapest options ($5-15), while traditional banks are more expensive. For amounts under $500, SWIFT is not cost-effective — it is better to use stablecoins or Wise.

What are BIC and SWIFT codes?

BIC (Bank Identifier Code) and SWIFT code are the same thing. It is an 8- or 11-character bank identifier in the SWIFT network. Structure: 4 bank letters + 2 country letters + 2 city characters + optionally 3 branch characters. For example, CHASUS33 is JPMorgan Chase in New York. You can find your bank’s BIC on your statement, on the bank’s website, or in the SWIFT directory.

What is ISO 20022 and why is it important?

ISO 20022 is a new XML-based financial messaging standard with rich structured data. From November 22, 2025, all SWIFT cross-border messages must use ISO 20022 (MX); the old MT format no longer works. The main practical consequence: when sending a SWIFT transfer, you must provide the recipient’s full structured address (country, city, street, postal code — in separate fields). Unstructured addresses will be fully prohibited from November 2026.

What is SWIFT gpi?

SWIFT gpi (Global Payments Innovation) is a SWIFT upgrade introduced in 2017. It provides real-time tracking via the UETR code (a unique payment ID), transparent fees (you can see how much was charged and by whom), and guaranteed speed through Service Level Agreements. 40% of gpi transfers arrive within 5 minutes, and 80% arrive on the day they are sent. Most major banks support gpi in 2026.

How does SWIFT differ from SEPA?

SWIFT is a global system for transfers between any currencies and countries. Expensive ($30-130), slow (1-3 days). SEPA is a regional system for EUR transfers across 36 eurozone countries. Free, fast (1 business day for standard SEPA, 10 seconds for SEPA Instant from October 2025). Use SEPA if both accounts are in EUR and within the SEPA zone. SWIFT is for all other cases.

SWIFT was disconnected in Russia — what does this mean?

Since 2022, 7 major Russian banks have been disconnected from SWIFT (Sberbank, VTB, Gazprombank, Otkritie, and others). By 2026, most Russian banks are either disconnected or face serious restrictions. This does not ban international transfers from Russia, but it makes them several times more expensive and slower — via alternative channels (SPFS, direct correspondent relationships, Chinese banks). Ukrainian banks operate fully within SWIFT.

Is SWIFT safe?

SWIFT is one of the safest financial systems in the world: end-to-end encryption, multi-layer authentication, and the required Customer Security Programme (CSP) for all member banks. There have been incidents (the 2016 Bangladesh Bank Heist, an $81M theft), after which security was strengthened dramatically. For the end user, the main protection is your bank’s compliance and AML checks at every stage of the transfer.

Will stablecoins replace SWIFT?

In 2026 — no, they are more likely to be integrated than replaced. Stablecoins ($390B in volume, +733% YoY B2B growth) are growing faster, but SWIFT remains the standard for institutional payments, the regulated environment, and the banking sector. SWIFT itself is actively integrating with stablecoins — in January 2026, it successfully conducted a multi-bank experiment with EURCV for settlements of tokenized bonds. By 2030, a hybrid future is likely: SWIFT messaging + blockchain settlement.

How can a Ukrainian receive SWIFT payments?

There are several options: (1) Directly to a Ukrainian bank (PrivatBank, Monobank, PUMB) — a simple route, but with enhanced AML checks and conversion into hryvnia at the bank’s exchange rate; (2) KAST USD Account — a virtual US account + automatic conversion to USDC; (3) Wise — the best exchange rate, $5–15 fee; (4) N26 — if you live in the EU; (5) Trustee Plus — for receiving SEPA into crypto. For regular incoming payments, KAST or Wise is recommended rather than a direct Ukrainian bank account.

What is a UETR code?

UETR (Unique End-to-End Transaction Reference) is a unique identifier for a SWIFT transfer, like a courier parcel tracking number. Example: eb6305c9-1f7f-49de-aed0-16487c66fcb1. With a UETR, your bank can see in real time where the payment is currently located, what fees have been deducted, and when it will arrive. Always ask the bank for the UETR for large transfers — it provides transparency.

Can a SWIFT transfer be canceled?

Technically, yes — via the SWIFT Stop & Recall service. Your bank sends a special message to all banks in the chain requesting that the payment be stopped and returned. This works if the funds have not yet been credited to the recipient. If they have already been credited, you need to arrange it directly with the recipient. A recall usually costs an additional $25-50.

SHA, OUR, BEN — which one to choose?

SHA (Shared) — each party pays their own fees. Cheaper for the sender, but the recipient will receive less than the amount sent. OUR — the sender pays all fees in the transfer chain. More expensive for the sender, but the recipient receives the full amount. BEN (Beneficiary) — the recipient pays everything. The recipient receives significantly less. The best choice for paying for a service: OUR (the recipient receives the full amount). For family transfers: SHA (a compromise).

What should you write in the SWIFT payment purpose?

The payment purpose (Purpose of Payment) is crucial for compliance. Write it clearly and truthfully in English: for a salary — Salary payment for [month], for services — Payment for [specific service], for a refund — Refund for invoice #XXX. DO NOT write “help” or “gift” without context — this will trigger AML questions. For business payments, always include the invoice number or contract number.

Conclusion

In 2026, SWIFT is not a “financial dinosaur” but an actively evolving infrastructure. Having completed its main migration to ISO 20022 in November 2025, SWIFT is preparing for the next stage — integration with stablecoins, CBDCs, and tokenized assets. This is not a “SWIFT vs crypto” battle, but a synergy of two worlds.

Key takeaways:

✅ SWIFT is a messenger for banks, not a payment system
✅ 11,000+ banks in 200+ countries use SWIFT
✅ ISO 20022 has been required for cross-border payments since November 2025
✅ SWIFT gpi provides tracking and same-day processing for 80% of transfers
✅ Cost: $30–130 for a typical transfer
✅ Stablecoins are growing faster, but they do not replace SWIFT
✅ KAST + SWIFT hybrid is optimal for accepting payments
⚠️ Full structured addresses are now required
⚠️ AML checks make transfers slower than crypto

When to use SWIFT in 2026:

✅ Institutional payments of $1M+
✅ Regulated environments where compliance is essential
✅ The recipient does not use crypto
✅ You need the ability to recall a payment
✅ Trade finance, securities settlement

When to use alternatives:

❌ Stablecoins — for speed, low cost, and 24/7 availability
❌ SEPA Instant — for EUR payments in the EU (10 seconds!)
❌ Wise — for the best exchange rate on multi-currency transfers
❌ KAST + Solana — for a hybrid of traditional receiving and crypto withdrawals

For Ukrainians, the main thing in 2026:

Direct SWIFT transfers to a Ukrainian bank remain possible, but the optimal strategy is the following combination: receive via KAST or Wise (virtual SWIFT/SEPA details) → convert to USDC → further use (Visa card, withdrawal to Solana/Tron, conversion to hryvnia via P2P).

If you are a freelancer, remote worker, or entrepreneur, explore KAST as an entry point. If you receive irregular large sums, Wise is the better choice. If you live in the EU, use N26 together with Wise.

In a world where SEPA Instant works in 10 seconds, stablecoins settle in 400 milliseconds, and CBDCs are already on the horizon, SWIFT remains the most reliable infrastructure for global transfers. But it is no longer the only one. The future is hybrid, and those who know how to use both worlds at the same time come out ahead.