> For the complete documentation index, see [llms.txt](https://versawallet.gitbook.io/versa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://versawallet.gitbook.io/versa-docs/functions-and-plugins/pay-gas-with-any-erc-20-token.md). # Pay gas with any ERC-20 Token In any blockchain network, transaction fees play a critical role. Previously, you would need to have ETH in your wallet to receive ETH. This creates significant user burdens and has limited adoptions of wallets and protocol interactions. In order to simplify the process of sending funds and interacting on-chain, these fees should be able to be paid in any ERC-20 tokens, and not just the native token of the corresponding network. With Account Abstraction, users can use any ERC-20 token as a subsidize for native tokens upon paying for network transaction fees (gas). Additionally, the option to pay gas via native tokens will still remain valid. * **Paying transaction fee via non-native tokens:** {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://versawallet.gitbook.io/versa-docs/functions-and-plugins/pay-gas-with-any-erc-20-token.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.