Slots / App
bKash is the payment rail built into your bo66 account wallet — connect it once and every deposit or withdrawal moves through the same mobile number you already use. This page covers how your bKash wallet works inside the platform, where to find each step, and what to do when something needs attention.
Your bo66 account treats bKash as the primary mobile wallet for Bangladesh — not a secondary option. When you open the cashier panel inside your account, bKash appears in the wallet row alongside Nagad and Rocket, and each one requires a one-time verification against the mobile number registered on your account.
Open the cashier panel, choose bKash, and enter the mobile number tied to your active bKash account. The platform sends a confirmation step to that number. Follow the fields exactly as shown — a mismatch between your bo66 account name and the bKash registered name can pause the link until support reviews it.
After the wallet link is confirmed, select bKash in the deposit screen and enter the amount within the limits shown on that screen. The platform displays a merchant number and a reference code. Open your bKash app, use Send Money or Payment as instructed on the deposit screen, paste the reference code in the message field, and confirm.
Go to the withdrawal tab in your account cashier, choose bKash, and enter the amount. The platform checks that the destination number matches your verified wallet before queuing the request. If the numbers do not match, the withdrawal screen will prompt you to update your wallet details through the account settings path first.
Every bKash movement — deposit or withdrawal — appears in your account history tab with a reference number and a status marker. If your bKash app shows a deducted amount but your bo66 balance has not changed, note the bKash transaction reference and bring it to the support channel along with a screenshot.
Each bKash transaction through bo66 generates a platform reference and a bKash transaction ID. Both are visible in your account history tab. Keep the bKash transaction ID separately in case a dispute needs cross-referencing with the bKash side of the record.
Your account history tab shows each transaction as pending, completed or flagged. Pending means the platform has received your request and is processing it. Completed means funds have moved. Flagged means the wallet number check or a platform review step has paused the transaction — check your account notification area for next steps.
The deposit and withdrawal screens each display the minimum and maximum amounts for bKash at the time you initiate. These limits are shown in BDT on the screen itself — do not rely on a remembered figure from a previous session, as limits can be updated and the screen always reflects the current value.
If a transaction shows completed in your bo66 account history but the amount is not visible in your bKash app balance, the published support route is the live chat channel in your account dashboard. Have the bo66 reference number and bKash transaction ID ready before you open the chat.
The account dashboard includes a live chat button visible once you are signed in. Use this channel for bKash transaction queries — share the bo66 reference number, the bKash transaction ID and the date. This is the fastest route for wallet-related questions shown on the site.
When a bKash deposit or withdrawal requires an action from you — such as a wallet verification re-check or an identity confirmation — the platform posts a notification inside your account dashboard. Check this area first before opening a support ticket, as many wallet holds are resolved by completing the prompted step.
The bo66 help centre, accessible from the account menu, contains specific articles covering bKash linking steps, common error messages and the process for disputing an unresolved transaction. Articles are written for Bangladesh mobile wallets and reference bKash, Nagad and Rocket separately so the steps stay accurate for each rail.
The platform matches your bo66 account registration details against the bKash number you enter. This is not a friction step for its own sake — it prevents funds from being sent to an unintended number. The verification record is stored in your account settings and is visible to you at any time from the wallet management screen.
bKash, Nagad and Rocket are configured as separate wallet options, each with their own cashier screen and reference workflow. The steps shown on the bKash screen are specific to how bKash processes merchant payments — they do not apply to Nagad or Rocket, which have their own equivalent screens and reference formats.
Your account history tab is the authoritative record for all bo66-side transaction data. It does not depend on the bKash app history, which records only what happened on the bKash network side. Keeping both records aligned — bo66 reference and bKash transaction ID — is the practice that resolves most discrepancy queries quickly.
The platform's terms of service include a wallet and payment section that covers bKash usage conditions, what happens if a number change is requested and how flagged transactions are reviewed. You can access this section from the footer of any page without logging in. Availability depends on local law and eligible regions.
A merchant payment in bKash is a transfer sent from your personal bKash wallet to a registered business account. On bo66, the deposit screen provides the merchant number and reference code you need to complete this type of transfer correctly.
Wallet verification is the one-time process where the platform confirms your bKash mobile number matches the details on your bo66 account. Without this step, fund movements to or from that wallet number cannot be processed.
A platform-generated code assigned to each bKash deposit or withdrawal request on bo66. It appears in your account history tab and is the primary identifier when you contact support about a specific transaction query.
Pending means your bKash transaction request has been received and is being processed by the platform. It has not yet reached a completed or flagged state. Pending status is normal for a short period after initiating a deposit or withdrawal.
The unique code issued by bKash for each transfer you make through their app or USSD. It appears in your bKash confirmation message and is separate from the bo66 reference number — keep both if you ever need to raise a query.
Flagged means the platform has paused the transaction for a review step — usually because the wallet number did not match the verified number on file, or a further account check is needed. The notification area in your dashboard will show what action is required.
Open the cashier panel once you are signed in, select bKash from the wallet row, and enter your bKash mobile number. Follow the confirmation step sent to that number.
When you initiate a deposit through the bKash screen in your cashier, the platform displays a reference code. Open your bKash app, go to Payment or Send Money as directed on screen, and paste that code into the message or reference field before confirming. Using the wrong code means the platform cannot match your payment automatically.
First check your bo66 account history tab to see if the transaction shows as pending or flagged. If it is not there at all, copy the bKash transaction ID from your bKash app confirmation message and open a live chat from your account dashboard.
Yes — go to the wallet management section inside your account settings, remove the existing verified number and follow the linking steps for the new number. The new number goes through the same verification process before it becomes active for deposits and withdrawals. Check the published terms under the payment section for any conditions that apply.
The current limits are displayed in BDT directly on the bKash deposit and withdrawal screens at the time you initiate a transaction. The platform updates these limits on screen, so always read the displayed figure at that moment rather than relying on a previously noted amount.
Nagad and Rocket are also available in the cashier wallet row and each has its own dedicated screen with separate merchant details and reference workflows.