<!-- tempo-docs-context -->
> Source: [/docs/partners/wallets](https://tempo.com/developers/docs/partners/wallets.md)
> Section: [Partners](https://tempo.com/developers/docs/partners.md). Find wallet providers, bridges, RPC infrastructure, data services, and other third-party integrations.
> [Documentation index](https://tempo.com/developers/llms.txt) · [Docs skill](https://tempo.com/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.com/developers/llms.txt) and Markdown pages directly.

<span id="wallets-embedded-and-external-options" />

# Wallets

Choose how users connect accounts and how signing keys are managed. The providers below cover embedded wallets, custody, self-custodial wallets, and agent wallets.

Start with [Accounts](https://tempo.com/developers/docs/accounts) for Tempo Wallet and payment workflows. If you are adding Tempo to an existing wallet, use the [wallet integration guide](https://tempo.com/developers/docs/quickstart/wallet-developers) alongside your provider's documentation.

Jump to [embedded wallets](https://tempo.com/developers/docs/partners/wallets#embedded), [custody and institutional providers](https://tempo.com/developers/docs/partners/wallets#custodial--institutional), [self-custodial wallets](https://tempo.com/developers/docs/partners/wallets#self-custodial), or [agent wallets](https://tempo.com/developers/docs/partners/wallets#agentic).

For account abstraction providers, use [Smart accounts](https://tempo.com/developers/docs/partners/smart-accounts). To compare providers by signing and payment requirements, use [Choose a wallet](https://tempo.com/developers/docs/resources/guides/embedded-wallets).

## Embedded

### Blockradar

[Blockradar](https://blockradar.co) provides non-custodial wallet infrastructure for fintechs running stablecoin payments, such as merchant settlement and cross-border payouts. See the [Blockradar Docs](https://docs.blockradar.co/).

Its API issues wallets for users, merchants, or treasury; accepts fiat through virtual accounts; sponsors network fees; runs AML checks; sweeps balances; and swaps or bridges across chains. Start with the Blockradar API or [Blockradar Dashboard](https://dashboard.blockradar.co/), or [book a demo](https://www.blockradar.co/contact) for high-volume programs.

<span id="crossmint" />

### Crossmint Wallets

Create embedded or server-side wallets with [Crossmint Wallets](https://docs.crossmint.com/wallets/overview). Its [product matrix](https://docs.crossmint.com/introduction/supported-chains) lists Tempo wallets as self-serve; checkout, onramp, and tokenization require project access, and offramp is unsupported. Use `tempo` on mainnet and `tempo-testnet` in staging.

[Wallet documentation](https://docs.crossmint.com/wallets/overview) · [Project console](https://crossmint.com/console)

<span id="dynamic" />

### Dynamic Embedded Wallets

Add authentication and embedded wallets with [Dynamic Embedded Wallets](https://www.dynamic.xyz/docs/embedded-wallets/mpc/overview).

[Tempo feature support](https://www.dynamic.xyz/docs/embedded-wallets/chains/overview)

### Para

Use [Para](https://getpara.com) for embedded wallets and authentication. Start from its [React SDK quickstart](https://docs.getpara.com/v3/react/quickstart), then configure the selected Tempo chain and transport with the [custom RPC guide](https://docs.getpara.com/v3/react/guides/web3-operations/evm/configure-rpc).

Para's [Tempo announcement](https://blog.getpara.com/tempo-para/) covers testnet. Generic EVM signing doesn't give you batching or fee sponsorship; check Para's support for those before relying on them.

### Privy

[Privy](https://www.privy.io/) provides key management and embedded wallets. Create self-custodial wallets for users and manage treasury wallets.

Privy's Tempo integration supports native transaction features such as batched calls and fee-token selection. Privy's Tempo-specific React hook supports `sponsor: true`; follow its [Tempo transaction guide](https://docs.privy.io/wallets/using-wallets/tempo/send-a-transaction) for SDK-specific signing and sponsorship requirements.

[Create an Ethereum-type wallet](https://docs.privy.io/wallets/wallets/create/create-a-wallet#param-chain-type-1) in Privy. For Tempo mainnet, the CAIP-2 identifier is `eip155:4217`; use the [Tempo-specific transaction instructions](https://docs.privy.io/wallets/using-wallets/tempo/send-a-transaction) when adding batching, memos, or fee-token selection.

:::tip
Check out the [Tempo + Privy guide](https://docs.privy.io/wallets/using-wallets/tempo/send-a-transaction) and Privy's [example](https://github.com/privy-io/examples/tree/main/examples/privy-next-tempo) peer-to-peer payments app that uses Tempo transaction memos.
:::

### Turnkey

[Turnkey](https://www.turnkey.com) provides programmable key management and non-custodial wallets with signing policies. Use it to sign Tempo Transactions, automate wallet operations, and sponsor network fees through signing policies.

[Create your Turnkey account](https://app.turnkey.com/dashboard) and follow the [Turnkey Embedded Wallet Kit guide](https://docs.turnkey.com/sdks/react/getting-started) to integrate embedded wallets into your Tempo app.

:::tip
Turnkey's SDK includes a [`with-tempo`](https://github.com/tkhq/sdk/tree/main/examples/chain-integrations/with-tempo) example.
:::

## Custodial & Institutional

### Bridge Wallets

Create hosted stablecoin wallets, read balances, and transfer funds with Bridge Wallets. Connect them to Bridge Orchestration for bank funding or Bridge Cards for spending.

[Wallet product](https://www.withbridge.com/product/wallets) · [Wallet documentation](https://apidocs.bridge.xyz/get-started/guides/wallets/overview) · [Tempo integration guide](https://apidocs.bridge.xyz/get-started/guides/move-money/tempo-integration-guide)

### BitGo

Use [BitGo's Tempo guide](https://developers.bitgo.com/docs/tempo) for MPC wallets: custodial cold, or self-custody cold and hot. Its Tempo integration does not use the provider's multisig wallet model.

For deposit attribution, BitGo encodes `memoId` in an address suffix, but the onchain transfer must carry the corresponding TIP-20 memo. When sending from another wallet, follow its `transferWithMemo` instructions to encode that memo against the underlying EVM address.

### Coinbase

Eligible [Coinbase Prime](https://www.coinbase.com/prime) clients can access custody support for Tempo, with availability varying by asset and contracting entity.

Coinbase also supports Tempo for retail and exchange trading and transfers, including in its iOS and Android apps. For supported assets and regions, customers can select Tempo as the network when sending or receiving. See [Coinbase trading and transfers](https://tempo.com/developers/docs/partners/exchanges#coinbase).

<span id="cubist" />

### Cubist CubeSigner

Use [CubeSigner](https://cubist.dev/products/cubesigner-end-user-custody) for wallet key management, authentication, and signing policies.

[Payments and tokenization](https://cubist.dev/use-cases/payments-tokenization) · [Product suite](https://cubist.dev/product-suite)

### DFNS

DFNS lists Tempo mainnet as a [specialty network available upon request](https://docs.dfns.co/networks), with `TempoModerato` as its testnet. Request access before creating wallets.

Use the [DFNS quickstart](https://docs.dfns.co/introduction/quickstart) for authentication and wallet operations, then configure permissions and [signing policies](https://docs.dfns.co/core-concepts/policies).

<span id="fireblocks" />

### Fireblocks Wallets

Manage custody, transfers, and approval policies with [Fireblocks Wallets](https://www.fireblocks.com/products/wallets). Its supported-assets directory lists Tempo and Moderato testnet, with per-asset availability.

[Supported networks and assets](https://www.fireblocks.com/supported-assets) · [Developer documentation](https://developers.fireblocks.com/)

### Utila

[Utila](https://utila.io) provides MPC wallets and asset-management tooling. Manage Tempo payments and treasury operations across wallets and chains, with an approval engine that controls how funds move.

See [Utila payments](https://utila.io/product/payments/) or [request a demo](https://utila.io/request-a-demo/).

## Self-Custodial

### Bitget Wallet

[Bitget Wallet](https://web3.bitget.com) is a self-custodial multi-chain wallet supporting 130+ blockchains, with in-app trading and MPC-based key security.

Get started at [Bitget Wallet](https://web3.bitget.com).

### Bridge Wallet

[Bridge Wallet](https://www.mtpelerin.com/bridge-wallet) is Mt Pelerin's self-custodial mobile wallet with Tempo support. Users hold their own secret phrase and can send, receive, manage, buy, swap, or cash out supported assets through the app.

Download Bridge Wallet from the [Mt Pelerin website](https://www.mtpelerin.com/bridge-wallet).

### Gem Wallet

[Gem Wallet](https://gemwallet.com) is an open-source, self-custodial mobile wallet for iOS and Android with native Tempo support. Users can store, send, receive, and swap Tempo assets.

Download Gem Wallet from the [Gem Wallet website](https://gemwallet.com) or explore its [open-source repository](https://github.com/gemwalletcom/wallet).

### OKX Wallet

[OKX Wallet](https://www.okx.com/web3) is a self-custodial multi-chain wallet with native Tempo support. Users can store, swap, and manage Tempo-based assets, with built-in DEX aggregation and DApp connectivity.

Get started at [OKX Wallet](https://www.okx.com/web3).

### Rabby

[Rabby](https://rabby.io) is an open-source EVM wallet built by DeBank. It switches chains automatically when connecting to apps and simulates transactions before signing.

Get started at [Rabby](https://rabby.io).

### Safe

Use [Safe smart accounts](https://tempo.com/developers/docs/partners/smart-accounts#safe) for shared ownership and signature thresholds.

## Agentic

### Enact

[Enact](https://www.enact.finance/) provides programmable wallets for teams and AI agents. Set a policy (spending limits, multisig thresholds, approval windows, automation rules) and agents act within it onchain. Enact never holds your funds.

Get started with the [Enact CLI](https://docs.enact.finance/) or the [Enact app](https://app.enact.finance/) to create a self-custodial passkey wallet, add signers, and deploy your first onchain policy.

### Sponge

[Sponge](https://paysponge.com) gives AI agents wallets to hold, send, and swap stablecoins on Tempo, with spending controls, allowlists, and audit logging. It integrates with Claude and other agent frameworks through MCP and an SDK.

Get started on the [Sponge platform](https://paysponge.com) and explore the [Sponge docs](https://paysponge.com/docs).
