A Rocket payment dispute should begin with the payment provider. If the issue remains unresolved, the available route may progress from Rocket support to the provider’s Complaint Cell and then to Bangladesh Bank’s CIPC. A cyber incident has a different reporting route through BGD e-GOV CIRT.
These channels do not perform the same job. Provider records concern the payment account and transaction. CIPC receives unresolved complaints within its stated process. CIRT collects technical incident information. None of those steps, by itself, proves who controls a recipient account, establishes a casino relationship, determines gambling legality or guarantees recovery.
Author: Casino Check BD Evidence Desk
Editor: Casino Check BD Editorial Verification Desk
Last reviewed: 28 August 2026
Corrections: Privacy and corrections
1. Start with Rocket support
For a DBBL Rocket complaint, first identify what happened without mixing separate claims. Record whether the issue concerns a wrong recipient, an unauthorised transaction, a service problem, a disputed recipient identity or a payment that another party says was not credited.
The Rocket FAQ captured on 28 August 2026 says customers should never share a PIN. For money sent to a wrong number, it directs the customer to contact the Rocket helpline immediately or visit a mobile-banking office. The FAQ does not promise that a completed transfer will be reversed.
Do not publish or send a PIN in a complaint attachment. Keep the original transaction record intact and provide only information required by the relevant official channel. The Rocket payment hub explains the broader payment context, while the wrong-recipient guide focuses on mistaken destination details.
A transfer record confirms that a transaction record exists; it does not establish why the recipient received the money. Likewise, a payment-provider listing does not prove that the recipient belongs to a casino, that a casino is legal, or that a refund is due.
2. Separate the identities and claims
A useful complaint distinguishes five matters: provider identity, recipient identity, transaction evidence, any casino claim and the authority of the complaint channel. Combining them can make the request unclear and may cause evidence to be interpreted too broadly.
| Matter | Evidence to preserve | What it may support | What it does not prove |
|---|---|---|---|
| Provider identity | Official Rocket account or service records | Which payment service handled the transaction | Recipient ownership or a casino relationship |
| Recipient identity | Recipient number or identifier shown in the transaction record | The destination entered or recorded | The beneficial owner, merchant status or wrongdoing |
| Transaction evidence | Transaction reference, amount, date, time and status shown in available records | That a particular payment event was recorded | The purpose of payment, refund entitlement or final liability |
| Casino claim | Messages, account records or terms already held by the customer | What another party represented | Legality, provider endorsement or adjudicated responsibility |
| Complaint remit | Provider response, Complaint Cell response, CIPC submission or CIRT acknowledgement | Which channel received which issue | Guaranteed recovery or a decision outside that channel’s scope |
Preserve original files where available rather than repeatedly editing or cropping them. Note what each record shows and what remains unknown. The transaction-evidence guide provides a focused checklist, and the recipient-identity guide explains why a number alone should not be treated as proof of ownership.
3. Build a clear provider complaint
A provider complaint should be short enough to follow but detailed enough to locate the transaction. State the issue, identify the relevant transaction record, explain the requested review and attach supporting material that is safe and necessary to share. Avoid presenting assumptions as established facts.
Keep a copy of the submitted complaint and any acknowledgement. If the provider replies, preserve the full response, including the date and any reference visible in it. The response matters because the later CIPC procedure calls for the provider response and supporting documents when an unresolved complaint is submitted.
Use a simple chronology:
- When the payment or account event appeared in the available record.
- What destination, status and reference the record displayed.
- When Rocket support was contacted and through which official support route.
- What response was received, without paraphrasing away important qualifications.
- What issue remains unresolved and what review is requested.
Do not claim that silence, delay or refusal proves fraud. Do not add an invented deadline, fee, refund rule or legal conclusion. For a broader explanation of payment uncertainty, use payment risks.
4. Move from support to the Complaint Cell and CIPC
The Bangladesh Bank CIPC procedure captured on 28 August 2026 sets out a sequence for an MFS customer: contact the provider first, escalate an unresolved issue to the provider’s Complaint Cell, and then submit the unresolved complaint to CIPC with the provider response and supporting documents.
That sequence makes the provider response important. It shows what was raised, what the provider addressed and what remains disputed. If no substantive resolution was received, retain whatever acknowledgement or correspondence is available and describe the unresolved point accurately rather than inventing a response.
CIPC escalation does not guarantee recovery and does not decide a casino balance. A complaint should therefore ask for action within the stated payment-complaint remit, such as review of the provider’s handling or transaction records, rather than treating CIPC as a casino dispute tribunal.
| Stage | Appropriate action | Records to retain | Boundary |
|---|---|---|---|
| Rocket support | Report the payment or account issue through an official provider route | Transaction details, submission copy and acknowledgement | Initial contact is not a recovery promise |
| Provider Complaint Cell | Escalate the unresolved provider issue | Earlier complaint, provider response and supporting records | Escalation does not establish recipient wrongdoing |
| Bangladesh Bank CIPC | Submit the unresolved MFS complaint with the provider response and supporting documents | Complete chronology and copies of relevant correspondence | CIPC does not decide a casino balance or guarantee repayment |
| BGD e-GOV CIRT | Report a qualifying cyber incident with technical evidence | Domain or IP information, logs, incident details, impact and prior steps where applicable | The incident form is not a police complaint or payment adjudication |
The complaint-routes guide can help keep payment, regulatory and other reporting channels distinct.
5. Use CIRT only for the cyber-incident remit
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. Those requested fields indicate a technical incident-reporting purpose.
Use that route when the matter genuinely involves a cyber incident and the requested technical information can be supplied accurately. Do not relabel an ordinary payment disagreement as a cyberattack merely to create another escalation path. Conversely, if technical compromise is suspected, preserve available logs and evidence rather than replacing them with conclusions.
Submitting the CIRT form is not a police complaint, a casino adjudication or a recovery guarantee. CIRT reporting also does not replace the provider-first complaint sequence described by Bangladesh Bank for an unresolved MFS issue. One event may produce different records for different channels, but each submission should stay within the receiving channel’s remit.
6. Protect evidence and personal information
Keep a working evidence set and a separate sharing copy. The working set can retain original records; the sharing copy should contain only what the official recipient needs. Never disclose a Rocket PIN. Avoid posting transaction evidence publicly because it may expose account identifiers, recipient details or other personal information.
Name files consistently and keep a chronology of submissions and responses. Do not alter a screenshot or receipt in a way that removes context needed to understand it. If redaction is necessary for a particular recipient, retain the unredacted original securely and note that a redacted copy was supplied.
Evidence should remain descriptive. A receipt may show an amount, reference, status and destination, but it does not automatically show recipient ownership, intent or liability. Messages from another party may document a representation, but they do not convert that statement into a verified provider record.
7. Frequently asked questions
Where should a Rocket complaint start?
A Rocket complaint should start with Rocket through an official provider support route. Describe the payment or account issue, preserve the transaction record and keep the acknowledgement or response. If the issue remains unresolved, the Bangladesh Bank procedure says an MFS customer should escalate it to the provider’s Complaint Cell before approaching CIPC.
Why keep the provider response?
The provider response records what Rocket or its Complaint Cell addressed and what may remain unresolved. Bangladesh Bank’s stated CIPC procedure calls for the provider response and supporting documents. Keeping the complete response also reduces the risk of overstating, misquoting or losing relevant qualifications.
When should I approach CIPC?
Approach CIPC after contacting the provider and escalating the unresolved issue to the provider’s Complaint Cell, following Bangladesh Bank’s stated sequence. Submit the provider response and supporting documents. CIPC escalation does not guarantee recovery and does not decide a casino balance.
When should I use the CIRT form?
Use the BGD e-GOV CIRT form for a cyber incident where relevant technical details and evidence can be supplied, such as the affected domain or IP, logs, incident details, attack vector, impact and steps already taken. It is not a police complaint, casino adjudication or recovery guarantee.
A disciplined escalation keeps the payment complaint with Rocket and its Complaint Cell, an unresolved MFS complaint within the CIPC process, and technical incident evidence within the CIRT route. The central task is not to send the same allegation everywhere; it is to give each channel accurate records relevant to its remit while preserving unresolved facts as unknown.