# Para - Full Text: Pillar Guides and Buyer Guides > Plain-markdown full text of Para's core embedded wallet and wallet-as-a-service guides, for LLM retrieval and citation. --- # What Are Embedded Wallets? The Complete Guide (2026) URL: https://www.getpara.com/blog-posts/embedded-wallets-101 For most of crypto's history, the first thing an app asked a new user to do was the hardest thing about crypto. Install an extension. Write down twelve words. Never lose them. Fund the wallet with gas before doing anything useful. A huge share of would-be users quit right there, and the app never saw them again. Embedded wallets remove that wall. A user signs up with an email address or a passkey and gets a working crypto wallet in seconds, inside your product, under your brand. For founders, that is the difference between a funnel that leaks at the front door and one that converts like a normal signup. For developers, it means shipping wallet features without becoming a cryptography team. This guide covers what embedded wallets are, how they work, how the security models compare, and how to choose and ship one. ## What is an embedded wallet? An embedded wallet is a crypto wallet that lives inside an application rather than as a separate extension or standalone app. The user signs in with a familiar method, email, a social account, or a passkey, and the wallet handles key generation and transaction signing in the background. There is no seed phrase to record and nothing to install. To the user, it feels like an account, not a wallet. That last point is the whole idea. The wallet becomes invisible. Someone using a payments app or a game does not think about private keys any more than they think about the database behind their bank balance. The crypto is there, they control it, and the mechanics stay out of the way. Embedded wallets pair naturally with [wallet-as-a-service infrastructure](/blog-posts/what-is-wallet-as-a-service), which is the developer-facing layer that provisions and secures those wallets through an API. The user experiences an embedded wallet. The team building the app buys wallet-as-a-service to power it. ## Why embedded wallets exist Embedded wallets exist to fix onboarding. Traditional external-wallet flows lose a large majority of new users at the install-and-back-up step, because managing a seed phrase is genuinely hard and the stakes are permanent. Every dropped user is lost revenue and a smaller network. Embedded wallets close that gap by mapping crypto onboarding onto login patterns people already know. Seed phrases are the specific villain here. A twelve or twenty-four word recovery phrase is a single, unrecoverable secret. Lose it and the funds are gone. Leak it and they are stolen. Asking mainstream users to safeguard one perfectly, forever, was never realistic. Embedded wallets replace that burden with authentication and cryptography that recover gracefully when a user changes phones or forgets a password. There is a business reason too, beyond conversion. When wallets live inside your app, you own the relationship, the branding, and the data about how people use your product. You are not sending users out to a third-party wallet and hoping they come back. The economics follow directly from the funnel. If external-wallet onboarding loses the majority of new users at setup and an embedded wallet keeps conversion close to a normal social login, the difference compounds through every downstream metric: activation, retention, and revenue per user. A founder does not need a crypto thesis to care about that. It is the same reason fintechs obsess over reducing signup steps. Every removed point of friction is users who make it to the part of the product that actually earns money. ## How embedded wallets work Embedded wallets work by turning a normal login into a secure signing key without ever showing the user a private key. The flow has three stages: authentication, key generation, and signing. Understanding these stages helps you evaluate providers, because the differences between them are mostly hidden in stage two. ### Authentication The user signs in with email, a social provider, a phone number, or a passkey. This looks identical to a Web2 login. No wallet popup, no "connect wallet" button, no browser extension. The authentication method establishes who the user is so the wallet layer can associate the right keys with them. ### Key generation Once the user is authenticated, the wallet needs a key to sign transactions. The strongest providers use multi-party computation (MPC) so that the private key is never created or held in one piece. Para, for example, uses Distributed Key Generation: independent key shares are generated separately and never combined. One share lives on the user's device, protected by a secure enclave through a passkey; another lives in Para's infrastructure. Because the full key is never assembled, there is no single secret to steal or lose. ### Signing To send a transaction, the shares cooperate to produce a valid signature without ever reconstructing the whole key. The app calls a sign method, the MPC protocol runs, and the signed transaction is broadcast to the relevant chain. Good SDKs hide the chain-specific details, so the same signing call works whether the transaction lands on an EVM chain, Solana, or Cosmos. If you want the mechanics in depth, see our explainer on [MPC wallets](/blog-posts/what-is-an-mpc-wallet). ## Embedded wallets vs. external wallets The clearest way to place embedded wallets is next to their opposite. An external wallet is installed and managed by the user. An embedded wallet is provisioned by the app and feels like part of it. Neither is strictly better. They serve different users, and plenty of apps offer both. | | Embedded wallet | External wallet | |---|---|---| | Who manages it | The app, on the user's behalf | The user | | Setup | Email, social, or passkey in seconds | Install app or extension, back up seed phrase | | Seed phrase | None shown to the user | User records and safeguards it | | Best for | Mainstream users, new-to-crypto audiences | Crypto-native users who already have one | | Branding | Your app's UI | The wallet provider's UI | | Portability | Depends on provider design | User carries it across any app | Most consumer apps benefit from an embedded wallet as the default, with the option to connect an external wallet for users who prefer one. Para supports both, including connecting external wallets like Phantom on mobile. For a deeper breakdown, read [embedded vs. external wallets](/blog-posts/embedded-vs-external-wallets). ## Embedded wallet security models Security is where embedded wallet providers actually differ, and it deserves scrutiny. The core question is simple: who can access the private key, and under what conditions? Several architectures answer it differently. | Security model | How it works | Trade-off | |---|---|---| | Multi-party computation (MPC) | Key split into shares held by different parties; signing is collaborative; the full key is never assembled | Strong and non-custodial when shares are well distributed; implementation quality matters | | Threshold signatures (TSS) | An MPC variant where a set threshold of shares must cooperate to sign | Flexible thresholds; still depends on where shares live | | Secure enclave | Key material isolated in device hardware (Face ID, Touch ID) | Excellent per-device protection; usually paired with another layer for recovery | | Smart contract wallets | Access controlled by onchain programmable logic rather than a single key | Enables recovery and policies; adds gas and contract-level considerations | The strongest designs combine approaches. Para pairs Distributed MPC with device secure enclaves through passkeys, so the key never exists in full and one share is bound to hardware the user already trusts. That combination gives you strong cryptographic guarantees and a login that feels ordinary. Para is non-custodial by design, independently audited by Least Authority, and SOC 2 Type II compliant. If passkeys are new to you, our guide on [passkey wallets](/blog-posts/what-are-passkey-wallets) walks through how they replace seed phrases. A useful way to pressure-test any of these models is to ask what happens in the worst case. If the provider's servers are breached, can an attacker reach a complete key? With well-distributed MPC, one compromised share is not enough to sign. If a user's login is phished, does the wallet fall too? When a key share is bound to a device secure enclave through a passkey, a stolen password alone does not unlock the funds. If the provider vanishes overnight, can users still reach their assets? A non-custodial design with key export says yes. These questions matter more than any marketing claim, because they describe how the system behaves when something goes wrong rather than when everything goes right. ## What to look for in an embedded wallet provider When you evaluate providers, push on a handful of dimensions that tend to reveal the real differences. Start with the security model: do keys ever exist in full, and can the provider or the app move funds without the user? Then check chain coverage, platform coverage across web, mobile, and server, authentication options, exportability, compliance, and pricing structure. Portability deserves special attention. Some embedded wallets only work inside the single app that created them, which locks users in and resets onboarding every time they move. Para wallets are portable across every Para-integrated app, so a user onboards once and carries the same wallet everywhere. We cover the full evaluation process in [how to choose an embedded wallet provider](/blog-posts/how-to-choose-embedded-wallet-provider), including a printable checklist and a list of red flags. ## Embedded wallet use cases by vertical Embedded wallets show up across very different products, and the reason they help changes with the vertical. **Fintech.** Neobanks and payment apps use embedded wallets to add stablecoin balances and onchain payouts without asking customers to understand crypto. The wallet sits under existing account UX, and compliance-ready infrastructure handles the parts that would otherwise require a wallet team. **Payments and stablecoins.** Remittance and payout products need a wallet for every user or every corridor, created programmatically. Embedded wallets make that a single API call rather than an engineering project. Our guide to [wallet-as-a-service for remittance businesses](/blog-posts/wallet-as-a-service-for-remittance-businesses) goes deeper on this pattern. **Gaming.** Games live and die on onboarding speed. Making a player install an extension before they can play is a funnel killer. Embedded wallets let someone start playing in seconds and pick up items, points, or tokens along the way. **AI agents.** Autonomous agents that pay for services or manage funds need wallets they can operate programmatically, with policy controls that define exactly what is allowed. Embedded wallet infrastructure with an API-first design fits this cleanly. ## What integration actually looks like For developers, the practical question is how much work an embedded wallet adds to a build. With a good provider, less than you would expect. The typical shape is: install the SDK, wrap your app in a provider component, drop in an authentication modal, and call a method to create a wallet and another to sign a transaction. The MPC and chain-specific logic stay inside the SDK, so your code reads like ordinary application code rather than cryptography. A basic integration can be running in minutes, with a prototype auth flow and a working wallet. A production integration, with custom branding, error handling, and the edge cases that only show up with real users, usually takes one to two weeks. The libraries you already use tend to work as-is: an embedded wallet from Para plugs into ethers, viem, and wagmi on EVM, and the equivalent tooling on Solana and Cosmos, so you are not rewriting your app around the wallet. If you build in React, our [step-by-step React guide](/blog-posts/add-embedded-wallets-react) walks through each call with real code. ## Where Para fits Para is wallet infrastructure for teams that want embedded wallets without the trade-offs that usually come with them. Wallets are non-custodial, powered by Distributed MPC so private keys never exist in full, and portable across every Para-integrated app so users onboard once and keep the same wallet everywhere. Concretely, Para supports EVM chains, Solana, and Cosmos through a single SDK, with Stellar and other networks available too. Authentication covers email, phone, social login, and passkeys. There are SDKs for web (React, Next.js, Vue, Svelte), mobile (React Native, Expo, Flutter, Swift), and server (Node.js), plus Telegram and browser extensions. Para is SOC 2 Type II compliant, audited by Least Authority, and runs at real scale, with 15M+ wallets across partners including ENS, Vana, and Camp Network. You can start building from the [Para docs](https://docs.getpara.com) or see plans on the [pricing page](/pricing). ## Frequently asked questions ### What is an embedded wallet? An embedded wallet is a crypto wallet that lives inside an app instead of a separate extension or standalone app. Users sign in with email, a social account, or a passkey, and the wallet handles key generation and signing behind the scenes. There is no seed phrase to write down and nothing to install. ### Are embedded wallets safe? A well-built embedded wallet can be very safe. The strongest designs use multi-party computation, so the full private key is never assembled in one place, and pair it with device secure enclaves through passkeys. Look for a provider that is non-custodial, independently audited, and SOC 2 Type II compliant. ### Are embedded wallets custodial? Not necessarily, and the best ones are non-custodial. Custody depends on who can access the keys. With Para's Distributed MPC, private keys never exist in full, and neither Para nor the app can move a user's funds. Always confirm the custody model before you integrate, because it varies by provider. ### What is the difference between an embedded wallet and an external wallet? An external wallet, like a browser extension or a mobile wallet app, is installed and managed by the user. An embedded wallet lives inside your app and feels like a normal account. External wallets suit crypto-native users who already have one. Embedded wallets suit everyone else, and many apps offer both. ### How much do embedded wallets cost? Pricing usually follows a monthly active user model. Some providers add per-transaction fees on top, which can grow unpredictably at scale. Para charges per monthly active user with no transaction fees and a free tier, so costs track your growth rather than spiking with usage. ### Can users export their keys from an embedded wallet? With a genuinely non-custodial provider, yes. Users can export their keys and move to self-custody or another provider without asking permission. Exportability is one of the clearest signals that a wallet is truly non-custodial, so ask any provider how it works before committing. --- # What Is Wallet-as-a-Service (WaaS)? The 2026 Guide URL: https://www.getpara.com/blog-posts/what-is-wallet-as-a-service Every crypto-enabled app needs a wallet. Building one in-house means months of cryptographic engineering, recurring security audits, and compliance work that has nothing to do with the product you actually want to ship. Wallet-as-a-service exists to take that off your plate. The model mirrors how Stripe abstracted payments and Twilio abstracted messaging. Your app owns the user experience. The provider owns the cryptographic backend: key generation, distributed signing, secure storage, chain interactions, and recovery. This guide explains what wallet-as-a-service is, how it works, who needs it, how to weigh building versus buying, and how to evaluate providers without getting locked in. ## What is wallet-as-a-service? Wallet-as-a-service (WaaS) is developer infrastructure that lets you create, manage, and operate crypto wallets inside your own app through an API. Instead of building key management, transaction signing, recovery, and multi-chain support from scratch, your team integrates a provider's SDK and ships wallet features in days rather than months. The provider handles the cryptography and the chain plumbing. You handle your product. A complete WaaS platform typically bundles wallet creation via REST API or SDK, key management, authentication across email, social, phone, and passkeys, multi-chain support, transaction signing and broadcasting, recovery so users do not lose access, and compliance tooling. In 2026, the category has matured well past simple custodial key vaults. Modern platforms like Para deliver non-custodial embedded wallets with MPC key management, passkey authentication, a policy engine, and money movement, all through a single integration. Three trends turned WaaS from a nice-to-have into core infrastructure. Stablecoins went mainstream, so fintechs, neobanks, and payment processors all suddenly needed wallets to hold and move digital assets on behalf of users. Onboarding stayed the industry's hardest problem, and WaaS is the cleanest way to erase the seed-phrase-and-extension friction that kills conversion. Wallets also stopped being purely human: trading bots and payment agents now need to hold funds and transact programmatically, which requires exactly the API-first, policy-controlled infrastructure WaaS provides. Each trend points at the same conclusion. Wallets are becoming a default component of software, and few teams want to build that component from scratch. ## Wallet-as-a-service vs. embedded wallets These two terms travel together and get blurred, so it helps to separate them cleanly. Wallet-as-a-service is the infrastructure a developer buys. An [embedded wallet](/blog-posts/embedded-wallets-101) is what the end user experiences: a wallet that lives inside the app and feels like a normal account. WaaS is the engine; the embedded wallet is the result. Put differently, the developer buys WaaS and the user gets an embedded wallet. A single provider's WaaS can power embedded wallets across many different apps. It also often powers more than embedded wallets: the same infrastructure can provision server-side wallets for treasury or agents, connect existing external wallets, and manage policy across all of them. So the two concepts overlap heavily, but they are not the same layer. If you only remember one thing: users never buy WaaS, and developers never ship a bare "embedded wallet" without infrastructure underneath it. ## How wallet-as-a-service works Every WaaS platform solves the same core problem: how do you generate, store, and use private keys securely without asking users to manage them? The answer has three layers. We will use Para's architecture as the reference, since it reflects how the strongest providers are built. ### The authentication layer When a user signs up, the provider authenticates them with whatever method you configured: email one-time code, Google or Apple sign-in, a passkey, or a phone number. To the user it looks like an ordinary Web2 login. No seed phrase, no extension, no third-party popup. Para handles this with a prebuilt, customizable flow or fully headless APIs when you want to own the UX end to end. ### The key management layer This is where providers differ most, and where your evaluation should focus. There are three dominant approaches in 2026. Server-side custody has the provider hold the key and sign on the user's behalf. It is operationally simple but creates a trust dependency and a high-value target. MPC (multi-party computation) never assembles the key in one place: it is split into shares across the user's device, the provider's infrastructure, and sometimes a recovery share, and a threshold of shares cooperates to sign. Smart account abstraction makes the wallet a smart contract governed by programmable logic rather than a single key. Para uses Distributed MPC paired with passkey authentication. Key shares are generated independently through Distributed Key Generation and are never combined. The user's share sits in a hardware-backed secure enclave via a passkey, which decouples wallet access from the login itself. Even if a social login is compromised, the wallet stays safe, because the attacker cannot reach the device-bound share. The design is non-custodial: neither Para nor the app developer can access keys, and users can export and exit at any time. Our [MPC wallet explainer](/blog-posts/what-is-an-mpc-wallet) and [custodial vs. non-custodial guide](/blog-posts/custodial-vs-non-custodial-wallets) go deeper on both points. ### The signing and policy layer Once authenticated, the user signs transactions through your app. The SDK sends a signing request, the shares cooperate to produce a signature, and the transaction is broadcast to the right chain. Good platforms abstract chain-specific differences, so the same call works across EVM, Solana, and Cosmos without chain-specific code. On top of signing, a policy engine lets you define programmable rules: spending caps, whitelisted destinations, approval workflows, and role-based access. These controls become essential as apps scale and as wallets start being operated by agents rather than people. ### The money movement layer A wallet that can only hold assets has limited value. The strongest WaaS platforms bundle money movement directly: on-ramps to convert fiat to crypto, off-ramps to convert back, bridging across chains, and token swaps. Done well, these hide the underlying liquidity providers, compliance checks, and cross-chain complexity behind the same API you already use for wallets. That turns a payout, a top-up, or a cross-chain transfer into a single call rather than a separate integration with its own vendor, contract, and failure modes. For fintech and stablecoin products in particular, this is often the difference between shipping a complete financial flow and stitching one together from four services. Para bundles money movement into the platform so developers can offer full flows without integrating a separate provider for each function. ## Who needs wallet-as-a-service? A quick test: do you have a dedicated cryptography team, six or more months to spend before launch, and ongoing budget for audits and multi-chain engineering? If not, WaaS is the right call. More specifically, it fits a handful of clear profiles. **Fintechs** adding stablecoin balances, cross-border payouts, or onchain treasury features get compliance-ready wallet infrastructure without becoming a wallet provider. Para has a dedicated [fintech product](https://www.getpara.com/fintech) for this. **Stablecoin and remittance apps** need a wallet for every user or corridor, created programmatically, plus on and off-ramps and monitoring. Our [remittance guide](/blog-posts/wallet-as-a-service-for-remittance-businesses) covers this end to end. **Marketplaces and consumer apps** need Web2-grade onboarding. External-wallet connection flows lose most new users at the install step; embedded wallets keep conversion near normal signup rates. **AI agents and autonomous systems** need wallets they can operate through an API, with policy controls that define exactly which transactions are allowed. WaaS provides the API-first foundation these agents require. **Ecosystems and identity apps** give every user a wallet for governance, identity, or portability. ENS chose Para so anyone could claim an ENS name without a wallet installed beforehand, then carry that identity into any other app. The common thread across all of these is that the wallet is a means, not the product. A remittance company sells fast, cheap transfers. A game sells fun. A fintech sells a better account. In each case the wallet has to be excellent and invisible, which is precisely what WaaS is for. ## Developer experience and SDKs Integration speed is a real evaluation criterion, not a footnote. The gap between a provider you can wire up in an afternoon and one that consumes a sprint is the difference between shipping and stalling. What matters is first-class SDK coverage for your actual stack, current documentation, and sensible defaults you can override rather than fight. The strongest platforms cover web, mobile, and server through one coherent API. Para, for example, ships SDKs for React, Next.js, Vue, and Svelte on web; React Native, Expo, Flutter, and Swift on mobile; and Node.js on the server, plus Telegram and browser extensions. A basic integration runs in minutes, and the SDKs work with the libraries teams already use, ethers, viem, and wagmi on EVM and the equivalents on Solana and Cosmos, so you are not rebuilding your app around the wallet. If you build in React, our [React integration guide](/blog-posts/add-embedded-wallets-react) walks through the calls with working code. ## Build vs. buy, in brief Building wallet infrastructure in-house means committing to maintain it indefinitely. Every chain upgrade, transaction-format change, or vulnerability patch pulls your team off product work. Key management bugs carry existential risk, since one flaw can drain user funds. WaaS shifts that burden to a specialist: multi-chain support works from day one, security patches ship automatically, and the infrastructure scales with your user base. The short version is that if wallet infrastructure is not your core product, it should not be your core engineering investment. Building can still be the right answer in specific cases, and we lay out the full trade-off in [wallet infrastructure: build vs. buy](/blog-posts/build-vs-buy-wallet-infrastructure). ## How to evaluate providers Press on the security model first: MPC, TSS, HSM, or hybrid, and where the key shares live. Confirm the provider is non-custodial, meaning it genuinely cannot move user funds, and ask which third-party audits it has published. From there, check chain coverage against what you will need in a year, SDK quality and framework support, authentication options, recovery flows, portability, compliance, and pricing structure. Portability is the criterion most teams underweight and later regret. Many wallets only work inside the single app that created them, which locks users in and resets onboarding every time. Para wallets are portable across every Para-integrated app, so users onboard once and keep the same wallet everywhere. For the full process, including a printable checklist and red flags, see [how to choose an embedded wallet provider](/blog-posts/how-to-choose-embedded-wallet-provider), and for the underlying stack, see [what is wallet infrastructure](/blog-posts/what-is-wallet-infrastructure). ## Pricing models in the market WaaS pricing generally falls into two shapes. Per-monthly-active-user pricing charges for the people who actually use their wallet in a given month, which makes costs predictable and ties them to engagement. Per-transaction pricing charges for each signed transaction, which can look cheap early and turn punitive once volume climbs. Some providers layer the two, or add fees for money movement, extra chains, or enterprise features. Get a quote at both your current volume and ten times that before signing anything. Para uses per-monthly-active-user pricing with no transaction fees and a free tier, so the model stays predictable as you grow. You can see the details on the [pricing page](/pricing). ## Para's approach Para is wallet-as-a-service built around a thesis most providers have not caught up to: users should not need a new wallet for every app. Traditional WaaS creates an isolated wallet inside each app. Para creates a portable wallet that works across every Para-integrated app, so a user's identity, assets, and history travel with them. That is why teams like ENS chose Para: users can claim an ENS name without a pre-existing wallet, then carry that identity anywhere. Underneath, Para runs Distributed MPC with passkey authentication, so private keys never exist in full and one share is bound to the user's device. It supports EVM chains, Solana, and Cosmos through a single SDK, with Stellar and additional networks available, plus money movement and a programmable policy engine in the same integration. Para is non-custodial, SOC 2 Type II compliant, and audited by Least Authority, and it runs at scale with 15M+ wallets across partners including the Ethereum Foundation, ENS, Vana, and Camp Network. You can start free with no sales call at the [Para docs](https://docs.getpara.com), and integrate embedded wallets in minutes rather than months. ## Frequently asked questions ### What is wallet-as-a-service? Wallet-as-a-service (WaaS) is developer infrastructure that lets you create, secure, and operate crypto wallets inside your app through an API. Instead of building key management and multi-chain support yourself, you integrate a provider and ship wallet features in days. It powers the embedded wallets your users see. ### Is wallet-as-a-service custodial or non-custodial? It depends on the provider. The strongest modern platforms are non-custodial: with MPC-based key management, the provider never holds a complete private key and cannot move user funds. Older or HSM-based designs can be more custodial in practice, so always confirm the specifics before you integrate. ### How much does wallet-as-a-service cost? Pricing usually follows a monthly active user model, often with a free tier for development. Some providers add per-transaction fees, which can grow unpredictably at scale. Para charges per monthly active user with no transaction fees, so your costs track user growth rather than usage spikes. ### What is the difference between wallet-as-a-service and an embedded wallet? Wallet-as-a-service is the infrastructure a developer buys. An embedded wallet is what the end user experiences: a wallet that lives inside the app. WaaS is the engine; the embedded wallet is the result. One provider's WaaS can power embedded wallets across many different apps. ### What happens if my WaaS provider goes out of business? With a genuinely non-custodial provider, user funds stay accessible regardless of the provider's status, because users can export their keys and move to self-custody or another provider. This is a core reason to favor non-custodial MPC designs over custodial ones. Confirm the export path before committing. ### How long does it take to integrate wallet-as-a-service? A basic integration with a well-designed SDK can take under a day, sometimes under an hour for a prototype. A production integration with custom auth flows, branding, and edge-case handling usually takes one to two weeks. Framework coverage and documentation quality are the biggest factors. --- # How to Choose an Embedded Wallet Provider (2026) URL: https://www.getpara.com/blog-posts/how-to-choose-embedded-wallet-provider Choosing an embedded wallet provider is a decision you will live with for years. The wallet sits at the center of your product, holds your users' funds, and shapes your onboarding conversion. Switching later is possible but rarely pleasant. So it pays to evaluate carefully and against the right criteria, not the loudest marketing. This guide is criteria-driven on purpose. Rather than ranking vendors, it gives you the questions that separate a serious provider from a fragile one, in the order that matters. Work through them with any provider you are considering, including Para, and you will end up with a decision you can defend to your CTO and your users. ## Start with the security architecture Security is the first filter, and it is close to non-negotiable. The single most revealing question is this: does the full private key ever exist in one place? If the answer is yes, at any moment, you are trusting the provider to protect that moment perfectly, forever. If the answer is no, you have a structurally stronger system. Ask these directly: - **Do keys ever exist in full?** The strongest answer is never. Multi-party computation splits the key into shares that sign collaboratively, so the whole key is never assembled. Para uses Distributed Key Generation, where shares are created independently and never combined. - **What happens if the provider disappears?** Users should be able to export their keys and move on without anyone's permission. If a provider outage or shutdown can freeze funds, that is a serious risk. - **Is the system censorship resistant?** Can the provider or the app block or reverse a user's transaction? With a genuinely non-custodial design, keys cannot be accessed by the app, the provider, or anyone but the user. - **Has the architecture been independently audited?** Ask for named audit firms and dates. Para has been audited by Least Authority and is SOC 2 Type II compliant. For the underlying mechanics, our [MPC wallet explainer](/blog-posts/what-is-an-mpc-wallet) breaks down how collaborative signing works and why it removes single points of failure. ## Confirm the custody model Security architecture and custody are related but distinct. A provider can use sophisticated cryptography and still be custodial in practice if it can sign on a user's behalf. Custody is about authority, not just storage. Ask whether the provider, or you as the app, can move a user's funds without the user's action. With a non-custodial MPC design, the honest answer is no: the provider holds only a share and cannot produce a signature alone. This matters for user trust and for your regulatory position, since not holding user assets simplifies classification in many jurisdictions. Our guide on [custodial vs. non-custodial wallets](/blog-posts/custodial-vs-non-custodial-wallets) covers the spectrum and why it matters for fintechs. ## Check authentication options Your users arrive with different expectations, so the provider's authentication menu should be broad. First-time users want email, Google, or Apple. Some users want a phone number. Enterprise buyers may need SSO. Crypto-native users may want to connect an existing external wallet. Passkey support is a useful leading indicator, because it signals a modern architecture that has moved past passwords and seed phrases. Para supports email, phone, social login, passkeys, and external wallet connection through one integration. ## Verify chain and platform coverage Chain coverage and platform coverage are two separate axes, and both trip teams up. On chains, EVM support is easy and nearly universal. Real Solana and Cosmos support is harder, because they use different signing schemes, and it separates serious providers from lightweight ones. Ask which chains work today and which you will realistically need in twelve months. Para supports EVM chains, Solana, and Cosmos through a single SDK, with Stellar and other networks available. On platforms, check web, mobile, and server support for your exact stack. Mobile is where coverage gets thin, especially for non-EVM chains. Few providers support connecting external wallets on Solana inside a mobile SDK, for example, so if that is on your roadmap, confirm it explicitly. Para ships SDKs for web (React, Next.js, Vue, Svelte), mobile (React Native, Expo, Flutter, Swift), and server (Node.js), plus Telegram and browser extensions. ## Weigh portability and lock-in Portability is the criterion most teams underweight and later regret. Many embedded wallets only work inside the single app that created them. When a user moves to another app, even one in the same ecosystem, they start over with a brand-new wallet. That resets onboarding and caps the network effects your product could otherwise earn. Para wallets are portable by design. A wallet created in one Para-integrated app works across every other Para-integrated app, across every supported chain. The user onboards once and the wallet travels with them. If you are building into an ecosystem, or want to benefit from other apps in your space, portability is not a nice-to-have. Ask any provider directly whether a user's wallet can leave their app intact. ## Review compliance and scale Two trust signals round out the shortlist. Compliance: confirm SOC 2 Type II status, and check for the specific certifications your buyers or regulators require. Scale: ask for evidence the provider has handled real growth without degradation, ideally references at the scale you are planning for. Para is SOC 2 Type II compliant and runs at scale with 15M+ wallets across partners including ENS, Vana, and Camp Network. ## Understand the pricing structure Pricing is where a good decision can quietly become an expensive one. Per-monthly-active-user pricing is the most predictable, because it tracks engaged users. Per-transaction pricing can look cheap in a demo and punish you once volume climbs. Watch for add-on fees for money movement, extra chains, or enterprise features. Model the cost at both your current volume and ten times that before signing. Para uses per-monthly-active-user pricing with no transaction fees and a free tier, so the model stays predictable as you grow. See the [pricing page](/pricing) for specifics, and our [build vs. buy analysis](/blog-posts/build-vs-buy-wallet-infrastructure) for how those numbers compare to building in-house. ## Evaluation checklist Use this as a printable scorecard. Run each provider through it and compare side by side. | Criterion | Question to ask | What good looks like | |---|---|---| | Key architecture | Do keys ever exist in full? | Never; MPC with distributed key generation | | Custody | Can you or the provider move funds without the user? | No; fully non-custodial | | Exit path | Can users export keys and leave? | Yes, without permission | | Audits | Which firms, which dates? | Named third-party audits, recent | | Compliance | SOC 2 Type II? | Yes, plus any required certs | | Chains | EVM, Solana, Cosmos coverage? | All you need now and in 12 months | | Platforms | Web, mobile, server for your stack? | First-class SDKs for each | | Auth | Email, social, phone, passkey, external wallet? | Full menu through one integration | | Portability | Does the wallet work across apps? | Portable by design | | Scale | Proven under real growth? | References at your target scale | | Pricing | Per-MAU or per-transaction? | Predictable, no surprise fees | ## Red flags A few signals should give you pause during evaluation: - **The full key is assembled at any point.** Even a brief moment of a complete key in memory is a weaker posture than never assembling it. - **No clear export path.** If you cannot get a straight answer on how users leave, assume leaving is hard. - **Vague or missing audit history.** "We take security seriously" is not an audit. Ask for names and dates. - **Per-transaction pricing with no MAU option.** This tends to punish exactly the growth you are hoping for. - **Mobile support that only covers EVM.** If your roadmap includes Solana or Cosmos on mobile, confirm it works today, not "soon." - **Wallets locked to a single app.** Lock-in limits your users and your network effects. ## Where Para lands Run Para through the same checklist and it holds up on the criteria that matter most. Keys never exist in full, thanks to Distributed MPC; the system is non-custodial, so users can export and leave; it is SOC 2 Type II compliant and audited by Least Authority; it covers EVM, Solana, and Cosmos across web, mobile, and server; and it is portable across every Para-integrated app. Pricing is per monthly active user with no transaction fees. Start from the [Para docs](https://docs.getpara.com), and if you are still deciding whether to buy at all, read our [build vs. buy guide](/blog-posts/build-vs-buy-wallet-infrastructure). ## Frequently asked questions ### What should I look for in an embedded wallet provider? Start with the security model: do keys ever exist in full, and can the provider or app move funds without the user? Then weigh custody, chain coverage, platform coverage across web, mobile, and server, authentication options, portability, compliance, pricing structure, and proven scale. Security and custody are the ones you cannot compromise on. ### Is an embedded wallet provider non-custodial? Some are, some are not. Non-custodial means the provider genuinely cannot access or move user funds. MPC designs where the full key is never assembled are the clearest way to achieve this. Ask directly whether the provider can sign on a user's behalf and whether users can export their keys and leave. ### What happens if my embedded wallet provider shuts down? With a non-custodial provider, users keep access to their funds regardless, because they can export their keys and move to self-custody or another provider. With a custodial one, a shutdown can put funds at risk. This is why the exit path is one of the most important questions to ask up front. ### Do embedded wallet providers support both web and mobile? Most cover web, but mobile support varies widely, especially for non-EVM chains. Few providers support connecting external wallets on Solana inside a mobile SDK, for example. If you ship on iOS or Android, verify your exact chain and platform combination against the provider's current SDKs before you commit. ### How do embedded wallet providers charge? Usually per monthly active user, sometimes with per-transaction fees layered on, and occasionally with extra charges for money movement or additional chains. Per-transaction pricing can look cheap early and grow unpredictably. Always model pricing at your projected scale, not just today's volume. --- # Wallet Infrastructure: Build vs. Buy (2026 Analysis) URL: https://www.getpara.com/blog-posts/build-vs-buy-wallet-infrastructure Every team building a crypto-enabled product hits the same fork: build the wallet infrastructure yourselves, or buy it from a provider. It is a real decision with real trade-offs, and the honest answer is not always "buy." This analysis is for founders and CTOs weighing the total cost of ownership, not just the sticker price. We will look at what building actually requires, the timeline reality, when building genuinely makes sense, when buying wins, the hybrid paths in between, and how to keep your exit options open either way. The goal is a decision you can defend, not a foregone conclusion. ## What building wallet infrastructure actually requires The mistake most build estimates make is treating a wallet as a feature rather than an ongoing system. A crypto wallet that holds real user funds is closer to running a small bank's vault than adding a settings page. Here is what it involves. **Key management.** You need a way to generate, store, and use private keys without ever exposing them. Doing this non-custodially means multi-party computation or hardware security modules, both of which require genuine cryptographic expertise. Getting this subtly wrong is how funds get drained. Our [MPC wallet explainer](/blog-posts/what-is-an-mpc-wallet) shows why this layer is so unforgiving. **Signing and multi-chain support.** Each chain family signs differently. EVM uses one scheme, Solana another, Cosmos yet another. Supporting more than one means maintaining more than one signing path and keeping each current as chains upgrade. **Recovery.** Users lose devices and forget passwords. A recovery system that does not reintroduce a single point of failure is hard to design and easy to get wrong. **Audits and compliance.** Third-party security audits are not optional for a system holding funds, and they recur. SOC 2 Type II is table stakes for selling to serious customers, and it takes months to achieve and continuous effort to maintain. **On-call and operations.** A wallet system is a 24/7 responsibility. Bugs here are not cosmetic; they can be catastrophic and irreversible. That means real on-call rotations staffed by people who understand the cryptography. Each of these is a specialty. Together they are not a project you finish. They are a team you staff indefinitely. Our overview of the full [wallet infrastructure stack](/blog-posts/what-is-wallet-infrastructure) lays out every layer you would be signing up to own. ## The timeline reality A realistic timeline for a production-grade, non-custodial, multi-chain wallet system is six to twelve months with a specialized team, and that is before the maintenance clock starts. The first working prototype comes faster, but the distance between a prototype and a system you would trust with real funds across multiple chains, audited and compliant, is where most of the time goes. By contrast, integrating a provider gets you a basic embedded wallet in days, often less. That gap is the crux of the decision. Every month spent building wallet infrastructure is a month not spent on the product that actually differentiates you. ## Build vs. buy at a glance | Dimension | Build in-house | Buy from a provider | |---|---|---| | Time to launch | 6 to 12 months for production-grade | Days to a couple of weeks | | Cost | Specialized salaries, audits, compliance, ongoing ops | Predictable per-user pricing | | Risk | Existential if key management has a flaw | Shared with an audited specialist | | Control | Total, including every edge case | High, within the provider's model | | Maintenance | Permanent team commitment | Handled by the provider | | Multi-chain | Each chain is a new project | Available from day one | | Compliance | You build SOC 2 and audits yourself | Inherited from the provider's certifications | ## When building makes sense It is worth saying plainly: sometimes you should build. Buying is the right default, but not the right answer for everyone. Building makes sense when custody or cryptography is your core differentiator. If your product is a custody solution, a key management platform, or something where the wallet mechanics are the value you sell, then owning that stack is the point. It also makes sense when you have genuinely unusual requirements that no provider supports, such as an exotic chain, a bespoke signing scheme, or a policy model outside what any platform offers. It can also make sense when regulatory constraints require full in-house control of the entire system. In these cases the cost is justified because the wallet is the product, not a supporting feature. The team you staff indefinitely is building your actual moat. ## When buying wins For everyone else, buying wins, and it usually is not close. If wallet infrastructure is a means to an end, a payments app, a game, a fintech, a marketplace, then the specialized team, the audit budget, and the on-call rotation are pure overhead against your real goal. A provider gives you multi-chain support on day one, ships security patches automatically, carries the compliance certifications, and scales with your user base while your engineers stay focused on the product. The math tends to favor buying until you reach very high scale, and often past it, once you honestly account for cryptographic engineers, recurring audits, compliance work, and operations. The short version: if wallet infrastructure is not your core product, it should not be your core engineering investment. ## Hybrid paths The choice is not always all-or-nothing. Several teams land in the middle. You can buy the hard part and build around it: use a provider for key management and signing, the pieces where mistakes are catastrophic, while building your own UX, policy logic, and product-specific flows on top. A good provider supports this with both prebuilt components and headless APIs, so you take exactly as much control as you want. You can also start by buying to reach the market quickly, then revisit in-house options later if scale or requirements ever justify it, provided you chose an exportable, non-custodial provider that does not trap you. ## Migration and exit considerations Whatever you choose, protect your exit. The single most important safeguard is non-custodial, exportable keys. With a non-custodial provider, users own their keys and can export them, so you can migrate to self-custody or another provider without stranding funds. Confirm this before you commit: ask exactly how a user's wallet leaves the system, and get the answer in writing. This is where the buy path can actually be safer than the build path. A non-custodial provider gives you a clean exit by design, whereas a rushed in-house build can quietly lock your users into an architecture only your original team understands. Para is non-custodial and exportable by design, and its wallets are portable across every Para-integrated app, so neither your users nor your team are locked in. ## Where Para fits Para is built for teams that decide to buy and refuse to give up control. It is non-custodial, powered by Distributed MPC so private keys never exist in full, and portable across every Para-integrated app. It covers EVM chains, Solana, and Cosmos through one SDK, with Stellar and other networks available, and it is SOC 2 Type II compliant and audited by Least Authority. Basic integration takes minutes rather than months, and pricing is per monthly active user with no transaction fees. If you have worked through this analysis and landed on buying, start from the [Para docs](https://docs.getpara.com), compare providers with our [buyer's guide](/blog-posts/how-to-choose-embedded-wallet-provider), or read the broader [wallet-as-a-service guide](/blog-posts/what-is-wallet-as-a-service). ## Frequently asked questions ### Should I build or buy wallet infrastructure? Buy it unless wallet infrastructure is your core product. Building means committing a specialized team to key management, audits, compliance, and on-call indefinitely, while a provider ships that on day one and maintains it for you. Building makes sense mainly when custody or cryptography is your actual differentiator. ### How long does it take to build wallet infrastructure in-house? A production-grade, non-custodial, multi-chain system realistically takes six to twelve months with a specialized team, and that is before ongoing maintenance. A provider integration can be live in days. The gap is why most teams buy unless wallets are the product itself. ### What does building wallet infrastructure actually require? Key management with MPC or HSM expertise, secure signing, multi-chain support, recovery flows, third-party audits, SOC 2 compliance, and 24/7 on-call for a system where bugs can drain funds. Each piece is specialized, and together they add up to a permanent engineering commitment, not a one-time project. ### When does building wallet infrastructure make sense? When custody or cryptography is your core differentiator, when you have unusual requirements no provider supports, or when regulatory constraints force full in-house control. In those cases the cost is justified because the wallet is the product. For everyone else, buying is faster, cheaper, and lower risk. ### Can I migrate off a wallet provider later? With a non-custodial provider, yes. Users can export their keys, so you can move to self-custody or another provider without stranding funds. This is a key reason to choose a non-custodial, exportable design up front, and to confirm the migration path before you commit.