Nagad Payment Guide for Merchants: Flows, Timing and Reconciliation

What Nagad is

Nagad is a mobile financial service operating under the Bangladesh Post Office, widely used for peer transfers, bill payments and online merchant purchases. For merchants it is a wallet rail: the customer authorises a debit from their Nagad balance and the merchant receives a confirmation callback.

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. Customer selects Nagad at checkout and the merchant creates a transaction with a unique reference.
2. The customer is taken to the Nagad authorisation step and confirms with their PIN or in-app approval.
3. A callback is delivered to the merchant's webhook endpoint with the terminal state and a rail reference.
4. The transaction is included in the day's settlement batch and appears on the reconciliation statement.

Timing and confirmation

Confirmation is normally within seconds, but callbacks can lag under network congestion. Treat anything without a terminal state as pending rather than failed and let the status endpoint resolve it.

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

Limits and ticket sizes

Customer wallet balances and per-transaction limits cap ticket size, so higher-value purchases usually need a bank rail alternative on the same checkout.

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 Nagad transaction should carry three identifiers in your ledger: your order reference, the gateway reference and the rail reference returned by Nagad. 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

• Marking a transaction failed on timeout instead of leaving it pending.
• Not storing the Nagad rail reference, which makes refunds and disputes hard to match.
• Assuming bKash logic transfers unchanged — the state semantics differ.
• Hiding the bank transfer option, which loses the higher-value segment.

Merchant benefits

• Nagad 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

Is Nagad suitable for large transactions?

Not usually. Wallet limits mean larger amounts are better routed to bank transfers, which is why merchants normally offer both.

How quickly does Nagad settle?

Wallet volume typically settles on a T+0 or T+1 basis depending on the agreed schedule.

Can Nagad payments be refunded?

Refund handling depends on the configured flow; storing the rail reference on every collection is what makes a refund or dispute traceable.