Google Wallet Is Now Available in 50 More Countries — What This Means for Global Pass Distribution

Google Wallet's 2025 expansion was the largest single rollout in the platform's history. More than 50 new countries gained access, pushing the total supported market count past 100. For businesses that issue wallet passes, this is straightforward good news: your existing Google Wallet integration now reaches a significantly larger share of the global population without a single line of code changing on your end.

But “available” and “optimised for” are different things. This article covers which markets opened up, what genuinely changes for your pass programme and where localisation work is still needed.

Which regions gained access

Three broad regions drove the bulk of the 2025 expansion.

Southeast Asia was the most significant addition by population. Vietnam, Thailand and the Philippines all gained full Google Wallet availability. Combined, these three markets represent over 200 million smartphone users, with Android commanding a dominant share of the device market in all three countries. If you operate a loyalty or membership programme in any of these markets, the addressable pass audience roughly doubled overnight.

Latin America saw meaningful additions beyond the existing large markets of Brazil and Mexico. Colombia, Chile and Peru are now fully supported. These are commercially active markets with high smartphone penetration and growing demand for digital-first engagement. Retailers, event organisers and transport operators in these countries can now issue Google Wallet passes without directing customers to alternative wallet platforms.

Eastern Europe rounded out the expansion, with Romania, Bulgaria and Croatia added to the supported list. These markets are EU members, which matters for data handling — passes distributed to customers in these countries fall under the same GDPR framework as the rest of the EU. Businesses already operating under GDPR do not need new compliance infrastructure.

What changes for your pass programme

The short answer is: not much, technically. The Google Wallet Passes API operates the same way regardless of which country the end user is in. You create a pass class, issue a pass object, generate a save link and distribute it. That workflow does not change based on geography.

What changes is the proportion of your customer base that can act on a Google Wallet save link. Before the expansion, customers in newly added markets who tapped an “Add to Google Wallet” button received an error — Google Wallet was not available in their country. That is no longer the case. If you have been suppressing wallet pass distribution in certain markets due to availability constraints, you can remove those suppressions.

Apple Wallet availability is a separate question. Apple has broadly supported its Wallet feature across most major markets for several years, but with regional activation differences tied to financial partnerships and local regulatory requirements. In general, pass distribution via both platforms is now available across most commercially significant markets globally.

Localisation: where you still have work to do

Geographic availability and localisation are not the same thing. A customer in Vietnam can now add your Google Wallet pass, but if the pass displays dates in MM/DD/YYYY format and monetary values in USD, the experience will feel foreign and potentially confusing.

Currency display. Wallet passes display currency as plain text in their fields. There is no automatic currency conversion or local formatting. If your loyalty pass shows a voucher value of “$10.00” to a customer in Colombia, they will see exactly that string. For multi-market programmes, consider either displaying a neutral value (e.g. “10 reward points” rather than a monetary amount) or maintaining market-specific pass templates with the appropriate currency symbol and formatting.

Date formats. The same applies to dates. An expiry date of “03/07/2026” reads as 3 July to a European customer and 7 March to a North American one. For passes with expiry dates, use an unambiguous format — “7 Mar 2026” or ISO 8601 “2026-03-07” — to avoid any possible misreading regardless of market.

Right-to-left languages. Google Wallet has added right-to-left language support for markets such as Israel (Hebrew) and several Arabic-speaking countries. Pass fields will render correctly in RTL when the device language is set appropriately, but the text content itself — your field labels, message copy and any descriptive text — must be provided in the appropriate language. If you are distributing passes in these markets, plan for translated field content as part of your pass template.

Character set support. Vietnamese, Thai and Filipino scripts all require Unicode, which Google Wallet supports fully. However, if you are pulling field values from a database or CRM that was set up for Latin-character markets, verify that your data pipeline handles multi-byte characters correctly end to end. A customer name stored as “Nguyễn Văn An” should appear exactly that way on the pass.

Multi-region infrastructure and pass distribution

Global pass distribution creates an infrastructure question: where do you host your pass management backend? Google Wallet passes are served via the Google Wallet Passes API regardless of geography, but Apple Wallet passes require your own web service URL for push notifications and pass updates. If that service is hosted in a single region, customers in Southeast Asia or Latin America may experience higher latency when their device fetches an updated pass.

We run Issuepass on a dual-region infrastructure — EU and US — built on Cloudflare Workers, which serves pass updates from the nearest edge node to the requesting device. This means a customer in Bangkok retrieving an updated loyalty pass gets the same response time as a customer in London. For programmes distributing passes across multiple continents, this matters both for the end-user experience and for the reliability of push notification delivery.

Pass templates created in Issuepass work identically across Apple Wallet and Google Wallet. When a customer in a newly supported Google Wallet market saves your pass, it arrives via the same infrastructure that has been serving customers in established markets. There is no separate configuration for new markets.

What to do now

If you are currently distributing wallet passes, audit your distribution logic for any market-based suppression that was put in place because Google Wallet was unavailable. Remove those suppressions for the newly supported markets.

If you have been waiting for Google Wallet availability before launching a pass programme in Southeast Asia, Latin America or Eastern Europe, the technical blocker is now gone. The remaining work is localisation — translated copy, appropriate currency display and correct date formatting for your target market.

The 2B+ people globally who already use mobile wallets are now joined by a significant new cohort. The window to build wallet-based loyalty and engagement programmes in these markets before competitors do is open. Start free and issue your first pass to any of these new markets today.