> For the complete documentation index, see [llms.txt](https://docs.viction.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viction.xyz/how-to/how-to-verify-gas-sponsored-transactions.md).

# How to verify gas sponsored transactions

## Background <a href="#background" id="background"></a>

As the current status of VRC25 standard, a few partner or users had been issued the token successfully. However, they are unable to regconize whether their transactions had been applied for ZeroGas or not. Hence this article is a guidance for how can they ensure that they applied the ZeroGas successfully.

## Prerequisite <a href="#prerequisite" id="prerequisite"></a>

* Assumed that the Token had been applied succesfully. If the token had not been created or not event apply it. Then kindly follow the guidance as here: <https://docs.viction.xyz/developer-guide/integration/vic-zerogas-integration>
* If the token had been issue via **VicIssuer**, then you can follow this guidance:[How to issue token, apply ZeroGas & testing on Viction Blockchain Testnet](https://coin98.atlassian.net/wiki/spaces/TT/pages/268075011)

## Getting Started <a href="#getting-started" id="getting-started"></a>

As the following image, the. user issued the token successfully. However, they know how to rectify whether the transaction is zero gas or not.

New Issued Token contract: <https://testnet.vicscan.xyz/address/0x4ff96908a19a2AF0E70404eF6Bc0925C0e43700A#code>

VicIssuer Apply Tx: <https://testnet.vicscan.xyz/tx/0xde1aa5624aa5ab025b2b65c0a5c278b3791e930d79aaa3fedfb74d01aa133cba>

Step to verify with the example Tx:  [![](https://testnet.vicscan.xyz/favicon-dark.svg)VIC Scan - The most intuitive Viction explorer](https://testnet.vicscan.xyz/tx/0xf0ea48e8f8e0d02595ccb64821e0fc89ce06c284c976ea552490fc326483c19b)

In the example Tx we would notice a few following detail:

* **Tx Type**: Gas Sponsored
* **Sender** : 0xCc48C437020B17D881C719Ff53DF4e56022Fb61A&#x20;
* **Receiver**: 0xaa3984428fe62211c6485165c30584507175B3fb
* **Fee Payer (Token contract address)**: 0x4ff96908a19a2AF0E70404eF6Bc0925C0e43700A

<figure><img src="/files/AjwpfkMg41dyrdmzTyE5" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ed0T1Ko8Neev3631HRdN" alt=""><figcaption></figcaption></figure>

As we can see, The Fee payer now is neither **Sender** or **recepient.** It is the token contract address, which means that the token had been **registered** for ZeroGas successfully.

For further testing, you can vist the **VRCIssuer** **contract** to figure whether the token is registered or not & the amout of sponsored fund is remaining by querying the token address.

**Testnet**: <https://testnet.vicscan.xyz/address/0x8c0faeb5c6bed2129b8674f262fd45c4e9468bee>

**Mainnet**: <https://www.vicscan.xyz/address/0x8c0faeb5c6bed2129b8674f262fd45c4e9468bee>

<figure><img src="/files/eIeYzWdE5kfaUmgqzBBU" alt=""><figcaption></figcaption></figure>


---

# 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://docs.viction.xyz/how-to/how-to-verify-gas-sponsored-transactions.md?ask=<question>&goal=<endgoal>
```

`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.
