How two-factor authentication works on mikoto
We require a second authentication factor to add an extra confirmation layer after your password. When enabled, the account flow adds one short step between password entry and account access. The second factor can be an authenticator app code or an SMS code tied to a verified mobile number.
Steps are explicit: we ask for a password, send or generate a one-time code, and accept the code for access. If a player loses access to the second factor, our support process requires identity checks before resetting 2FA. That process helps keep account-linked payment instruments and tournament entries intact.
Key takeaways
- Enable 2FA before you deposit or join a tournament.
- Use an authenticator app for offline codes; SMS is a secondary option.
- Keep recovery options updated to avoid verification delays.
We show how 2FA links to common tasks on mikoto: account verification, withdrawal review, and promo claim checks. For example, when a withdrawal triggers extra verification, a 2FA code confirms the session as a control step. We also explain how 2FA affects participation in referral and tournament mechanics without promising outcomes for any offer.
Authenticator app vs SMS
Authenticator apps generate time-based codes and work without a network connection. SMS requires mobile service and is tied to a phone number registered in your profile. We recommend choosing one method and adding a backup mobile number when available.
We support common authenticator apps and standard SMS delivery for verification. If a number changes, update it under profile verification before you attempt withdrawals or tournament registration.
Step-by-step: enable 2FA on mikoto
-
Open account settings
Sign in and go to security or verification in your profile.
-
Choose your 2FA method
Select authenticator app or SMS and follow the on-screen prompt.
-
Verify the first code
Enter the generated or received code to confirm setup.
-
Save recovery details
Store backup codes or update your verified phone to avoid service interruptions.
We log the device and the 2FA method used at setup. Subsequent logins prompt only for password plus code. Certain sessions from recognized devices may see fewer prompts, while new devices or credential changes will prompt 2FA each time.
A second factor reduces account takeover risks while keeping routine actions smooth for verified users.
2FA and deposit / payout flow
When you deposit using a local payment method such as DANA or one of our supported banks, a 2FA check may appear during sensitive changes like adding a new payout account. We do not block deposits for 2FA, but we may delay high-value actions until verification completes.
For tournament registration, we verify identity and session control; 2FA helps confirm the player behind the entry. Referral reward claims that require identity checks can also trigger a 2FA prompt before we proceed with eligibility checks.
Common issues and recovery
If you lose access to an authenticator app or lose the registered phone, we run a recovery flow. Recovery steps require a combination of profile data, transaction history, and document verification. We do not remove 2FA without confirming account ownership.
For quick references, consult city pages and event notices that tie into verification timing. For example, event deadlines around Liga 1 match windows or holiday periods such as Idul Fitri can affect support response times in Jakarta or Surabaya.
We list short guidance for frequent scenarios:
- Changing phone number: update the number under profile before initiating withdrawals.
- Resetting 2FA: open a support ticket and follow identity verification prompts.
- Lost backup codes: request recovery and prepare proof of recent deposit or withdrawal history.
Note on local payments and timing
Keep your linked payment apps such as e-wallet or mobile banking updated in profile. Timing for verification around holidays like Idul Adha or Imlek may vary by city.
For players in Bandung, Medan, or Semarang, we advise checking device time sync and authenticator app settings before a match day or tournament start. A time skew can prevent a valid code from being accepted during a critical login.
We maintain logs of 2FA challenges for audit and support. If you report a failed code, provide the approximate time, device model, and your last transaction trace to help speed review. Service available only where local law permits.