A merchant selling outdoor gear in Toronto does not think much about WeChat Pay. Neither does the operator of a gaming platform in Amsterdam, or a luxury retailer in London. They have their payment gateway set up, their checkout payment flow tested, their processing contracts signed. The electronic payment system works — for the customers they already have.
The customers they can't yet serve are a different matter. Hundreds of millions of people across China, Southeast Asia, and South Korea conduct much of their financial activity inside super apps — platforms that consolidated messaging, commerce, and payments into a single environment, and that have developed rapidly over the past decade. When those users travel, study abroad, or shop from international merchants, they expect to pay the way they always pay. They may reach checkout and find that their preferred wallet is not supported. The merchant loses the sale without knowing why, and the customer moves on.
This is not a niche problem. It reflects a systematic gap in how most Western merchants have approached international payment gateways — building for the customer base they understand and treating everyone else as an edge case.
What Super Apps Are, and Why They Complicate Cross-Border Payment Acceptance
Super apps developed most prominently in Asian mobile-first markets, through a combination of consumer adoption, platform network effects, and infrastructure designed to connect payments with everyday digital services. A single application could do what dozens of separate apps do in the West — messaging, food delivery, banking, payments — through embedded mini-programs or integrated services running inside the parent platform. WeChat alone has more than 1.38 billion monthly active users as of 2025, with Alipay serving a comparable base across China's consumer economy. Kakao Pay and Grab offer popular payment services within broader digital ecosystems in South Korea and Southeast Asia.
For merchants and platforms trying to serve these users, super apps create a payment integration challenge that is harder than it first appears. When accessed through different providers or integrated directly, these wallets can involve different APIs, user flows, reporting formats, settlement arrangements, and operating requirements. A merchant who wants to accept several of them may find that the operational overhead accumulates quickly — each additional payment method potentially introducing its own reconciliation logic, reporting format, and failure mode. Most mid-market merchants don't have the internal infrastructure to absorb that complexity at scale.
This is where payment orchestration becomes the most fitting approach to what's actually happening.
Payment Orchestration and What It Means for Merchants Entering New Markets
Payment orchestration is a layer that applies routing, retry, and rules-based logic across multiple processors, gateways, and payment methods. A payment orchestration platform generally coordinates gateways and processors rather than replacing every underlying provider — the value is in normalizing the logic that sits above them, so that a merchant doesn't rebuild routing and fallback rules from scratch for every new market or method.
The distinction matters because most merchants who expand internationally start by stitching things together manually. They add a PSP for one market, a payout vendor for another, a separate banking partner for currency settlement. Each addition creates a new integration, a new reconciliation workflow, a new support relationship. By the time they're operating in three or four markets, they have a payment stack that nobody fully understands, and that breaks in unpredictable ways when any single vendor changes something upstream.
Super app acceptance sits at the end of that chain. A merchant who wants to accept WeChat Pay on an e-commerce checkout, or through a gaming platform where users buy in-game currency, is asking their payment infrastructure to handle the relevant wallet, provider, acquiring, and regulatory requirements — simultaneously, without lengthy custom engineering for each new payment method. Whether that's achievable depends largely on what's already in place at the infrastructure level.
The Merchant Case for Supporting Locally Preferred Payment Methods
The original framing of this problem focused on the consumer — the traveler frustrated at the register. That frustration is real, but it understates the commercial stakes for operators. The more relevant case is the platform or marketplace whose user base includes a meaningful segment of Asian consumers, or who is actively expanding into Asian markets.
A gaming platform that does not support locally preferred methods may create additional friction for some users, even if those users have access to alternative payment options. A marketplace processing payments across Southeast Asia that doesn't support local wallets or bank transfer methods may be asking some sellers and buyers to use payment methods they don't typically use. The friction compounds over time in ways that don't always show up as explicit lost sales — they show up as lower conversion, higher checkout abandonment, and narrower effective reach. The Baymard Institute's aggregated research puts the global average cart abandonment rate above 70%, with unsupported payment methods among the documented causes.
Pockyt's infrastructure is built for this problem. The combination of 300+ locally preferred payment methods, developer-friendly APIs, and local checkout, treasury, and payout capabilities within a single platform is designed for merchants who need to accept regional wallets without building a separate integration for each one. The underlying integrations, payment-method connectivity, settlement infrastructure, and reporting are handled through the platform rather than rebuilt independently for every market. SOC 2 Type II attestation and PCI DSS Level 1 validation demonstrate audited security controls and card-data protections, while broader regulatory and licensing requirements still vary by market and product.
What Changes When the Infrastructure Is Already in Place
Super apps spread through a combination of consumer adoption, platform network effects, and infrastructure designed to connect payments with everyday digital services. What made WeChat Pay work seamlessly inside WeChat was that the payment layer was engineered into the platform from the beginning — the routing, the settlement, the user authentication all resolved within the same ecosystem.
Western merchants serving those users are building toward an infrastructure that already exists on the other side of the transaction. The World Bank's Global Findex 2025 report documents significant variation in preferred payment methods across economies, based on surveys of around 148,000 adults in 141 economies conducted in 2024. Where that preference for local wallets is strong — and in several high-value segments it is — the question for the merchant is whether their payment integration can meet it.
That's a problem solved at the infrastructure level, and increasingly merchants don't have to build that infrastructure themselves.
If your platform is expanding into markets where locally preferred wallets are the default payment method, or you're seeing checkout conversion losses you can't fully explain, get in touch for a personalized evaluation.