International Payment Gateway Bangladesh: How Foreign Merchants Accept Local Payments

Why global gateways do not solve Bangladesh

Most international payment gateways are card-first. They were designed for markets where a Visa or Mastercard number is the default instrument, and their coverage in Bangladesh is either absent or limited to a small minority of cardholders. Bangladesh runs on mobile financial services. A customer who has never held a card will still have a wallet balance topped up at an agent point, and that wallet is the default way they pay online.

The practical result is that a foreign merchant who launches with a global processor sees a conversion rate that looks catastrophic. The traffic is real, the intent is real, but the payment instrument on the page is one the customer does not hold. An international payment gateway for Bangladesh therefore has to mean something specific: a gateway that presents mobile financial services (MFS) wallets plus BEFTN and NPSB bank transfers to the customer while giving the merchant a single foreign-facing integration and settlement relationship.

Average ticket sizes are small and frequent, so approval rate and confirmation speed matter far more than the headline fee.

What an international gateway must actually provide

There are four separate problems hiding inside the phrase "accept payments in Bangladesh".

1. Local acceptance. The checkout must offer instruments customers hold, in BDT, with local-language conventions and mobile-first layouts.
2. Local collection. Funds have to land somewhere regulated inside the country before they can move anywhere else.
3. Cross-border settlement. Local collections are denominated in BDT and repatriation must follow Bangladesh Bank foreign-exchange guidance, which is why most international merchants settle through a licensed local partner rather than holding accounts themselves.
4. Reporting that survives an audit. Every payout to the merchant has to be traceable back to individual customer transactions.

A provider that solves only the first is a checkout widget, not a gateway. PayEurasia's cross-border payment solutions exist because the last three problems are where most projects stall.

Payment methods that matter in Bangladesh

International merchants usually start by asking which method has the largest market share. The better question is which combination covers the widest range of ticket sizes, because bKash and bank transfers serve very different customers.

• bKash — supported through PayEurasia's Bangladesh acceptance stack with reference data returned on every transaction.
• Nagad — supported through PayEurasia's Bangladesh acceptance stack with reference data returned on every transaction.
• Upay — supported through PayEurasia's Bangladesh acceptance stack with reference data returned on every transaction.
• Rocket — supported through PayEurasia's Bangladesh acceptance stack with reference data returned on every transaction.

Bank rails are covered through dedicated collection accounts with BRAC Bank, Dutch-Bangla Bank, Eastern Bank and other local institutions, which is what makes larger ticket sizes practical. Coverage per market is listed on the countries hub.

Settlement out of BDT

Collections settle on T+0 for wallet volume and T+1 for bank rails. Money collected locally is aggregated, reconciled against transaction references, and then paid out to the merchant according to an agreed schedule and currency.

Local collections are denominated in BDT and repatriation must follow Bangladesh Bank foreign-exchange guidance, which is why most international merchants settle through a licensed local partner rather than holding accounts themselves. In practice this means the merchant signs with a partner that holds the local relationships, and receives consolidated settlements with a statement that maps every payout line back to underlying transactions. That statement is what makes the arrangement auditable — and it is the single most common gap when merchants try to assemble a solution from local agents.

Compliance expectations for foreign merchants

Bangladesh Bank sets the framework that local acquirers and payment service providers operate under, and those obligations flow through to you as a merchant. Expect to provide:

• Certificate of incorporation and ownership structure for the operating entity
• Licences relevant to your vertical, where one is required
• A description of the service being sold and the customer journey
• AML and KYC policy documents, including how you handle sanctions screening
• Historical processing statements if you have them

Wallet transactions are pull-and-confirm rather than card-style authorisations, so disputes are handled through evidence and reference matching rather than scheme chargeback cycles. Our compliance page sets out the standards we apply, and the KYC and AML policies describe the underlying process.

Integration model

A well-built international integration in Bangladesh looks the same regardless of vertical:

• One create-transaction call that returns a redirect or intent for the chosen method
• Signed webhooks for every state change, with retries and idempotency keys
• A reconciliation endpoint that can be replayed for any date range
• Separate credentials for sandbox and production

Full details are in the API documentation, and the general design principles are covered in our payment infrastructure overview.

Common mistakes

• Treating a wallet like a card. Agent-assisted payments are common, so a checkout that expires in 90 seconds will lose real customers who are still walking to a top-up point.
• Ignoring failure taxonomy. "Failed" is not a reason. Insufficient balance, limit exceeded, user cancelled and timeout each need a different retry or message.
• Under-provisioning payouts. Merchants often plan collections carefully and then discover they also need local disbursements, which requires separate capability and approvals.
• Skipping reconciliation until month one closes. Build it on day one; retrofitting it across thousands of transactions is painful.

Merchant benefits

• Local acceptance in BDT without incorporating in Bangladesh
• One API for bKash, Nagad, Upay and bank rails
• Consolidated settlement with per-transaction reporting
• Routing across multiple local providers so a single outage does not stop revenue
• Underwriting that understands complex verticals rather than rejecting them by category

Related guides and solutions

• Bangladesh Payment Gateway
• High Risk Payment Solution Bangladesh
• bKash Payment Gateway
• Nagad Payment Gateway
• Solutions overview
• Cross-Border Payment Solutions
• Payment Infrastructure
• High-Risk Merchant Payment Processing
• Countries hub

Talk to our team

If you are evaluating acceptance in Bangladesh, the fastest way to get a useful answer is to share your vertical, expected monthly volume and required payout frequency. Our team can confirm which rails are available to your business, what documentation underwriting will ask for, and how quickly you can go live. Start with merchant onboarding or contact us directly.

Frequently asked questions

Can a foreign company accept BDT payments in Bangladesh?

Yes, through a licensed local partner. The merchant does not need a local entity, but the collection must happen inside a regulated structure in Bangladesh, and settlement out of BDT must follow the applicable foreign-exchange rules.

Which payment methods should an international merchant launch with?

bKash and Nagad cover the majority of consumer transactions, and bank transfers handle larger amounts. Launching with both wallet and bank coverage is normally worth the extra integration effort.

How long does settlement take?

Settlement typically runs on T+0 for wallet volume and T+1 for bank rails, with payout frequency agreed during onboarding based on volume and risk profile.

What documents are needed to onboard?

Incorporation documents, ownership details, any vertical-specific licence, AML and KYC policies, and a clear description of the product being sold. Processing history helps but is not mandatory.

Is a local bank account required?

No. Collections land in the partner's regulated local accounts and are settled onward to the merchant, which is what removes the need for the merchant to hold BDT accounts directly.