Clarification on MAU billing and external wallets

Help - Plug n Play
1

Hello

I’d like to clarify the billing rules regarding Monthly Active Wallets (MAU).

From the documentation, I understand that MAU is counted based on active wallets that use Web3Auth’s key infrastructure (e.g., social login / embedded wallets).

Could you please confirm:

  • If a user connects to my application via an external wallet such as MetaMask, WalletConnect, or Phantom (without using Web3Auth’s embedded wallet infrastructure),
    → will this connection still be counted as an active wallet (MAU) for billing purposes?

Thank you for your help in clarifying this matter.

2

Thank you for your question and for providing clear context!

Summary of Your Query:
You are seeking clarification on Web3Auth’s Monthly Active Wallet (MAU) billing, specifically whether users who connect to your application via external wallets (like MetaMask, WalletConnect, or Phantom) — without using Web3Auth’s embedded wallet infrastructure (social login, etc.) — are counted as MAUs for billing purposes.

Clarification on MAU Billing

Based on Web3Auth’s official documentation, MAU (Monthly Active Wallet) is only counted for users who:

  • Use Web3Auth’s key infrastructure (such as social logins, passwordless, or embedded wallets).

If a user connects solely via an external wallet (MetaMask, WalletConnect, Phantom, etc.) and does not use Web3Auth’s embedded wallet infrastructure, that user is not counted as an MAU for Web3Auth billing.
This means you are billed only for users who utilize Web3Auth’s authentication and key management, not for those who connect using external wallets through your dApp.

Reference:

Additional Notes

  • If you enable both Web3Auth and external wallet connectors in your app, only those users who actually complete a login using Web3Auth’s infrastructure will count toward your MAU total.
  • You can further control which connectors appear in your modal using the modalConfig property.

No further action is required from your side if you simply want to offer external wallet connections without incurring additional MAU charges from Web3Auth.

If you have any more questions or need help configuring your modal, let us know!

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

1 Like
3

Please schedule a call with our BizDev team to understand exact methodology for this.