Skip to main content
Passage is wallet-agnostic. The SDK ships no wallet stack, is not coupled to any provider, and never connects a wallet itself. 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, and the SDK drives it. Do that once and every on-chain flow works: Ondo buys and sells, Superstate swaps, Centrifuge vault orders and claims, 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

Para

Embedded wallets, MPC keys

What a wallet partner has to satisfy

One interface, five members. EvmSigner covers address and signMessage, which is enough to prove wallet ownership or sign in with a wallet. EvmWallet adds writeContract, broadcastRawTx, and awaitTx, which covers everything on-chain: approvals, swaps, allowlist transactions, and vault orders and claims. The SDK ships viem types, so a provider that already exposes a viem account or wallet client is most of the way there. See Wallets for the full interface, the adapter pattern, and how wallet errors are classified. Two more things make a provider’s wallets behave well in the SDK’s screens:
  • Disconnects. When a wallet disconnects or changes account, stop listing its address in the WalletSelection you pass. A checkout then reopens its wallet step, once nothing is being sent, and asks the user to reconnect or choose another wallet. A checkout that skipped its wallet step for a preselected wallet has no step to reopen, so there only a send that fails because the wallet went away shows that message. An Ondo or Centrifuge checkout on a wallet sign-in session instead shows a “Connect your wallet” card while external on the selection is not the session’s wallet. The SDK recognizes EIP-1193 error code 4100 and wagmi’s ConnectorNotConnectedError; any other stack throws WalletDisconnectedError from @passage-cl/react/universal from its EvmWallet.
  • Loading. A stack that restores wallets after page load sets status: 'loading' on the WalletSelection until every embedded wallet is listed. A claim card with a Centrifuge vault offer on it waits for it instead of reporting that the user has no orders. Other screens ignore it.
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.

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.

Talk to us

Scope a wallet integration with the Passage team.