Cross-Border Payment Guide for South Asia

Collecting money in South Asia and settling it into a foreign bank account is a solved problem — but only if you understand the structure. Merchants who treat it as a single integration problem usually fail. Merchants who treat it as a banking, compliance and reconciliation problem with an API attached usually succeed.

This guide explains the cross-border model across Bangladesh, India, Pakistan and Nepal: how funds actually move, what determines cost, where flows break, and how to build an operation that scales across four markets.

The core structural problem

Every South Asian market shares a common shape. Consumers pay with local instruments — mobile wallets and domestic bank rails — denominated in local currency. Those instruments settle domestically, into local bank accounts, held by locally registered entities.

A merchant incorporated outside the region cannot usually hold those accounts. That single fact explains almost everything about cross-border payments here: the industry exists to bridge domestic collection and international settlement, legally and reconcilably.

There are three broad models:

1. Local entity model — you incorporate locally, obtain local banking, contract a domestic PSP and repatriate funds yourself. Maximum control, maximum administrative burden, slowest to launch, and often impossible for restricted verticals.
2. Cross-border PSP model — a provider with local collection capability and international settlement pays you abroad on a defined cycle. Fastest to launch, one relationship per region rather than per market.
3. Hybrid model — local entity in your largest market, cross-border provider for the rest. Common for merchants at scale.

Most international merchants start at model two, and many stay there permanently because the operational simplicity outweighs the marginal cost.

Market-by-market collection reality

Bangladesh

Mobile financial services dominate consumer payments: bKash, Nagad and Upay together cover the overwhelming majority of wallet users. Bank rails handle larger tickets. Settlement is BDT to local accounts. See the Bangladesh payment gateway page and the best payment gateway Bangladesh guide.

India

UPI dominates consumer payments, with IMPS, NEFT and RTGS handling progressively larger values and cards playing a supporting role. Regulatory supervision is the most active in the region and merchant category alignment matters materially. See India payment gateway and the UPI merchant payment guide.

Pakistan

JazzCash and Easypaisa dominate, with interbank rails covering higher value and instant payment infrastructure improving settlement speed. See Pakistan payment gateway.

Nepal

eSewa and Khalti lead wallet usage, with bank-linked rails handling larger transfers. Market size is smaller, so provider stability and support quality matter disproportionately. See Nepal payment gateway.

How the money actually moves

A typical cross-border collection has four stages.

Stage one — capture. The customer pays through a local wallet or bank rail. The provider receives a domestic credit in local currency and confirms the transaction to your system via webhook.

Stage two — pooling. Domestic credits accumulate in the provider's local banking infrastructure, reconciled transaction by transaction against merchant references.

Stage three — conversion. Local currency is converted to the settlement currency, typically USD or EUR, at an agreed rate methodology. This is where hidden cost usually lives.

Stage four — remittance. Converted funds are remitted to your international account on the contracted cycle, net of fees and any reserve withholding, accompanied by a settlement report you can reconcile.

Each stage has a failure mode: capture failures cost conversion, pooling failures cause unmatched credits, conversion failures cost margin, remittance failures cost trust and cash flow. Diligence should probe all four.

The true cost of cross-border settlement

Merchants compare MDR and ignore the rest. A complete cost model has six components.

• Collection cost — MDR and fixed fees per method.
• FX spread — the difference between the interbank rate and the rate applied. Ask for the reference rate, the spread in basis points, and the timestamp used. "Market rate" without a definition means an undefined margin.
• Remittance cost — wire fees, correspondent charges and intermediary deductions.
• Reserve drag — the working-capital cost of held funds.
• Dispute and refund cost — including cross-currency refund losses when rates move.
• Failure cost — conversion lost to declined or abandoned payments, usually the largest and least measured item.

Compute landed cost per successful order in your home currency. That number, not MDR, is what determines profitability.

Compliance across four jurisdictions

Cross-border flows attract scrutiny for good reasons. Providers and their banks must satisfy sanctions screening, anti-money-laundering obligations, source-of-funds expectations and correspondent banking standards. Practically, merchants should maintain:

• Accurate corporate records and UBO disclosure
• KYC on their own customers proportionate to the vertical
• Transaction monitoring with documented thresholds and escalation
• Clear, truthful description of the flow of funds
• Licensing evidence where the activity requires it
• Records retention that survives an audit request years later

Merchants who present this proactively onboard faster and negotiate better terms. Merchants who resist it get slower cycles, larger reserves and eventual offboarding.

Reconciliation: the operational core

Multi-market cross-border operations fail on reconciliation before they fail on technology. Build the following from day one.

One internal ledger. Every transaction, in every market, in both local and settlement currency, keyed by your own order ID and the provider reference.

Daily automated matching. Compare provider reports to your ledger every day. Investigate breaks within twenty-four hours, not at month-end.

FX recording at two points. Record the transaction-time rate and the settlement-time rate separately so you can measure FX drift as a distinct line item.

Payout and refund reconciliation. Outbound flows and returns are the most common source of silent losses.

Reserve tracking. Maintain a schedule of held funds and expected release dates so reserves appear as a receivable, not a mystery.

Building the operating model

One integration or four?

Four local providers give you local pricing and direct relationships but multiply integration work, reconciliation surfaces, compliance relationships and failure modes by four. A single multi-market provider trades a little rate for a large reduction in operational overhead. Most merchants below very large scale are better served by consolidation, with a secondary route per critical market for redundancy.

Redundancy planning

Maintain live secondary capability in your highest-volume market. Test it with real traffic monthly. Document who authorises a route switch and how long it takes.

Local method depth

Cross-border success is decided at the checkout, in local terms. Native wallet branding, local-language labels, correct amount formatting and locally plausible payment ordering all measurably improve completion.

Payout capability

Many merchants need outbound flows: customer withdrawals, affiliate settlements, partner payments. Cross-border payout capability is less commoditised than collection. Verify per-market coverage, limits, beneficiary validation and return handling before you promise anything to customers.

Where high-risk changes the picture

For Forex, gaming, betting and casino merchants, the cross-border problem is harder because the pool of willing providers is small and the banking relationships behind them are the real constraint. What matters is not the checkout UI but whether the provider's underlying banking can sustain your category over time. Ask how long the current banking relationship has been in place, whether there is a second one, and what happens to your settlement if the primary is withdrawn. Further reading: how high-risk payment processing works.

Diligence questions to ask any cross-border provider

1. Which entity holds funds between collection and settlement, and in which jurisdiction?
2. What is your FX reference rate and spread, and at what timestamp is it struck?
3. What is the settlement cycle per market, and what triggers a delay?
4. What is the reserve percentage, holding period and release mechanism?
5. Do you have direct local banking or do you sit behind another aggregator?
6. What per-method success rates have you delivered in the last ninety days?
7. How do you notify merchants during a rail outage?
8. What is your payout coverage and limit structure per market?
9. What documentation triggers a compliance review or hold?
10. What happens to in-flight funds if the relationship is terminated?

Providers that answer these clearly are the ones worth shortlisting.

How PayEurasia operates

PayEurasia runs dedicated local banking and direct wallet integrations across Bangladesh, India, Pakistan and Nepal, giving merchants one integration, one reconciliation surface and cross-border settlement on transparent terms. We publish method-level performance, define reserve and FX treatment in writing, and support high-risk verticals that mainstream providers decline.

Read the cross-border payment solutions overview or contact us with your markets, entity structure and volumes.

Frequently asked questions

How do cross-border payments work in South Asia?

A provider collects locally through domestic wallets and bank rails in local currency, pools and reconciles those credits in local banking infrastructure, converts to a settlement currency and remits to the merchant's international account on an agreed cycle, accompanied by a reconcilable settlement report.

Do I need a local company in each South Asian market?

Not if you use a cross-border capable provider. A local entity gives maximum control and often better local pricing, but requires local incorporation, banking and administration in each market, and is frequently unavailable for restricted verticals.

What does cross-border settlement actually cost?

Total cost combines collection MDR and fixed fees, FX spread, remittance and correspondent fees, reserve drag, dispute and refund costs, and lost revenue from failed payments. Compare landed cost per successful order rather than headline MDR.

How long does cross-border settlement take?

Typically one to five business days after the domestic settlement cycle, depending on market, corridor, banking partner and reserve policy. Contractual cycles should be stated per market, along with the events that can delay them.

Should I use one provider for all four markets or one per market?

One multi-market provider dramatically reduces integration, reconciliation and compliance overhead, which usually outweighs marginal local pricing advantages. Larger merchants often consolidate primary volume with one provider and retain a secondary route per critical market for redundancy.

What compliance documentation is required for cross-border flows?

Expect corporate registration and UBO records, director identification, licensing evidence where applicable, a documented flow of funds, your own customer KYC and transaction monitoring policies, and processing history. Providing this proactively speeds onboarding and improves terms.