Skip to content

bKash payment gateway integration: what you need, how it works and what to watch

A customer is ready to pay. They press Pay with bKash, enter the OTP and PIN, the money leaves their account, and your website still says “payment pending”. The customer calls, angry, and your team spends an hour proving the payment happened. Payment integration is not about the button. It is about everything that happens after the button is pressed.

Building software4 min readBy Reoncore Labs

Short answer

To accept bKash on a website or app, a business applies for bKash's online payment gateway, usually with a valid trade licence, NID, a bank account and a live website with clear policies, and receives API credentials for testing and live use. Alternatively, an aggregator such as SSLCommerz offers bKash, cards and other methods through one integration. Either way the essentials are the same: confirm every payment with the provider server to server, protect the credentials, handle failures and refunds, and reconcile settlements.

01Two routes: direct bKash, or an aggregator

Customers can pay with
Direct bKash gateway
bKash
Aggregator (for example SSLCommerz, aamarPay, ShurjoPay)
bKash, other mobile wallets, cards and internet banking, depending on the provider
Integrations to build
Direct bKash gateway
One for each method you add
Aggregator (for example SSLCommerz, aamarPay, ShurjoPay)
One for all its methods
Fees
Direct bKash gateway
Agreed with bKash per business; no public rate card
Aggregator (for example SSLCommerz, aamarPay, ShurjoPay)
Set by the aggregator, often per payment method
Settlement
Direct bKash gateway
From bKash to your account
Aggregator (for example SSLCommerz, aamarPay, ShurjoPay)
From the aggregator to your bank account
Good for
Direct bKash gateway
Businesses whose customers mostly pay by bKash
Aggregator (for example SSLCommerz, aamarPay, ShurjoPay)
Businesses that need several payment methods

Fees and settlement times change and are often negotiated. Ask every provider for current rates and terms in writing before you choose.

02What you usually need

  • A registered business with a valid trade licence.
  • The owner's or authorised person's NID, and often a TIN.
  • A business bank account for settlements.
  • A live website or app with real products and prices.
  • Clear policy pages: refunds and returns, privacy, terms and conditions, and contact details.
  • HTTPS across the whole site. bKash's developer documentation requires a valid SSL certificate.

The exact documents vary by provider and type of business; your account manager confirms the list.

03How one online payment works

  1. 01The customer presses Pay with bKash at your checkout.
  2. 02Your server asks bKash's API to create a payment for that order and amount.
  3. 03The customer is taken to bKash's own page and enters their number, the OTP and their PIN. Your website never sees these.
  4. 04bKash sends the customer back to your site with a result.
  5. 05Your server asks bKash directly to complete and confirm the payment, and records the transaction ID.
  6. 06Only then is the order marked paid and the confirmation sent.

Step five matters most, and it is the step most often done wrong.

04Five rules that protect your money

  • Never mark an order paid because the customer's browser came back saying “success”. Confirm with the provider, server to server, every time.
  • Keep API keys and secrets on the server only. Never in the website's JavaScript, the app's code, a public repository or a chat.
  • Guard against double payments and double orders: treat each order's payment as one operation, even if the customer clicks twice or the network repeats a request.
  • Handle every outcome, success, failure, cancellation and timeout, with a clear message for the customer and a clear status in your system.
  • Log every payment attempt with the provider's transaction ID, for disputes and reconciliation.

05After launch: refunds and reconciliation

Taking the money is half the job. You also need:

  • A refund process: who may approve a refund, how it goes back through the gateway, and how the order and stock are updated.
  • Reconciliation: matching every settlement from the provider against paid orders, so missing or extra amounts are caught within days, not months.
  • Monitoring: an alert when payments start failing, because a broken checkout looks exactly like a slow sales day.

06A go-live checklist

  1. 01Test every outcome in the provider's sandbox: success, failure, cancellation, timeout, double click.
  2. 02Confirm the credentials are stored only on the server, and switched to the live ones correctly.
  3. 03Check that policy pages, prices and contact details are live and accurate.
  4. 04Make one small real payment and one refund, end to end.
  5. 05Set a daily or weekly reconciliation routine and a failure alert.
  6. 06Write down who to contact at the provider when something goes wrong.

Questions

How much does bKash charge for its payment gateway?

bKash does not publish a public rate card for its online payment gateway; merchant rates are agreed per business, depending on factors such as business type and volume. Ask for the rate and settlement terms in writing during onboarding.

Can I accept bKash without a trade licence?

For the online payment gateway, a valid trade licence is normally required. Very small sellers can look at bKash's options for small retailers, which have different requirements and limits.

Is SSLCommerz better than direct bKash?

Neither is better in general. An aggregator gives several payment methods through one integration; direct bKash can suit businesses whose customers mostly pay with bKash. Compare fees, settlement times, support and the methods your customers actually use.

Can a WooCommerce or Shopify site accept bKash?

Usually through a plugin or app from the gateway or an aggregator. Check that it comes from a trusted source, is actively maintained and confirms payments server to server.

How long does it take to go live?

Onboarding depends on the provider and on how complete your documents and website are. The technical integration and testing take from days to a few weeks, depending on your platform.

Last updated

Tell us what is not working.

Describe the problem in your own words. We will tell you honestly whether we can help, and how we would approach it.