> ## Documentation Index
> Fetch the complete documentation index at: https://developers.fireblocks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Solana Gasless

> Pay Solana fees from a fee payer vault account for SPL transfers and program calls. Covers setup, key set, useGasless, and feePayerInfo.

## Overview

New to Solana Gasless? See [Configuring Solana Gasless transactions](https://support.fireblocks.io/hc/en-us/articles/20170988182300) in the Help Center for the Console walkthrough, then use this guide for the API behavior.

Solana Gasless lets a vault account send SPL tokens without holding SOL. It uses Solana's native fee payer: one vault account in your workspace is set as the *fee payer* and pays the SOL fee for every gasless transaction. Each transaction is signed by two vault accounts, the source (token owner) and the fee payer. The two signatures are bundled, so only one signing action is needed. Solana Gasless does not cover SOL transfers.

Solana Gasless also covers Solana program calls in Early Access. See [Program calls (Early Access)](#program-calls-early-access).

For how gasless compares across chains, see the [Gasless Transactions Overview](https://developers.fireblocks.com/docs/gasless-transactions.md).

## Requirements

* **A fee payer vault account** in your workspace, holding enough SOL to pay fees. The fee payer must be in the same workspace. External workspaces, the Fireblocks relay, and Wallet Pools are not available as the fee payer on Solana.
* **Same key set.** The source vault account must share a key set with the fee payer vault account.

## Step 1. Set the fee payer in the Console

Go to **Settings** > **Initiate gasless transactions**, turn on **Solana**, select the fee payer vault account, then select **Save**.

Solana has no default-mode setting. Once a fee payer is set, eligible SPL transfers and program calls from other vault accounts use it automatically.

## Step 2. Send a transaction

Submit a standard SPL token transfer with [Create a new transaction](https://developers.fireblocks.com/reference/createtransaction.md). You need no extra fields.

`POST /v1/transactions`

```jsonc theme={"system"}
{
  "assetId": "SOL_USDC_PTHX",
  "amount": "250",
  "source": {
    "type": "VAULT_ACCOUNT",
    "id": "42"
  },
  "destination": {
    "type": "ONE_TIME_ADDRESS",
    "oneTimeAddress": {
      "address": "7xKX..."
    }
  },
  "useGasless": true // Optional - Set false to pay the fee from the source vault account instead
}
```

**Field notes:**

* `useGasless`: omit it to use the fee payer. Set `false` to have the source vault account pay its own fee.
* `source`: the vault account needs the token balance only. When the source is the fee payer itself, the transaction is sent as a standard transaction.
* `assetId`: an SPL token. SOL transfers are not covered.

## Step 3. Confirm the fee payer paid

[Get a transaction](https://developers.fireblocks.com/api-reference/transactions/get-a-specific-transaction-by-fireblocks-transaction-id.md) or read the [transaction webhook](https://developers.fireblocks.com/reference/monitoring-transaction-status.md). The fee payer is reported in `feePayerInfo`.

```json theme={"system"}
{
  "id": "9d3a...",
  "status": "COMPLETED",
  "assetId": "SOL_USDC_PTHX",
  "feePayerInfo": {
    "feePayerAccountId": "3"
  }
}
```

| Field | Description |
| - | - |
| `feePayerInfo.feePayerAccountId` | The vault account that paid the fee. |

## Program calls (Early Access)

> [!NOTE]
>
> Fee payer support for program calls is in Early Access. To enable it for your workspace, contact your Customer Success Manager (CSM).

Program calls (`PROGRAM_CALL`) use the fee payer automatically, whether you submit them through the API or a dApp sends them through WalletConnect. In a program call, the source is the vault account that signs the call rather than a token owner. You need no extra fields. For how to build `programCallData`, see [Interact with Solana programs](https://developers.fireblocks.com/transactions/solana-program-calls.md).

`POST /v1/transactions`

```jsonc theme={"system"}
{
  "operation": "PROGRAM_CALL",
  "assetId": "SOL",
  "source": {
    "type": "VAULT_ACCOUNT",
    "id": "42"
  },
  "extraParameters": {
    "programCallData": "<serialized transaction>"
  },
  "useGasless": true // Optional - Set false to pay the fee from the source vault account instead
}
```

### Who pays the fee

Solana charges the fee to the first account in the transaction's account list (`accountKeys[0]`). Fireblocks reads that account in the transaction you submit and decides whether to apply the fee payer:

| First account in the submitted transaction | Result |
| - | - |
| The source vault account | Fireblocks makes the fee payer the first account, and the fee payer pays and signs. |
| The fee payer vault account | The transaction is sent unchanged, and the fee payer pays and signs. |
| Any other address | The transaction is sent unchanged, and that address pays. The fee payer is not used. |

The last case covers dApps that sponsor their own fees: the dApp keeps paying, and your fee payer is not charged.

### Security checks

Fireblocks validates every program call before the fee payer signs it and refuses transactions that put the fee payer vault account at risk. A refused transaction fails with a sub-status and a failure reason that describe the problem. See [Troubleshooting](#troubleshooting).

### Program calls from dApps

Some dApps build transactions in a way that is not compatible with an added fee payer, and those transactions are refused. If a dApp transaction is refused, contact [Fireblocks Support](https://support.fireblocks.io/).

## Troubleshooting

| Symptom | Cause | Fix |
| - | - | - |
| Error `1448` "Fee payer is not allowed for asset" | The asset does not support a fee payer | For transfers, check that the asset is an SPL token. |
| Error `1449` "Fee payer can't pay" | The fee payer has no SOL wallet or not enough SOL | Fund the fee payer vault account with SOL. |
| A program call fails before it is signed | The transaction did not pass the fee payer security checks | Read the failure reason in the transaction details, then rebuild the transaction. To send it without the fee payer, set `useGasless` to `false`. |
| A program call fails because Fireblocks could not read blockchain data | A temporary connection problem, not a problem with the transaction | Resubmit the transaction. |

See [API error codes](https://developers.fireblocks.com/reference/api-error-codes.md) for the full list.

## Related

* [Gasless Transactions Overview](https://developers.fireblocks.com/docs/gasless-transactions.md): compare gasless mechanisms across chains.
* [EVM Gasless (Universal Gasless)](https://developers.fireblocks.com/docs/evm-gasless.md): gasless transactions on EVM chains.
* [Monitoring transaction statuses](https://developers.fireblocks.com/reference/monitoring-transaction-status.md): track transactions through webhooks.
