Privy — user-attributed wallet accounting for Web3 apps
Privy's embedded wallets mean every user has an on-chain address tied to their email or social login. We connect that to the books.
Privy is the leading embedded-wallet platform for Web3 apps — users sign in with email, social, or passkey, and Privy provisions an on-chain wallet behind the scenes. For Web3 SaaS finance teams, the question becomes: how do you attribute wallet activity to individual users for accounting purposes? The Wag3s integration ingests the Privy user-to-wallet mapping (with privacy-preserving handling) and produces user-attributed reports.
What the Privy integration does
User-to-wallet mapping
Privy-issued wallets linked to user identifiers for the audit trail (PII handled per DPA).
Multi-app support
Multiple Privy apps under one Wag3s workspace.
Smart-account aware
Privy smart accounts (EIP-4337) decoded with the entry-point pattern.
The connection in 4 steps
Connect Privy via SDK API key
Provide your Privy app ID and API key in the Wag3s integration settings. Wag3s reads the user-to-wallet mapping from the Privy API — no user PII is stored beyond what is covered under the DPA.
Ingest user-to-wallet mapping
Wag3s pulls the list of Privy-issued embedded wallets and their associated user identifiers, building a mapping table for attribution in accounting reports.
Track on-chain activity per user wallet
For each embedded wallet, Wag3s ingests on-chain activity across all supported EVM chains, including smart-account (EIP-4337) UserOperation decoding via the EntryPoint contract.
Generate user-attributed financial reports
Revenue, fees, and disbursements are attributed to individual user wallets in the report output, enabling SaaS-style per-user revenue reporting alongside the aggregate GL view.
Common configurations
The app provisions an embedded wallet for each user via Privy at sign-up. Finance needs to attribute on-chain protocol fees to individual users for revenue recognition. Wag3s ingests the Privy user-wallet mapping and produces a per-user revenue report alongside the aggregate GL entries.
The app distributes USDC rewards to user wallets weekly. Wag3s ingests the Privy wallet list, matches each reward disbursement to the corresponding user ID, and produces a compensation expense schedule per period for the books.
Users earn and spend tokens through Privy embedded wallets. The finance team needs to distinguish user-side transactions (not revenue) from platform-side fee collection. Wag3s uses the Privy user mapping to segregate user activity from treasury activity in the accounting output.
Privy integration questions
How does Wag3s handle PII from Privy user data?
Wag3s processes only the Privy user ID (a non-PII opaque identifier) and the wallet address for attribution purposes. Email addresses and social login details from Privy are never ingested. Data handling is covered under the standard Wag3s Data Processing Agreement.
Does Wag3s support Privy smart accounts (EIP-4337)?
Yes. Privy's embedded smart accounts follow the EIP-4337 standard. Wag3s decodes UserOperations via the EntryPoint contract, presenting them as standard transactions in the accounting output rather than opaque bundle calls.
Can Wag3s handle multiple Privy apps under one workspace?
Yes. Multiple Privy app IDs can be connected to one Wag3s workspace, each with its own user-wallet mapping and configuration. This is the standard setup for companies with a suite of Web3 products sharing a single finance function.
Other connectors that pair with this one.
Connect Privy in minutes
Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.