Local Bank Transfers in Bangladesh: BEFTN, NPSB and Merchant Collections

What local bank transfers is

Bank transfers in Bangladesh move over BEFTN for batch clearing and NPSB for interbank transfers, with dedicated merchant collection accounts held at local banks such as BRAC Bank, Dutch-Bangla Bank and Eastern Bank.

Bangladesh runs on mobile financial services. A customer who has never held a card will still have a wallet balance topped up at an agent point, and that wallet is the default way they pay online.

How the flow works

1. The merchant issues collection instructions with a unique reference tied to the order.
2. The customer initiates a transfer from their own bank or internet banking channel.
3. The credit lands in the collection account and is matched to the reference.
4. The matched transaction is confirmed to the merchant and enters the settlement batch.

Timing and confirmation

Bank rails clear on a batch cycle rather than instantly, so confirmation may take longer than a wallet payment. Communicate expected timing at checkout to prevent duplicate payments.

Average ticket sizes are small and frequent, so approval rate and confirmation speed matter far more than the headline fee.

Limits and ticket sizes

There is far more headroom than wallets provide, which is what makes bank rails the right destination for high-value orders and business customers.

This is why most Bangladeshi checkouts present a wallet option and a bank option side by side rather than choosing one. Coverage for the full Bangladesh method set is described on the Bangladesh Payment Gateway page.

Reconciliation

Every local bank transfers transaction should carry three identifiers in your ledger: your order reference, the gateway reference and the rail reference returned by local bank transfers. With all three stored, a settlement statement can be matched line by line, refunds can be traced, and disputes can be evidenced without manual investigation.

Settlement for Bangladesh volume runs on T+0 for wallet volume and T+1 for bank rails. Build your daily close around that window rather than assuming same-day equivalence.

Common integration mistakes

• Reusing references across orders, which makes automatic matching impossible.
• Not handling partial or over-payments, which are common on manual transfers.
• Failing to expire stale collection instructions, leaving unmatched credits in suspense.
• Treating an unmatched credit as revenue before it is reconciled.

Merchant benefits

• local bank transfers acceptance through the same API as every other Bangladesh method
• Signed webhooks with idempotency and replay safety
• Line-level reconciliation data for finance teams
• Settlement on T+0 for wallet volume and T+1 for bank rails
• Fallback routing when an upstream connection degrades

Related guides and solutions

• Bangladesh Payment Gateway
• High Risk Payment Solution Bangladesh
• bKash Payment Gateway
• Nagad Payment Gateway
• Solutions overview
• Cross-Border Payment Solutions
• Payment Infrastructure
• High-Risk Merchant Payment Processing
• Countries hub

Talk to our team

If you are evaluating acceptance in Bangladesh, the fastest way to get a useful answer is to share your vertical, expected monthly volume and required payout frequency. Our team can confirm which rails are available to your business, what documentation underwriting will ask for, and how quickly you can go live. Start with merchant onboarding or contact us directly.

Frequently asked questions

When should I use bank transfers instead of wallets?

When ticket sizes exceed comfortable wallet limits, or when the customer is a business rather than a consumer.

How are transfers matched to orders?

Through a unique reference issued per order and matched against the credit in the collection account, with a manual queue for exceptions.

How long do bank collections take to confirm?

Longer than wallet payments, because clearing runs on a batch cycle rather than in real time.