Mobile financial services are part of the payment mix for most consumer-facing businesses in Bangladesh. A customer expects to pay from a wallet, a merchant expects the money to arrive in the right account, and finance expects the transaction to reconcile without a spreadsheet. The integration that connects those expectations is not a single API call.
This guide explains the cost structure of an MFS integration in Bangladesh. It does not quote provider fees or fixed development prices, because both are commercial terms that change by volume, risk profile and negotiation. Instead, it gives you the lines to price with your own quotations.
What the integration actually includes
- Collections. Requesting a payment, presenting a confirmation screen, receiving the result and handling a timeout.
- Payouts. Sending money to a customer, supplier or agent, with limits and approval rules.
- Refunds. Returning a payment to the original wallet and linking it to the original sale.
- Settlement. Matching the provider's settlement file to your ledger and bank account.
- Reconciliation. Explaining every difference between the order, the payment and the settlement.
- Onboarding. Merchant or agent registration, document collection and limit configuration.
- Reporting. Daily, weekly and monthly views by channel, branch, provider and status.
- Support. A process for pending, failed and disputed transactions after launch.
The nine cost lines
1. Provider commercial terms
Merchant discount rate, payout fee, settlement timing and minimum volume are set by the provider and negotiated. They are not a software cost, but they belong in the total cost of ownership. Ask for the full schedule in writing, including what changes at higher volume and who bears the cost of a reversal.
2. Integration scope
A hosted checkout page is cheaper than a direct API integration. A collection-only flow is cheaper than collections plus payouts plus refunds. A multi-provider abstraction costs more than a single connection but reduces the cost of adding a second provider later. Decide which channels are in the first release and which are explicitly out of scope.
3. Security and identity
API keys, IP allowlists, mutual TLS, request signing and secret rotation all need design and testing. Staff who trigger payouts need strong authentication and role separation. If card data is ever in scope, PCI DSS requirements apply even when a provider hosts the payment page; confirm the boundary in writing.
4. Reconciliation and settlement
The provider's settlement file is the source of truth for cash. Your system must import it, match it to transactions, explain fees and post the net amount to the ledger. This is often the largest hidden cost because it touches finance process, not only code.
5. Failure handling
Timeouts, duplicate callbacks, pending transactions and partial failures need a state machine and an exception queue. A payment that is neither successful nor failed is the most expensive state to leave unresolved.
6. Compliance and records
Keep transaction records, consent, settlement evidence and dispute notes for the period your legal and finance advisers require. Data protection duties apply to customer information, and sector rules may apply depending on the business. Confirm retention and access rules before launch.
7. Provider certification and testing
Providers often require a sandbox test, a review of the callback endpoint and a production verification. Budget time for the provider's process, not only your own QA. A successful sandbox test does not prove that settlement and refunds work.
8. Operations and monitoring
Someone must watch success rates, pending transactions and settlement differences every day. That is an operating cost, whether it is an internal person or a managed service. Include the alerting, runbook and on-call path in the budget.
9. Change and multi-provider support
Provider APIs change. Commercial terms change. A second provider may be added for resilience or coverage. A clean abstraction layer costs more at the start and less at each subsequent change.
A cost model you can fill in
- One-time cost = discovery and process design + integration build + security setup + reconciliation build + provider certification + testing + training + project management.
- Monthly cost = provider fees (separate line) + hosting and infrastructure + monitoring + support + internal operations + expected change hours.
- Monthly benefit = manual reconciliation hours saved × loaded hourly cost + failed-payment recovery + reduced cash leakage + faster settlement where it releases working capital.
- Payback months = one-time cost ÷ monthly net benefit.
Do not put provider fees in the same line as development cost. They behave differently: development is mostly fixed, while fees scale with volume.
Calculator worksheet
- Transactions per month, split by collection, payout and refund.
- Average ticket size and peak transactions per hour.
- Current manual hours spent on reconciliation and dispute handling.
- Loaded hourly cost of finance and support staff.
- Quoted integration cost for each provider and each flow.
- Monthly platform, hosting and support quotation.
- Expected change requests in the first year.
- Provider fee schedule, settlement timing and reversal terms.
Questions to ask a vendor
- Have you integrated this provider before, and can you show the reconciliation design, not only the payment screen?
- How do you handle a timeout where the customer is debited but the order is not confirmed?
- Who owns the settlement file mapping when the provider changes its format?
- How are secrets stored and rotated, and who can trigger a payout?
- What is in the support contract after go-live, and what is billed as a change?
90-day plan
- Days 1–15: confirm provider terms, volumes and the exact flows in scope.
- Days 16–30: design the payment state machine and the settlement mapping.
- Days 31–50: build the collection flow and the callback handling in sandbox.
- Days 51–65: add refunds, payout controls and the reconciliation report.
- Days 66–80: run provider certification and a parallel reconciliation with live-like data.
- Days 81–90: launch to a small group, review success and pending rates, then widen.
Metrics
- Payment success rate by provider and channel.
- Pending transactions older than the provider's stated window.
- Unreconciled settlement amount and age.
- Refund completion time.
- Manual touches per hundred transactions.
Where this fits in our work
MFS integration is a commerce and payments problem before it is a coding problem. Our Commerce Systems division designs the collection, payout and reconciliation flow around your operations; the pricing page explains how scope is set. For the longer view of the same topic, read mobile financial services integration, year by year.
Sources
- Bangladesh Bank, Mobile Financial Services data, accessed 17 November 2026.
- bKash Developer Portal, accessed 17 November 2026.
- PCI Security Standards Council, accessed 17 November 2026.
- The Daily Star, Bangladesh Bank issues 17-point cybersecurity directive, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.