> For the complete documentation index, see [llms.txt](https://spozz-club.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spozz-club.gitbook.io/whitepaper/7.-direct-micro-payments.md).

# 7. DIRECT MICRO PAYMENTS

SPOZZ uses a dual-layer payment system:

**1. SPOZZ Token (SPZZ)**

* An on-chain utility token used for:
  * Artist payouts
  * Marketplace transactions
  * Peer-to-peer tipping
  * Staking for membership benefits
* Built on Polygon for low fees and fast confirmation
* Can be held or converted by users, depending on region and preference
* May later support liquidity on decentralized exchanges

**2. SPOZZ Credits (Off-Chain)**

* SPOZZ Credits are 1:1 backed by SPZZ tokens but used for simplicity
* Users can purchase credits using credit card, Apple/Google Pay, etc.
* Used in the app for streaming, subscriptions, and purchases
* Fully convertible to SPZZ when/if users want to exit to crypto

The dual system allows blockchain-native users to go fully on-chain, while letting mainstream users enjoy the platform without any wallet or crypto experience.


---

# 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://spozz-club.gitbook.io/whitepaper/7.-direct-micro-payments.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.