Slots / Mobile
When you fund your cb666 account via Bank Transfer, FPX or DuitNow, the time it takes for funds to appear in your wallet depends on the channel you pick and the processing window your bank applies.
Bank Transfer payment timing at cb666 follows a straightforward path — you initiate the transfer through your chosen channel, the payment rail routes the instruction to our receiving account, and once the bank confirms settlement, the amount is credited to your cb666 wallet.
Not every bank transfer channel moves at the same speed. FPX routes your instruction through the national online banking gateway and confirms the debit within the same session — making it the fastest path for getting your wallet funded before a Liga Super match kicks off.
FPX deducts from your bank account within the same online banking session and sends a real-time confirmation to cb666. Your wallet balance typically reflects the credited amount once that confirmation clears — check the transaction log inside your account to track the current status.
DuitNow uses the national instant-payment network. Transfers to merchant accounts go through a settlement step beyond the peer-to-peer flow. The network publishes its own processing window, and your cb666 wallet updates as soon as our system receives the settled notification from DuitNow.
When you pay with Boost, the debit hits your Boost balance immediately, and Boost sends a settlement instruction to cb666. The time between your Boost confirmation and your wallet update reflects how quickly Boost closes the merchant settlement — visible in your account transaction log.
A direct bank-to-bank transfer follows your bank's own inter-bank clearing cycle. This window is wider than FPX or DuitNow, particularly outside business hours or on public holidays. Check the timing your bank publishes for inter-bank credits before choosing this route for time-sensitive deposits.
The table below captures the key variables that determine how quickly your bank transfer moves through to your cb666 wallet. Because timing is controlled by the payment rail and your bank, the figures here reflect the general behaviour of each channel rather than a fixed promise.
FPX (online banking), DuitNow (national instant network), Boost (e-wallet), Standard Bank Transfer — each follows a different processing path with a different typical window.
FPX confirms within the same session. DuitNow follows the network's merchant settlement cycle. Boost depends on Boost's merchant close. Standard transfer follows your bank's inter-bank clearing schedule.
Standard bank transfers submitted outside business hours or on Malaysian public holidays may fall into the next clearing batch. FPX and DuitNow are less affected by business hours but can experience brief queue delays during high-volume periods.
Your account transaction log after login shows the current status of every transfer — pending, confirmed or credited. This is the most accurate single source; no page refresh or support ticket is needed unless the status has not moved past its channel's normal window.
On a phone screen, the bank transfer status view inside your cb666 account fits within a single scroll. The transaction log renders in a stacked list format in portrait orientation — each entry shows the channel name, the submitted amount and the current status label side by side without any horizontal scrolling required.
If your transfer status has not moved past what the channel's normal window suggests, or if the credited amount does not match what you submitted, there are clear help routes available. Before contacting support, pull the transaction reference number from your bank's confirmation message or your DuitNow or FPX receipt — it speeds up the lookup significantly.
Open the live chat from your account page and share your transaction reference number from your FPX, DuitNow or Boost confirmation. The team can check the receiving record on our side and tell you whether the delay is at the payment rail or pending internal crediting.
Your account transaction log is the first place to look. It shows the channel, submitted amount, submission timestamp and current status. A status that reads 'pending' after the channel's typical window has passed is the signal to escalate to live chat with your reference number ready.
Keep your FPX session receipt, DuitNow transfer confirmation or Boost transaction notification. These contain the reference number and timestamp that support needs to match your transfer to our records. Without this, tracing a delayed transfer takes considerably longer.
Every bank transfer that passes through cb666's wallet system generates a transaction record tied to the payment rail's own confirmation. FPX, DuitNow and Boost each produce a reference number on their side, and our system logs the corresponding receipt timestamp when we receive it. That linkage is what makes disputes traceable — support staff work from the same reference chain, not from a manual ledger.
Every FPX, DuitNow or Boost transfer generates a reference number that our system logs on receipt. That reference is what ties your bank's outgoing record to our incoming credit — and it's what support pulls when tracing a delayed or mismatched transfer.
The confirmed transfer amount lands in your cb666 wallet as a single credit line with no fee deduction applied on our side. What you see in the transaction log is what cleared — compare it against your bank confirmation to verify the figures match end to end.
FPX and DuitNow are national payment infrastructure channels with their own confirmation protocols. Our system waits for a confirmed settlement signal from the rail before crediting your wallet — not just a debit notification from your bank.
Your account transaction log retains a full history of every transfer attempt — submitted, pending and confirmed. This is available after login at any time, giving you a complete audit trail for any transfers you need to review or reconcile against your bank statement.
These are the terms that come up most often when you're tracking a bank transfer through to your account wallet. Each definition below uses plain language to explain what the term means in the context of payment timing at cb666.
Settlement is the point at which funds move from your bank's possession to the recipient's account in a final, confirmed way. A pending instruction is not settled; only a confirmed credit is. Settlement timing differs by channel — FPX and DuitNow have distinct settlement cycles from standard bank transfer.
A unique code generated by your bank or payment app — FPX session receipt, DuitNow confirmation or Boost notification — that identifies your specific transfer. Support uses this reference to locate the matching record on the receiving side when tracing a delayed or unmatched credit.
Pending means your transfer instruction has been submitted and logged, but the payment rail has not yet sent a settled confirmation to cb666. Your wallet will not update until that confirmation arrives. Pending beyond the channel's normal window is the trigger to contact support with your reference number.
The scheduled batch process banks use to exchange and finalise transfers between different financial institutions. Standard bank transfers move through this cycle, which runs at fixed intervals and can extend overnight or across public holidays — unlike FPX or DuitNow which route differently.
A wallet credit is the addition of a confirmed transfer amount to your cb666 account balance. It appears as a single line in your transaction log. The credit is spendable across sports betting and live casino categories the moment it shows as confirmed — no further action needed from your side.
FPX, or Financial Process Exchange, is Malaysia's national online banking payment gateway. It routes a real-time debit instruction from your chosen bank and sends a confirmation to the merchant — in this case cb666 — within the same online banking session, making it one of the faster deposit channels available.
Real questions from people tracking transfers to their cb666 wallet — with straight answers covering FPX, DuitNow, Boost and standard bank transfer timing.
FPX processes the debit and sends a real-time confirmation to cb666 within the same online banking session. Once we receive that confirmation signal, your wallet balance updates. In practice this is among the faster paths, but the exact moment depends on when your bank's FPX gateway returns the confirmation to our system — check your transaction log after completing the session.
DuitNow transfers to merchant accounts like cb666 go through a merchant settlement step that differs from a peer-to-peer transfer between two individuals. Your Pending status means we have not yet received the settled confirmation from the DuitNow network. If the status has not moved past DuitNow's published merchant settlement window, open live chat with your DuitNow confirmation reference number ready.
For standard inter-bank transfers, yes — transfers submitted outside business hours or on Malaysian public holidays enter the next available clearing batch, which can push the credit to the following working day. FPX and DuitNow are less tied to business hours, but high-volume periods can still cause brief queue delays on the rail side.
First compare your bank's outgoing confirmation — the FPX receipt, DuitNow notification or Boost transaction record — against the line item in your cb666 transaction log. If the figures differ, contact support via live chat and share both numbers along with the transaction reference. Our team will check the receiving record against the rail's settlement data.
Log in and navigate to the transaction log inside your account dashboard. Each entry shows the channel used (FPX, DuitNow, Boost or bank transfer), the submitted amount, the submission timestamp and the current status — pending, confirmed or credited. This updates in real time as the payment rail sends us status signals, so it is always the most current view.
Yes, Boost is available as a deposit channel where local law permits and your account is eligible. When you confirm the payment in Boost, your Boost balance is debited immediately and Boost sends a merchant settlement instruction to cb666. Your wallet updates once we receive and process that settlement notification — the exact timing follows Boost's merchant processing cycle, visible in your account transaction log.