Growth plan feature-access fails with MFA settings error even though is_mfa_settings=false

Embedded Wallets (Web3Auth)
2

Thanks — I’m on the MetaMask & Web3Auth team. This is an error report. From what you’ve shared, the most likely cause is the backend gating treating the mere presence of is_mfa_settings in the feature-access request as “MFA requested”, and the SDK is sending that query param by default (common in older versions / with whitelabel flows). Quick guidance and next steps:

  1. Likely root cause
  • Backend feature-gating is keying off presence of the is_mfa_settings parameter, not its value. The SDK is including the param even when false, which triggers the Growth-plan block.
  1. Recommended immediate actions
  • Upgrade @web3auth/modal and related @web3auth/* packages to the latest release (this is the cleanest fix; newer builds omit optional flags unless enabled).
  • As a quick diagnostic, try setting is_whitelabel=false and reproduce; if the param stops being sent and the error disappears, that confirms the SDK/whitelabel behavior.
  • If you cannot upgrade, you can temporarily patch/intercept the request in your app to remove the is_mfa_settings query param before it’s sent (workaround only).
  1. Info I need to escalate this for you
  • Exact @web3auth/modal version (from package.json or npm ls) — please provide this.
  • Confirm you’re using the Openlogin adapter / any other @web3auth adapters (yes/no).
    (You already provided team_id 85076 and the failing request — that’s useful.)
  1. Next from our side
  • If you want, I’ll escalate to the backend team to confirm whether the gating check is based on parameter presence and ask them to verify/fix project gating for team_id 85076. Please confirm you want me to open that internal ticket and share the exact @web3auth/modal version so we can reproduce.

If you prefer, first try upgrading @web3auth/modal and re-test — if the issue persists, reply with the exact package version and I’ll escalate immediately.

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 monthly Office Hours to discuss this with our engineering team. MetaMask Developer Office Hours