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

# Call Execution

> Execute transactions across any chain, pay with any token

<img src="https://mintcdn.com/unevenlabs/htC0XN902y8EVqpy/images/Call-execution.png?fit=max&auto=format&n=htC0XN902y8EVqpy&q=85&s=6b3f47ab1ac4222f989bc4f45957fdae" alt="title" width="2160" height="1008" data-path="images/Call-execution.png" />

Relay supports cross-chain transaction execution for arbitrary cross-chain transactions. This means a user can execute any call on any chain and pay with any token on any other chain. This feature is perfect for cross-chain checkout experiences as well as full chain abstraction.

<Note>
  **Gas requirement**: With standard EOA wallets, the user still needs a small amount of native gas token (e.g., ETH) on the **origin chain** to broadcast the initial deposit transaction. Relay handles all destination chain gas and deducts fees from the user's tokens, but the origin chain submission requires native gas. For a fully gasless experience where users hold **zero native tokens**, see [Gasless Swaps](/features/gasless-swaps) to find the right approach for your app, or explore [Smart Accounts](/references/api/api_guides/smart_accounts/smart-accounts) (EIP-7702 or ERC-4337) directly.
</Note>

## How it Works

Relay's cross-chain execution is powered by cross-chain intents. This model results in low-cost, low-latency (1-10 seconds) cross-chain transactions. When a user wishes to perform a cross-chain action, they submit the call data to get a quote from relayers for execution. When they accept the quote, the order is validated and they submit a transfer to the [Relay Depository Contract](/references/protocol/overview). A relayer then instantly fills the transaction on the destination chain before unlocking the funds on the origin.

Learn how to integrate cross-chain call execution with our [Call Execution Integration Guide](/references/api/api_guides/calling-integration-guide).
