Sudden Error 1003

Embedded Wallets (Web3Auth)
,
1

Hello Everyone!

Unfortunately a sudden error happened on one of our WEB applications that uses web3auth.

The error is simple, in the web application we can no longer log in.

The error states:

“code”: 1003,“error”: “The current subscription plan is growth and requesting features (wallet service) are not available on growth plan. Please upgrade to a higher plan at https://dashboard.web3auth.io to use these features”,“success”: false,

The PROBLEM is that this application has been working flawlessly for more than a month and the last update was released on 1 April 2026. This morning the web app was still working fine. The mobile apps are still working fine.

Any ideas what this error might be and why it appeared out of nothing with no code changes?

Thanks in advance!

2

Hi Levente — I’m on the MetaMask & Web3Auth team. Short answer: this looks like subscription enforcement from Web3Auth — error 1003 explicitly says the Growth plan does not allow the “wallet service”, so requests that require that feature will start failing even if your code didn’t change.

Why it could appear suddenly

  • Web3Auth started enforcing plan feature gates (or billing/payment changed) for the web project.
  • Web and mobile often use different Dashboard projects / Client IDs — mobile may be using a project that still has the feature or has active cached sessions.

Immediate actions to take (quick checklist)

  1. Check the Web3Auth Dashboard for the web project: plan tier, billing status, and whether “wallet service” or related toggles are enabled.
  2. Confirm the Client ID used by your web app (env/config) and verify it matches the Dashboard project that has the wallet-service capability.
  3. Compare web vs mobile Client IDs / projects — mobile working usually means they use a different project or have long-lived sessions.
  4. Check dashboard audit logs / recent emails from Web3Auth about plan or policy changes.
  5. If you need the feature immediately, upgrade the plan or switch the web app to a project that has wallet service enabled.

What I checked for you

  • I searched the Embedded Wallets docs and confirmed wallet-service features are gated by subscription and that Client ID / project mismatch is a common cause for web vs mobile differences.

If you want me to escalate / have someone from the Web3Auth team look into it, please reply with these items (don’t paste secrets):

  • Web SDK + version you’re using
  • Client ID used by the web app (Client ID only)
  • Whether web and mobile use the same Dashboard project
  • Timestamp(s) of failed login attempts and the exact error payload / a console network screenshot if available

If you prefer, you can first check the Dashboard/billing and let me know what you find — I’ll escalate immediately if it looks like a billing/plan enforcement issue.

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

3

My billing on my dashboard is fine, everything paid and I am on growth plan as I always wanted to be.

The project uses Web3Auth Modal SDK (@web3auth/modal) at version ^10.15.0

Client ID BHYblKeaHsZrjTlJL8UIb-hZ3ubrJexugEqFDxuzK8Ot-QOTN8BznW3Ak-k2Q5jdz5RtN5HoRM4yW__lA4I6kkI

Web and Mobile use the same dashboard project, logic in the code is different (next.js on web and react native on mobile)

the error starts with this endpoint failing:

https://api.web3auth.io/signer-service/api/feature-access

resulting in the upper error where I an unauthorised

then https://api-wallet.web3auth.io/auth/verify fails too

{
“statusCode”: 400,
“error”: “Bad Request”,
“message”: “Validation failed”,
“validation”: {
“body”: {
“source”: “body”,
“keys”: [
“signatures.0”
],
“message”: ““signatures[0]” length must be less than or equal to 500 characters long”
}
}
}

My question still remains: I NEVER had SCALE plan, only GROWTH Plan, I developed something, tested it, it was working fine, then suddenly stops working because of “subscription enforcement“ does not sound logical, more like a TRAP. I mean you let people release their applications to PRODUCTION, let it work or a month, then shut ot down or enforce to pay $399 instead of $69 does not sound logical to me. I hope this is just some internal error and you will be able to fix it.

If the error is on my end and I indeed use by mistake wallet services, then I would like a clear explanation why it was working in the first place on production.

Please let me know,

Thanks in advance

4

Seems like it is not working because of this error: Auth/verify fails: signatures[0] must be ≤ 500 characters (account abstraction) .

1 Like
5

I’ve hit the same issue, I didn’t change anything. Glad I am not the only one, was driving my crazy trying to find the issue.

6

Hi @szilagyi84 ! We have passed your case to our team and we will reply you as soon as we can.

7

@Aussie We have rolled out a fix on our web app and the problem seems to be solved:

The solution was to remove Web3Auth’s built-in accountAbstractionConfig, which was activating the Wallet Services flow, and instead, after login, locally construct a separate Biconomy Account Abstraction provider on top of the standard Web3Auth provider. This way, the existing smart account address is preserved and minting works, while avoiding the Web3Auth Wallet Services package limits. So the 1003 error was on our end, and literally did nothing, but the “signatures[0]” length must be less than or equal to 500 characters long“ error was really the one blocking users to access their accounts, and that one is solved with this change.

For some strange reason we still see the subscription error, trying to figure out what Scale plan features “are used“ in our app.

The “signatures[0]” length must be less than or equal to 500 characters long“ error completely disappeared, the app works, this thread can be closed.

2 Likes
8

Oh great thank you. Will dig into this workaround. Appreciate it, my prod site was also down.