How Do Global Merchants Expand into APAC Without a Local Entity? Cross-Border Payment Processing Explained

TL;DR

• Expanding into Asia-Pacific's emerging markets traditionally required establishing local entities in each country—a process involving 6–18 months of legal setup, local banking relationships, regulatory approvals, and ongoing compliance management per market.
• Cross-border payment processing eliminates this barrier, allowing global merchants to collect payments locally across multiple APAC markets through a single integration, without local incorporation.
• This guide explains how cross-border processing works in APAC, what regulatory models enable it, which markets require what, and how enterprises are using this approach to scale across the region.

Cross-border payment processing in APAC is a model where a global merchant accepts payments from consumers in local currencies and local payment methods (wallets, bank transfers, QR codes) without establishing a legal entity in each country.
A licensed payment provider acts as the local collection agent, handling regulatory compliance, local acquiring, FX conversion, and settlement—while the merchant operates from their existing international entity (typically in Singapore, the US, or Europe).
This model enables market entry in days rather than months, with full access to local payment ecosystems.

Why Is Local Entity Setup So Difficult in APAC?

The Traditional Approach (and Its Problems)

For a merchant targeting multiple APAC markets, this means potentially separate entity setups, banking relationships, and regulatory compliance frameworks in each country—a multi-year, multi-million-dollar undertaking.

The Cross-Border Alternative

Cross-border payment processing compresses this timeline from years to days:

How Does Cross-Border Payment Processing Work in APAC?

The Collection Agent Model

The most common cross-border model in APAC uses a collection agent structure:

1. Consumer pays locally: The consumer sees local payment methods (GoPay, UPI, GCash, PromptPay) in their local currency.
2. Licensed provider collects: The payment provider (e.g., dLocal), operating under local licenses or regulated partnerships, collects funds on behalf of the merchant.
3. Compliance handled locally: KYC, tax withholding, central bank reporting, and data localization requirements are managed by the provider.
4. Funds consolidated: Collections across multiple markets are consolidated into a single dashboard.
5. Settlement to merchant: Funds are converted (if cross-border) and settled to the merchant's international bank account in their preferred currency.

The Architecture

Step-by-Step: Cross-Border Collection

1. Consumer in Indonesia selects GoPay at checkout on the merchant's website/app.
2. Merchant's system sends payment request to dLocal via single API.
3. dLocal's local infrastructure routes the transaction to GoPay/QRIS via local acquiring connection.
4. Consumer authenticates in their GoPay app and confirms payment in IDR.
5. Funds settle to dLocal's local Indonesian bank account.
6. dLocal converts IDR to merchant's preferred settlement currency (USD, EUR, SGD, etc.).
7. Merchant receives consolidated settlement with full transaction reporting.

Settlement Models

What Are the Key Regulatory Challenges in APAC Cross-Border Payments?

Market-by-Market Regulatory Landscape

Data Localization

Several APAC markets mandate that payment data be stored locally:

• India: All payment data must reside on servers in India (RBI mandate).
• Indonesia: Bank Indonesia requires certain transaction data to be processed locally.
• Vietnam: Data localization requirements for financial services.

A cross-border payment provider must maintain local data infrastructure in these markets—something global merchants cannot easily do without local entities.

FX Controls and Restricted Currencies

Case Study: How a Leading Global Streaming Platform Expanded Across APAC Without Local Entities

The Challenge

A major global streaming service routed all their APAC card volume through their Singapore entity as an intra-regional card transaction. This created:

• Additional costs from cross-border interchange and scheme fees
• Lower acceptance rates due to international transaction flags
• Poor user experience including additional taxes, international fees, and currency conversion charges visible to consumers

The Solution

dLocal's collection agent model allows this merchant to collect locally across APAC markets whilst still leveraging their Singapore entity. This enables:

• Lower fees by processing as local transactions rather than cross-border
• Higher acceptance rates by removing international transaction flags
• Removed customer friction around cross-border taxes and international fees

The Expansion

Since working on the card project, this merchant also unlocked AyoConnect—a prevalent account-to-account payment method in Indonesia—which was integrated as their first-ever APM in APAC.

The Pattern

This case study illustrates the typical APAC expansion journey:

1. Start with cards processed locally (immediate cost and conversion improvement)
2. Add local APMs (unlock 60–80% of consumers who don't use cards)
3. Expand to new markets (same API, same contract, new country)

What Payment Methods Are Available Cross-Border in APAC?

A cross-border model does not mean limited payment method access. Through dLocal's single API, merchants access the full local payment ecosystem:

dLocal supports 15+ live alternative payment methods across APAC with strong conversion rates across local rails.

How Do Payouts Work Cross-Border in APAC?

Cross-border processing isn't just about collecting payments—global merchants also need to disburse funds to local partners, suppliers, contractors, and creators.

dLocal APAC Payout Capabilities

Key Payout Highlights

• Processing available every day (including weekends) for most markets
• Instant or same-day settlement in most corridors
• Low single-processor risk on major payout rails

How Does dLocal Compare to Competitors for Cross-Border APAC Processing?

Competitive Landscape

How dLocal Differentiates

• Single API across 9 APAC markets — no other provider offers this breadth with this depth.
• Payout + Payin combined on one platform — competitors typically offer one or the other.
• Emerging-markets-first regulatory depth — operating where global players have limited presence.
• Strong local APM conversion rates across the portfolio.

What Should Merchants Evaluate When Choosing a Cross-Border APAC Provider?

Decision Framework

What Is the Merchant-of-Record (MoR) Model, and When Is It Needed?

In some APAC markets, particularly Japan, a Merchant-of-Record model is required or advantageous:

MoR vs. Collection Agent

dLocal's Japan MoR scheme is live, enabling global merchants to sell to Japanese consumers without navigating the Fund Settlement Act and consumer protection regulations independently.

What Is the Typical APAC Expansion Playbook?

Phase 1: Cards First (Weeks 1–4)

• Integrate dLocal's single API
• Enable local card acquiring across target markets
• Immediate benefit: lower fees, higher acceptance rates, removed cross-border friction

Phase 2: Add Local APMs (Weeks 4–8)

• Enable dominant wallets and bank transfers per market
• Unlock the majority of consumers unreachable via cards alone

Phase 3: Expand Markets (Ongoing)

• Same API, same contract—add new countries in days to weeks
• Prioritize by market size, regulatory readiness, and merchant demand

Phase 4: Enable Payouts (As Needed)

• Disburse to local bank accounts and wallets
• Critical for marketplaces, gig platforms, and creator economies
• Instant settlement in most markets

Fact Sheet: Cross-Border APAC Processing with dLocal

Key Takeaways

1. Local entity setup in APAC takes 6–18 months per country — cross-border processing compresses this to days.
2. The collection agent model enables global merchants to collect locally while operating from a single international entity (e.g., Singapore).
3. Global enterprises are already using this model to scale across APAC without local entities in each market.
4. Bangladesh and Pakistan are among the most restricted markets — few providers offer compliant cross-border payin capabilities there.
5. Payouts are a dominant APAC use case, with instant settlement and strong conversion rates.
6. Conversion rates match local processing when the provider routes through local acquirers and local payment rails.
7. dLocal's single API across 9 markets with combined payin + payout capabilities is differentiated from both global challengers (Adyen, Stripe) and regional players (Xendit, Razorpay, 2C2P).