OMS Wallet SDKs

OMS Wallet SDKs provide the same wallet model across TypeScript, React Native, Swift, and Kotlin. Choose the SDK for your application runtime, then follow that SDK’s quickstart and workflow pages.

​

SDK model

Create one OMSWallet entry point from your publishable key. It exposes two clients: Authentication establishes a credential. Automatic wallet selection then selects or creates an Ethereum, Solana, or Tron wallet and starts the active wallet session; when the user owns no wallet of the requested type, the SDK first claims a wallet your project preallocated for the user’s email. Manual selection leaves authentication pending until the application selects, creates, or imports a wallet. For native Swift, Kotlin, and React Native applications, prefer OIDC ID-token authentication when the provider SDK returns an ID token. Use redirect authentication when sign-in must run through a browser. Fixed OMS relay providers and custom OIDC providers are separate configurations.

​

Choose an SDK

Expo Go cannot load the React Native SDK because it contains native code. Use an Expo development build or a bare React Native application.

​

Common workflows

Each SDK documents the same sequence of developer decisions:

1. Authenticate the user and activate a wallet.
2. Restore and manage the wallet session, imported wallets, and direct or remote access grants.
3. Send EVM transactions, Solana transfers, or Tron transactions through the prepare, fee-selection, execute, and status lifecycle.
4. Sign and verify EVM, Solana, or Tron messages, and sign and verify EIP-712 typed data for Ethereum wallets or TIP-712 typed data for Tron wallets.
5. Read EVM balances and transaction history, or Solana and Tron balances, for any address.