Bangladesh Payment Gateways: A Merchant Evaluation Checklist

Header image: conceptual illustration.

Bangladesh has a busy digital payments market: mobile financial services such as bKash and Nagad, card schemes, and bank transfers through national rails. Bangladesh Bank, the central bank, regulates payment and mobile financial services and publishes its rules and circulars on its website. For merchants, the practical question is which gateway to integrate and what to check before signing. This checklist is designed to be used in vendor calls.

1. Business acceptance

• Does the gateway accept your business category? Ask for written confirmation.
• Can it onboard a business registered outside Bangladesh, or only a local entity?
• What documents are required? Expect trade licence, registration documents and bank details for local entities; foreign entities should ask for the full list.

2. Payment methods

List which methods your customers use, then confirm per method:

• Mobile wallets (for example bKash, Nagad) — checkout, tokenised/agreement payments, refunds.
• Cards — local and international schemes.
• Bank transfers — see local bank transfers in Bangladesh.
• Payouts — whether the gateway can send money to customers, not only collect.

Many aggregator gateways list their supported methods in their developer documentation; SSLCOMMERZ's developer site is one example of the type of documentation to request.

3. Settlement

• Settlement frequency and cut-off times.
• Settlement currency and bank.
• Reserves, holds and their release conditions.
• How weekends and public holidays affect timing.

4. Fees

Ask for a written schedule covering transaction, refund, payout and settlement fees. Do not rely on public figures for your business type. Our Bangladesh gateway fees guide explains the components.

5. Technical integration

• Sandbox availability and documentation quality.
• Server-side transaction validation after the customer returns.
• Signed callbacks/webhooks and retry behaviour.
• Idempotency or duplicate-protection on payment creation.
• Status query API for reconciling pending payments.

6. Reporting and reconciliation

• Downloadable transaction and settlement reports.
• A unique reference you can store against your own order ID.
• Itemised fees.

7. Support and incidents

• Support hours and channels; Bangla and English support if your team needs both.
• How outages and method-specific downtime are announced.
• A named escalation contact.

Hypothetical evaluation

*Invented example.* A merchant shortlists two gateways. Both support bKash and cards. Gateway 1 offers next-business-day settlement but no payout API. Gateway 2 settles in two days and supports wallet payouts. Because the merchant needs to refund and pay customers regularly, Gateway 2 scores higher despite slower settlement.

What a payment gateway does in Bangladesh

A gateway sits between your checkout and the local payment rails. It presents the customer with the instruments they hold, initiates the transaction on the relevant rail, tracks its lifecycle, and reports the outcome back to your systems. 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 difference between a good and a poor gateway in Bangladesh is rarely the headline price. It is whether the gateway maintains enough redundant connections to keep approval rates stable, and whether it returns data clean enough to reconcile automatically.

Payment methods that matter in Bangladesh

Coverage is the first filter. A gateway that supports only one wallet forces a share of your customers to abandon, and in a market this concentrated that share is not small.

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.

Approval rate is the metric that matters

Two gateways quoting the same fee can differ by several percentage points in completion rate. The causes are usually structural:

• Number of upstream connections per method, and whether traffic can fail over automatically
• Timeout and retry behaviour when a wallet or bank is slow to confirm
• Whether the checkout is optimised for the mobile devices and connection speeds your customers actually use
• How quickly a degraded provider is detected and removed from the routing pool

Fees, and what they are actually made of

Pricing in Bangladesh generally combines a percentage of transaction value with per-transaction and payout costs. When comparing quotes, normalise for:

• Method mix — wallet and bank rail economics differ
• Refund and reversal handling
• Payout frequency and any minimum settlement amount
• Reserve requirements, if your vertical carries one
• Chargeback or dispute administration costs

A lower rate attached to a lower approval rate is more expensive in practice. Model the total cost per successful order, not per attempt.

Settlement and reconciliation

Finance teams should be able to close a day without opening a support ticket. If a provider cannot deliver reconciliation data in a machine-readable format, expect that to become a recurring monthly cost in staff time. The merchant payment infrastructure guide covers the ledger design that makes this straightforward.

Risk, compliance and merchant categories

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. Ecommerce, digital subscriptions, education platforms and gaming operators all see the same pattern: wallet-first checkout, low card penetration and heavy mobile traffic on modest bandwidth.

Merchants in regulated or high-risk categories should be candid during onboarding. Underwriting that knows what it is looking at can usually structure an approval; underwriting that discovers the truth later suspends the account. See high-risk merchant payment processing and High Risk Payment Solution Bangladesh for how that works in practice.

Integration checklist

1. Confirm method coverage against your actual customer base, not a generic list.
2. Test failure paths in sandbox: cancellation, timeout, insufficient balance, duplicate submission.
3. Implement idempotency keys on every create call.
4. Verify webhook signatures and make handlers replay-safe.
5. Reconcile a full day in staging before launch.
6. Agree monitoring and escalation contacts before go-live, not after the first incident.

Merchant benefits

• One integration covering bKash, Nagad, Upay and local bank transfers
• Redundant upstream connections with automatic failover
• Reconciliation data designed for finance teams, not just developers
• Support for complex verticals through dedicated underwriting

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

Frequently asked questions

Do I need a separate integration for each wallet?

Not always. Aggregators can offer several methods through one integration; direct integrations give more control but more work.

Where can I find official rules?

Bangladesh Bank publishes payment-system and MFS regulations and circulars on its website.

See also our Bangladesh payment gateway page.

Which payment gateway is best in Bangladesh?

There is no single answer; the right gateway depends on your vertical, ticket size and payout needs. Compare method coverage, approval rate per method, settlement timing and reconciliation quality rather than headline pricing.

How much does a payment gateway cost in Bangladesh?

Pricing is normally a percentage of transaction value plus per-transaction and payout costs, and varies by method and merchant category. Compare cost per successful order rather than per attempt.

Do I need to support both wallets and bank transfers?

In most cases yes. Wallets carry the majority of transactions by count while bank rails handle larger amounts, so supporting both widens the range of customers you can convert.

Can high-risk merchants get a gateway in Bangladesh?

Yes, but through providers that underwrite the category deliberately. Expect more documentation, possible reserves and closer monitoring than a standard ecommerce account.

Sources

• Bangladesh Bank: https://www.bb.org.bd/
• SSLCOMMERZ Developer documentation: https://developer.sslcommerz.com/