> For the complete documentation index, see [llms.txt](https://solana-unchained.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://solana-unchained.gitbook.io/whitepaper/why-this-exists/real-world-services/commerce-protocol.md).

# Commerce Protocol

**Problem:**\
Crypto users have few easy, non‑custodial ways to spend tokens on everyday items (gift cards, mobile top‑ups, eSIMs). Existing solutions are either centralized (requiring KYC and custody) or limited to a handful of merchants.

**Solution:**\
A decentralized payment network that allows any user to purchase digital vouchers (gift cards, mobile airtime, eSIM data packages) using SOLANA UNCHAINED tokens or SOL.

**Architecture:**

* Voucher Registry – An on‑chain catalog of available products, each with a fixed price in USD (or local currency) and a dynamic price in SOL/tokens (via a real‑time oracle).
* Payment Processor – A contract that accepts tokens, holds them in escrow, and emits a VoucherPurchased event.
* Fulfillment Service – A decentralized network of relayers that, upon seeing the on‑chain event, deliver the voucher code (e.g., a 16‑digit gift card number) to the user via an encrypted off‑chain channel (email, push notification, or wallet‑native message).
* Dispute Resolution – A simple multi‑sig council that handles missing or invalid codes. Relayers must stake tokens to participate, ensuring honest behavior.

**Fee model:**\
2% of each transaction is taken as protocol fee, split as follows:

* 50% to Solana Unchained Vault stakers
* 25% to the relayer who fulfilled the order
* 25% to the ecosystem treasury

**Integration for other dApps:**\
Any dApp can integrate the Commerce Protocol by importing the SDK. The dApp can either use the default fulfillment network or run its own relayer. Fees are paid in $UCHN tokens, creating persistent buy pressure.


---

# 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://solana-unchained.gitbook.io/whitepaper/why-this-exists/real-world-services/commerce-protocol.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.