Before enabling Nagad fee collection, verify: provider-specific readiness — every gateway runs with its own approval, terms and settlement timing; do not assume “whatever works on bKash works on Nagad”. Where you cannot confirm, write honestly “not verified” — sales claims remain claims until tested.
What to verify: provider-specific readiness; integration claims are yours to test
The Nagad readiness checklist:
| # | Step | Verification question | Pass criterion |
|---|---|---|---|
| 1 | Approval | does Nagad need a separate institutional approval? | document in writing |
| 2 | Software connection | does your software support Nagad — tested by you? | sample payment via link |
| 3 | Receipt | auto-receipt on Nagad payments? | instant PDF |
| 4 | Settlement | Nagad’s settlement timing (can differ from bKash) | written [VERIFY] |
| 5 | Failed payment | the process on Nagad failure | system message |
| 6 | Guardian guide | a Nagad-specific instruction sheet | one page |
Step 2 is the core: prove “the software supports Nagad” with a test payment from your own hands — existing in sales material and actually working are different things.
A usable sample: the provider verification checklist
Keep one form per gateway (bKash/Nagad/Rocket):
- Approval document: present/absent, date.
- Test payment: TrxID, date, auto-receipt produced?
- Settlement timing: __ days (written source).
- Failed-payment process: __.
- Demo note: which actions were seen live.
Archive these forms — at year-end they become the evidence in gateway comparisons and disputes.
Nagad fee collection: workflow steps and limitations
- With two gateways live, tell guardians a preference — “bKash link primary, Nagad alternative” style.
- Keep the two gateways’ settlement reconciliation in separate columns — merging makes mismatches hard to find.
- Limitation: provider terms change — re-verify both forms every six months.
Nagad: questions to ask before your demo
- Is Nagad included in the package, with separate setup cost?
- Can you show an auto-receipt on a Nagad payment right now?
See the gateway-comparison structure in fee management and the integrations page; the fuller preparation comparison in the bKash article and the contact page.
Nagad FAQ
If Nagad is absent, does bKash-only work?
It does — blocking fee collection on a guardian’s preferred gateway lowers collection rates; add the second gateway as demand shows.
Will receipt numbers run separately per gateway?
Yes — prefix receipt series per gateway (BK-, NG-) to ease reconciliation.
If the Nagad test payment gets stuck?
A written complaint to the provider — and an entry note “test failed, money pending”; do not delete.