Dynamic — embedded wallets, books that follow

Dynamic provisions wallets via email, social, or wallet login. We connect their user-to-wallet mapping into the accounting workspace.

identityread-only sync Real-time

Dynamic is a wallet-based authentication and embedded-wallet platform competing with Privy and Web3Auth. The integration profile is similar — ingest user-to-wallet mappings, attribute on-chain activity to user IDs, produce user-attributed reports. Privacy handling per DPA.

What the Dynamic integration does

User-to-wallet mapping

Dynamic-provisioned wallets linked to user IDs.

Multi-environment support

Multiple Dynamic environments under one workspace.

The connection in 4 steps

01

Generate a Dynamic API key

In the Dynamic dashboard, create a server-side API key for your environment. Wag3s requires read access to the users and wallets endpoints. No write or auth-flow permissions are needed.

02

Wag3s imports user-to-wallet mappings

All user IDs and their associated wallet addresses — including embedded wallets and externally-linked wallets — are imported. The mapping is refreshed on a daily schedule.

03

On-chain activity attributed to user IDs

Every on-chain transaction from a Dynamic-provisioned or linked wallet is attributed to the corresponding user ID in Wag3s. Revenue and expense events show the user context, not just the hex address.

04

User-attributed reports exported

Wag3s produces per-user or per-segment reports for the finance team — useful for revenue recognition by user, cohort-level yield analysis, or privacy-respecting B2B invoicing.

Common configurations

Web3 SaaS app billing per-wallet activity

A B2B Web3 SaaS uses Dynamic for user authentication. Customers pay on-chain per transaction or per month. Wag3s attributes each on-chain payment to the correct user ID via the Dynamic mapping, enabling per-customer revenue recognition for the monthly close.

Marketplace with embedded wallets for users

NFT or gaming marketplace provisions embedded wallets via Dynamic for onboarding users without seed phrases. Wag3s ingests the user-to-wallet mapping to attribute marketplace fee revenue and royalty flows to specific user accounts, useful for 1099 reporting at year-end.

Dynamic integration questions

How does Wag3s handle users who link multiple wallets via Dynamic?

Dynamic allows a single user ID to link multiple wallets (embedded + external). Wag3s ingests all wallet addresses for a given user and consolidates their on-chain activity under the same user ID in the attribution report.

Is user personal data stored by Wag3s?

No. Wag3s stores the user ID (pseudonymous token from Dynamic) and the wallet address mapping only. No PII (name, email, phone) from the Dynamic user record is imported. The DPA between your organization, Dynamic, and Wag3s governs data handling.

Does the integration work with Dynamic's sandbox and production environments?

Yes. You can connect both sandbox and production environments as separate Wag3s workspaces. Sandbox is useful for testing wallet attribution before going live.

Connect Dynamic in minutes

Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.