use-user-controlled-wallets

Create a user-controlled wallet by initializing the backend client with your API key, creating a user and session token, then calling createUserPinWithWallets to get a challengeId. The frontend Web SDK executes that challenge so the user approves wallet creation through Circle's hosted UI.

Configure your OAuth client ID in the Circle Developer Console, create a device token via createDeviceTokenForSocialLogin, then initialize the W3SSdk with a login callback and call performLogin. After OAuth redirect, the callback returns userToken and encryptionKey for wallet creation.

EOA accounts have no creation fees, broader chain support including Solana and Aptos, but require native tokens for gas. SCA accounts use ERC-4337 account abstraction with gas sponsorship and batching, but are EVM-only and costly on Ethereum mainnet.

The execute method silently fails if sdk.getDeviceId() was not called after SDK initialization, since that call establishes a session with Circle's service. Also ensure sdk.setAuthentication with userToken and encryptionKey is called before execute.

No. Developers can read wallet data and transaction history but cannot access private keys or act on a user's behalf. Account recovery depends entirely on the user re-authenticating with their original PIN, email, or social account.

Poll circleClient.getTransaction with the userToken and transaction ID until a terminal state is reached. The happy path moves from INITIATED through CLEARED, QUEUED, SENT, and CONFIRMED to COMPLETE, while FAILED, DENIED, and CANCELLED are terminal failure states.