Swift’s latest payments announcements point to a quiet change in the industry’s problem statement. The cross-border leg is already much faster than it used to be; the harder work now sits in the checks, data and domestic systems that determine when money can actually be used.

A new research paper has put numbers on one of the industry’s most persistent problems. Some 75% of payments travelling over the Swift network now reach beneficiary banks within 10 minutes, often much faster. Yet Swift says the international leg of a payment accounts for less than 20% of the overall journey on average. Around 80% of total processing time is spent in the last mile, after the payment has reached the final financial institution and before funds are checked, processed and credited to the recipient.

Alongside that research, Swift has launched a Payment Optimisation Index and Playbook to help banks identify where those delays arise. It has also reported early activity under a shared framework for retail payments, with 26 financial institutions processing payments across 25 corridors linking 17 markets. Separately, its blockchain-based ledger is ready for initial use, with 17 banks from six continents preparing to pilot live transactions using tokenised deposits.

Across the three initiatives, Swift is asking the industry to look past the moment a payment reaches a receiving bank. The more practical question is whether funds can be credited, confirmed, reconciled and explained quickly enough for the customer waiting for them. A payment that reaches a beneficiary bank quickly can still create uncertainty if the recipient has no confirmation, the treasury team cannot reconcile the movement or the local bank needs hours to complete final checks.

The last mile becomes the main constraint

Cross-border payments have improved materially in recent years, helped by investment in infrastructure, standards and connectivity. G20 targets have given the industry a 2027 deadline for faster, cheaper and more transparent international transactions.

Swift’s latest research suggests the main constraint now sits closer to the beneficiary than many users might assume. Once a payment has moved between financial institutions and arrived at the final bank, the experience still depends on local processing, account validation, compliance checks, domestic rails, operating hours and the quality of payment data.

For multinational companies, those technical milestones translate into more practical questions: whether a supplier has been paid, whether a customer receipt can be matched, whether payroll is certain, whether liquidity has moved and whether cash has reached the right counterparty. If the last mile is slow or unpredictable, finance teams carry that uncertainty in working capital forecasts, dispute management, reconciliation and supplier relationships.

Swift has identified five areas of structural friction in the final stage of a cross-border payment. They will be familiar to any bank or corporate that has chased delayed funds: local rules that dictate what must be checked before release, FX and capital conditions that shape conversion and crediting, data gaps that interrupt straight-through processing, risk controls that push payments into alert queues and domestic rails that decide whether final crediting happens instantly or waits for a batch window.

Faster international movement alone cannot remove those constraints. If a payment reaches the beneficiary bank in seconds but then waits for missing information, alert review or local batch settlement, the end user still sees a delayed payment.

Swift’s Payment Optimisation Index and Playbook are designed to give banks a clearer view of those market-level and institution-level frictions. More predictable final crediting depends on cleaner data, greater alignment around standards and fewer avoidable manual touchpoints.

For corporates, these are information gains as much as speed gains. A confirmed receipt shortens the chase. Predictable crediting improves cash forecasts. Clearer fees and FX show the real cost of a route before it is chosen.

Common rules across live corridors

Swift’s second recent development is its shared framework for retail cross-border payments, which is now being used in live corridors. Retail remittances are the proving ground, but the operating lessons travel into commercial payments. Speed, transparency, fee certainty and confirmation of receipt are just as valuable when the beneficiary is a supplier, platform seller or overseas contractor.

Over the past month, 26 financial institutions have started processing payments under the framework. They have activated 25 corridors across 17 markets, including major remittance links across Asia-Pacific, Europe, the Middle East and the Americas. More than 70 financial institutions have committed to implementing the framework during 2026.

Swift says payments from Australia to Spain have been completed in as little as 23 seconds, while Australia to India transfers have arrived in 37 seconds and payments from China to the US have been delivered in a minute. Those examples are drawn from retail corridors, but the underlying expectations are familiar to corporate users: upfront transparency, certainty over value delivered, trackability and confirmation when funds arrive.

SMEs selling cross-border, platforms paying merchants or gig workers, companies issuing refunds and finance teams making high-volume low-value payments all need confidence that funds will arrive when expected and with the right information attached. Payment speed helps, but predictability is often more valuable for operations.

A shared framework also creates a benchmark against which banks can organise their own processes. When participating institutions agree common expectations on transparency, value delivery and payment tracking, improvements depend less on a single bank’s internal project. Progress requires coordination across sending banks, receiving banks and local payment systems.

The framework may sit in retail payments, but it will still reset expectations around commercial flows. Once a small cross-border payment can be tracked from initiation to delivery, opaque payment status and unexplained deductions become harder to defend in business payments.

Tokenised deposits enter the live pilot phase

Swift’s new blockchain ledger pushes the story into regulated digital settlement. As previously reported on CTMfile, its blockchain-based ledger is ready for initial use, nine months after it was announced, and 17 early adopter banks are preparing to pilot live cross-border transactions using tokenised deposits.

Participants span the Americas, Europe, the Middle East, Africa and Asia-Pacific, with ANZ, BNP Paribas, Citi, DBS, First Abu Dhabi Bank, HSBC, Lloyds Bank, Standard Chartered, UBS and Wells Fargo among the group. The breadth of the bank list matters because any tokenised deposit model will need cross-regional participation if it is to move beyond a small number of closed corridors.

The ledger is designed as an orchestration layer for bank-issued tokenised deposits. Participating banks would issue deposits on their own ledgers, while Swift’s ledger records and validates commitments before final settlement takes place through existing systems. The initial use case is 24/7 cross-border payment availability, allowing funds to move overnight and at weekends while preserving compliance, credit, risk and control standards embedded in existing bank processes.

Thierry Chilosi, chief business officer at Swift, said the ledger would allow tokenised value to move across borders with greater “velocity and flexibility”, while maintaining the security and compliance expected in global finance.

For corporate treasury teams, tokenised deposits could eventually address a different set of pain points from last-mile optimisation. Continuous settlement availability would reduce the importance of cut-off times and weekends. Better liquidity efficiency could make it easier to move cash between regions without waiting for conventional banking windows. Programmable payment logic could support future use cases in areas such as conditional settlement, automated treasury actions or agentic commerce.

Near-term implications are more limited. Swift has described the first phase as a controlled go-live involving early adopters. Functionality and availability are expected to expand after that initial stage. Any corporate use will depend on which banks participate, which currencies are available, how final settlement works in practice and how tokenised deposit activity appears inside treasury management systems, ERP platforms, reconciliation tools and bank reporting.

The treasury system view will matter as much as the network view. Corporate adoption of digital settlement tools will depend on whether finance teams can use them inside controlled workflows. Faster money movement has limited value if it creates separate records, manual reconciliation or governance questions around approvals, sanctions screening, accounting treatment and audit evidence.

Improving today’s rails while testing tomorrow’s

Swift’s three announcements should be read as a connected infrastructure strategy. The cooperative is working to improve today’s cross-border payment experience through data, standards and shared operating frameworks, while also preparing for a future in which regulated digital assets move across bank infrastructure.

Current rails remain central to that strategy. The ledger is intended to sit alongside established systems, with final settlement still completed through existing arrangements. The retail framework operates through participating banks on Swift’s current network. The last-mile research focuses on improving the processes that determine how quickly funds are credited after they arrive.

That positioning reflects the realities of a fragmented global payments system. Delays can appear in different places in different markets: in local rules, operating hours, domestic infrastructure, data quality or compliance processes. Financial crime controls must still be strong enough to manage risk without turning routine payments into manual exceptions.

For a global corporate, those differences show up as corridor-by-corridor inconsistency. One supplier payment arrives and reconciles quickly. Another becomes trapped in a status query. A third arrives with deductions or incomplete information. Treasury may only discover the issue after a vendor has chased payment or after cash reporting fails to match expected flows.

Swift’s approach suggests that meaningful gains will come from several layers of improvement. Better data and standards can reduce exception handling. Shared frameworks can align bank behaviour across corridors. Domestic instant payment systems can accelerate final crediting where they are available. Tokenised deposits may eventually extend availability and liquidity flexibility beyond today’s processing windows.

The network question

Coverage will decide how far the gains travel. Fast examples in selected corridors do not automatically translate into universal performance. Last-mile frictions vary by market, and some of the biggest constraints sit outside Swift’s direct control. Domestic infrastructure, regulatory design, local operating hours and beneficiary-bank processes will all affect the end result.

Bank participation also matters. Retail corridors can improve as more institutions join the framework, but corporate users will look for coverage across their own bank groups, supplier markets and currencies. Tokenised deposit pilots will face the same network question.

Payment controls are part of the speed challenge. Banks need to let routine transactions move with less friction while still catching the payments that require closer scrutiny. As fraud, sanctions and cyber risks become more complex, that balance will determine how much speed can be added without weakening trust in the network.

Technology integration will be another practical test. Payment status, fees, FX information, settlement confirmation and remittance data need to flow into corporate systems. Improvements inside the banking network will have more value when they are visible in the treasury workstation, ERP and cash forecasting process.

Turning speed into certainty

Swift’s recent announcements pull the cross-border payments agenda closer to the point where users feel it: final crediting, confirmation, reconciliation and access to liquidity. Speed remains important, but the harder work is increasingly about consistency, transparency, final crediting and controlled access to new settlement models.

For banks, the task is to improve performance without fragmenting the infrastructure that supports global payments. For regulators and market operators, last-mile data offers a clearer view of where policy, compliance and domestic systems affect payment outcomes. For corporates, the prize is a payment environment that supports better cash decisions.

More predictable cross-border payments would make liquidity forecasting more reliable, reduce the cost of payment investigations and improve confidence in supplier settlement. Greater transparency over fees, FX and receipt status would give finance teams a clearer view of cost and risk before they initiate a payment.

No single announcement delivers that outcome on its own. The significance of Swift’s recent activity lies in the combination: measuring the last mile, setting common service expectations across live corridors and preparing a tokenised deposit ledger for controlled use by major banks.

The competitive question in cross-border payments is now whether banks can make the whole journey visible, confirmed and usable inside corporate finance systems. Swift’s latest announcements show it tackling that problem where payments still slow down: local processing, common service rules and the settlement infrastructure itself.