How to Accept bKash and Nagad Payments: A Platform's Guide to Bangladesh Payment Integration

If you are entering Bangladesh, bKash payment gateway integration is the first technical decision that determines whether your checkout converts or stalls. This is a mobile-money market before it is a card market. Getting acceptance right means connecting to the wallets people already use, not asking them to adapt to a card-first flow built for another region. Here is how the integration works and what it takes to do it well.

TL;DR: What You'll Learn

• Bangladesh runs on mobile financial services (MFS), with MFS account numbers reaching 239.3 million by January 2025 according to the Bangladesh Bank, so wallet acceptance is not optional.
• bKash and Nagad are the two wallets any platform must support to reach Bangladeshi buyers at scale.
• A card-first checkout fails here because over 90 percent of e-commerce shoppers still prefer cash on delivery and card penetration is thin.
• bKash payment gateway integration runs on a tokenized checkout model that keeps the customer inside your flow, with no redirect drop-off.
• Building each wallet and card connection separately is slow and costly. A single unified API consolidates bKash, Nagad, cards, and bank transfers into one integration.
• Compliance is a day-one requirement. Work with a partner that is already PCI DSS and ISO 27001 certified rather than certifying each rail yourself.

Why Bangladesh Is a Market Worth Getting Payments Right

Bangladesh's e-commerce market reached close to 7.5 billion US dollars in 2024, up from roughly 6.9 billion the year before, according to reporting in The Daily Star citing e-CAB figures. Online sales still make up only 3 to 5 percent of total retail, which tells you the runway is enormous and mostly untapped.

The demographic behind that runway is young, mobile-first, and already transacting digitally at scale. Bangladesh processed about 8.61 percent of the world's daily mobile money transactions in 2024, according to the GSMA State of the Industry report cited by The Business Standard, despite the country holding a much smaller share of the global population. For a platform, that means the buyers are here, and the payment habit is formed. The only question is whether your checkout speaks their language.

The Payment Methods You Need to Accept in Bangladesh

The wallet layer is where most of the volume sits. As of January 2025, MFS accounts in Bangladesh stood at 239.3 million, a rise of more than 32 percent in transaction value year on year, according to Bangladesh Bank data. These are accounts rather than unique people, since many users hold more than one, but the direction is unmistakable.

To accept payments from Bangladeshi customers, you need coverage across four channels:

1. bKash, the dominant wallet, with close to one million businesses already accepting it as a payment method.
2. Nagad, the significant second wallet, which any serious checkout should support alongside bKash.
3. Cards, including Visa, Mastercard, and UnionPay, for the banked urban segment and international buyers.
4. Bank transfers over BEFTN, the interbank settlement network, for higher-value and business payments.

A checkout that offers only one or two of these leaves conversions on the table. The goal of an online payment gateway in Bangladesh is to present every method a customer might reach for, without forcing them to leave your page.

Why a Card-First Checkout Fails in Bangladesh

Most global payment stacks lead with card entry. In Bangladesh, that is a design mistake. The U.S. International Trade Administration reports that over 90 percent of e-commerce users still prefer cash on delivery, a preference rooted in concerns about product quality and online payment trust rather than a lack of digital options.

Card-based e-commerce is growing, with card transactions reaching about 20.35 billion taka in February 2025, up 23.6 percent year on year, per The Daily Star, but it is growing from a small base. If your checkout treats cards as the primary rail and wallets as an afterthought, you are building for a fraction of the market. The winning pattern is the reverse: lead with wallet acceptance, present cards as a secondary option, and give merchants a clean prepaid alternative to cash on delivery so they can cut the return rates that come with it.

Expert Insight: Why Most Businesses Get This Wrong

Teams entering Bangladesh often assume the payment challenge is adding bKash as a button. The real challenge is conversion at the moment of payment. A redirect-based flow that bounces the customer to a separate wallet page loses a meaningful share of buyers who never come back to confirm. The platforms that win here treat the wallet handoff as a checkout-design problem, not a plumbing problem. Keep the customer inside your flow, confirm in real time, and you recover sales that a redirect quietly leaks.

How bKash Payment Gateway Integration Works

bKash payment gateway integration runs on a tokenized checkout model. Instead of exposing raw wallet credentials, the integration exchanges a secure token that authorizes the payment and confirms it back to your platform. The customer authenticates the transaction on their side, and your system receives a clear success or failure response to act on.

The technical steps are straightforward when the groundwork is in place:

1. Register the merchant and obtain API credentials for the acquiring environment.
2. Call the create-payment endpoint to initiate a transaction and receive a payment token.
3. Let the customer authorize the payment through their wallet.
4. Execute and confirm the payment, then reconcile the response against your order.

The detail that separates a good integration from a frustrating one is redirect behavior. A zero-redirect API keeps the entire exchange inside your checkout, which protects conversion. This is why we built our payment collection API around a no-redirect flow, so the customer never leaves your page to complete a wallet payment.

Adding Nagad and Bank Transfers to Your Checkout

Supporting bKash alone is not full coverage. Total MFS transactions reached 678.63 million in October 2025, worth about 1.58 trillion taka, according to Bangladesh Bank data reported by The Financial Express, and that volume is spread across more than one provider. Nagad carries a large share of it, and a checkout that ignores Nagad ignores real buyers.

The same logic applies to bank transfers. For business-to-business payments, higher-value orders, and customers who prefer moving money directly from a bank account, BEFTN rails matter. The practical target is a checkout that can accept bKash and Nagad payments, card networks, and bank transfers through one consistent interface, so you are not maintaining a separate codebase for each method. For e-commerce operators specifically, that breadth is what lifts completion rates, which is why we map these rails into our e-commerce payment solutions.

One Unified API or Several Direct Integrations

Here is the decision that shapes your cost and timeline. You can integrate directly with each wallet, each card network, and the bank rails one at a time, or you can connect once to a unified API that consolidates all of them.

Direct integration means separate onboarding, separate credentials, separate reconciliation logic, and separate maintenance for every rail. Each provider updates its API on its own schedule, and each change becomes your engineering problem. Multiply that across bKash, Nagad, cards, and BEFTN, and a project that looked simple becomes a standing burden on your team.

A single integration removes that fragmentation. One connection covers the full set of methods, one reconciliation model handles every transaction, and one partner absorbs the maintenance as rails evolve. For a platform that plans to operate in more than one frontier market, the compounding value is larger still, because the same integration extends beyond Bangladesh. That is the model we built Simpaisa on: connect once, accept everything, and go live without complexity.

Compliance and Security in Bangladesh Payment Integration

Payment integration is a trust exercise before it is a technical one. Bangladesh Bank sets the framework for mobile financial services in the country, and any acquiring partner you work with sits inside that regulated environment. Your exposure is directly tied to the security posture of the infrastructure you build on.

Two certifications carry the weight here. PCI DSS governs how card data is handled, and ISO 27001 governs information security management end to end. Achieving either independently for each market you enter is slow and expensive. Building on infrastructure that is already PCI DSS and ISO 27001 certified, specifically PCI DSS v4.0.1 and ISO 27001:2022, removes that burden and gives your enterprise and platform customers the assurance they expect from day one. We operate under regulated partnerships and hold both certifications, so compliance is handled at the infrastructure level rather than left to each merchant.

How Simpaisa Handles bKash and Nagad Acquiring

We connect your platform to bKash and Nagad, alongside Visa, Mastercard, and UnionPay cards and bank transfer rails, through one unified API. The integration uses a zero-redirect flow, so customers authorize and confirm payments without ever leaving your checkout. Pricing is transparent, with no hidden fees layered on top.

The same integration that covers acquiring in Bangladesh extends across the frontier markets we serve, so a platform scaling from Bangladesh into neighbouring markets does not rebuild its payment stack each time. You get local rail coverage, real-time confirmation, and compliance handled at the infrastructure level, which is what turns a payment integration from a recurring engineering cost into a solved problem.

Conclusion

Three things decide whether your Bangladesh launch converts. First, lead with wallets, because bKash and Nagad are where the volume lives and a card-first checkout is built for the wrong buyer. Second, protect conversion at the payment step by keeping the customer inside your flow with a zero-redirect integration. Third, choose a single unified API over a stack of direct integrations, so your team ships faster and maintains less.

Bangladesh's digital payment market is deep, growing, and ready for platforms that respect how people pay. If you are planning your integration, talk to our payments team, and we will map the fastest route to accepting bKash, Nagad, cards, and bank transfers on your checkout.

Frequently Asked Questions

How do I accept bKash payments on my website or app?

Connect through a payment gateway that supports bKash tokenized checkout, so payments authorize and confirm inside your flow. A unified API lets you add Nagad, cards, and bank transfers from the same integration.

Is bKash payment gateway integration different from adding a card gateway?

Yes. bKash uses a wallet authorization and tokenized checkout model rather than card entry, and the customer confirms on their wallet. A good integration keeps this exchange redirect-free to protect conversion.

Do I need to support Nagad as well as bKash?

For full market coverage, yes. Nagad carries a significant share of Bangladesh's MFS volume, and supporting both wallets captures buyers a bKash-only checkout would miss.

Why is cash on delivery still so common in Bangladesh e-commerce?

It stems from concerns about product quality and online payment trust, with over 90 percent of shoppers still preferring it. Offering a clean prepaid wallet option is how merchants shift buyers away from COD.

Can one integration cover Bangladesh and other frontier markets?

Yes. A unified API consolidates local rails across markets, so a platform can extend from Bangladesh into neighbouring countries without rebuilding its payment stack.