Can we identify the authentication method (SM/email/wllaet) used by a user at sign up?

Hello,

We are currently utilizing web3auth for a digital product with over 1,000 paying subscribers. However, we’ve encountered a challenge related to user account management, especially during sign-up at music festivals.

The issue arises from the fact that many users forget which method they initially used to sign up – whether it’s the Google account authentication or the email method linked to their Gmail address. As a result, when these users attempt to log in again, they inadvertently select the wrong method and are prompted to pay for a new subscription. This has led to user frustration, backlash, and increased support requests.

To address this problem, we are seeking a solution to merge two separate accounts belonging to the same user.
For example, we want to consolidate an account created through a social media login with another created using an email address if they both belong to the same user.
This would help eliminate confusion and streamline the user experience.

We would appreciate your guidance on whether such an account merging feature is feasible with web3auth and, if so, how we can implement it effectively. Any technical insights or instructions you can provide would be highly valuable in helping us enhance our user account management process.

Thank you for your support.

Our implementation is PnP

@madalin.bitoi Thanks for your recent post.

Your request has been forwarded to our Dev team and we will get when there is a meaningful update to share.

1 Like

Thank you, looking forward to hearing their suggestions :slight_smile:

Hey @madalin.bitoi, Please refer this doc and explore the possibility of using aggregate verifiers for your setup.

Hey @maharshi and thank you for your reply.
One question, though: wouldn’t this impact the existing user base? Wouldn’t they require to re-sign up and wouldn’t that entail new wallets?
We are using the wallets that web3auth generates to store users’ NFTs

Hey, @maharshi
Not sure if you saw my last reply last week, regarding your solution proposal:

wouldn’t this impact the existing user base? Wouldn’t they require to re-sign up and wouldn’t that entail new wallets?
We are using the wallets that web3auth generates to store users’ NFTs

Thank you1

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.