# Revenue Sharing

At Numpay, we believe that the value created within the ecosystem should flow back to the people who make it thrive the users, the builders, and the contributors.

## Not Just Participation. Ownership.

Numpay doesn't just offer a platform. It offers a stake in the system. While we do not take any cut from user transactions, the revenue generated from optional services, enterprise integrations, and token utility is distributed back into the community through a transparent and reward-driven system.

### Here's How It Works:

#### **1. Community Rewards Pool**

A portion of the platform’s revenue is allocated to a Community Rewards Pool. This pool supports a range of incentives, including:

* Loyalty rewards for active users
* Engagement bonuses for early adopters
* Performance-based rewards for referring new users or driving usage

#### **2. Token Stakers Share in the Upside**

Numpay token holders who stake their tokens contribute to the stability and security of the ecosystem. In return, they receive a portion of the revenue generated from optional services and partner integrations proportional to their stake and contribution duration.

#### **3. Contributor-Based Sharing**

Developers, validators, ambassadors, and ecosystem contributors receive earnings based on their input to platform growth. Whether it’s code, content, or community support, Numpay ensures that contribution is compensated.


---

# Agent Instructions: 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:

```
GET https://numpay.gitbook.io/numpay/revenue-model/revenue-sharing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
