Web3Auth — MPC embedded wallets with audit-ready accounting
Web3Auth was an early-mover on MPC-based embedded wallets. We integrate their user-to-wallet mapping for Web3 app finance teams.
Web3Auth provides MPC-based embedded wallets for Web3 applications. The integration ingests the user-to-wallet mapping and ties on-chain activity to user IDs for SaaS-style accounting reports.
What the Web3Auth integration does
User-to-wallet mapping
MPC wallets attributed to user IDs.
Multi-tenant support
Multiple Web3Auth tenants under one workspace.
The connection in 4 steps
Connect Web3Auth via project Client ID
Provide your Web3Auth project's Client ID and network (mainnet or testnet) in Wag3s. The integration reads the user-to-wallet mapping from the Web3Auth dashboard API — no user signing required.
Ingest MPC wallet addresses per user
Wag3s pulls the list of MPC wallet addresses provisioned by Web3Auth, grouped by user ID. Each wallet's public address is the basis for on-chain activity ingestion.
Track on-chain activity per embedded wallet
For each Web3Auth-provisioned wallet, Wag3s ingests on-chain transaction history across all supported EVM chains. Smart account (EIP-4337) activity is decoded via the EntryPoint contract.
Produce user-attributed accounting reports
Revenue, fee income, and disbursements are attributed to individual user wallet IDs in the report output, enabling per-user revenue tracking and SaaS-style cohort analysis alongside the aggregate GL.
Common configurations
The game uses Web3Auth so players sign in with Google and get an MPC wallet automatically. The finance team needs to separate player-to-player transactions (not revenue) from platform fee collections. Wag3s uses the Web3Auth user-wallet mapping to attribute fee income to the platform wallet and segregate user activity, producing a clean P&L for the monthly close.
The protocol distributes weekly staking rewards to users' Web3Auth wallets. Wag3s ingests the reward distribution transactions, attributes each to its user ID, and produces a reward expense schedule per period for the protocol's financial disclosures.
The platform provisions Web3Auth MPC wallets for enterprise clients who interact with smart contracts on their behalf. Finance needs to report on per-client transaction volumes and fee revenue. Wag3s maps each client's Web3Auth wallet to a Wag3s entity, producing per-client revenue reports from the on-chain data.
Web3Auth integration questions
How is user PII from Web3Auth handled in Wag3s?
Wag3s processes only the opaque Web3Auth user ID and the associated wallet address — no email addresses, OAuth tokens, or social login details are ingested. PII handling complies with the Wag3s Data Processing Agreement.
Does Wag3s support Web3Auth MPC Core Kit (non-custodial)?
Yes. Web3Auth's MPC Core Kit provisions non-custodial wallets using threshold signatures. Wag3s connects to the resulting wallet address directly, reading on-chain activity in the same way as any EOA or smart account — the MPC key management is transparent to the accounting layer.
What is the difference between connecting Web3Auth vs. importing wallet addresses manually?
Connecting Web3Auth provides the user-to-wallet mapping, enabling user-attributed reports and per-user revenue analysis. Importing wallet addresses manually provides the same on-chain transaction data but without the user attribution layer. For finance teams that need aggregate GL only, address import is sufficient; for user-level reporting, the Web3Auth integration is required.
Other connectors that pair with this one.
Connect Web3Auth in minutes
Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.