Module 4

International Expansion Playbook

The decision framework for launching payments in new markets, navigating regulatory complexity, and optimising for local payment methods

---

The Market Selection Framework: Risk, Regulation, and Readiness

International expansion is not a binary decision. It is a sequence of choices about which markets to enter, in what order, with what infrastructure, and when to commit capital. Most businesses choose markets poorly, entering geographies with high regulatory friction and low infrastructure readiness, or skipping markets with strong revenue potential because initial research suggests regulatory complexity. The framework helps you make data-driven decisions.

Every market sits at the intersection of three dimensions: revenue opportunity, regulatory complexity, and infrastructure maturity. High-opportunity markets might have high regulatory friction (think Australia) or lower infrastructure readiness (think Southeast Asia). Your expansion strategy must balance these factors against your company size, regulatory bandwidth, and strategic priorities.

International expansion succeeds when you choose markets you can actually serve, not markets with the highest theoretical revenue potential.

Revenue Opportunity Assessment

Revenue opportunity is not just population size. It is addressable market size adjusted for business model fit, payment maturity, and competitive intensity. A market might have one billion people but low online payment adoption, fragmented access to payment methods, or intense local competition.

Assess revenue opportunity by examining: total online commerce volume, growth rate, average transaction size, customer acquisition cost relative to transaction value, and depth of competitor presence. Statista, eMarketer, and Euromonitor provide market sizing data. For niche business models, conduct bottom-up analysis by surveying target customer density and purchasing power. A B2B SaaS company entering India, for example, should assess the number of addressable SMEs, their software spending levels, and how that translates to payment volume, not general ecommerce statistics.

Regulatory Complexity Scoring

Regulatory complexity varies dramatically by market, and it is the primary bottleneck to international expansion. Complexity has several dimensions: licensing requirements (do you need to become a Money Transmitter or payment institution), consumer protection rules (what liability you carry), cross-border movement rules (how you settle funds), and ongoing compliance obligations (KYC, AML, OFAC).

Score regulatory complexity on a scale: low (UK, Australia, Canada, Singapore, Hong Kong), moderate (EU, Brazil, Mexico, Japan), high (India, China, Russia). This is not a precise science. Regulatory frameworks change. Enforcement varies. But the scoring helps you allocate bandwidth. Low-complexity markets can often be served through a third-party processor with minimal integration. High-complexity markets require regulatory strategy, entity structure analysis, and often, local partnerships.

Infrastructure Maturity Assessment

Infrastructure maturity reflects payment method coverage, processor quality, settlement efficiency, and fraud ecosystem development. A mature market like Germany has extensive local payment method coverage (iDEAL, Bancontact, SEPA), multiple high-quality processors, next-business-day settlement, and sophisticated fraud networks that have reached operational equilibrium. An emerging market like Vietnam has limited local method coverage, fewer processor options, slower settlement, and evolving fraud patterns.

Infrastructure maturity affects your costs and complexity. A mature market lets you route to a single local processor with full payment method coverage. An immature market might require orchestration across multiple processors to cover payment methods, or reliance on card-only infrastructure if processors support it.

---

Regional Regulatory Requirements: A Compliance Blueprint

Regulatory requirements vary sharply by region, and each region imposes distinct compliance obligations. Understanding these obligations before market entry saves months of remediation and prevents unexpected blockers. We will examine the major regions and their licensing, consumer protection, and settlement requirements.

European Union and UK

The EU operates under Payment Services Directive 2 (PSD2) and the upcoming Payment Services Directive 3 (PSD3), which create a comprehensive framework for payment service providers. If you provide payment services (accept payments, issue wallets, or perform transfers), you must be licensed as a Payment Institution (PI) or Electronic Money Institution (EMI). Licensing is conducted by national regulators. The FCA in the UK, Finanstilsynet in Denmark, Banque de France in France, and equivalent bodies in each country.

Licensing requirements include: minimum capital reserves (typically 50,000 EUR to 1 million EUR depending on service type), detailed compliance policies, customer fund protection mechanisms, and governance structures. The process takes 3 to 6 months and requires legal representation. PSD2 also mandates Strong Customer Authentication (SCA), which requires two-factor authentication for consumer payments over 30 EUR (subject to exemptions). This was implemented in 2019 and remains a significant operational requirement.

PSD3 (in draft as of early 2026) will intensify these requirements by introducing open banking mandates, expanded data portability rules, and stricter consumer protection around instant payments. If you are planning 2026-2027 EU expansion, account for PSD3 timeline uncertainty.

Settlement in the EU occurs through SEPA (Single Euro Payments Area) for EUR transactions, with next-business-day settlement standard. UK post-Brexit is diverging from EU rules. The FCA operates a lighter-touch regulatory framework for smaller payment providers, creating a potential entry point for startups.

United States

The US has no single payments regulator. Instead, payment service providers navigate a patchwork of federal and state rules. At the federal level, the Bank Secrecy Act requires AML/KYC compliance, and the Gramm-Leach-Bliley Act requires data security and privacy policies. At the state level, each state issues Money Transmitter Licenses, with 48 states plus DC requiring licensure (only New Hampshire and Missouri have no requirement).

State money transmitter licensing is fragmented and expensive. Each state sets its own requirements, which typically include: minimum net worth (ranging from $25,000 to $500,000 depending on state), bonding requirements, quarterly financial reporting, and transaction monitoring. The total cost of nationwide licensure is 300,000 to 500,000 USD, with annual compliance costs of 50,000 to 150,000 USD.

For most international companies, the practical approach is to partner with a US-regulated processor like Stripe, Adyen, or Square rather than pursue licensure directly. These processors hold Money Transmitter Licenses and sub-acquire merchant accounts under their umbrella. Settlement is typically next-business-day to 2 days for domestic ACH, and 1 to 3 business days for card transactions.

APAC Region

Asia-Pacific has diverse regulatory regimes with no harmonisation. Singapore operates a relatively light-touch model under the Monetary Authority of Singapore (MAS), with fast-track licensing for FinTech companies. India requires registration with the RBI (Reserve Bank of India) and increasingly mandates use of local payment infrastructure like NPCI (National Payments Corporation of India) for digital payments. Japan operates under FSA (Financial Services Agency) oversight with strict requirements around consumer protection and data residency. Australia requires ASIC (Australian Securities and Investments Commission) authorisation for payment facilitation services.

The common theme across APAC is pressure toward local infrastructure adoption. India mandates use of UPI for certain transaction types. China restricts foreign payment providers and requires partnerships with local players. Southeast Asia (Thailand, Vietnam, Indonesia) has growing local payment method adoption but limited direct access for foreign providers without local partnerships.

For APAC expansion, the practical approach is often partnership with a local processor or payments platform rather than direct licensing. Wise (formerly TransferWise) in Southeast Asia, FINO in India, Stripe and Adyen in most major markets, provide entry points.

LATAM Region

Latin America has moderate regulatory complexity with country-level variation. Brazil requires registration with the Central Bank and Banco do Brasil for payment operations. Mexico requires CNBV (Financial Supervision Commission) authorisation. Argentina, Colombia, and Chile have their own banking regulators.

A common challenge in LATAM is settlement speed and FX exposure. Brazil settles in real-time through PIX (an instant payment system), creating different working capital dynamics than US/EU overnight settlement. Most LATAM countries have elevated FX volatility, creating basis risk for companies that receive local currency and settle to USD.

The practical approach is using a regional processor like Payoneer, 2Checkout, or Adyen that understands local regulatory and settlement requirements rather than pursuing direct licensing in each country.

---

Local Payment Methods: The Revenue Impact of Card-Only Limitations

A critical strategic decision is whether to support local payment methods or operate card-only. Card-only sounds simpler operationally, but it costs revenue in most markets outside North America. In developed European markets, 40 to 50 percent of online transactions use local payment methods (iDEAL, Bancontact, SEPA Credit Transfer). In emerging markets, the penetration is even higher. In Brazil, PIX now exceeds card payments for online commerce. In India, UPI and bank transfers exceed cards for digital transactions.

Major Regional Payment Methods

European markets have deeply entrenched local methods. Netherlands has iDEAL, which captures 50 percent of online payments. Belgium has Bancontact. Poland has BLIK. These methods exist because consumers trust them, they offer superior fraud prevention compared to cards, and they have better checkout conversion rates than cards. Conversion uplifts from adding local methods are typically 5 to 15 percent depending on market.

Southeast Asia has mobile payment dominance. Thailand uses PromptPay, Singapore uses PayNow, Indonesia uses QRIS and e-wallets like GCash. China is effectively entirely digital payments through Alipay and WeChat Pay.

India has two dominant systems: UPI (Unified Payments Interface) for peer-to-peer and merchant payments, and NPCI for network rules. UPI has captured 40 percent of digital payments and grows rapidly. Most Indian payment processors require UPI support for competitive positioning.

Brazil offers PIX, a real-time payment system launched in late 2020 that now processes more online payments than cards. PIX connects directly to bank accounts and settles instantly, providing working capital benefits for merchants.

The Integration Burden vs. Revenue Tradeoff

Each local payment method requires separate integration. You must understand local payment method rules, implement new reconciliation logic, handle different error codes, and support different settlement timing. Integrating 10 new payment methods adds significant engineering burden.

The tradeoff is clear: full local payment method coverage increases conversion and market competitiveness but increases engineering complexity. The decision framework is volume-based. If you are doing millions in transactions in a market, the conversion uplift justifies integration. If you are doing thousands, card-only suffices. Most companies take a tiered approach: card plus 1 to 2 local methods in each market, not full coverage.

---

Entity Structure and Local Acquiring Decisions

A critical strategic decision is whether to operate through a single global entity with cross-border acquiring, or establish local entities with local acquiring in each major market. This decision affects regulatory licensing, cost structure, settlement speed, and authorisation rates.

Single Global Entity with Cross-Border Acquiring

Operating through a single entity (e.g., a UK-based company accepting payments globally) is operationally simpler initially. You maintain one payment processor relationship, one compliance regime, and one ledger. Settlement occurs in a single currency to a single bank account. Integration complexity is minimised.

The costs of cross-border acquiring are higher. Cross-border authorisation rates are typically 5 to 15 percent lower than local acquiring, meaning more legitimate transactions get declined. Cross-border interchange fees are elevated. Settlement takes longer (2 to 5 business days vs. next-business-day for local). FX conversion happens at less favourable rates.

Cross-border acquiring is viable for smaller companies (under $5 million annual transaction volume) that prioritise operational simplicity over cost optimisation. As volume grows, the cost of cross-border acquiring compounds and becomes the primary driver for switching to local entities.

Local Entities with Local Acquiring

Operating through local entities (establishing a UK Ltd, a Singapore Pte Ltd, a Brazil Ltda) and acquiring locally provides significant advantages. Local acquiring yields auth rates that are 5 to 15 percent higher than cross-border, directly improving conversion. Interchange is lower because it is domestic. Settlement is faster. FX is eliminated if you settle in local currency.

The costs and complexity are higher upfront. You must establish legal entities in each market, which requires local accounting, tax filings, and regulatory compliance. You need multiple processor relationships. You need ledger structures that account for multi-currency settlements. Initial setup costs are 50,000 to 150,000 USD per market for legal entity establishment, banking, and compliance setup.

Local entities make economic sense at approximately $2 to 5 million in annual transaction volume in a given market. Below that threshold, cross-border acquiring is cheaper. Above it, local acquiring cost savings exceed the overhead of local entity operation.

Hybrid Approach

Many companies use a hybrid approach. Small markets (under $1 million annual volume) remain cross-border. Major markets (EU, US, UK, APAC, LATAM) operate through local entities. Mid-tier markets (Spain, Poland, Canada) operate through regional hubs. Stripe and Adyen support this model through their global platforms, allowing a single integration to route transactions to local entities in each region.

---

Currency Management: Settlement Currencies, FX Exposure, and Hedging Basics

International expansion introduces foreign exchange (FX) risk. When a customer in India pays in INR, you receive INR but operate with costs in USD or EUR. The daily INR/USD rate fluctuation creates both risk and opportunity. Managing FX is a financial decision that affects net margins.

Settlement Currency Choices

For each market, you choose a settlement currency. You can settle in local currency (INR for India, BRL for Brazil), in USD, or in your operational currency (usually EUR or USD for European companies). Settling in local currency eliminates conversion risk but requires local bank accounts and carries risk that local currency depreciates. Settling in USD or EUR involves FX conversion at processor-quoted rates, which typically add 0.5 to 1.5 percent to the effective rate.

The decision depends on your funding model and cost structure. If you have local revenue that you can keep in local currency, settle locally. If your costs are primarily in USD, settle to USD. Most companies use a mix: settle in local currency in mature markets where you can deploy local funds, settle to primary currency in emerging markets where you have lower volumes.

FX Exposure Management

FX exposure compounds over time. A company operating in 10 currencies with 50 million in annual transaction volume has significant currency exposure. A 5 percent currency move could add or subtract 2.5 million in reported revenue depending on accounting treatment.

Managing FX exposure requires choosing an accounting treatment (spot vs. forward rates) and potentially hedging through financial instruments. Most companies use spot accounting (converting at the rate on settlement date) and monitor currency exposure without formal hedging until exposure exceeds 10 to 20 percent of annual margins. Formal hedging through currency forwards or options becomes cost-justified at larger scales.

The practical advice: monitor FX exposure explicitly, make settlement currency decisions intentionally based on your actual fund flows, and revisit the framework annually as your transaction mix evolves.

---

Cross-Border vs. Local Acquiring: The Decision Framework

The core decision is whether to pursue local acquiring in each major market or operate through cross-border acquiring. This decision is not permanent. Most companies start with cross-border (simpler operationally) and migrate to local acquiring as volume justifies it.

---

International Expansion Compliance Checklist

Use this checklist when planning entry into a new market. It ensures you account for regulatory, operational, and financial considerations before committing.

Regulatory and Licensing

• Determine if your business model requires payment service provider licensing in the target market
• Identify the relevant regulator and licensing pathway (fast-track options, tiered licensing for smaller entities)
• Estimate licensing cost, timeline, and capital requirements
• Understand ongoing compliance obligations: KYC/AML, reporting, audit requirements
• Identify data residency requirements (do customer data, transaction data, and settlement data need to be stored locally)
• Assess consumer protection requirements and liability exposure

Payment Method Coverage

• Map dominant payment methods in the target market (card penetration, local methods, wallets, bank transfers)
• Identify which methods are available through existing processor relationships
• Assess conversion rate impact of supporting only card vs. multi-method
• Estimate integration cost and timeline for adding new payment methods
• Decide on minimum viable payment method coverage for market entry

Entity and Acquiring Structure

• Estimate transaction volume threshold where local entity + local acquiring becomes economically justified
• Identify legal and accounting requirements for establishing a local entity
• Evaluate cross-border vs. local acquiring impact on auth rates, effective rates, and settlement timing
• Determine whether partnership with a local processor or local licensing is the practical approach

Currency and Settlement

• Decide on settlement currency (local, USD, EUR)
• Estimate FX exposure given transaction volumes and settlement strategy
• Assess whether formal FX hedging is needed
• Understand settlement timing and fund flow implications

Risk and Monitoring

• Identify fraud patterns and dispute rates in the market
• Plan fraud prevention and chargeback monitoring
• Establish KYC/AML screening procedures and monitoring infrastructure
• Plan for market-specific risk controls (velocity limits, transaction caps, etc.)

---

Common International Expansion Mistakes

Learning from others' mistakes accelerates your expansion. Here are the patterns we see repeatedly.

Entering Too Many Markets Too Quickly

Early success in the home market sometimes triggers expansion fever. A company enters 8 markets simultaneously, spreading compliance bandwidth thin, creating support load across multiple regulatory regimes, and discovering too late that one market requires specific infrastructure adjustments. Expansion should be staged. Start with 2 to 3 markets with high revenue potential and low regulatory friction. Learn the patterns. Then expand.

Underestimating Compliance Burden

Companies often underestimate the time and cost of compliance. A market that "should be easy" because it is English-speaking (UK, Australia) still requires local entity setup, local banking relationships, and regulatory interactions. Building in time buffer is critical. Plan 3 to 6 months for markets that require licensing.

Card-Only Architecture by Default

Many companies operate card-only globally because it is simpler operationally. This costs revenue in most markets. Asia-Pacific, Europe, and LATAM all have meaningful local payment method adoption. A 5 to 10 percent conversion uplift from adding local methods easily justifies integration. Make a conscious choice. Do not default to card-only.

Not Monitoring FX Exposure

Companies that operate in 5 plus currencies without explicit FX management often discover unpleasant surprises. A currency crisis in a major market can wipe out a quarter's margins. Even without crises, normal market moves add or subtract from net revenue. Monitor FX exposure explicitly. Set thresholds for hedging decisions.

Choosing Wrong Local Partner or Processor

Many companies partner with a local processor or payments platform without sufficient due diligence. The partner becomes a critical dependency. If the partner lacks features you eventually need (local payment method support, multi-currency settlement, API stability), you discover it too late and face expensive migrations. Evaluate local partnerships with the same rigor you use for primary processors.

---

Sequence and Timeline for International Expansion

A typical international expansion timeline looks like this. Months 1 to 2: market selection and regulatory assessment. Identify top 3 priority markets, conduct regulatory deep dives, estimate licensing requirements and timelines. Months 3 to 4: processor and partner evaluation. Identify which existing processors support each market, evaluate local partnerships vs. direct licensing, run proof-of-concept transactions. Months 5 to 6: compliance and legal setup. Establish entities, submit licensing applications, build compliance monitoring infrastructure. Months 7 to 8: processor integration and payment method setup. Integrate with local processor or multi-processor orchestration, add priority local payment methods, build local reconciliation and settlement tracking. Months 9 onwards: go-live and monitoring. Launch in market, monitor auth rates and cost structure, iterate on payment method coverage based on actual transaction patterns.

This timeline assumes moderate regulatory complexity (UK, Australia, Canada) and existing processor relationships. High-complexity markets (India, Brazil) add 2 to 4 additional months. Early-stage companies with limited bandwidth should compress this by narrowing to fewer markets and leveraging existing processor platforms rather than building custom infrastructure.