Wallets

Wallets overview table

Category guide

• User Wallets: These are traditional consumer-facing wallets such as mobile apps, browser extensions, or exchange-linked wallets. They allow users to hold USDT, make transfers, connect to dApps, and interact directly with Stable.
• Wallet SDK: A software development kit that provides developers with prebuilt tools, APIs, and infrastructure to integrate wallet creation, key management, transaction signing, and blockchain interactions directly into their applications.
• Custodial / Institutional Wallets: Platforms providing regulated, enterprise-grade asset custody for institutions. These solutions focus on compliance, governance controls, secure key management, and treasury operations rather than end-user flows.
• Embedded / In-App Wallets: Wallets generated inside applications through SDKs or backend systems. These enable seamless onboarding for mainstream users without requiring them to install or understand external crypto wallets.
• Smart Wallets / Account Abstraction: Programmable wallets that support custom logic such as gasless transactions, bundled operations, or automated execution. These extend basic wallet functionality with developer-defined behaviors.
• MPC Wallet Providers: Key-management systems using multi-party computation (MPC) to distribute private key control across multiple parties or devices. Ideal for apps or enterprises needing high-security custody without traditional seed phrases.
• Connectivity Providers: Protocols such as WalletConnect (Reown) that connect wallets and dApps. They don't store assets or act as wallets themselves; instead, they provide secure communication channels for transaction signing and interaction.

1. User wallets

These are end-user wallets offered by major global exchanges. They allow users to hold USDT, transfer funds, and connect to applications on Stable.

Stable Pay

A non-custodial payment wallet built on Stable, designed for fast, stablecoin-native transactions. Stable Pay delivers instant USDT payments, predictable fees, and a simple user experience optimized for everyday transfers and commerce.

• Non-custodial wallet for Stable
• Instant USDT payments
• Predictable and consistent transaction costs
• Built directly on Stable’s USDT-native settlement layer
• Consumer-friendly UI designed for payments and commerce

Binance Wallet

A widely used multi-chain wallet integrated with the world’s largest exchange by volume.

• Supports Stable USDT
• Direct integration with Binance ecosystem
• Mobile and extension wallet options

Bitget Wallet

A multi-asset wallet connected to the Bitget exchange ecosystem, supporting crypto, stocks, and ETFs.

• Supports Stable USDT
• Built-in dApp browser
• Seamless integration with Bitget trading accounts

Gate Wallet (Gate Onchain)

A wallet product backed by one of the largest spot exchanges globally.

• Supports Stable USDT
• Easy transfers between Gate exchange and wallet
• dApp and web-app connectivity

OKX Wallet (OKX Onchain)

A powerful, multi-chain wallet used globally.

• Supports Stable USDT
• Deep OKX ecosystem integration
• Web, mobile, and extension wallet options

Atomic Wallet

A non-custodial multi-asset wallet available on desktop, mobile, and as a browser extension. Atomic Wallet integrates the Simplex by Nuvei on-ramp, so users can buy USDT on Stable directly inside the app with cards, Apple Pay, Google Pay, or bank transfer.

• Holds, sends, and receives USDT on Stable
• Private keys stored locally on the user device
• In-app buy flow for USDT on Stable via Simplex
• Available on Windows, macOS, Linux, iOS, Android, and Chrome

Get started: Download Atomic Wallet from atomicwallet.io, add Stable as a network, and use the in-app Buy flow to purchase USDT on Stable through Simplex.

2. Wallet SDK

Development Kit by Tether (WDK)

An open-source SDK from Tether for building self-custodial wallets across any platform and blockchain.

• Multi-Chain Support: Bitcoin, Ethereum, TON, TRON, Solana, Spark, and more
• Agentic Wallets: Native support for AI agent wallets and x402 payments on Stable
• DeFi Integration: Plug-in support for swaps, bridges, and lending protocols
• Extensible Design: Add custom modules for new blockchains or protocols

Get started: Install @tetherto/wdk and @tetherto/wdk-wallet-evm, then follow the WDK documentation to configure Stable as your target chain.

3. Custodial & institutional wallets

Anchorage

A federally chartered national bank providing institutional-grade custody for digital assets.

• Secure custody for Stable USDT
• Full compliance and regulatory oversight
• Enterprise-grade key management and access controls

4. Embedded / in-app wallets

Wallets embedded directly into applications via SDKs, enabling seamless user onboarding and payment flows.

Coinbase Developer Platform (CDP)

CDP provides non-custodial wallets for user-facing apps and backend systems. User-auth wallets use email, SMS, or social sign-in. API-key wallets let servers manage accounts while CDP protects private keys inside a trusted execution environment.

• Embedded wallets with no seed phrase
• API-key wallets for automated workflows and backend services
• EVM account creation and transaction signing
• Key export for user-controlled wallets

Coinbase Wallet API supports Stable because it supports all EVM-compatible networks. Configure Stable with chain ID 988 and https://rpc.stable.xyz, or sign with CDP and broadcast through Stable's RPC.

Coinbase Onramp is a separate product for fiat-to-crypto conversions and does not support Stable.

Get started: Follow the CDP non-custodial wallet documentation and choose the user-auth or API-key quickstart.

Dynamic

Enterprise-grade wallet infrastructure serving thousands of applications and over 40M users.

• Wallet creation and authentication
• Embedded wallet flows
• User onboarding for apps and fintechs

Get started: Follow the Dynamic SDK setup docs to install the SDK and configure Stable as a supported network in your app.

Privy

Privy provides embedded wallets for users, organizations, treasuries, and agents. Wallets can use non-custodial or custodial configurations.

• Authentication with email, social login, passkeys, or external wallets
• Embedded EVM wallet creation and transaction signing
• Policy controls for signers, recipients, contracts, and transfer amounts
• User-controlled key export for non-custodial wallets

Get started: Follow the Privy embedded wallet docs to create a wallet, then configure Stable as an EVM network in your app.

Portal

Portal provides MPC wallets through SDKs for web, iOS, Android, and React Native, plus an API for server-side integrations. MPC, or multi-party computation, splits signing authority across separate key shares.

• Embedded EVM wallet creation, backup, and recovery
• Message and transaction signing
• Custom RPC configuration for EVM networks
• Web, mobile, and API integration options

Get started: Follow the Portal SDK quickstart, then map Stable's CAIP-2 chain ID (eip155:988) to https://rpc.stable.xyz in rpcConfig.

Turnkey

Turnkey provides embedded wallets with signing and policy evaluation inside trusted execution environments (TEEs). A TEE is an isolated hardware-backed environment that protects keys during signing.

• Authentication with email, phone, social login, passkeys, or biometrics
• Embedded wallets across EVM-compatible networks
• Non-custodial, custodial, and hybrid custody models
• Programmable signing policies and per-user isolation

Get started: Follow the Turnkey embedded wallet overview, choose an SDK, and configure Stable as an EVM network.

Reown (formerly WalletConnect)

A widely adopted standard for connecting wallets to applications.

• Secure wallet-to-dApp connections
• Supports mobile, desktop, and extension wallets
• Broad ecosystem compatibility

Stable supports integrations with the Reown SDK to help developers deliver seamless wallet and onboarding experiences for users.

Reown provides an open-source, all-in-one SDK that serves as the official gateway to the WalletConnect Network. It enables smooth wallet connections, transactions, logins, embedded wallets (email and social login), on-chain payments, in-app swaps, and more within your application.

• Visit Reown's documentation: https://docs.reown.com/overview

5. Smart wallets & account abstraction

Infrastructure enabling programmable wallets, gasless transactions, spending rules, and advanced UX.

Overview table

Alchemy

Alchemy provides the core AA infrastructure and APIs needed to deploy smart accounts, sponsor gas, and build consumer-grade wallets.

• Smart account SDK & APIs
• Paymaster support for gasless actions
• Gas abstraction tooling
• Scalable infra for smart wallet developers

Get started: Use the Alchemy smart account SDK to deploy ERC-4337 smart accounts and configure a paymaster for sponsored gas on Stable.

Docs
https://docs.alchemy.com

Holdstation

A smart contract wallet offering account abstraction and biometric-secured interactions.
Capabilities

• Full AA-enabled smart wallet
• Gasless transactions and sponsored fees
• Biometric authorization and session keys
• Integrated trading and DeFi execution layer

Get started: Explore the Holdstation developer docs to integrate smart wallet flows and sponsored transactions into your application.

Daimo

A consumer-grade, account-abstraction wallet designed for instant stablecoin spending and payments.
Capabilities

• AA-based UX with smart wallet execution
• One-click payments across any chain
• No seed phrases; secure key recovery
• Ideal for payments apps and stablecoin utilities

Get started: Visit the Daimo Pay documentation to add one-click stablecoin payment flows to your application on Stable.

Safe

A Safe is a smart contract account that executes a transaction only after a set number of its owners approve it. This is called an m-of-n multisig: any m of the n owners must sign. Owners can be EOAs, hardware wallets, or other Safe accounts, and modules and guards add programmable logic such as spending limits or recovery.

• Multisig smart accounts with a configurable signature threshold
• Batched transactions, so several calls settle atomically in one transaction
• Modules and guards for spending policies, recovery, and automation
• Owner and threshold changes without moving assets to a new address
• ERC-1271 contract signatures and off-chain signature collection
• Passkey owners, so a Safe can be signed with a device biometric or security key instead of a seed phrase
• ERC-4337 execution through the Safe4337Module, for bundled user operations and sponsored gas
• Safe{Core} SDK kits for account deployment, transaction proposal, and indexing

Safe supports Stable as a network in Safe{Wallet}, the Safe{Core} SDK, and the Safe Transaction Service. The chain prefix is stable, so a Safe address is written stable:0x… and opens at https://app.safe.global. The Transaction Service for Stable runs at https://api.safe.global/tx-service/stable, which is what the API Kit uses when you pass chain ID 988.

The canonical contracts are deployed at their deterministic addresses for versions 1.3.0, 1.4.1, and 1.5.0, so tooling that hardcodes Safe addresses works on Stable without a custom deployment. The 1.4.1 addresses are:

Fund the Safe with USDT0 before your first transaction, since USDT0 is the gas asset on Stable.

A passkey owner is a WebAuthn credential, such as a device biometric or a security key, that signs on behalf of the Safe. SafeWebAuthnSignerFactory deploys a signer contract for a credential's public key, and that contract is then added as a Safe owner. SafeWebAuthnSharedSigner is the alternative when you want a passkey owner without deploying a contract per credential. Both are deployed on Stable, along with the Daimo P-256 verifier that the signer configuration points to for signature checks.

Safe4337Module is deployed on Stable and is enabled on a Safe as both a module and a fallback handler, which lets the account execute user operations through an ERC-4337 bundler with an optional paymaster for sponsored gas. SafeModuleSetup enables the module during Safe deployment. The module targets EntryPoint v0.7; EntryPoint v0.6 is also deployed for older tooling.

Get started: Create an account in Safe{Wallet} and select Stable as the network, or use the Safe{Core} Protocol Kit with https://rpc.stable.xyz to deploy and operate a Safe from your own application.

Stable network setup

Adding Stable to your wallet

• Network Name: Stable
• Chain ID: 988
• Currency: USDT0
• RPC URL: https://rpc.stable.xyz
• Block Explorer: https://stablescan.xyz

Building wallet integrations

You can add Stable support by:

• Enabling signing and gas estimation via Stable RPC
• Supporting USDT-native transfers
• Integrating WalletConnect for dApps
• Adding Stable to chain lists or metadata registries

Have a wallet integrating Stable?

You can reach the team at bizdev@stable.xyz to be listed in this section.