# Revenue from Web & Application Payments

### Revenue derived from web & application payments includes earnings from merchandise and Travel Products.

Revenue derived from web & application payments will be allocated as follows:

* **Development and Operational Costs**: As with other sources of income, a certain percentage is assigned for ongoing developmental work and operational costs.
* **Ecosystem Development & Reward Pool**: To stimulate user engagement within our ecosystem further we'll assign funds towards reward programs that benefit both holders as well as general users alike.
* **Marketing & Community Activities**: Funds are reserved for promotional activities aiming at expanding our reach while ensuring active community participation.
* **Future Business Expansion/Partnerships**: In line with WBC's growth objectives some part of these funds are earmarked for exploring new business avenues or establishing strategic partnerships.
* **Reserve/Contingency Fund**: We also plan on adding to our contingency reserves thus ensuring financial stability even under unforeseen circumstances.
* **Dividends For Holders:** A proportionate share of 3% of the profits from merchandise and Travel Products is distributed to holders who own BUDDHI Points (to be converted into ecosystem coins in the future).

This approach ensures balanced utilization of resources while keeping an eye out on future expansion plans.

**Note: Some plans may change depending on the progress of the project.**


---

# 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://wisebuddhiclub.gitbook.io/wbc-whitepaper/fund-management/revenue-from-web-and-application-payments.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.
