Sending transactions from your server

Many apps would like users to explicitly authorize transactions, but to send transaction requests from their server for increased reliability, retries, and various other use cases.

To send transactions from your server by default:

Using Privy as your authentication provider

1. Create wallets with a user owner

   To ensure the wallet can only be controlled by the user, create the wallet with a user owner. If you use one of Privy’s client-side SDKs to create wallets, wallets are created with a user owner by default.

2. Request a signature over your transaction request

   Construct your transaction request and use Privy’s client-side SDKs’ methods to have the user sign the transaction request.

3. Execute the transaction request from your server

   Send your user’s authorization signature from your client to your server, and send your transaction request with the user’s signature to Privy’s API.

Using your own authentication provider

1. Create wallets with a user owner

   To ensure the wallet can only be controlled by the user, create the wallet with a user owner. If you use one of Privy’s client-side SDKs to create wallets, wallets are created with a user owner by default.

2. Request a user key

   Next, given a user’s access token from your authentication provider, request a user key from Privy’s API. You will use this key to sign transaction requests to Privy’s aPI.

3. Sign the request with your user key

   Next, construct your transaction request and sign the transaction request with the user key

4. Execute the transaction request from your server

   Send your user’s authorization signature from your client to your server, and send your transaction request with the user’s signature to Privy’s API.