Why traditional wallet onboarding fails
Every step in the classic crypto onboarding flow is a drop-off point:- Installing a browser extension or wallet app
- Generating and safely storing a seed phrase
- Funding a new address before it can do anything
- Switching back and forth between your app and an external wallet
- Approving transactions through an unfamiliar interface
Core features
Passkey authentication
SocketFi uses the WebAuthn standard for authentication. Instead of a password or private key, users prove their identity with a device-backed biometric or PIN. This means:- Phishing resistance — passkeys are bound to your domain and cannot be replayed on another site
- Biometric convenience — Face ID, Touch ID, Windows Hello, and hardware security keys all work out of the box
- No passwords to breach — credentials never leave the user’s device
Embedded smart wallets
Every SocketFi user receives a programmable Soroban smart wallet that is provisioned automatically on first authentication. Because these are smart contract wallets rather than plain externally-owned accounts, they support custom authorization logic, spending policies, contract-aware permissions, and application-specific controls — all without your users needing to understand any of that.Transaction approval
Before any state-changing operation executes, SocketFi presents the user with a clear, hosted approval interface that shows exactly what the transaction does, which assets move, and what fees apply. Users never approve a transaction they haven’t explicitly reviewed.Account recovery
Users can regain access to their wallet if they lose a device, without requiring seed phrases and without replacing the wallet itself. Recovery rotates the wallet’s authentication credentials while preserving the wallet address, balance, and history.Fee abstraction
You choose how fees work for your users. Pay fees on their behalf during onboarding, let users pay with any supported asset, or configure maximum fee caps — all without your users needing to hold native XLM before they can transact.Soroban contract integration
Read and write to any Soroban smart contract directly through the SDK usingreadContract() and requestTransaction(). SocketFi handles transaction construction, signing, submission, and result parsing.
Architecture
Your application talks to the SocketFi SDK, which coordinates with SocketFi’s hosted services. Those services manage the authentication layer, wallet resolution, and policy enforcement before submitting signed transactions to the Stellar network via Soroban smart wallet contracts.Platform components
React SDK
@socketfi/react — authentication, wallet initialisation, transaction approval, and contract reads for React web applications.React Native SDK
@socketfi/react-native — the same surface area as the React SDK, adapted for iOS and Android with Expo support.Server SDK
@socketfi/server — verifyAuth() for validating SocketFi access tokens and protecting your backend APIs.Smart Wallet Contracts
Soroban contracts deployed per user that handle authorization, policy enforcement, transaction execution, and recovery.
What you can build
SocketFi is designed for any application that wants blockchain features without blockchain friction:- Fintech — payments, remittances, savings products, and investment platforms
- Consumer apps — social platforms, creator tools, rewards systems, and loyalty programs
- Gaming — in-game asset ownership, digital item marketplaces, and player-to-player transfers
- Web3 applications — DeFi protocols, NFT marketplaces, and DAO participation
Next steps
Ready to integrate? Follow the steps below in order:- Install the SDK — set up your environment and get your Client ID
- Quick Start — authenticate a user and send a transaction in under 15 minutes
- Production Checklist — review what you need before going live