A disputed bKash transfer can involve several separate questions: whether the MFS transaction was processed correctly, who controlled the recipient account, what a casino claimed about a balance, and whether there are signs of a cyber incident. Those questions do not automatically belong to the same complaint authority.
The practical sequence is provider first, the provider’s Complaint Cell if the matter remains unresolved, and Bangladesh Bank’s CIPC with the provider’s response and supporting documents when the MFS complaint is still unresolved. A cyber-incident report has a different purpose and should not be treated as a substitute for that sequence.
Author: Casino Check BD Evidence Desk
Editor: Casino Check BD Editorial Verification Desk
Reviewed: 28 August 2026
Corrections: Request a correction
Start by defining the disputed event
Before asking how to complain about a bKash payment, identify what can actually be documented. Record the transaction identifier, date and displayed amount, the sending account, the recipient details shown in the receipt, and the status displayed by the provider. Preserve the original receipt rather than relying only on a cropped image or a rewritten reference.
Keep later conversations separate from the transaction record. A message saying that money will be credited to a casino balance is a casino claim; it is not confirmation from bKash Ltd. that the recipient belongs to that casino. Likewise, a completed transfer establishes that an MFS transaction occurred, but not why it occurred, who ultimately controlled the recipient, whether gambling activity was lawful, or whether a refund is due.
Use the bKash transaction-ID evidence guide to organise the core record. If the displayed recipient appears unexpected, follow the wrong-recipient steps without assuming fraud or ownership.
Decision and evidence matrix
The correct route depends on the issue being reported. Avoid combining every concern into a single unsupported accusation.
| Question or event | Evidence to preserve | Appropriate starting boundary | What it does not prove |
|---|---|---|---|
| Transfer is pending, failed, duplicated or otherwise disputed | Original receipt, transaction ID, date, displayed amount, status and provider correspondence | bKash provider support | Recipient ownership, casino legality or refund entitlement |
| Provider reply does not resolve the MFS issue | Initial complaint, case reference, complete provider reply and follow-up record | Provider Complaint Cell | That CIPC will order recovery or determine a casino balance |
| Complaint Cell process is complete but the MFS complaint remains unresolved | Final provider response, chronology and supporting transaction documents | Bangladesh Bank CIPC | Wrongdoing by a recipient or reversal of a particular transfer |
| Account access, phishing or technical compromise is suspected | Access alerts, relevant messages, logs, affected domain information and steps already taken | Secure the account, notify the provider and consider the cyber-incident route | That a CIRT submission is a police complaint or recovery claim |
| Casino says a payment was not credited | Receipt plus the casino’s exact balance or deposit message | Separate the MFS service issue from the casino balance claim | That the payment provider has verified the casino relationship |
A provider listing, account label or successful transfer should not be used as proof that bKash endorses a recipient or has a commercial relationship with a casino. The recipient and merchant-check guide explains how to record displayed identifiers without extending them into an ownership conclusion.
Use the provider-first sequence
The first complaint should focus on the MFS event and the remedy or explanation being requested from the provider. Give the transaction identifier and other relevant receipt details, explain the discrepancy in chronological order, and retain the complaint reference. Do not send a PIN, password or one-time authentication credential as evidence.
The official sequence matters. Bangladesh Bank’s CIPC procedure, captured on 28 August 2026, tells an MFS customer to contact the provider first, escalate an unresolved issue to the provider’s Complaint Cell, and then submit an unresolved complaint to CIPC with the provider response and supporting documents. It does not guarantee recovery or decide a casino balance.
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. The regulations do not establish the identity of a casino recipient or promise reversal of a particular transfer.
These records support a complaint pathway, not a conclusion about the merits of an individual dispute. Keep the provider’s acknowledgement, any case number and each substantive response together.
Escalate to the provider’s Complaint Cell
Complaint Cell escalation is appropriate when ordinary provider support has responded but the MFS issue remains unresolved, or when the provider’s stated process directs the customer there. Send a concise chronology rather than a collection of unexplained screenshots. Identify what was first reported, what the provider answered, and what remains unanswered.
Preserve the final provider response in its original form. That response is important if the complaint later goes to CIPC. If no final response has been received, preserve the acknowledgement and subsequent follow-ups, and accurately describe the status as pending rather than rejected.
Do not rewrite a casino balance dispute as a provider finding. For example, a casino’s statement that a deposit was not credited remains the casino’s statement unless the provider independently confirms a relevant transaction issue. Conversely, a provider confirmation that a transfer completed does not decide whether a casino correctly maintained an internal balance.
Prepare an unresolved complaint for CIPC
CIPC is the later stage for an unresolved MFS complaint after provider and Complaint Cell handling. The official procedure calls for the provider response and supporting documents. A useful submission therefore connects each assertion to a record and distinguishes confirmed transaction data from claims made by another party.
| Stage | Action | Records to retain | Boundary |
|---|---|---|---|
| Provider support | Report the specific MFS discrepancy | Receipt, transaction ID, complaint reference and acknowledgement | Provider reviews its service and records |
| Provider Complaint Cell | Explain why the first response did not resolve the issue | Initial complaint, full response, chronology and relevant attachments | Internal escalation does not guarantee reversal |
| Bangladesh Bank CIPC | Submit the still-unresolved MFS complaint with provider response and support | Final response or documented status, transaction evidence and concise issue statement | CIPC procedure does not decide a casino balance or guarantee recovery |
| Cyber-incident reporting | Report relevant technical indicators when a cyber incident is suspected | Affected domain or IP, logs, incident details, vector, impact and prior steps where available | Not a police complaint, casino adjudication or recovery process |
The complaint should avoid unsupported labels such as “verified merchant,” “casino-owned account” or “confirmed fraud.” State what the receipt displays and what each party said. The broader complaint-routes guide can help separate an MFS grievance from other reporting channels.
Keep the casino claim separate
An MFS service complaint can address matters within the provider’s records and grievance process. A casino balance dispute concerns what the casino claims happened inside its own system. The two may refer to the same payment attempt, but they remain different evidentiary questions.
A transfer receipt may support that money moved to the displayed recipient. It does not independently prove that the casino instructed the transfer, owned the recipient account, received the funds beneficially, or owed a balance credit. A casino message may support what the casino represented, but it does not alter the provider’s transaction record.
Build two short chronologies if necessary: one for the provider transaction and one for the casino communications. Mark unresolved points as unknown. General payment-risk guidance provides additional boundaries for handling claims about recipients and payment instructions.
When a cyber-incident route is relevant
A cyber route becomes relevant when the available facts indicate a technical-security event, such as suspected account compromise, phishing or malicious infrastructure. Immediate account-security steps and provider notification should not be delayed while evidence is organised. Follow the account-compromise guide for a focused record of access concerns.
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. Submitting the form is not a police complaint, a casino adjudication or a recovery guarantee.
A failed credit, delayed response or disputed recipient is not by itself proof of a cyber incident. Use the CIRT route only when the incident information fits its technical remit. Do not present speculation as a log, an identified attack vector or a confirmed compromise.
Protect evidence without exposing credentials
Keep original files where possible and create working copies with unnecessary personal details concealed. Preserve enough context to show where a receipt or message came from, but never publish or casually circulate authentication credentials. Transaction evidence should be shared only with the relevant complaint body through an appropriate channel.
Use a simple evidence index: item number, date, source, short description and the claim it supports. Avoid editing screenshots in ways that change meaning. If a crop is needed for privacy, keep the original separately. Record whether a statement came from bKash, another recipient, a casino, Bangladesh Bank or a cyber authority; those sources have different roles.
Frequently asked questions
Where should a bKash complaint start?
It should start with the bKash provider process for the specific MFS transaction or service issue. Preserve the transaction record, complaint reference and provider response before moving to later escalation stages.
When should I escalate to the complaint cell?
Escalate when the initial provider response has not resolved the MFS issue or when the provider’s process directs the complaint there. Explain what remains unresolved and keep the Complaint Cell’s final response or documented status.
Which documents should accompany a CIPC complaint?
Include the provider response and supporting documents relevant to the unresolved MFS complaint, such as the transaction record, complaint reference and a concise chronology. Their inclusion does not guarantee recovery or establish a casino claim.
When is the CIRT route relevant?
It is relevant when there is a suspected cyber incident supported by technical or security information, such as an affected domain, logs, incident details, impact or steps already taken. A submission is not a police complaint and does not adjudicate a casino balance.