- Bridge SDKs
- Digital Wallets
- Fintechs
- Infrastructure Providers
- Payments
- B2B Payments
- Cross-Chain Transfers
- Payment Settlement
- Arbitrum
- Arc
- Avalanche
- Base
- Celo
- Android
- iOS
- Web
- APAC
- Europe
- LATAM
- Middle East and Africa
- North America
- United States
Passkey-native smart account infrastructure for EVM apps. Give every user a self-custodial account with one-tap onboarding, gasless stablecoin payments, programmable permissions, and ENS identity.
JAW.ID is smart account infrastructure that lets any app give users self-custodial onchain accounts without building wallet infrastructure from scratch.
Users onboard with a fingerprint or Face ID scan. The private key is generated and stored inside the device’s hardware security chip - never exposed, never transmitted, and never held by JAW or any third-party. From the user’s perspective, it feels like signing into a banking app: no seed phrases, no browser extensions, and no prior crypto experience required.
Every JAW.ID account is an ERC-4337 smart account, enabling capabilities that standard EOA wallets cannot offer:
- Gasless Transactions: apps can sponsor gas or users pay fees in digital dollars or any supported ERC-20 token. No one needs to hold ETH.
- Batch Transactions: multiple operations in a single user approval (e.g., approve + swap, mint + transfer) - any combination, atomically.
- Programmable Permissions: spending limits per period, expiry dates, whitelisted contracts, AI agent delegation; rules enforced onchain by the account itself.
- Recurring Payments: users approve a payment schedule once. The app charges within the approved limits on schedule with no repeated wallet confirmations.
- Multi-Chain: one account identity across all EVM-compatible networks.
Integration
JAW.ID is Wagmi-compatible; adding the JAW connector to an existing Wagmi configuration takes only two lines of code. Existing hooks (e.g., useBalance, useSendTransaction, useSignMessage) work unchanged with the only difference being what’s underneath: a smart account instead of an EOA.
Identity Layer
Every account comes with a human-readable ENS name (e.g., alice.yourapp.id) and social profile, issued gaslessly at onboarding through ENS identity SDK - JustaName.id (our ENS infrastructure product and official ENS Service Provider, funded by ENS Labs). There are no hex addresses and the name is portable across any ENS-compatible application.
Built for fintechs, neobanks, dApps, AI agent platforms, and any product that needs to give users self-custodial onchain accounts without 12–18 months of wallet infrastructure development, JAW.ID replaces three vendor integrations - wallet SDK, account abstraction, and identity - with a single, unified SDK.
This site contains content and information, including links to other sites and resources, that was prepared by third parties ("Third Party Content") who are not affiliated with Circle or any of its affiliates (collectively "Circle"). Circle makes no representations on the accuracy, suitability, or validity of Third Party Content. As such, Circle is neither responsible nor liable for any Third Party Content, including any errors, omissions, or delays, or for any actions taken in reliance upon any Thirds Party Content. Reference to any specific company, product, service, or website of any third party does not constitute an implied or express endorsement, recommendation, favoring or validation by Circle. All content provided is for educational and informational purposes only. Circle shall not be liable for any damage or loss relating to use of, or reliance upon, the Third Party Content.