MFA settings error code 1003

[betnow]

• 10.0.0(package.json):
• Nextjs:

Following the example from here web3auth-examples/quick-starts/nextjs-quick-start at main · Web3Auth/web3auth-examples · GitHub , i have replaced with my clientId .

Getting the below error

Failed to connect with socials . Invalid params, {"code":1003,"error":"The current subscription plan is growth and requesting features (MFA settings) are not available on growth plan. Please upgrade to a higher plan at https://dashboard.web3auth.io to use these features","success":false}

We are on growth plan , previously mfa was supported in this plan

const web3AuthContextConfig: Web3AuthContextConfig = {
  web3AuthOptions: {
    clientId,
    web3AuthNetwork: WEB3AUTH_NETWORK.MAINNET,
  },
}

[w3abot]

Thank you for sharing the details and the screenshot! Here’s a summary of your issue for the support team:

---

Issue Summary:

• SDK: PnP Web SDK
• SDK Version: 10.0.0
• Platform: Next.js
• Error:

  Failed to connect with socials. Invalid params, {"code":1003,"error":"The current subscription plan is growth and requesting features (MFA settings) are not available on growth plan. Please upgrade to a higher plan at https://dashboard.web3auth.io to use these features","success":false}
  

• Web3Auth Initialization:

  const web3AuthContextConfig: Web3AuthContextConfig = {
    web3AuthOptions: {
      clientId,
      web3AuthNetwork: WEB3AUTH_NETWORK.MAINNET,
    },
  }
  

• Screenshot Provided: Yes

---

Next Steps & Suggestions

This error indicates that your current subscription plan (Growth) does not support MFA (Multi-Factor Authentication) settings. According to the Web3Auth Pricing Page, MFA is a feature available only on higher-tier plans.

Possible reasons for this error:

• The Growth plan may have recently changed and no longer includes MFA.
• Your project may be attempting to use MFA-specific features or settings in the SDK initialization or login flow.

What you can do:

1. Double-check your plan:
   • Visit Web3Auth Dashboard and verify your current subscription and its features.
2. Review your code:
   • Make sure you are not explicitly enabling MFA features in your SDK initialization or login options. If you are, try removing or commenting out any MFA-related configurations.
3. Check documentation:
   • Review the PnP Web SDK docs for any recent changes in plan requirements for MFA.

If you believe this is a mistake:

• Please confirm if you were previously able to use MFA on the Growth plan and when this stopped working.
• If you have any MFA-related settings in your code, please share those snippets for further review.

---

If you need to use MFA, you may need to upgrade your plan. If you think your current plan should support it or this is a recent change, let us know, and the support team can investigate further.

Let me know if you have any MFA-related code snippets in your integration, or if you have further questions!

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

[betnow]

I’m using the exact code from your GitHub repo — the only changes I’ve made are updating the clientId and web3AuthNetwork. Given that, it should ideally work as expected.

Also, I don’t see any option on the Web3Auth dashboard to modify or disable MFA settings, so I’m not sure how to proceed from my end.

Would appreciate any guidance on how to resolve this!

[yashovardhan]

Hey @betnow can you share your whole code? Looks like you are using MFASettings; MFALevel is supported in growth plan and MFASettings is supported in Scale plan. You can read more over here as well: Multi Factor Authentication | Documentation | Web3Auth

We haven’t changed anything, it has always been the same, you can check in our pricing page as well, which hasn’t been updated recently: Web3Auth | Pricing - Personalised plans for everyone!

[betnow]

@yashovardhan

MFALevel

My code

"use client"

// IMP START - Setup Web3Auth Provider
import {
  Web3AuthProvider,
  type Web3AuthContextConfig,
} from "@web3auth/modal/react"
import { IWeb3AuthState, WEB3AUTH_NETWORK } from "@web3auth/modal"
// IMP END - Setup Web3Auth Provider
// IMP START - Setup Wagmi Provider
import { WagmiProvider } from "@web3auth/modal/react/wagmi"
import { QueryClient, QueryClientProvider } from "@tanstack/react-query"
import React from "react"
// IMP END - Setup Wagmi Provider

// IMP START - Dashboard Registration
const clientId = process.env.NEXT_PUBLIC_WEB3AUTH_CLIENT_ID // get from https://dashboard.web3auth.io
// IMP END - Dashboard Registration

// IMP START - Setup Wagmi Provider
const queryClient = new QueryClient()
// IMP END - Setup Wagmi Provider

// IMP START - Config
const web3AuthContextConfig: Web3AuthContextConfig = {
  web3AuthOptions: {
    clientId,
    web3AuthNetwork: WEB3AUTH_NETWORK.MAINNET,
    // IMP START - SSR
    ssr: true,
    // IMP END - SSR
  },
}
// IMP END - Config

// IMP START - SSR
export default function Provider({
  children,
  web3authInitialState,
}: {
  children: React.ReactNode
  web3authInitialState: IWeb3AuthState | undefined
}) {
  // IMP END - SSR
  return (
    // IMP START - Setup Web3Auth Provider
    // IMP START - SSR
    <Web3AuthProvider
      config={web3AuthContextConfig}
      initialState={web3authInitialState}
    >
      {/* // IMP END - SSR */}
      {/* // IMP END - Setup Web3Auth Provider */}
      {/* // IMP START - Setup Wagmi Provider */}
      <QueryClientProvider client={queryClient}>
        <WagmiProvider>{children}</WagmiProvider>
      </QueryClientProvider>
      {/*// IMP END - Setup Wagmi Provider */}
      {/*// IMP START - Setup Web3Auth Provider */}
    </Web3AuthProvider>
    // IMP END - Setup Web3Auth Provider
  )
}

[yashovardhan]

Hey @betnow

I am able to reproduce the issue on my end. I have contacted the dev team regarding the same, they will fix it as soon as possible.

[betnow]

Thanks for looking into it and coordinating with the dev team!

[yashovardhan]

This is fixed, feel free to login as usual.