How to add bKash payment to your website: 4 ways compared

If you sell online in Bangladesh, bKash is not optional. It is how a large share of customers prefer to pay before delivery, and every bKash payment is one fewer cash-on-delivery parcel that might come back. The question is not whether to accept bKash on your website but how — and there are four quite different answers, from a developer project to a checkbox.

This guide compares them without hype. Where fees are involved we tell you where to look rather than quote a number that will be out of date next quarter.

First, what a "bKash payment gateway" actually is

When a customer pays with bKash on a website, three things happen: the site asks bKash to start a payment, the customer approves it in the bKash app or with their PIN, and bKash tells the site the payment succeeded so the order can be confirmed. The "gateway" is whatever piece of software does that conversation.

bKash provides the underlying service — the bKash Payment Gateway, used through its Checkout API — to approved merchants. Everything else in this guide is a different way of connecting your website to it.

You will need a bKash merchant account in every option except one: aggregator gateways, which use their own bKash relationship. That distinction matters for who holds your money, so keep it in mind as you read.

Option 1: Your own merchant account + bKash Checkout API

What it is. bKash gives approved merchants API credentials. Your developer integrates the Checkout flow into your site: create payment, redirect or pop up the bKash screen, execute the payment on callback, verify it, mark the order paid.

What it needs. A bKash merchant account with API access, a developer who has done a payment integration before, a server to handle the callbacks securely, and time to get through bKash's sandbox testing. Plan for maintenance too — credentials and API versions change.

Who it suits. Businesses with a custom-built website and in-house or contracted developers, who want money to land directly in their own merchant account and are willing to own the integration.

Watch out for. Handling the callback badly is the classic mistake — marking an order paid before verifying the payment, or losing the order when the customer closes the app halfway. This is where real money goes missing.

Option 2: An aggregator gateway (SSLCommerz, AamarPay, ShurjoPay and others)

What it is. A payment gateway company that has already integrated bKash — along with cards, Nagad, Rocket and bank transfers — and offers you one integration for all of them. Your site talks to the aggregator; the aggregator talks to bKash.

What it needs. A merchant agreement with the aggregator (they do their own KYC), and an integration on your site. Most provide plugins for WooCommerce and SDKs for custom sites, so the developer effort is lower than Option 1. Fees are a percentage per transaction plus, in some cases, setup or annual charges — check the current pricing pages and read the settlement terms carefully.

Who it suits. Stores that want many payment methods at once, or that sell higher-value items where card payments matter.

Watch out for. Your money goes to the aggregator first and is settled to you on their schedule — daily, weekly, or after a hold period. For a cash-flow-sensitive small business, the settlement cycle can matter more than the fee.

Option 3: A WooCommerce or Shopify plugin

What it is. If your store runs on WordPress + WooCommerce, there are third-party plugins that connect to bKash's Checkout API using your own merchant credentials, and aggregator plugins that connect through Option 2. Shopify does not have a native bKash method for Bangladesh; you add a third-party gateway app.

What it needs. The plugin licence (many are paid), your bKash merchant API credentials or an aggregator account, and someone to keep WordPress, WooCommerce and the plugin updated together — a plugin that breaks after a WooCommerce update takes bKash off your checkout until it is fixed.

Who it suits. Existing WooCommerce stores with someone responsible for maintenance.

Watch out for. Abandoned plugins. Check when it was last updated and whether the developer answers support requests before you put your checkout on it. We cover the wider trade-offs in Eazifiy vs WooCommerce and Eazifiy vs Shopify.

Option 4: A platform with bKash built in

What it is. A hosted ecommerce platform built for Bangladesh, where bKash checkout is part of the product rather than an add-on. On Eazifiy, you connect your own bKash merchant account under Payment Methods in the admin panel, and bKash appears at checkout — no plugin, no developer, no separate gateway contract.

What it needs. A bKash merchant account (yours) and your platform subscription. That is the whole list.

Who it suits. Merchants who want to sell rather than maintain software, and who want the payment to land in their own bKash account directly. On Eazifiy the payment never passes through the platform; it goes from the customer to your merchant account, and the store only records the order and its payment status.

What comes with it. Because bKash is part of the checkout rather than bolted on, it can do things a plugin cannot:

• Advance payment on cash-on-delivery orders — require a partial bKash payment (the delivery charge, or a fixed amount) to confirm a COD order, and collect the rest at the door. This is the single most effective fake-order filter there is.
• A bKash extra discount — an additional discount shown at checkout when the customer pays the full amount with bKash, calculated server-side before charging so the amounts always match.
• Delivery fee collected in advance, with the product price still on COD.

The details are on the bKash payment page.

Side by side

	Own Checkout API	Aggregator	WooCommerce / Shopify plugin	Built-in platform (Eazifiy)
Developer needed	Yes	Some	Some	No
Your own bKash merchant account	Required	Not needed (theirs)	Required (or aggregator)	Required
Where the money lands	Your account	Aggregator, then settled to you	Your account (or aggregator)	Your account, directly
Other methods (cards, Nagad)	Each one separately	Included	Via plugins	COD built in
Ongoing maintenance	You	Low	You (plugin + WordPress updates)	None
Advance payment on COD	Build it	Build it	Depends on plugin	Built in

How to get a bKash merchant account

Every option except the aggregator needs one, so start here regardless of which route you take:

1. Apply through bKash's merchant onboarding. bKash asks for business identity documents — typically a trade licence and the owner's NID, plus the business address and the bKash-registered number. Check bKash's current requirements; they do change.
2. Wait for approval. It is not instant. Apply before you need it, not the week you launch.
3. Ask for API/Checkout access if you are going the direct or plugin route. A merchant account for taking payments by number is not the same as one with gateway API access.
4. Test in sandbox before going live if you are integrating yourself. If you are on a platform, connect the credentials and place a small real order.

Which option should you choose?

• You have a developer and a custom site: Option 1, or Option 2 if you also want cards and Nagad in one contract.
• You run WooCommerce already: Option 3, but budget for the plugin licence and for keeping it updated.
• You want the store live this week and do not want to maintain software: Option 4. Connect your merchant account and turn on advance payment for COD orders on day one.

Whichever you pick, do not launch with COD only "for now." The store that takes bKash from day one has fewer returns, faster cash and customers who come back — and it is the difference between a Facebook page with a website and an actual online business.

Frequently asked questions

Does the money go through the platform or the gateway? Aggregators receive it and settle to you. With your own merchant account — whether through the Checkout API, a plugin using your credentials, or a platform like Eazifiy — it goes to your bKash merchant account directly.

Can I take bKash without a merchant account? Only through an aggregator, which uses its own. Sending customers a personal bKash number and asking for a screenshot is not a payment gateway — it does not confirm the order, and it does not scale.

Can I ask for a partial bKash payment on cash-on-delivery orders? Yes, if your checkout supports it. On Eazifiy it is a setting called Advance Payment; on other routes it is something to build or look for in the plugin.

Does bKash work with my own domain? Yes. The payment is tied to your merchant account, not your domain name. On Eazifiy you can start on a free yourname.eazifiy.com address and connect your own domain later without touching the bKash setup.

Want to see how it looks in practice? Every Eazifiy plan includes bKash and cash-on-delivery checkout, and the first 2 months are ৳200 a month — see pricing.