# \[Archive\] Switching to custom authentication verifiers

**URL:** <https://builder.metamask.io/t/archive-switching-to-custom-authentication-verifiers/1701>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [November 6, 2023, 1:44am UTC](https://builder.metamask.io/t/archive-switching-to-custom-authentication-verifiers/1701 "2023-11-06T01:44:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![adammchambers](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/adammchambers/32/273_2.png) [@adammchambers](https://builder.metamask.io/u/adammchambers)\
**Post date:** [November 6, 2023, 1:44am UTC](https://builder.metamask.io/t/archive-switching-to-custom-authentication-verifiers/1701/1 "2023-11-06T01:44:46Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **adammchambers** on 11/6/2023.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

Hi there, if I switch to custom verifiers for social logins will my users have to create new accounts with new wallet addresses or will their keypair remain consistent as it’s tied to their social account?

We would like to launch with the basic tier and then upgrade after a successful trial run but I wanted to check this first.

Thanks.

---

<div class="post-metadata">

**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\
**Post date:** [November 6, 2023, 2:44am UTC](https://builder.metamask.io/t/archive-switching-to-custom-authentication-verifiers/1701/2 "2023-11-06T02:44:38Z")

</div>

@adammchambers Welcome Aboard!

Your request is under review and I will get back to you.

---

<div class="post-metadata">

**Author:** ![pepper](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@pepper](https://builder.metamask.io/u/pepper)\
**Post date:** [November 6, 2023, 6:38am UTC](https://builder.metamask.io/t/archive-switching-to-custom-authentication-verifiers/1701/3 "2023-11-06T06:38:47Z")

</div>

Hello @adammchambers , welcome to the community.  
If you want to use various social login verifiers, and want to get same result (same account),  
you need to use `Aggregate verifier`.

 ![](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/1X/4bea15d5fdfd372b2e7fae21263c61fab3da9379.png)

```
  <a href="https://web3auth.io/docs/auth-provider-setup/aggregate-verifier" target="_blank" rel="noopener">web3auth.io</a>

```

### [Creating Aggregate Verifier on the Web3Auth Dashboard | Documentation | Web3Auth](https://web3auth.io/docs/auth-provider-setup/aggregate-verifier)

Creating Aggregate Verifier on the Web3Auth Dashboard | Documentation - Web3Auth

Please refer to this documentation.  
Note that you need to be a paid customer if you want to use aggregate verifier on sapphire mainnet.

---

<div class="post-metadata">

**Author:** ![adammchambers](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/adammchambers/32/273_2.png) [@adammchambers](https://builder.metamask.io/u/adammchambers)\
**Post date:** [November 6, 2023, 10:57am UTC](https://builder.metamask.io/t/archive-switching-to-custom-authentication-verifiers/1701/4 "2023-11-06T10:57:59Z")

</div>

Hi @pepper, thanks for your response. That’s not quite what I meant though. We dont want to get the same account across various social logins. I just want to confirm that our customers wont lose their accounts if we start with the basic web3auth tier and the default social providers and then upgrade and switch to our own social account verifiers at a later stage.

Referring to this specifically: [https://web3auth.io/docs/pnp/going-live#2-create-a-web3auth-production-verifier](https://web3auth.io/docs/pnp/going-live#2-create-a-web3auth-production-verifier)

[![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/e/ee7fd3b5b9556c77d6f89121b84b5bcfa3d6910d.png)
image1976×686 96.9 KB
](https://web3auth.io/community/uploads/default/original/2X/6/6eeb5babe0bef482d7264d1b173d51b078b4b9b9.png "image")

---

<div class="post-metadata">

**Author:** ![adammchambers](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/adammchambers/32/273_2.png) [@adammchambers](https://builder.metamask.io/u/adammchambers)\
**Post date:** [November 6, 2023, 10:59am UTC](https://builder.metamask.io/t/archive-switching-to-custom-authentication-verifiers/1701/5 "2023-11-06T10:59:59Z")

</div>

For example, will a user retain the same account / wallet if they sign up with google while we are using the default social providers and then we switch to our own google account / api creds at a later stage?

---

<div class="post-metadata">

**Author:** ![pepper](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@pepper](https://builder.metamask.io/u/pepper)\
**Post date:** [November 7, 2023, 6:08am UTC](https://builder.metamask.io/t/archive-switching-to-custom-authentication-verifiers/1701/6 "2023-11-07T06:08:10Z")

</div>

Hello @adammchambers , I got the point.  
If you change your verifier then the result account will also be changed.  
So if you want to use your own verifier later but keep your user’s account unchanged,  
the only way to do that is to pay to create a verifier from scratch.

or there’s another way, to use default verifier from the scratch.  
The advantage is that you don’t have to pay up front.  
So, the point is that the verifier should never change to get the same account back.

Thanks