2026-07-01 Author : ZCS
Southeast Asia's retail payment landscape in 2026 looks nothing like it did five years ago — and it looks nothing like Europe, North America, or Northeast Asia. Three of the region's largest economies — Thailand, Vietnam, and Indonesia — have independently developed national QR payment infrastructures that now handle the majority of everyday retail transactions. Card-based contactless payment, the dominant hardware discussion in Western markets, is a secondary consideration in most of these environments. QR code acceptance is the primary one.
For hardware buyers — whether ISVs building regional payment applications, distributors supplying merchants, or procurement teams standardising terminal fleets across countries — this creates a set of hardware requirements that differ in specific, technical ways from global-standard POS configurations. GMS certification determines which payment flows are available. Network architecture determines whether a terminal functions reliably outside major urban centres. Currency and language configuration determines whether a single hardware platform can serve multiple markets without re-engineering.
This guide addresses each of those requirements by market, then draws the cross-regional implications for hardware procurement decisions.
The dominance of QR-based payment in Thailand, Vietnam, and Indonesia is not a cultural preference that emerged arbitrarily. It is the result of deliberate infrastructure investment by each country's central bank in response to a specific structural problem: card terminal deployment is expensive, requires PCI-certified hardware, and depends on a banking relationship that excludes a large proportion of small merchants. QR codes solved the merchant acquisition problem — a merchant needs only a printed QR code or a low-cost display to accept payments — and the infrastructure scaled rapidly.
According to the Bank for International Settlements' 2024 report on fast payment systems, QR-based fast payment adoption in Southeast Asia has outpaced card contactless adoption across all three markets examined here. The hardware implication is direct: a POS terminal deployed in Thailand, Vietnam, or Indonesia that cannot present a dynamic QR code for payment — one that encodes the transaction amount and reference in real time — is missing the dominant payment acceptance mode in these markets.
Static QR codes (printed stickers) are used by micro-merchants but are not appropriate for formal retail POS deployments: they cannot encode a transaction amount, require the customer to enter the amount manually, and create reconciliation gaps. Dynamic QR generation is a software function, but it requires the terminal to have a display capable of rendering a high-contrast QR code at sufficient resolution — a minimum of 200 pixels per side for reliable scan performance at standard counter distances.
Dynamic QR code generation for payment: POS terminals in Thailand, Vietnam, and Indonesia typically require a minimum 480×320 screen resolution and dynamic QR rendering capability to support PromptPay, VietQR, and QRIS transaction flows. Confirm the terminal screen resolution and QR generation API support before deployment in QR-dominant retail environments.
Thailand's national QR payment system, PromptPay, operates on the NITMX (National ITMX) interbank switching infrastructure and is administered under the oversight of the Bank of Thailand. PromptPay enables real-time account-to-account transfers triggered by a QR code scan, with settlement occurring within seconds. By 2024, PromptPay was processing over 20 million transactions daily — a volume that makes it the dominant retail payment method for amounts below 5,000 THB in most merchant categories.
For POS hardware to participate in PromptPay acceptance, the terminal must be able to generate a PromptPay-compatible QR code (following the Thai QR Payment Standard, which specifies the EMVCo QR code data format with Thai-specific merchant information fields) and receive real-time payment confirmation from the acquiring bank's API. This is an online transaction that requires stable connectivity — offline PromptPay acceptance is not currently supported by the infrastructure.
Thailand's urban connectivity — Bangkok, Chiang Mai, Pattaya — is generally reliable across 4G LTE networks, with 5G rollout advancing in central Bangkok. However, a significant share of SMB retail activity occurs in suburban and provincial locations where 4G coverage is available but congested during peak periods, and where Wi-Fi infrastructure at the merchant level is inconsistent.
For POS terminals deployed outside Bangkok and major tourist centres, built-in 4G LTE with dual SIM capability provides a meaningful operational advantage: the ability to switch to a secondary carrier when the primary network is congested or unavailable, without requiring staff intervention. Terminals that rely solely on Wi-Fi, or on a separate mobile hotspot device, introduce a dependency that is difficult to manage reliably across a distributed merchant fleet.
Thai script requires a dedicated font stack that is not included in all Android builds. A terminal running a stripped-down Android export build without Thai Unicode support will render Thai characters as boxes. Confirm CJK-equivalent font completeness for Thai script in any terminal being evaluated for the Thai market — the same verification requirement applies to Japan's SMB retail market, which demands its own set of hardware standards around font rendering and character support: test character rendering on the actual device, not from the OS version number.
Vietnam's QR payment standard, VietQR, was launched in 2021 under the coordination of the State Bank of Vietnam (SBV) and NAPAS (the National Payment Corporation of Vietnam). VietQR standardises QR code format across all participating Vietnamese commercial banks, enabling a single QR code to be scanned by any VietQR-compatible banking application regardless of the customer's bank.
By 2025, VietQR had achieved near-universal adoption among Vietnam's major commercial banks and was the primary payment interface for the majority of smartphone-using consumers in urban Vietnamese retail environments. The hardware implication is consistent with Thailand: QR generation capability and real-time connectivity are baseline requirements, not optional features.
Vietnam's retail market outside major urban centres — Hanoi, Ho Chi Minh City, Da Nang — retains a significant cash transaction share. Provincial and peri-urban merchants frequently operate in environments where the customer mix includes both VietQR-enabled smartphone users and cash-only customers. A terminal deployment that removes cash handling capability prematurely will lose transactions in these environments.
The practical hardware implication: terminals for Vietnamese provincial deployment should support both QR payment flows and cash drawer integration (RJ11 or USB), without requiring separate hardware for each. A single-device solution that handles both avoids the counter space and fleet management complexity of running parallel systems.
Vietnam's 4G LTE coverage, while expanding rapidly, remains uneven in highland provinces and rural areas. For merchants in these locations, offline transaction caching — the ability to store payment attempts locally when connectivity drops and sync when it restores — is operationally significant. Confirm the terminal's offline transaction cache limit explicitly; this figure is rarely prominently disclosed in vendor marketing materials but determines whether a terminal is viable for rural Vietnamese deployment.
Indonesia's approach to QR payment standardisation is the most structurally distinctive of the three markets. QRIS (Quick Response Code Indonesian Standard), introduced by Bank Indonesia in 2019 and made mandatory for all QR payment providers operating in Indonesia by 2020, requires every QR payment application — including GoPay, OVO, Dana, LinkAja, ShopeePay, and bank applications — to generate and accept the same QR code format.
The practical result is that a merchant displaying a single QRIS QR code accepts payment from all major Indonesian e-wallet and banking applications simultaneously. For hardware vendors, this is relevant in two ways. First, the QRIS standard follows the EMVCo Merchant Presented Mode QR specification — the same format that underlies PromptPay and VietQR — so a terminal platform that correctly implements this format can be configured for all three markets with application-layer adjustments rather than hardware changes. Second, Bank Indonesia's QRIS certification process for acquirers and payment service providers means that the hardware must support the ISV integration through which QRIS certification has been obtained.
Indonesia's geography creates a connectivity challenge with no parallel in the other two markets. Outside Java, Bali, and the major Sumatran urban centres, 4G LTE coverage varies dramatically — some island merchant locations operate on 3G as their best available network, and Wi-Fi infrastructure is absent or unreliable. A terminal deployed across a multi-location Indonesian merchant network may face very different connectivity conditions at different sites.
Hardware requirements for Indonesian multi-location deployment include: built-in multi-band 4G LTE supporting both FDD-LTE and TD-LTE (the two band types used by different Indonesian carriers), dual SIM capability for carrier failover, and offline transaction caching with a cache limit sufficient to cover an extended connectivity gap. The offline cache requirement in Indonesian provincial deployment is materially higher than in Bangkok or Hanoi — a terminal with a 50-transaction offline limit is inadequate for a merchant location that may lose connectivity for hours at a time.
Bali and Lombok handle a high volume of international tourist transactions, creating a multi-currency payment requirement that is less common in the other two markets. POS hardware deployed at tourist-facing merchants in these locations must support dynamic currency conversion (DCC) or at minimum display transaction amounts in the customer's home currency before confirmation — a feature that requires both software configuration and a terminal platform with sufficient display resolution for clear currency presentation.
Connectivity and offline caching for Indonesia deployment: POS terminals in Indonesian provincial and island deployments typically require dual-SIM 4G LTE (FDD-LTE + TD-LTE), offline transaction caching of 200+ transactions, and multi-band cellular support. Confirm these specifications before deploying across a distributed Indonesian merchant network where connectivity conditions vary significantly by island location.
Google Mobile Services (GMS) certification is the mechanism by which an Android device gains access to the Google Play Store, Google Pay, and the full suite of Google APIs. In the context of Southeast Asian POS deployment, GMS certification matters for three specific reasons.
First, many ISVs building payment applications for Southeast Asian markets distribute through Google Play. A non-GMS terminal cannot install these applications through the standard channel, requiring the ISV to set up an alternative APK distribution and update mechanism — adding deployment complexity and removing the automatic update pathway that Google Play provides. For ISVs evaluating terminal platforms with deeper API access and integration flexibility beyond GMS compliance alone, see our guide to open SDK access and custom ODM configuration for Android POS terminals.
Second, Google Pay — while not the dominant payment method in these markets — is used by a growing share of international visitors and younger urban consumers with Google Wallet-linked cards. A GMS-certified terminal running SoftPOS can accept Google Pay without a separate NFC payment reader, reducing hardware component count at the counter.
Third, and most practically, GMS certification signals a level of Android build quality and API completeness that correlates with ISV integration reliability. Non-GMS builds frequently have missing or non-standard API implementations that create compatibility issues during ISV integration — issues that surface months into a deployment rather than during initial testing.
GMS-certified POS terminal (Southeast Asia, 2026): a terminal holding Google Mobile Services certification supports Google Play distribution, Google Pay via SoftPOS, and full Android API access for ISV integration. GMS certification is a hardware-level qualification — confirm GMS status for the specific terminal model being evaluated, as it cannot be added post-production.
This point requires emphasis because it is consistently misunderstood. GMS certification is granted to a specific hardware configuration — a combination of processor, RAM, storage, and Android build — not to a vendor or a product line. A vendor may hold GMS certification for one model configuration (e.g., 4 GB RAM, Android 13) but not for a cost-reduced variant (e.g., 2 GB RAM, same Android version). Confirm GMS certification for the exact model and configuration being ordered, not for the vendor's product line in general.ZCS's Z92 terminal, for instance, holds GMS certification at the model level and supports SoftPOS-based Google Pay acceptance — an example of the certification specificity buyers should verify when evaluating any vendor's product line for Southeast Asian deployment.
Despite their differences, Thailand, Vietnam, and Indonesia share a set of hardware requirements that define the baseline specification for any terminal intended to operate across the region.
| Requirement | Thailand | Vietnam | Indonesia | Hardware Implication |
|---|---|---|---|---|
| QR payment (dynamic) | PromptPay | VietQR | QRIS | Screen resolution ≥480×320; QR generation API |
| Real-time connectivity | 4G LTE | 4G LTE | 4G LTE + 3G fallback | Built-in cellular; dual SIM preferred |
| Offline caching | Limited need | Moderate need | High need (islands) | Confirm cache limit per deployment location |
| GMS certification | Strongly preferred | Strongly preferred | Strongly preferred | Verify per model configuration |
| Local script rendering | Thai Unicode | Vietnamese diacritics | Latin + regional scripts | Confirm font stack completeness on device |
| Cash drawer support | Urban: optional | Provincial: required | Provincial: required | RJ11 or USB cash drawer interface |
| Multi-currency | Tourist zones | Limited | Bali/Lombok tourist areas | DCC support or display-layer configuration |
The common thread is that standard "global export" terminal configurations — built for card contactless dominance, with minimal offline capability, single SIM, and non-GMS builds — are systematically mismatched with Southeast Asian deployment realities. The hardware decisions that define a viable Southeast Asian deployment profile are made at the specification and procurement stage, not resolved through software configuration after deployment. This mismatch is not unique to Southeast Asia — procurement teams standardising across multiple regions will find a comparable set of connectivity, certification, and currency constraints in Middle East and Africa POS hardware deployments, where infrastructure conditions diverge just as sharply from global-standard assumptions.
Thailand, Vietnam, and Indonesia represent three of the fastest-growing retail payment markets in Asia — and three of the markets most likely to expose the gaps in a global-standard terminal deployment. The QR-first payment infrastructure, variable connectivity environments, local script rendering requirements, and GMS certification dependency together define a hardware profile that must be assembled deliberately, not assumed from a global certification.
For hardware buyers, the procurement checklist is consistent across all three markets: dynamic QR rendering capability, built-in 4G LTE with dual SIM, offline transaction caching with an adequate cache limit, GMS certification confirmed for the specific model configuration, and local font stack completeness verified on the physical device.
For the broader framework of deploying Android POS hardware across multiple countries — including TMS configuration for managing certification, firmware, and language settings across a regional fleet — see our guide to deploying Android POS terminals across multiple countries.
Q1: What is the main difference between Southeast Asian and Western POS payment requirements?
Thailand, Vietnam, and Indonesia rely primarily on QR-based national payment systems—PromptPay, VietQR, and QRIS—rather than card contactless payment. POS terminals must support dynamic QR code generation with a minimum 480×320 screen resolution, making QR rendering capability a baseline hardware requirement rather than an optional feature.
Q2: Why does GMS certification matter for POS terminals in Southeast Asia?
GMS certification enables Google Play distribution, Google Pay via SoftPOS, and full Android API access needed for ISV integration. It is granted per hardware configuration, not per vendor or product line, so certification status must be confirmed for the exact model and RAM/storage configuration being ordered.
Q3: What connectivity features are required for POS deployment across Indonesian islands?
Indonesian provincial and island deployments typically require dual-SIM 4G LTE supporting both FDD-LTE and TD-LTE bands, offline transaction caching of 200 or more transactions, and 3G fallback capability. Connectivity conditions vary significantly by location, making carrier failover and extended offline caching essential for reliable operation.
Q4: Do POS terminals in Vietnam still need cash drawer support?
Yes. Provincial and peri-urban Vietnamese merchants serve customer bases that mix VietQR-enabled smartphone users with cash-only customers. Terminals deployed outside major cities should support both QR payment flows and cash drawer integration via RJ11 or USB interfaces within a single device to avoid parallel hardware systems.
Q5: Can one POS hardware platform serve Thailand, Vietnam, and Indonesia simultaneously?
PromptPay, VietQR, and QRIS all follow the EMVCo Merchant Presented Mode QR specification, allowing a single terminal platform to serve all three markets through application-layer configuration rather than hardware changes. GMS certification, local font stack support, and connectivity specifications still require per-market verification.