All articles
Web & appsSample content

Adding bKash and Nagad payments to your website: what to plan first

Mobile wallet payments can make checkout easier for local customers, but only if the order flow around them is designed carefully.

Abstract monochrome grid of rounded cards with one highlighted

Sample content — replace before launch. This article is a sample written to preview the reading layout. It will be replaced or rewritten by Shameem before publishing.

For many customers in Bangladesh, paying with a mobile wallet feels more natural than entering card details. Adding bKash or Nagad to a website is therefore a common request. The integration itself is only one part of the job; the order flow around it matters just as much.

Choose the right integration path

You can integrate directly with each provider's merchant API, or use a payment gateway that bundles several methods together. Direct integration gives more control, while a gateway can be quicker to launch with. Check the current merchant requirements and fees with each provider before you decide.

Design the order states

Every order should move through clear states, and your system should never mark an order as paid based only on what the browser reports. Confirm each payment on the server with the provider before releasing the order.

  • Pending: order created, payment not yet confirmed
  • Paid: payment verified on the server
  • Failed or cancelled: customer can retry
  • Refunded: recorded with a reason and a date

Plan for failed and duplicate payments

Networks drop, customers press the button twice, and confirmation messages sometimes arrive late. Make your payment handling safe to run more than once, and give customers a clear way to check their order status. A short help message with a support contact prevents most panic.

Keep reading