Most “best payment gateway in Bangladesh” articles republish the same Top 10 list. Merchants need a different question: best for which operating profile — and which scoring criteria should decide it.
Why generic Top 10 lists fail operators
Fee tables help, but they hide the decisions that break projects: slow KYC, missing mobile wallet coverage for your audience, unclear settlement, weak refund tooling, chargeback handling, or docs that stop at “hit this endpoint.” A gateway that looks cheapest on MDR can be expensive in failed checkouts and support load. Security expectations (including PCI DSS for card data where applicable) belong in the same scorecard as pricing.
Use lists as inventory — then score against your profile. Public round-ups often recycle SSLCommerz, aamarPay, ShurjoPay, PortWallet and wallet merchant products; that inventory is useful only after you know which payment methods and API depth your ecommerce or SaaS flow requires. If you still need the rails map first, read payment gateway BD rails before ranking brands.
Scoring criteria that actually predict fit
| Criterion | What to verify | Why it matters |
|---|---|---|
| Onboarding | Document list, review timeline, category restrictions | Blocks launch more often than API complexity |
| MFS coverage | Which wallets are live for your MCC | Local conversion depends on familiar wallets |
| Cards / banking | 3DS behaviour, EMI, net banking stability | Higher tickets and B2B-adjacent flows |
| Settlement | T+N, cut-off times, statement format | Cashflow and finance reconciliation |
| Refunds & disputes | Partial refunds, wallet reversal rules | Support cost after go-live |
| Docs & sandbox | Signed callbacks, test projects, examples | Engineering time and production risk |
| Ops tooling | Search by order ID, export, alerts | Daily merchant operations |
Weight the criteria for your business. An education portal may prioritise settlement predictability and low dispute rate; a fashion store may prioritise wallet coverage and mobile checkout speed.
Profile: SME ecommerce
Needs: bKash/Nagad-first checkout, simple hosted page or plugin, predictable settlement, refund policy that support can execute.
Watch-outs: setup fees that dwarf early volume; plugins that confirm on redirect; missing partial refunds.
Evaluation tip: run a test purchase on mobile data, force one failure, and confirm the order system stays pending until the signed status arrives. Review payment method planning before promising every wallet on the homepage.
Profile: SaaS and digital services
Needs: API clarity, recurring or repeat-pay patterns where allowed, strong transaction search, webhook reliability.
Watch-outs: category bans on digital goods; weak idempotency guidance; settlements that are hard to map to subscription invoices.
Evaluation tip: ask how retries, duplicate callbacks, and cancelled invoices should be modelled. The integration guide outlines why browser success pages are never enough.
Profile: education and fee collection
Needs: high trust messaging, clear payer receipts, stable settlement for institutional finance, often preferential education pricing where offered.
Watch-outs: parent payers using different wallets than students; reconciliation across many small tickets; limited dispute tooling.
Evaluation tip: insist on exportable settlement files with payer references your registrar system already stores.
Profile: marketplaces and multi-seller platforms
Needs: operational design for multiple sellers, clear ownership of refunds, status visibility per order line, and a path toward split or payout logic if the model requires it.
Watch-outs: assuming split payments exist because international gateways advertise them; underestimating KYC for platform + sellers.
Evaluation tip: document who initiates refunds and who absorbs chargebacks before integration starts. Many Bangladesh projects need process design more than exotic APIs.
How to apply the matrix in one working session
- Write the profile in one paragraph. Audience, average ticket, top two methods, refund frequency.
- Score 3–5 shortlisted gateways on the criteria table with the same evidence standard (screenshots, docs quotes, sandbox results).
- Eliminate any option that fails a must-have (for example, no required wallet for your MCC).
- Pick the leader for a pilot, not a five-year exclusive — prove settlement and refunds on real traffic.
When the shortlist is ready, move to execution with the online payment gateway Bangladesh go-live checklist. To discuss fit without a public price list, contact the team with your profile paragraph attached.
FAQ
Is there a single best payment gateway in Bangladesh?
No. Fit depends on merchant category, methods, settlement needs, and technical model.
Should I choose on MDR alone?
No. Failed checkouts, refund labour, and delayed onboarding often cost more than a small MDR difference.
Do I need international gateways?
Only if cross-border cards or foreign settlement are real requirements. Most local ecommerce volume still concentrates on BDT and local MFS.
