We checked the sources for this guide on 24 Sept 2026. Use the linked sources for current availability, terms and network details. See subsequent updates
Choose a wallet model by answering who may authorize a payment, who can recover access and how spending rights are removed. “Embedded” describes the experience; it does not answer those control questions.
Start with the user’s job
An external wallet can suit a user who already holds assets and expects to approve each transaction. An embedded wallet can reduce onboarding steps. A server-managed wallet can support a business workflow that needs scheduled or policy-controlled execution. Each choice changes where authorization and recovery belong.
Circle Wallets describes user-controlled and developer-controlled approaches. Arc’s account-abstraction reference lists providers for smart accounts, bundlers, paymasters and signing infrastructure.
| Decision | Question to resolve before integration |
|---|---|
| Authorization | Who signs, and can they sign without the user present? |
| Recovery | Who restores access after a lost device or account lockout? |
| Spending policy | Can permissions limit asset, amount, recipient and duration? |
| Portability | Can the user export or move the account? Under what conditions? |
| Operations | What happens when the wallet provider or signer is unavailable? |
Separate account type from login method
Email, social login and passkeys are authentication mechanisms. The onchain account might still be an externally owned account or a smart account. Check the documented implementation before relying on signatures, session keys or token approvals.
For an agent or recurring payment, define a permission narrower than “sign anything.” Record who granted it, when it expires and how the user revokes it. Make revocation discoverable in the product, then test that a cached session cannot keep spending after revocation.
Decide who funds gas
Arc transaction fees use USDC. Sponsoring those fees can remove a funding step for the user, but the sponsor still needs a funded balance and an abuse policy.
The sponsorship guide distinguishes EIP-3009 transfer relayers, ERC-4337 paymasters and EIP-7702 delegation. Match the route to the actual operation: a transfer-only authorization is different from permission to execute arbitrary calls.
Test the crosschain requirement early
A wallet that can send a normal transaction may still need a different signing flow for a unified balance. The App Kit Unified Balance guide calls out wallet models that need a delegate signer and smart-account deposits that use onchain approval.
Make a proof of concept for your hardest required flow before polishing onboarding. Include a deposit, a spend, a rejected action and a recovery path. Keep the exact wallet type, adapter, chain and SDK version in the test notes so the result can be reproduced after an upgrade.
Sources & references
Documents cited in this guide.