Context and Chronology

Thunes has activated a Pay-to-Wallet capability together with Banco Cathay, enabling banks to repurpose existing SWIFT connections to route payouts directly into recipient mobile wallets. The link sits on Thunes’ payments stack, treasury liquidity layer and compliance platform and translates traditional bank disbursement messages into mobile‑wallet credits without requiring deep API integrations at the sender bank. Company representatives framed the integration as a production rollout rather than a pilot, giving Banco Cathay immediate access to Thunes’ network for cross‑border disbursements.

Operationally this removes an intermediate local‑account hop that commonly forces senders to hand off funds to local partners for wallet payout. For banks already on SWIFT the marginal work is configuration and compliance onboarding, reducing adoption friction for remittances, payroll and merchant settlement programs in mobile‑first corridors. Treasury and reconciliation teams can consolidate multiple local payout relationships into a single counterparty endpoint, shortening settlement chains and improving fee transparency.

Complementing the fiat-to-wallet capability, Thunes also offers tokenized settlement options that convert fiat instructions into balances denominated in dollar‑pegged tokens (e.g., USDC/USDT) and push those balances to wallets over blockchain rails. That capability surfaces a different set of benefits—round‑the‑clock finality, potentially faster intraday settlement and a single‑message sender experience—but it also introduces distinct dependencies such as on‑ramp/off‑ramp coverage, custody arrangements and issuer redemption mechanics.

Because public reach claims aggregate different endpoint types, readers should treat headline numbers as distribution potential rather than guaranteed, on‑demand cash convertibility everywhere. For example, tokenized rails may advertise access to large counts of on‑chain wallets, while fiat wallet figures reflect mobile payment endpoints; in many corridors, reliable fiat withdrawal still depends on local agent networks, custodians or PSP partners to provide off‑ramp liquidity.

The combined product architecture centralizes message translation, liquidity orchestration and compliance screening within Thunes’ platform. That centralization simplifies sender integration and shortens routing paths, but it concentrates corridor liquidity and operational risk in the platform—tradeoffs that banks will weigh against multi‑provider fabrics that offer failover and liquidity diversification at the cost of heavier engineering and commercial complexity.

Regulatory frameworks and varied legal treatments of tokenized assets remain decisive constraints on where token rails scale fastest. Divergent rules around reserve treatment, custody and freezing powers mean banks are likely to use Thunes’ tokenized option selectively and within existing compliance agreements rather than as a universal replacement for correspondent banking overnight.

Commercially, the Banco Cathay activation demonstrates how incumbent banks can reuse existing SWIFT tunnels to reach wallet‑first markets with limited systems overhaul—a capability that will pressure correspondent margins on low‑value, high‑volume flows and create upsell opportunities for networked processors. For corporates and PSPs, the net effect is the potential to compress time‑to‑payout, reduce reconciliation overhead and improve auditability of cross‑border disbursements.

Adoption will be uneven: large banks with SWIFT links can repurpose them quickly, while smaller banks and local PSPs may prefer partnering or relying on multiple providers to preserve resilience. Market observers will watch corridor performance, partner liquidity behavior and regulatory responses to determine whether Thunes’ combination of fiat-to-wallet and tokenized rails becomes routine plumbing or remains an optional channel for specific flows.