Accepting bKash, Nagad and Cards: A Practical Guide

You can build a beautiful online store and still lose most of your customers at the final step — because the payment method they trust is not on the checkout page.

In Bangladesh that method is usually a mobile wallet. bKash, Nagad and Rocket are not alternatives to cards here; for a great many shoppers they are the payment system. Getting them working properly, alongside cards for the customers who prefer them, is what separates a store that takes orders from a store that merely displays products.

TL;DR

• Offer mobile wallets and cards. Choosing one loses you customers from the other group.
• Cash on delivery still converts, but it carries return risk — price that in before you offer it.
• Every gateway needs live business documents. Start that paperwork early; it is usually the long pole.
• Test the failure paths, not just the happy path. Most bad checkout experiences are half-finished payments.

What You Can Actually Offer

One Aggregator, or Direct Integrations?

You have two routes. An aggregator gives you every method through a single integration and a single dashboard. Direct integration with each provider means more setup work but a tighter, faster checkout and usually better rates at volume.

For most stores launching their first storefront, an aggregator is the pragmatic choice: one set of paperwork, one integration to test, and you are live sooner. Revisit the decision once monthly volume makes the rate difference meaningful.

Get the Paperwork Moving First

This is the step that delays launches, almost every time. Whichever route you take, expect to provide a trade licence, TIN, a bank account in the business name, and NID for the authorised signatory. Some providers also want to see the live site with visible refund and delivery policies before they approve.

Start it in week one, not the week before launch.

Designing a Checkout People Finish

The technical integration is only half the job. The rest is not giving anyone a reason to stop.

1. Show the methods on the product page, not only at checkout. Seeing a familiar logo early removes doubt before it forms.
2. Do not force account creation. Guest checkout, with an optional account offered after the order.
3. Ask for as little as the order needs. Every extra field costs you completions.
4. State delivery cost and timing before the payment step. Surprises on the last screen are the most common abandonment trigger there is.
5. Confirm on-screen and by SMS. A confirmation that arrives only by email will be missed.

Test on a real mid-range Android phone over mobile data, not on a desktop over office wi-fi. That is the actual condition most of your customers are buying in.

The Part Most Stores Skip

Payments fail. The wallet balance is short, the OTP times out, the network drops halfway through. What matters is what your store does next.

• The cart must survive a failed payment — never make anyone rebuild the order.
• The error must say what happened in plain language, and offer another method.
• Nothing ships on an initiated-but-unconfirmed payment. Reconcile against the gateway's own record, never against the browser redirect alone.
• A duplicate submission must not create a duplicate order.

Each of these is a five-minute test before launch, and a very expensive lesson afterwards.

After Launch

Reconcile settlements weekly against your own order records for the first couple of months. Gateway fees, refunds and settlement timing all have to line up with your accounting, and small mismatches are far easier to trace in week one than in month six.

See how we build online stores, or talk to us about yours.