> ## Documentation Index
> Fetch the complete documentation index at: https://docs.passage.coinlist.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Wallet partners

> Passage ships no wallet stack. Any provider that can satisfy the EvmWallet interface can support it, provider by provider.

Passage is wallet-agnostic. The SDK ships **no wallet stack**, is not coupled to any provider, and never asks a user to connect. Wallet discovery, connection, and signing stay with your app and whatever wallet infrastructure it already uses.

That inversion is what makes a wallet partner possible. Instead of adopting someone else's wallet, you implement one small interface, [`EvmWallet`](/sdk/wallets), and the SDK drives it. Do that once and every on-chain flow works: Ondo buys and sells, Superstate swaps, token-sale approvals, and wallet ownership proofs.

The pages in this section cover providers whose customers can plug Passage in, including what their wallets are, how keys are held, and what the integration takes on each side.

## Partner profiles at a glance

| Partner | What they provide | Key model | Networks |
| - | - | - | - |
| [Para](/wallet-partners/para) | Embedded wallets created at sign-up from email, phone, social login, or a passkey | MPC. Keys are split between the user's device and Para, so neither Para nor your app holds a complete key | EVM: Ethereum and Base, mainnet and Sepolia |

<Columns cols={3}>
  <Card title="Para" icon="wallet" href="/wallet-partners/para">
    Embedded wallets, MPC keys
  </Card>
</Columns>

## What a wallet partner has to satisfy

One interface, five members. `EvmSigner` covers `address` and `signMessage`, which is enough to prove wallet ownership. `EvmWallet` adds `writeContract`, `broadcastRawTx`, and `awaitTx`, which covers everything on-chain: approvals, swaps, and allowlist transactions.

The SDK ships [viem](https://viem.sh/) types, so a provider that already exposes a viem account or wallet client is most of the way there. See [Wallets](/sdk/wallets) for the full interface, the adapter pattern, and how wallet errors are classified.

<Note>
  Users keep custody throughout. Passage has no ability to access, recover, freeze, or otherwise control assets in a user's wallet, whoever provides it. See [Wallets and chains](/wallets-chains).
</Note>

## Become a wallet partner

If you provide wallets, embedded wallets, or wallet-as-a-service infrastructure and want your customers to reach Passage assets without leaving your stack, we can scope the integration with you.

<Card title="Talk to us" icon="envelope" href="mailto:sales@coinlist.co">
  Scope a wallet integration with the Passage team.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.