Session signers allow your app to request server-side access to user wallets. This enables your app to execute transactions from user wallets from your servers directly, giving you more control and the ability to execute transactions even when the user is offline (e.g., for limit orders or agentic trading).

You can also configure session signers to have specific permissions via policies, such that you can request server-side access for only certain transaction types.

At a high-level, you can use session signers to request server-side access to user wallets.

1

Add a session signer to the user's wallet

Follow the session signer quickstart to first request access to a user’s wallet. Store the private key(s) associated with your signer ID securely in your server.

Session signer quickstart

Request access to user wallets with session signers.

2

Execute actions with your signer

Next, execute actions with your session signer by signing requests with the private key(s) of your signer ID. Follow the guides below to learn how to sign requests and execute actions with wallets.

Sign requests

Sign requests to the Privy API with your session signer.

EVM

Take actions on EVM chains with Privy’s NodeJS SDK or REST API.

Solana

Take actions on Solana with Privy’s NodeJS SDK or REST API.