Swift announced on 28 September that it is working with banks, payment service providers and technology firms on four continents on pay by alias, an initiative that would let consumers send money internationally using a mobile number, email address or virtual payment address instead of full account details. The project aims to extend the front-end experience of domestic systems such as Bizum in Spain, PayID from Australian Payments Plus (AP+) in Australia and Pix in Brazil across borders. The BusinessWire release, issued from Brussels, describes a proof of concept and not a live service.

What Swift pay by alias is meant to do

Millions of people already send money in their home markets without knowing the recipient’s bank details, because the domestic system resolves a phone number or email address to an account. Swift wants the same identifiers to be securely matched for international transactions over its network. The sender would type a familiar alias and the matching would happen behind the scenes, across the domestic scheme and the Swift payment.

Fourteen organisations are named as participants: AP+, Banco de Crédito del Perú, Banorte, BBVA, Bizum, Bradesco, Caixabank, Citizens Bank, Commonwealth Bank of Australia, DBS, IDFC FIRST Bank, Ouribank, TerraPay and Veritran. The release says they come from four continents, and that spread is what gives the announcement its credibility.

Why the alias approach fits Swift’s consumer strategy

The initiative builds on Swift’s consumer payments framework, launched in June and involving more than 100 banks according to the release. The framework focuses on full-value transfers, predictability and fast settlement. Swift also says 75 percent of payments over its network reach the receiving bank within 10 minutes, often within seconds. That covers the back half of the journey. The initiative targets the front half, where senders give up because they lack a recipient’s account number, branch code or bank identifier.

My assessment is that the front end has been Swift’s weakest point against fintech rivals. Wise, Revolut and the remittance apps built their consumer pitch on easy sending, while bank customers on Swift have usually faced a clunky form. Alias-based sending is the most natural way to close that gap, and it lets banks reuse an interface their customers already trust at home.

The hard problems behind alias matching

Alias matching sounds simple and is not. A phone number registered as a Pix key in Brazil has no obvious global meaning, and each domestic scheme has its own registry, privacy rules and fraud controls. The release says identifiers will be securely matched. It does not say who holds the directory, how a lookup is authorised, or how misdirected payments are handled. Those answers decide whether the scheme is safe enough for real money.

Fraud is the sharpest problem. Authorised push payment scams work best when the sender needs only a phone number, so easy sending carries a cost. The participants include several large banks that will have views on liability, and the release contains no liability model. The Bizum executive quoted in the release calls the work a proof of concept and an early step, which is the accurate description.

How pay by alias connects to Swift’s retail work

The announcement follows a run of Swift consumer launches. We covered Bank of America and JPMorgan going live on the retail transfer standard and Itaú Unibanco enabling clearer transfers in Brazil. Those launches cover what happens after the sender presses send. The initiative covers what the sender sees before that, so the two efforts fit together. The Bizum quote in the release also ties the work to the G20 cross-border payments objectives, which signals that Swift wants regulators to see it as part of that agenda.

What to watch next for Swift’s alias project

The clear milestone is a live corridor. A pilot between two participants, for example Spain to a Latin American market through Bizum and a participating bank, would show whether alias resolution works in production. Swift will also need to say who operates the alias directory and how disputes and fraud are handled. Until a corridor is live and a liability model is published, Swift pay by alias is a credible design without a customer yet.