> For the complete documentation index, see [llms.txt](https://docs.gpubase.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpubase.network/how-it-works/payment-and-transaction-flow.md).

# Payment and Transaction Flow

The GPUBase Network token serves as the primary means of payment on the platform. Here’s a typical transaction flow:

1. **User Requests and Payment**: The user initiates a task and transfers the necessary amount of tokens into a smart contract.
2. **Provider Execution**: The provider receives the task and executes it using their GPU resources.
3. **Completion and Verification**: Once the task is completed, the system verifies the output, and the smart contract releases the payment to the provider.
4. **Reward Distribution**: A portion of transaction fees or staking rewards may be distributed back to active participants to maintain ecosystem engagement.

This workflow ensures that GPUBase Network operates efficiently and securely, leveraging decentralized technology to provide a reliable solution for both users and GPU providers.


---

# 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.gpubase.network/how-it-works/payment-and-transaction-flow.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.