Name the action you started
Verify that the code request followed your own withdrawal or security change. If no action was initiated, do not approve it and review the account through the official support channel.
Expect a Fresh Code for a Sensitive Account Action
A remembered login can be valid while a higher-risk account action still needs a new verification code. BetOnline identifies withdrawals and security-preference updates as examples. The code confirms the action; it should never be supplied to a caller or chat agent.
Open the secure login routeCheck the destination channel
Compare the masked email or phone with the registered contact. Secure that mailbox or handset first if access is shared, lost or recently changed.
Enter the code only on the account page
Do not read a code to support, paste it into email or follow a link sent by an unsolicited caller. Enter it only in the verified signed-in workflow for the action you recognise.
Confirm the resulting account event
After verification, record the withdrawal ID or security-change confirmation. If the code succeeded but the action remains pending, keep the same reference for support.
What to keep
Keep the initiated action, masked delivery route, verification time and resulting transaction or change reference. Never preserve the code itself.
More from this section
Quick answers
Can a withdrawal require another code?
Yes. Sensitive actions can trigger step-up verification.
Should a code be given to support?
No. Enter it only in the official account workflow.
What if no action was initiated?
Do not approve it; secure the account and contact official support.
Last reviewed: 30 July 2026