Short answer: Sending money to Bangladesh from the UK, the Gulf, the US, Australia or Canada means meeting your own regulator's rules at home and working through partners that are authorised in Bangladesh to pay out. Bangladesh Bank regulates the receiving side, and the government runs an incentive for remittances that arrive through formal channels. For the operator, the corridor succeeds or fails on four things the platform must handle well: payout rails, name screening, partner reconciliation and clear customer messaging.
RemitSo is white-label remittance software for licensed money transfer operators. We are a technology company, not a remitter, and nothing here is legal advice.
Who this guide is for
This is for licensed operators who already send, or plan to send, to Bangladesh: a UK payment institution serving the British-Bangladeshi community, a Gulf exchange house serving migrant workers, or an MSB in the US, Australia or Canada. Your licence and your home regulator stay the same. What changes is the receiving side: who pays the recipient, how, and how you prove each payment happened.
The receiving side, in brief
Inward remittances to Bangladesh are paid through banks and other institutions authorised by Bangladesh Bank, which publishes its foreign exchange rules as circulars. Anti-money laundering in Bangladesh is overseen by the Bangladesh Financial Intelligence Unit. As a foreign operator, you usually reach the market through a contract with a Bangladeshi bank or a payout aggregator, and that partner applies the local rules to each payout.
The practical consequence: your partner's requirements become your platform's requirements. If the partner needs a field, a document or a reference, your system has to capture it before the transfer leaves.
Payout rails: bank, wallet and cash
Recipients in Bangladesh expect choice. Most operators offer some mix of:
- Bank deposit into the recipient's account, which needs accurate bank and branch details.
- Mobile financial services wallets, which are widely used in Bangladesh. Wallet payouts are usually reached through a partner bank or aggregator, so ask your partner which wallets it covers.
- Cash pickup at a partner bank branch or agent, where the recipient proves identity at the counter.
What that means for your platform:
- All three rails, through your partners. On RemitSo, bank deposit, mobile wallet and cash pickup are supported. You hold the contract with each payout partner, and we connect and test it. Which Bangladeshi partners and wallets are available depends on the partners you contract with.
- Fields set per channel. Payout channels, banks and onboarding fields are set up by configuration, so the recipient details each rail needs can be set for the corridor, not hard-coded.
- Payouts that can't be redirected. Once a payout is approved, nobody can change it.
Name screening: the corridor's biggest operational load
Bangladeshi names often share a small set of common words, appear in several transliterations, and may include honorifics or initials. That's a problem in two places: sanctions screening at home and name checks at the payout partner.
On RemitSo:
- Eight sanctions lists, kept up to date. Every sender, recipient and staff member is screened, and everyone is re-screened when the lists change. A possible match holds the transfer until an officer on your team rules on it, and the reason is kept.
- Built for common names. Matching is tuned to keep possible matches on short and common names to a number your officers can genuinely review.
- Fewer false failures before payout. Beneficiary name checks tolerate common presentation differences, so a valid payout isn't refused over formatting, while a genuine mismatch still stops it.
Screening rules and the lists you rely on are your compliance officer's call. The platform's job is to keep the queue to what genuinely needs a person.
Reconciling payout partners
On a high-volume corridor, a small reconciliation gap grows quickly. Three questions should be answerable at any time: what you owe each partner, what each partner actually paid, and which transfers are still with a partner.
On RemitSo:
- Every movement booked. A double-entry ledger records every payment, payout, refund, fee and FX movement as it happens. The amount owed to payout partners sits in its own account, and partner fees are tracked separately, so you see real margin on the corridor.
- Balances you can trace. Click any balance to see the transactions behind it. Entries are never edited; mistakes are reversed, and both stay visible.
- Bulk updates, previewed. When a partner sends a file of payout outcomes, you can upload the file with each transfer's new status, and every row shows what it would do, or why it's refused, before anything changes.
The remittance incentive: inform, don't promise
The Government of Bangladesh pays an incentive on eligible remittances that arrive through formal channels. The receiving bank pays it to the recipient in Bangladesh under rules Bangladesh Bank publishes in its circulars. The rate, who is eligible and what's excluded can change, so read the current circular rather than relying on a figure you saw last year.
For an operator, the incentive is a marketing point and a compliance risk at the same time:
- Tell customers it exists; let the bank confirm it. Your app and campaigns can point out that formal remittances may qualify. Avoid quoting a rate or promising an amount you don't pay.
- Keep your own pricing separate. Your exchange rate and fee are yours. The incentive is paid in Bangladesh, by the receiving bank.
- Capture what partners need. If a partner needs the transfer's purpose or the sender's relationship to the recipient, collect it at checkout.
Rates and fees on a competitive corridor
Bangladesh is a price-sensitive corridor, and customers compare. On RemitSo, you can change every rate in one sitting, give larger transfers a better rate tier by tier, give chosen customer groups their own rate, and set fees per corridor with a review reminder. An optional live rate feed applies your margin to market rates, and an optional Competitor Analysis add-on shows your price beside competitors', fees included. Every rate change records who made it, when, and what it was before.
Your home regulator still applies
The receiving side is only half the corridor. Your licence, your KYC, your monitoring and your reports are set by your home regulator. Our guides cover the UK, Australia, Canada, the US and the UAE.
On RemitSo, each operator runs its own instance in its own AWS account, in the AWS region it chooses. AWS bills the operator directly, and nothing is shared with another operator. RemitSo is ISO 27001:2022 certified, with clear audit trails, user access logs and exportable compliance reports.
What we've learned on this corridor
Two lessons from operators on our platform, anonymised:
- Every payout must carry the partner's reference. When a partner later reports a payout as paid or failed, the update has to land on the right transfer. Make sure each payout records the partner's own reference, and ask any vendor how partner status updates are matched to transfers.
- Honorifics can fail good payouts. A recipient entered with or without "Mr" or "Mrs" can fail a strict name check even when the name is right. Agree with each partner how names are compared, so presentation differences don't refuse valid payouts and real mismatches still stop.
Checklist: what the platform should handle on the Bangladesh corridor
| Area | What the platform should handle and evidence |
|---|---|
| Payout rails | Bank deposit, mobile wallet and cash pickup through your contracted partners |
| Recipient data | The fields each rail and partner requires, captured before the transfer leaves |
| Name screening | Lists screened, possible matches held, each ruling and its reason |
| Name checks | Checks that tolerate presentation differences, not real mismatches |
| Partner reconciliation | What you owe each partner, what each partner paid, and the partner reference on every payout |
| Incentive messaging | Accurate, non-promissory wording; your pricing kept separate |
| Pricing | Rates and fees per corridor, with change history |
| Records | Audit trails, user access logs and exportable compliance reports |
Frequently asked questions
Does RemitSo pay out in Bangladesh itself?
No. RemitSo is the technology. You contract with payout partners authorised in Bangladesh, and RemitSo connects and tests them.
Can recipients receive into mobile wallets?
RemitSo supports mobile wallet payouts. Which Bangladeshi wallets you can reach depends on the payout partners you contract with, so confirm coverage with them.
Does RemitSo calculate or pay the remittance incentive?
No. The incentive is paid in Bangladesh by the receiving bank under Bangladesh Bank's rules. Your pricing on RemitSo stays your own.
How do you handle common names in sanctions screening?
Eight sanctions lists are kept up to date, and a possible match holds the transfer until an officer rules on it. Matching is tuned so short and common names produce a queue your officers can genuinely review.
Where is our customer data held?
In your own instance, in your own AWS account, in the AWS region you choose. AWS bills you directly, and nothing is shared with another operator.
For more, see our KYC, AML and sanctions tools, the admin panel features, how to choose and run payout partners and high-risk corridors and the rules that keep them safe. Book a demo to see a transfer to Bangladesh screened, paid out and reconciled.
Rules change, and Bangladesh Bank's circulars and your home regulator's pages are the authority. Treat this as a guide to what your platform should handle, not as legal advice. Check with your compliance adviser.