> For the complete documentation index, see [llms.txt](https://docs.qrbase.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qrbase.xyz/business/purchasing-policy.md).
# Purchasing Policy
When you buy a game attempt on QRbase, you are paying for access to play a skill-based puzzle game.
You are not placing a bet, wager, or gambling stake.
***
### 1. Attempt fee
The $SCAN you pay gives you access to one QRbase puzzle session.
This payment is a service fee for using the game and platform.
It is not:
* a bet
* a wager
* a stake
* a deposit against a result
***
### 2. What you receive from each attempt
Every purchased attempt gives you access to QRbase game features, regardless of whether you solve the puzzle or not.
This may include:
* playing one QR puzzle session
* appearing in leaderboards
* improving your player stats
* building your game history
* public profile visibility inside QRbase, such as your linked X/Twitter profile
* becoming eligible for NFT whitelist
* contribution to your on-chain activity record
These benefits are part of the platform experience and are not guaranteed financial returns.
***
### 3. Skill-based game risk
QRbase puzzles are time-based and skill-based.
You understand that you may fail to solve the puzzle before the timer ends.
If you do not solve the puzzle, this is not considered losing a bet. It simply means the game session was not completed successfully.
Attempt fees are not refunded for unsolved puzzles.
***
### 4. Platform changes
QRbase is still in active development.
Features, rewards, game rules, prize structures, puzzle settings, eligibility rules, and platform mechanics may change over time.
Buying an attempt does not guarantee:
* profit
* future rewards
* token value
* NFT allocation
* campaign eligibility
* any financial return
QRbase is a game and engagement platform, not an investment product.
***
### 5. Treasury wallet and revenue wallet
QRbase uses separate wallets for different platform purposes.
#### Treasury wallet
The treasury wallet is used for community reward distribution.
This wallet may receive:
* $SCAN from partners who purchase puzzle packages
* $SCAN used to reward users who solve partner/token puzzles
* USDC and/or $SCAN from SCAN mode campaigns
* campaign reward funds intended for winners
Funds received in the treasury wallet are intended to be redistributed to the QRbase community through rewards, winners, claims, campaigns, and related platform incentive systems.
#### Revenue wallet
The revenue wallet is used for QRbase platform revenue.
This wallet may receive:
* $SCAN from user attempt purchases
* USDC from Boost purchases
* USDC from Task purchases
Funds received in the revenue wallet may be used for platform operations, development, infrastructure, ecosystem growth, and other QRbase business needs.
***
By purchasing an attempt, you confirm that you understand these terms and agree to play QRbase as a skill-based puzzle game.
---
# 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.qrbase.xyz/business/purchasing-policy.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.