Live / Slots
When you use CIMB Clicks through FPX on bx00, the timing of your transaction depends on the handoff between your bank session and our wallet confirmation step — and knowing where that gap sits helps you avoid unnecessary follow-ups. We've laid out every stage here so you can track the status confidently from your account dashboard.
Every CIMB Clicks transaction routed through FPX follows a defined sequence — your bank authorises, FPX relays the confirmation, and our system updates your wallet balance. We do not insert manual steps that extend that window unnecessarily. The status you see in your account after completing the bank session reflects the latest signal we have received from the payment rail. If the status stays pending longer than the window described by your bank, our support team can pull the transaction reference and check where it sits in the relay chain. We keep this process consistent across Bank Transfer routes too, so you have one clear path for escalation regardless of which CIMB channel you used.
CIMB Clicks transactions go through FPX's relay before hitting our wallet. That relay step is where the bank's authorisation is translated into a confirmation signal our system can read and record against your account.
Your account dashboard shows the current state of any CIMB Clicks transaction after login. We update that status as soon as FPX or the Bank Transfer channel passes us a confirmed or failed signal — no manual refresh needed on your end.
If CIMB Clicks via FPX is delayed or unavailable, Bank Transfer remains an active route on bx00. The timing window for Bank Transfer follows standard interbank clearing, which your bank's confirmation screen will indicate at the time of submission.
When you contact our support team about a CIMB Clicks timing query, share the transaction reference from your CIMB Clicks history. That reference lets us locate the exact relay record and tell you which stage the transaction is currently sitting at.
A CIMB Clicks payment on bx00 moves through four distinct stages. First, you select FPX at the deposit screen and choose CIMB Bank from the bank list — this opens the CIMB Clicks login session in a secure redirect. Second, you authorise the amount inside your CIMB Clicks session using your TAC or registered authentication method. Third, FPX receives the bank's approval signal and relays it to bx00's payment processor. Fourth, our system credits your wallet and updates your account dashboard.
Knowing the mechanics behind each stage of a CIMB Clicks transaction on bx00 removes the guesswork from your deposit experience. Each step below corresponds to a real handoff point in the FPX chain, and knowing where you are in that chain helps you decide whether to wait, refresh your dashboard, or contact support with the right information ready.
At the bx00 deposit screen, selecting FPX and then CIMB Bank opens a redirect to your CIMB Clicks session. The timing clock starts here — if you leave this page idle beyond the session timeout set by CIMB, the transaction will not proceed and no funds will move.
Inside your CIMB Clicks session, you enter your TAC within the time window CIMB allows. This window is set by CIMB, not by bx00. Completing authorisation before the window closes is the single most important action for a smooth transaction outcome.
Once CIMB confirms authorisation, FPX sends a relay signal to bx00. This relay is near-instantaneous under normal load, but during high-traffic periods there can be a short queuing delay. Your dashboard will move from 'pending' to 'confirmed' once this relay lands.
After the FPX relay completes, your wallet balance updates and the transaction appears under your account history. If the status stays 'pending' beyond what your bank indicates is normal, note your transaction reference number before reaching out to support.
These data points reflect how CIMB Clicks transactions behave on bx00 in terms of routing, timing transparency and account visibility. We do not publish invented processing speeds — the timing shown in your account dashboard and in your CIMB Clicks history together give you the most accurate real-time picture available for your specific transaction.
FPX (with Bank Transfer as an alternate route)
Current transaction status shown in your account dashboard after login
TAC window expiry or FPX relay queue during high-traffic periods
Malaysia — availability depends on local law and eligible regions
Running a CIMB Clicks deposit from your phone introduces one friction point that desktop users rarely encounter — the FPX redirect opens CIMB Clicks inside a browser tab, and switching between tabs or apps during the TAC entry window can break the session. Keep the CIMB Clicks tab active until you see bx00's confirmation screen. In portrait orientation, the deposit amount field and bank selector stack vertically and stay within thumb reach, so you can complete the selection without scrolling. The TAC field on the CIMB Clicks redirect page is large enough to tap accurately on standard phone screen sizes.
When a CIMB Clicks transaction does not confirm as expected, there are three clear paths to resolution. The first is your account dashboard — the status shown there after login reflects the latest signal from FPX, and a 'pending' status that resolves on its own means no further action is needed. If the status does not change, collect your CIMB Clicks transaction reference before escalating. Our support team can match that reference against the FPX relay log and tell you exactly where the transaction stands — whether it failed at the bank authorisation stage or is waiting on the relay queue. Bank Transfer queries follow the same escalation path with the bank's own transfer receipt as your reference document.
Log in and open your account dashboard first. The transaction status there reflects the most current FPX signal we have. A status of 'pending' that resolves within the window your bank indicates means no escalation is needed on your end.
If the status stays 'pending' beyond the expected window, locate the transaction reference in your CIMB Clicks history. Share this reference with our support team — it maps directly to the FPX relay record and shortens the resolution process significantly.
Contact bx00 support with your transaction reference and the amount in question. Our team checks the FPX relay log and your account wallet record together. For Bank Transfer routes, provide the bank's own transfer receipt as the reference instead of a CIMB Clicks session ID.
These definitions cover the key terms that come up when tracking a CIMB Clicks transaction on bx00. Each explanation uses plain language so you know exactly what each term means in the context of your deposit.
FPX (Financial Process Exchange) is the interbank payment network that carries your CIMB Clicks authorisation from the bank to the merchant. It acts as the relay layer between your bank session and the bx00 wallet confirmation step.
'Pending' means bx00 has received your payment initiation but is still waiting for the FPX relay confirmation from CIMB Bank. It does not mean the transaction has failed — it means the confirmation signal has not yet arrived at our end.
TAC stands for Transaction Authorisation Code — a one-time code sent by CIMB to verify your identity during a transaction. Entering it within the displayed time window completes the bank-side authorisation step that triggers the FPX relay.
A session timeout happens when you do not complete the TAC entry within CIMB's allowed window. The session closes, no funds are moved, and you need to start a new deposit attempt from the bx00 deposit screen.
A transaction reference is a unique identifier generated when your CIMB Clicks payment is initiated. It appears in your CIMB Clicks history and is the key piece of information our support team needs to locate your specific relay record.
Bank Transfer is an alternate deposit route on bx00 that follows standard interbank clearing rather than the FPX instant relay. Timing for this route is determined by the clearing window your bank displays at submission time.
These are the questions our account holders ask most often about CIMB Clicks payment timing on bx00. Each answer is specific to how FPX and Bank Transfer transactions behave on our platform.
Once you complete TAC authorisation inside your CIMB Clicks session, the FPX relay sends a confirmation to bx00. Your wallet balance updates as soon as that relay lands. The exact duration depends on CIMB's processing and FPX relay load — your account dashboard shows the live status so you can track it without guessing.
A prolonged 'pending' status usually means either the TAC was not completed within CIMB's session window, or the FPX relay is queuing during a high-traffic period. Check your CIMB Clicks transaction history first — if the debit shows there, your reference number is the key to escalating with our support team.
If your CIMB Clicks session times out before TAC entry, no debit is made and no funds move. If a debit appears in your CIMB account but your bx00 wallet has not updated, that indicates an FPX relay gap — contact our support with the CIMB transaction reference to resolve it.
Bank Transfer is available on bx00 as a separate deposit route. Its timing follows standard interbank clearing rather than FPX instant relay. Your bank's transfer confirmation screen will show the expected clearing window, so you can decide which route suits your situation before submitting.
Have your CIMB Clicks transaction reference, the deposit amount and the approximate time of the attempt ready before reaching out. This lets our support team pull the specific FPX relay record quickly and tell you whether the transaction is still in the queue or has reached a terminal state.
We do not add a manual processing layer on top of FPX relay confirmations. Once the relay signal reaches our system, your wallet updates automatically. Any delay sits within the bank-to-FPX-to-bx00 relay chain, not in a separate internal queue on our end.