Cowrie Research

exodus

5 min read

Exodus

  • Name: Exodus
  • URL: https://www.exodus.com/
  • Category: multichain wallet-and-payments company / embedded-wallet and stablecoin-checkout operator / open-source wallet-infrastructure company
  • Tags: bitcoin-ecosystem ethereum-ecosystem solana-ecosystem
  • Summary: Exodus belongs in companies/ because the useful control surface is not only the consumer wallet app. Exodus Movement, Inc. sits above a broader operator shell that now spans the flagship wallet, the Checkout API for hosted stablecoin payments and payouts, the Passkeys embedded-wallet stack, and a substantial open-source and docs surface for wallet and web3 infrastructure. The practical question is not just what can the wallet do? but which company controls app distribution, partner packaging, API-key issuance, merchant signer and settlement workflow, passkey-wallet defaults, and the dashboard / docs shell that developers inherit?
  • What it does:
    • Operates the Exodus self-custodial wallet and consumer product surface for sending, swapping, buying, selling, staking, and card-linked spending
    • Packages the Checkout API for hosted stablecoin checkouts, subscriptions, refunds, payouts, beneficiaries, customer KYC flow, and merchant reporting
    • Packages Passkeys as an embedded-wallet and passkey-native onboarding stack for apps that want MPC-backed multichain wallets without extension-first UX
    • Publishes one documentation hub that bundles Checkout, Passkeys, XO Swap, wallet-building resources, and open-source packages rather than presenting them as disconnected experiments
    • Maintains open-source wallet and asset infrastructure packages across Bitcoin, Ethereum, Solana, web3 management, and the Hydra app framework
  • Key claims:
    • The Exodus homepage says the company has been Trusted by millions since 2015, is Publicly listed, and markets one broad product surface for sending money, managing crypto, and spending worldwide rather than a narrow wallet SKU
    • The same homepage markets Exodus Pay, the Exodus Card, swapping, buy / sell flows, staking, and multichain support while explicitly saying Exodus Movement, Inc. is a financial technology company and that some services are provided through third-party providers, which is a strong clue that the company boundary matters more than any one wallet feature
    • Exodus’s docs hub groups Checkout, Passkeys, XO Swap, wallet-building resources, and open-source infrastructure under one developer shell, which is exactly the kind of bundled operator surface that deserves a company note
    • The Checkout docs show that Exodus controls a merchant workflow shell with API-key authentication, hosted checkout and subscribe pages, signed requests for fund-moving actions, webhook delivery, reports, and a settings surface for registering merchant signers and settlement addresses
    • The Checkout settings docs say merchants manage business mode, per-chain signer status, branding, PaymentFactory address, settlement address, and webhook configuration from the dashboard or settings endpoints, which makes Exodus an operational control plane rather than a neutral payment primitive
    • The Passkeys site says the embedded wallet supports Bitcoin, Ethereum, Solana, and major EVM chains, uses multi-party computation, and can be added with just a few lines of code, while the footer reads ©2026 Exodus Movement, Inc., tying that signer and onboarding stack back to the named company boundary
    • The docs llms.txt also shows Exodus exposing developer-facing packages such as @exodus/web3-ethereum, @exodus/web3-solana, @exodus/web3-management, and Hydra components, reinforcing that the company is packaging reusable infrastructure as well as consumer UX
  • Whitepaper: No classic standalone company whitepaper is the useful artifact here. The strongest current primary materials are the Exodus homepage, the developer docs hub, Checkout docs, Checkout settings docs, and the Passkeys site, plus the earlier product-layer captures in ../whitepapers/grateful-merchants-api-primary-sources-2026-05-04.md and ../whitepapers/passkeys-foundation-primary-sources-2026-05-04.md.
  • Sources:

Internal linkages

  • Product-layer note for the hosted merchant rail: grateful-merchants-api.
  • Adjacent embedded-wallet entity note: passkeys-foundation.
  • Useful adjacent company reads where consumer wallet distribution and developer control planes blur together: block, consensys, and moonpay.
  • Reusable lens: when one wallet company also runs merchant APIs, passkey wallet onboarding, swap / card packaging, and open-source integration tooling, the real dependency shifts from wallet brand to a named operator shell.

Protocol / company boundary

  • There is no especially useful standalone Exodus protocol boundary doing the work here.
  • [[../projects/grateful-merchants-api]] stays useful for the merchant-facing checkout and payout product surface, and [[passkeys-foundation]] stays useful for the embedded-wallet / passkey signer entity boundary.
  • This company note isolates the higher operator shell above them: app distribution, partner composition, docs and dashboard packaging, merchant API keys, signer and settlement workflow, hosted-page configuration, and the corporate release and legal perimeter those products sit inside.
  • That split matters because downstream users and integrators are not only depending on a wallet UI, a passkey wallet SDK, or a hosted checkout page. They are depending on Exodus Movement, Inc. as the company that packages all of those flows into one default stack.

Control surface

  • Practical leverage sits in wallet release and distribution, asset and partner packaging, buy / sell / swap / card provider composition, Checkout API-key issuance, signed-request and merchant-signer workflow, settlement-address management, webhook truth, hosted branding and redirect behavior, customer and beneficiary payout workflow, and Passkeys chain / provider defaults.

  • The wallet may be self-custodial, but the company still shapes what becomes easy: which chains and assets are prominently supported, which partner rails are bundled, how developers authenticate, how merchants configure settlement, and which passkey-wallet and payout flows are normalized.

  • Read Exodus as a multichain wallet-and-payments operator with meaningful developer and merchant control surfaces, not as only a consumer wallet brand.

  • Last reviewed: 2026-08-10 UTC

Graph View

Backlinks