Arc 🤝 Dynamic: Better onboarding for apps built on Arc
# Partner Spotlights
# Spotlights
# Payments
# Product Launches
Dynamic gives Arc builders a cleaner way to handle authentication, embedded wallets, and first-session UX.
Tim Baker
Wallet onboarding is still one of the easiest ways to lose users in an onchain app.
You can have the payments flow right, the contract logic right, and the product positioning right, then still lose people because the first session turns into wallet setup, auth friction, and a bunch of context switching before the user has done anything useful.
Dynamic gives builders on Arc a cleaner way to handle authentication, wallet creation, and onboarding. Instead of forcing every team to stitch together login, wallet provisioning, and recovery UX on their own, Dynamic gives Arc builders a more usable default.
Arc is built for onchain finance. That means the ecosystem needs better ways to onboard real users, not just people who already show up with a browser wallet and know exactly what to do. Dynamic helps close that gap with support for email, SMS, social login, passkeys, and external wallet auth, alongside non-custodial embedded wallets and account abstraction support.
The practical value here is pretty simple.
If you are building a payments app on Arc, you can let a user sign up with a familiar login method, create a wallet in the background, and move them straight into sending, receiving, or holding USDC without making wallet setup a separate project.
If you are building a marketplace or merchant flow, you can onboard sellers or operators without forcing them to install an extension before they even understand the product.
If you are building treasury or internal finance tooling, you can keep wallet creation and access inside the product instead of pushing users into disconnected wallet flows.
That is the real point of this integration. Less friction for the user. Less auth and wallet plumbing for the team.
A good way to think about using Dynamic on Arc is this:
Start with Dynamic for authentication and wallet provisioning. Use it to get the user from signup to a live wallet with as little overhead as possible. Then route them directly into the first meaningful onchain action in your product, whether that is a payment, deposit, transfer, or balance flow.
And if you want a more concrete Arc-specific reference point, Dynamic already has a Circle Gateway recipe that includes Arc Testnet in a crosschain USDC flow. That makes the integration story more useful for teams that want to think beyond simple login and into actual movement of funds.
A few examples ideas
1. Consumer payments apps
If you are building a product where the first meaningful action is "send or receive USDC," Dynamic lets you remove a lot of unnecessary wallet setup friction.
A simple flow looks like:
User signs in with email, social, or passkey
Dynamic creates an embedded wallet on Arc
The app routes the user directly into the first payment or balance flow
That is a much better default than asking the user to go find a wallet before they even understand the product.
2. Treasury and operator dashboards
A lot of internal finance tools need faster wallet provisioning, cleaner auth, and better backend visibility.
With Dynamic, you can keep the wallet layer inside the product instead of offloading it to an external extension flow. That is useful for treasury dashboards, payout tooling, settlement consoles, and internal operator workflows where users need to act onchain but should not have to think about wallet setup every time.
3. Marketplaces and payout products
Seller onboarding is one of the best places to use this kind of stack.
Instead of telling a merchant, contractor, or seller to install a wallet before they can receive funds, you can create the wallet as part of onboarding and move them straight into payout settings, balances, and settlement.
