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

# Pay Gas with Any Token

> Users can pay gas in any permit-compatible, non-native token

## Overview

Trails supports paying gas fees in any permit-compatible (EIP-2612) token, including popular stablecoins like USDC and USDT. This removes the friction of needing native tokens on each chain.

## Why This Matters

Common problems this solves:

* **New chain onboarding**: Users bridge to a new chain but have no native tokens for gas
* **Stablecoin-first users**: Users who hold primarily stablecoins don't need to manage gas tokens
* **Simplified UX**: One token type for both payment and gas fees

## How It Works

When a user initiates a transaction, the widget presents available fee tokens alongside the default native gas option. For permit-compatible tokens (EIP-2612), the user signs an off-chain permit rather than an on-chain approval — no separate gas-spending transaction is required. The Trails relayer uses that permit signature to cover the fee, deducting it from the user's selected token balance.

## Supported Fee Tokens

Any token implementing EIP-2612 (permit) can be used as a fee token.

See the [API Integration Guide](/api-reference/introduction) for the complete permit flow implementation at an API level.

## Widget Behavior

In the Trails widget, alternative fee tokens are automatically presented to users when available. No additional configuration is required—the widget handles permit signatures and fee selection automatically.