restore access to my first account Web3Auth wallet and make the 6-digit verification code

Developer Discussions Web3 Services (Infura)
1

Dear Web3Auth Support Team,

My Gmail address is shanakaarawinda@gmail.com. I created a Web3Auth account using this email, and it worked well for about two and a half months.

Later, I created another account using arawishan89@gmail.com. After creating this new account, the code for my first account didn’t come. (shanakaarawinda@gmail.com). When I log in using arawishan89@gmail.com, it seems to use the same password for both accounts.

I kindly request you to restore access to my first account Web3Auth wallet and make the 6-digit verification code available again for shanakaarawinda@gmail.com.

Thank you for your help and understanding

Screenshot 2025-10-04 173343
Screenshot 2025-10-04 1733431197×760 81.9 KB

Screenshot 2025-10-04 173254
Screenshot 2025-10-04 1732541282×813 48.4 KB

2

Hi Shan — thanks for the clear description and screenshots. I’m sorry you’re locked out of your original Web3Auth account — I’ll help collect what the support team will need and suggest next steps.

What I’ve captured from your message

  • Issue: Can’t receive 6‑digit verification code for shanakaarawinda@gmail.com after creating a second Web3Auth account (arawishan89@gmail.com). When signing in with the newer account, it appears to use the same password for both. You want access to the first Web3Auth wallet restored.
  • Emails involved: shanakaarawinda@gmail.com (original) and arawishan89@gmail.com (new)
  • Screenshots: 2 images attached (names in your post)
  • SDK Details: Generic question (no SDK/version provided)
  • Platform: not specified

Quick troubleshooting you can try right away

  • Check spam/junk/promotions folders in Gmail for the 6‑digit code email.
  • Make sure you’re signing in with the correct Google account/profile (switch profiles in the browser if needed).
  • Try an incognito/private window or a different browser/device (clears cached auth state).
  • Clear cookies/cache for the site and attempt to resend the code.
  • If you have a seed phrase/private key backup for that wallet, use it to restore access to the wallet address directly.

Information that will help the support team (please provide if you can)

  • Platform/browser/OS you used when trying to sign in (e.g., Chrome on Windows 11, Safari on iPhone).
  • Whether you signed in with “Sign in with Google” (OAuth) or an email OTP flow.
  • Any wallet address (public) previously linked to the original account (if you have it).
  • Approximate date you created the original account and the date you created the second account.
  • Whether you are an end user of Web3Auth or a developer integrating Web3Auth into an app. If you’re a developer, please also include your Web3Auth SDK version and your code snippets for initialization & login.
  • Any browser console logs (or confirm whether your attached screenshots are console logs or email screenshots).

If the above steps don’t fix it

  • The recovery will likely need Web3Auth support to investigate. When you contact them, include: both emails, the two screenshots, the associated wallet address (if known), device/browser/OS, and creation dates. That will speed their investigation.

Would you like me to:

  • Help draft a support message to Web3Auth with the details above? OR
  • Forward this info to the MetaMask Developer team for advice (if you were using MetaMask integrations)?

If you can reply with platform/browser, whether you used Google OAuth or email OTP, and whether you have the wallet address or seed phrase, I’ll prepare the exact support payload to submit. I’m here to help get this resolved.

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. MetaMask Developer Office Hours