> For the complete documentation index, see [llms.txt](https://nexon-3.gitbook.io/nexon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nexon-3.gitbook.io/nexon-docs/part-iv-products/04-product-stack/marketplace.md).

# Marketplace — The Real-Consumption Leg

The Marketplace connects an approved financial route to travel, hotels, goods and services — and keeps payment and delivery as two separate facts.

*Product stage · Roadmap*

The NEXON Marketplace is where **a financial route becomes a right of use**: a trip, a night's stay, a product, a service. It is the "Digital to Real" half of the tagline.

Its job **does not end** the moment payment settles. Completion needs evidence that the supplier accepted the order and fulfilled it.

## From route to order

A marketplace leg begins with an approved intent and fresh supplier data. The preview names the item or booking, inventory, total cost, accepted payment method, where a conversion sits if one is needed, the cancellation window, delivery conditions and the supplier responsible.

If price or availability changes before approval, the route **updates** — it does not quietly substitute something else.

After execution, the route records at least two states:

{% columns %}
{% column %}
**① Payment / reservation**

Submitted · authorized · settled · failed · refunded
{% endcolumn %}

{% column %}
**② Fulfillment**

Confirmed · delivered · consumed · cancelled · disputed
{% endcolumn %}
{% endcolumns %}

**A settled payment with no delivery is not a successful real-world leg.**

## What the supplier owns

Merchants, hotels, travel operators and service providers control their own inventory and fulfillment. Delivery, cancellation, refund and consumer protection follow their terms. NEXON can coordinate the experience and preserve the receipts; a token transfer overrides no supplier obligation and conjures no inventory.

Supplier onboarding should include identity and business verification, product and jurisdiction checks, data-security requirements, service terms and an escalation path. Ratings and social reputation can inform discovery ordering; they replace neither diligence nor a formal dispute process.

## Payment and token boundaries

The approved Tokenomics **does not** define EXON as a current universal Marketplace payment asset, and does not define XO as merchant collateral. Accepted payment methods, conversion, spreads, fees, settlement timing and refunds are specified by the responsible product and provider before the user approves an order.

EXON's broader trading, payment, exchange, fee and consumption function belongs to its long-term Circulation Engine role. **Where it becomes a real capability depends on what rules that product publishes.** Staking rewards and redemption burns stay inside the separate Staking Platform mechanism.

## Data and privacy

Real-world orders may need names, addresses, travel dates or identity information. The marketplace shares only the fields the supplier actually needs, states retention, and keeps private order data apart from anything the user chooses to share in the Social App.

**A receipt can prove route history without making personal travel or purchase detail public.**

## What has to ship before launch

Supported categories and jurisdictions, supplier contracts, inventory and pricing interfaces, payment and refund terms, privacy controls, fraud prevention, customer support and dispute procedures. Specific suppliers, dates, fees and accepted assets are [Open Parameters](/nexon-docs/appendix/open-parameters.md) (OP-P04).

*Previous:* [*Wallet*](/nexon-docs/part-iv-products/04-product-stack/wallet.md) *· Next:* [*Stablecoin Card*](/nexon-docs/part-iv-products/04-product-stack/stablecoin-card.md)


---

# 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://nexon-3.gitbook.io/nexon-docs/part-iv-products/04-product-stack/marketplace.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.