Start with the Nagad provider
If a Nagad payment is disputed, begin with the provider process rather than treating the transfer itself as proof of who received it or why it was made. Bangladesh Bank’s CIPC procedure, captured on 28 August 2026, says an MFS customer should contact the provider first. If the issue remains unresolved, the customer should escalate it to the provider’s Complaint Cell before submitting an unresolved complaint to CIPC. Read the Bangladesh Bank CIPC procedure.
For background, see the Nagad payment hub and the guide to MFS transaction evidence.
Use the provider’s Complaint Cell for an unresolved service issue
The provider-first sequence has three practical stages: contact Nagad, retain the response, and escalate an unresolved matter to the provider’s Complaint Cell. The Complaint Cell is part of the provider-level route described in the Bangladesh Bank CIPC procedure. It is not the same as proving a claim against a casino or deciding whether a disputed balance is payable.
Keep a dated record of what you submitted and any response received. Avoid changing the original evidence. A clear chronology can distinguish a payment-service complaint from a separate disagreement about goods, services, account access, or a claimed gambling balance. If the provider replies that it cannot determine the recipient’s underlying business relationship, that limitation should be preserved rather than converted into an allegation.
| Situation | Appropriate boundary | Evidence to preserve | What the route does not establish |
|---|---|---|---|
| A Nagad transaction appears incorrect or disputed | Start with Nagad and follow its provider process | Transaction reference, date, amount, account records, and correspondence already held | It does not establish recipient ownership or a refund entitlement |
| The provider-level response does not resolve the issue | Escalate to the provider’s Complaint Cell | Your original submission and the final provider response | It does not decide a casino balance or prove wrongdoing |
| The issue remains unresolved after provider escalation | Consider a CIPC submission with the provider response and supporting documents | Complete chronology and relevant documents | It does not guarantee recovery or reverse a particular transfer |
The Bangladesh Mobile Financial Services Regulations 2018 include transaction-authentication safeguards and a complaint and grievance-redressal framework, including provider dispute handling and CIPC escalation. Read the Bangladesh Bank MFS Regulations 2018. Those regulations do not establish the identity of a casino recipient or promise reversal of a particular transfer.
Prepare a CIPC escalation only after provider steps
Bangladesh Bank’s CIPC procedure places provider contact before CIPC escalation. For an unresolved MFS complaint, include the provider response and supporting documents identified by the procedure. A CIPC submission should explain what happened, what was reported to the provider, what response was received, and why the matter remains unresolved. Keep the wording limited to facts you can support.
| Before CIPC escalation | Why it matters | Boundary to keep clear |
|---|---|---|
| Contact the provider | It follows the provider-first sequence | Contact does not prove the recipient’s identity |
| Escalate to the provider’s Complaint Cell when unresolved | It records that the provider-level route was used | Complaint Cell handling is not a casino adjudication |
| Preserve the provider response | The response forms part of the supporting record | A response is not a recovery promise |
| Organise transaction and supporting documents | It helps present a consistent chronology | Documents do not automatically prove fraud, illegality, or entitlement |
| Submit the unresolved issue to CIPC when appropriate | It follows the stated escalation boundary | CIPC does not guarantee recovery or decide a casino balance |
CIPC is a regulatory complaint route within the scope stated by Bangladesh Bank’s procedure. It should not be described as a guaranteed reversal mechanism, a court decision, or a finding that a named recipient acted unlawfully. If the underlying disagreement is about a claimed casino balance, keep that claim separate from the MFS service complaint. The payment record can be evidence for the transaction question without resolving the separate claim.
Separate payment evidence from a casino claim
A disputed Nagad payment can involve several distinct questions: whether the transaction occurred, whether authentication was used, who controlled the recipient details, what service was allegedly offered, and whether any refund or other remedy is available. These questions may require different records. The MFS route addresses the provider-service and transaction-handling boundary described in the supplied Bangladesh Bank records; it does not determine every issue arising from a separate commercial or gambling dispute.
Use neutral descriptions such as “the recipient shown in the transaction record” unless reliable evidence supports a more specific identity. Do not infer that a recipient is licensed, legal, authorised, or connected to a particular operator from a payment name alone. Likewise, a failed complaint does not by itself prove that a payment was legitimate or illegitimate.
Relevant internal guidance includes checking recipient or merchant details, preserving a transaction ID, and handling a wrong recipient. These routes help separate transaction documentation from conclusions about the recipient.
Use the CIRT route for a possible cyber incident
The BGD e-GOV CIRT incident form, captured on 28 August 2026, asks for the affected domain and IP, logs or evidence, incident details, attack vector, impact, and steps already taken. Open the BGD e-GOV CIRT incident form. Use that route for the cyber-incident information requested by the form when the facts suggest a relevant incident.
CIRT reporting is not a substitute for the provider-first MFS complaint sequence. It is also not a police complaint, a casino adjudication, or a recovery guarantee. The form’s request for a domain, IP, logs, impact, and prior steps should not be treated as proof that an attack occurred. Describe what is known, identify what remains uncertain, and retain copies of the material submitted.
| Indication in the available record | Route to consider | Record to keep | Limit |
|---|---|---|---|
| Transaction or account-service dispute | Nagad, then its Complaint Cell if unresolved | Transaction details and provider correspondence | Does not determine a casino claim |
| Unresolved issue after provider escalation | Bangladesh Bank CIPC | Provider response and supporting documents | No guaranteed recovery or reversal |
| Suspected cyber incident with relevant technical details | BGD e-GOV CIRT incident form | Domain or IP information, logs, incident details, impact, and steps taken | Not a police complaint or adjudication |
| Unclear recipient identity | Keep the identity unresolved while collecting records | Original payment evidence and neutral chronology | A payment record alone is insufficient |
See payment risk guidance and phishing and fake support guidance when the concern includes suspicious contact or possible account compromise.
Keep a disciplined evidence bundle
Preserve the transaction reference, date, amount, account or wallet records available to you, the original complaint wording, provider correspondence, Complaint Cell response, and any supporting material relevant to the issue. Do not add a date, fee, deadline, phone number, refund promise, merchant identity, or legal conclusion unless it appears in a verified record. Separate documents supplied by the provider from your own account of events.
A useful bundle has four labels: transaction evidence, provider correspondence, recipient-identity material, and cyber-incident material. The labels prevent one record from being treated as proof of a different proposition. For example, a transaction reference can support that a payment record exists; it cannot alone prove who owned the destination or whether a claimed service was lawful.
For privacy handling, use receipt privacy guidance and the correction route. Redact unnecessary personal information when a submission process permits it, while retaining the material needed to understand the complaint.
A calm escalation sequence
The safest description of the route is procedural rather than promissory: contact Nagad first; escalate an unresolved issue to the provider’s Complaint Cell; retain the provider response; then consider CIPC with supporting documents if the issue remains unresolved. Use CIRT separately when the available facts concern a possible cyber incident and the form’s requested information can be provided.
This sequence does not decide whether money will be recovered. It does not establish that a recipient was a casino, confirm casino legality, or determine a gambling balance. It creates a clearer record by keeping provider identity, recipient identity, transaction evidence, any casino claim, and the remit of each complaint route separate.
Key questions answered
Where should a Nagad complaint start?
Start with Nagad as the MFS provider. Bangladesh Bank’s CIPC procedure captured on 28 August 2026 places provider contact before escalation to the provider’s Complaint Cell and then CIPC for an unresolved complaint. See the CIPC procedure.
When should I use the complaint cell?
Use the provider’s Complaint Cell when the issue remains unresolved after contacting Nagad through its provider process. Keep the original submission and the Complaint Cell response. This route does not decide a casino balance or establish recipient wrongdoing.
Which documents should go to CIPC?
The supplied Bangladesh Bank procedure identifies the provider response and supporting documents as part of an unresolved CIPC complaint. Keep a factual chronology, transaction evidence, the provider submission, and the response. CIPC does not guarantee recovery or reversal of a particular transfer.
When should I use the CIRT route?
Consider the BGD e-GOV CIRT incident form when the available information concerns a possible cyber incident and you can describe the affected domain or IP, logs or evidence, incident details, attack vector, impact, and steps already taken. The form is not a police complaint, casino adjudication, or recovery guarantee. See the CIRT form.
Does a Nagad transfer prove that a casino received the money?
No. A payment-provider record may support that a transaction occurred, but it does not by itself establish the recipient’s ownership, a casino relationship, casino legality, refund entitlement, or wrongdoing. Keep the recipient identity as unresolved unless separate evidence supports it.
Does CIPC guarantee that a payment will be recovered?
No. The supplied Bangladesh Bank CIPC record describes an escalation procedure for an unresolved complaint. It does not guarantee recovery or decide a casino balance.
Where should a Nagad complaint start?
Start with Nagad as the MFS provider. Bangladesh Bank’s CIPC procedure captured on 28 August 2026 places provider contact before escalation to the provider’s Complaint Cell and then CIPC for an unresolved complaint. See the CIPC procedure.
When should I use the complaint cell?
Which documents should go to CIPC?
When should I use the CIRT route?
Consider the BGD e-GOV CIRT incident form when the available information concerns a possible cyber incident and you can describe the affected domain or IP, logs or evidence, incident details, attack vector, impact, and steps already taken. The form is not a police complaint, casino adjudication, or recovery guarantee. See the CIRT form.