How to reset Google Authenticator on MEXC? (Account Recovery)

Understanding MEXC Two-Factor Authentication

1. MEXC enforces mandatory two-step verification for all user accounts to prevent unauthorized access.

2. Google Authenticator is not officially supported by MEXC; the exchange mandates use of its proprietary MEXC Authenticator app for time-based one-time passwords (TOTP).

3. The MEXC Authenticator app requires iOS 12.0 or later on Apple devices and iPadOS 12.0 or newer for iPads.

4. Account recovery does not involve resetting Google Authenticator because MEXC does not integrate with it at the protocol level.

5. Users who previously attempted to link Google Authenticator manually may face TOTP mismatch errors during login.

MEXC Authenticator Backup Limitations

1. MEXC Authenticator does not store backup codes on its servers or in iCloud.

2. If device loss occurs and no manual backup of the secret key was performed during initial setup, cryptographic binding becomes irrecoverable through automated means.

3. The app only backs up account names—not seed values—for work, school, or third-party services like Amazon or Gmail.

4. Restoration of TOTP functionality depends entirely on re-adding the account using the original QR code or secret key.

5. No cloud sync exists between MEXC Authenticator installations across devices.

Account Recovery Workflow on MEXC

1. Users must log in to their MEXC web interface using valid credentials and pass email/SMS verification.

2. Navigate to Security Settings > Two-Step Verification > Disable, which triggers a 72-hour cooldown period before re-enabling.

3. After cooldown, generate a new TOTP configuration via QR code scan using the official MEXC Authenticator app.

4. During re-setup, users are prompted to confirm identity using registered recovery email or verified phone number.

5. The system discards prior TOTP bindings immediately upon successful reactivation—no legacy codes remain valid.

Common Technical Failures During Recovery

1. Scanning an expired QR code results in “Invalid token” error regardless of clock synchronization status.

2. Device time drift exceeding ±30 seconds causes persistent code rejection even with correct secret key input.

3. Attempting manual entry without copying the full Base32-encoded secret—including padding characters—leads to generation failure.

4. Using unofficial forks or modified versions of authenticator apps breaks HMAC-SHA1 signature validation expected by MEXC’s backend.

5. Repeated failed attempts lock the TOTP endpoint for 15 minutes, requiring wait time before retry.

Frequently Asked Questions

Q: Can I reuse my old Google Authenticator secret key with MEXC Authenticator?A: No. MEXC Authenticator does not accept externally generated secrets. Only QR codes issued directly from MEXC’s security dashboard are accepted.

Q: Does MEXC store my TOTP secret after I disable two-step verification?A: No. The secret is cryptographically erased from MEXC systems once two-step verification is disabled.

Q: What happens if I uninstall MEXC Authenticator before backing up the secret key?A: You must initiate full account recovery through MEXC support with verified KYC documents. Automated self-service restoration is unavailable.

Q: Is there any way to bypass TOTP during login if I lose access to my authenticator app?A: No. MEXC does not provide fallback SMS or email codes. Recovery depends exclusively on completing the formal identity verification process with submitted legal documentation.