ovo33 — your Game Start.

e-wallet33 Two-Factor Authentication with Liga 1 and mobile banking

A user logs into their local payment33 account from a new device during the Liga 1 season and receives a verification code via SMS. They enter the code, confirm their identity, and access their football markets and payment methods without disruption. Two-factor authentication sits at the centre of account access on our platform—a second verification layer that protects your account, payment methods, and withdrawal requests.

Open an account

Two-Factor Authentication

Category

Live Table / Card

RTP

high

We implement two-factor authentication as a standard security checkpoint whenever you log in from an unrecognised device, request a withdrawal, or update your account details. This guide covers how 2FA works on online payment33, why we require it for sensitive actions, and how to manage your authentication settings to keep your account and e-wallet, mobile banking, local payment withdrawals secure.

Two-Factor Authentication on ovo33

Two-factor authentication requires a second proof of identity beyond your password. On e-wallet33, the second factor is most commonly a time-limited SMS code sent to your registered mobile number. When you attempt to log in from a new browser, reset your password, or confirm a withdrawal, our system triggers a 2FA prompt. You receive a 6-digit code via SMS within seconds, enter it into the login or action form, and the system verifies that the code matches the one generated for that session.

This second step prevents attackers from accessing your account even if they obtain your password. It also protects your payment methods—mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, online payment, e-wallet, mobile banking, local payment—because withdrawal requests require 2FA confirmation. If someone tries to change your registered payment account or move funds, you will receive an SMS code and have a chance to block the action before it completes.

Setting up two-factor authentication

During account creation, we ask for your mobile number and send a verification code to confirm it. This mobile number becomes your 2FA delivery address. To update or change your registered number, go to Account Settings → Security → Verify Phone Number. You will need to confirm your current number with an SMS code before we accept a new one.

If you do not receive an SMS code within 30 seconds, try requesting a new code—SMS delivery in Jakarta, Surabaya, Bandung, and Medan typically completes within seconds, but network congestion may cause short delays. If codes fail to arrive, contact our support team to review your phone number and network provider settings.

2FA during login and payment actions

When you log in from a new device or after clearing your browser cookies, the login form asks for your username and password as usual. After you submit those credentials, our system checks the device fingerprint—browser type, operating system, approximate location. If the device is new or unrecognised, we display a "Verify your identity" screen and send an SMS code to your phone. You have subject to verification to enter the code. Once you do, the login completes and your session begins.

Payment actions follow the same pattern. If you request a withdrawal to a new online payment, e-wallet, or mobile banking account, or if you update your local payment virtual account details, we send a confirmation code. You must enter this code on the action-confirmation screen before the system processes your request. This prevents an attacker from using your logged-in session to drain your account to an account they control.

Two-factor authentication is not optional on online payment33 for sensitive account changes—it is a mandatory second checkpoint to confirm that you authorise the action.

Common 2FA scenarios and how to respond

• New login from a phone: If you log into mobile banking33 from your phone for the first time, expect a 2FA prompt on the phone itself. Enter the SMS code you receive, and your phone is now a recognised device for the next 30 days.
• Clearing browser cookies: If you clear your browsing data (history, cookies, cache), your desktop browser is treated as a new device on next login and will require 2FA.
• Withdrawal to a different payment method: If you normally withdraw to a local payment account but change your withdrawal method to online payment virtual account, the system sends a 2FA code to confirm the change.
• Using multiple devices: You can use e-wallet33 on a phone, tablet, and desktop. Each device must complete 2FA on first login, but subsequent logins on the same device may skip 2FA depending on time elapsed and our security policy.
• Code expiry: SMS codes expire after subject to verification. If you do not enter the code in time, request a new one from the login or action screen.

What to do if you do not receive an SMS code

SMS delivery is usually instant, but international roaming, network congestion, or phone-number issues can cause delays. If you do not see an SMS within subject to verification:

1. Check that your phone has an active mobile plan and SMS is enabled.
2. Confirm that the mobile number registered on mobile banking33 (Account Settings → Security) matches the phone you are using.
3. Request a new code from the login or action screen. Do not close or reload the page until you receive the code.
4. If you are in a region with known carrier delays (travelling internationally), wait up to subject to verification before contacting support.
5. Contact our support team if codes do not arrive after multiple requests. Provide your registered email and phone number, and we will investigate carrier or account settings that may be blocking SMS delivery.

Protecting your 2FA and account

Because SMS codes are single-use and time-limited, they are relatively secure—but you should still treat them as private. Never share a 2FA code with anyone, even if they claim to be from our support team. Our staff will never ask you for a 2FA code. If someone requests your code, it is a sign of a phishing attempt or social engineering attack. Do not comply, and contact us directly if you suspect fraud.

Keep your registered mobile number current. If you change your phone or SIM card, update your number in Account Settings before you lose access to the old number. If you change your number without updating local payment33, you will be unable to receive 2FA codes on your new phone and will be locked out of your account.

SMS code validity

Each code is valid for subject to verification from the time it is sent. After subject to verification, the code expires and you must request a new one.

Device memory

After you complete 2FA on a device, online payment33 may remember that device for up to 30 days. You can reset device memory in Account Settings by signing out of all active sessions.

Backup codes

If SMS delivery fails persistently, contact support to generate backup authentication codes that work without SMS.

Account verification and 2FA together

Two-factor authentication works alongside account verification (KYC). When you first create an e-wallet33 account, we ask for your name, date of birth, and ID number to verify your identity. This is separate from 2FA—verification confirms who you are, while 2FA confirms that it is you attempting to log in or authorise a payment.

For withdrawal requests over certain thresholds, we may ask you to complete additional verification steps before processing the withdrawal. This is especially common on first withdrawal or when withdrawing to a new mobile banking, local payment, or bank virtual account. Additional verification protects both you and our platform by confirming that the withdrawal destination is legitimate and that you have control of the payment account.

If you have questions about your 2FA setup or encounter issues with SMS codes during withdrawal to a online payment or e-wallet account, our support team is available during business hours to assist. Include your registered email and a description of the issue, and we will review your account settings to resolve the problem.