# Unable to validate verifier id: invalid payload params, verifier\_id or extended\_verifier\_id not found **URL:** \ **Category:** Embedded Wallets (Web3Auth)\ **Created:** [May 8, 2025, 8:05am UTC](https://builder.metamask.io/t/unable-to-validate-verifier-id-invalid-payload-params-verifier-id-or-extended-verifier-id-not-found/1026 "2025-05-08T08:05:08Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![tech2](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@tech2](https://builder.metamask.io/u/tech2)\ **Post date:** [May 8, 2025, 8:05am UTC](https://builder.metamask.io/t/unable-to-validate-verifier-id-invalid-payload-params-verifier-id-or-extended-verifier-id-not-found/1026/1 "2025-05-08T08:05:08Z")
> **🏛 Content from Web3Auth Community** > > This topic was originally posted by **tech2** on 5/8/2025. > This content has been migrated from our previous community forum to preserve valuable discussions. * * * I have authentication with aggregate social login (Google) and custom (telegram jwt). The login for Google is working perfectly but for telegram it had issue with unable to validate verifier id. I have make sure that the verifierId and sub verifierId is already same. Any clue for this issue? [![Screenshot at May 08 15-04-44](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/1X/f12c932325f56b82a0ed84e012eafac89532a738.png) Screenshot at May 08 15-04-441064×542 18.4 KB ](https://web3auth.io/community/uploads/default/original/2X/e/e9bb1b09ef20112d7095835f6d6035531bd10f21.png "Screenshot at May 08 15-04-44") ---
**Author:** ![w3abot](https://avatars.discourse-cdn.com/v4/letter/w/4da419/32.png) [@w3abot](https://builder.metamask.io/u/w3abot)\ **Post date:** [May 8, 2025, 8:07am UTC](https://builder.metamask.io/t/unable-to-validate-verifier-id-invalid-payload-params-verifier-id-or-extended-verifier-id-not-found/1026/2 "2025-05-08T08:07:52Z")
Thanks for sharing the details and the screenshot! Here’s a summary of your issue for the support team: - **SDK:** Plug n Play - **Platform:** Not explicitly mentioned (please confirm if it’s web, mobile, or something else) - **Login Methods:** Aggregate social login (Google - working), Custom (Telegram JWT - issue) - **Error:** Unable to validate verifier id: invalid payload params, verifier\_id or extended\_verifier\_id not found - **Screenshot:** Provided To help you further, could you please provide: - The Web3Auth initialization & login code snippet (especially how you’re configuring the Telegram verifier and JWT) - The name of your Telegram verifier as set on the Web3Auth Dashboard - A sample (sanitized) idToken (JWT) you’re using for Telegram, and your JWKS endpoint (if you’re using your own authentication) - The SDK version number you’re using **Possible Cause & Suggestions:** This error usually means that the JWT payload is missing the required field (verifier\_id or extended\_verifier\_id), or the field is not matching what’s expected by your verifier configuration. Please ensure that: - The JWT payload contains the correct field (usually sub, email, or another field mapped as verifier\_id in your Web3Auth dashboard). - The Telegram JWT is correctly signed and the JWKS endpoint is accessible (if using custom JWT). - Your aggregate verifier configuration in the Web3Auth dashboard has the correct sub-verifiers and mapping. You can refer to the docs for [Aggregate Verifiers](https://docs.web3auth.io/guide/aggregate-verifier.html) and [Custom JWT Login](https://docs.web3auth.io/guide/custom-jwt-login.html) for more details. Once you provide the code snippet and other details, the support team can help you debug further! > Note: This response was generated by an AI bot and may require further verification. The Web3Auth support 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. [Web3Auth Developer Office Hours](https://web3auth.io/community/t/web3auth-developer-office-hours/8777) ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/9/92b599d3131e78cf3d3ff01b80e54d69d266f8df.png) [@system](https://builder.metamask.io/u/system)\ **Post date:** [May 22, 2025, 8:07am UTC](https://builder.metamask.io/t/unable-to-validate-verifier-id-invalid-payload-params-verifier-id-or-extended-verifier-id-not-found/1026/3 "2025-05-22T08:07:56Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed. ---
**Author:** ![maharshi](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/maharshi/32/1525_2.png) [@maharshi](https://builder.metamask.io/u/maharshi)\ **Post date:** [May 26, 2025, 9:18am UTC](https://builder.metamask.io/t/unable-to-validate-verifier-id-invalid-payload-params-verifier-id-or-extended-verifier-id-not-found/1026/4 "2025-05-26T09:18:29Z")
---
**Author:** ![maharshi](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/maharshi/32/1525_2.png) [@maharshi](https://builder.metamask.io/u/maharshi)\ **Post date:** [May 26, 2025, 9:31am UTC](https://builder.metamask.io/t/unable-to-validate-verifier-id-invalid-payload-params-verifier-id-or-extended-verifier-id-not-found/1026/5 "2025-05-26T09:31:36Z")
Hey @tech2 Can you please share Web3Auth related code snippet and your dashboard configuration?