> 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.md). # The NEXON Product Ecosystem Five product surfaces close one financial-social value loop, with AI-Native PayFi as the second focus of the narrative. > Discover in Social → decide in Wallet → route through PayFi → use in Marketplace or Card → return with data, relationships and activity. NEXON's product direction is a **financial-social ecosystem** built from five connected surfaces: AI-Native PayFi, the Wallet, the Marketplace, the Stablecoin Card and a decentralized Social App. They are not five unrelated feature lists — each owns **one particular moment** in the user's value loop, and each carries its own set of responsibilities. AI-Native PayFi is the **second focus** of the overall narrative. The first remains NEXON's own thesis and dual-asset architecture: NEXON connects capital, digital finance and real consumption; XO carries value, EXON drives circulation. PayFi is what makes that thesis tangible — it turns an objective into a route that can be checked, approved, executed and receipted. ## Five surfaces, one loop | Product | Its place in the loop | What it does not become | | ------------------------ | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------- | | Decentralized Social App | Discovery, communities, communication, strategy context, value interaction | Automatic financial authority, or investment advice | | Wallet | Asset state, permissions, staking access, decision support, third-party entry points | A new source of yield | | AI-Native PayFi | Intent capture, route preview, policy checks, approval, execution coordination, receipts | Custodian, merchant, compliance authority or return engine | | Marketplace | Travel, hotel, goods and services inventory, with supplier fulfillment evidence | A NEXON guarantee of every supplier's performance | | Stablecoin Card | Everyday acceptance through a licensed issuer/operator | A card that has already been issued | ## The target experience {% stepper %} {% step %} ### Discover in Social A user encounters a community discussion, a strategy, an event or a travel idea. Social context can help form an intent. It **cannot** spend, trade or approve on their behalf. A strategy someone shared is information, not an instruction. {% endstep %} {% step %} ### Decide in Wallet The user sees available balances, protected reserves, current staking positions, permissions already granted and relevant third-party experiences. The wallet helps them decide **which resources may even be considered**. {% endstep %} {% step %} ### Route through PayFi The user states the outcome and the constraints. PayFi structures the intent, compares eligible paths, applies policy, and lays out costs, timing, parties and irreversible steps. The user approves a bounded route. {% endstep %} {% step %} ### Use in Marketplace or Card The route reaches a real-world endpoint. The Marketplace connects to travel, hotel, goods or services inventory; the Stablecoin Card extends eligible value through a licensed issuer. **The supplier or issuer owns its leg, and payment settlement is booked separately from fulfillment.** {% endstep %} {% step %} ### Return with data, relationships and activity Receipts, preferences and outcomes can improve the next decision, within consent and retention rules. A completed action can return to the social layer if the user chooses. **Private financial state does not become social content by default.** {% endstep %} {% endstepper %} ```mermaid flowchart LR S["Social
discover"] --> W["Wallet
decide"] W --> P["PayFi
route and approve"] P --> M["Marketplace
use"] P --> C["Stablecoin Card
use"] M --> R["Receipts · preferences · relationships"] C --> R R -. "user decides" .-> S R -. "policy and history" .-> W classDef anchor fill:#047854,stroke:#047854,stroke-width:1.5px,color:#F5F3F0 classDef engine fill:#8B5CF6,stroke:#8B5CF6,stroke-width:1.5px,color:#F5F3F0 classDef solid fill:#F5F3F0,stroke:#141414,stroke-width:1.2px,color:#141414 class S,W,M,C solid class P anchor class R engine ``` ## The seams inside the loop The loop is a product narrative, not a circular guarantee. Both assets keep their confirmed mechanical roles. XO currently carries staking principal. EXON is currently the spot, release, purchase, check and burn asset. Every surface has to keep its **responsible executor** visible: * a wallet view does not merge custody; * a PayFi recommendation does not replace user approval; * a marketplace payment does not prove delivery; * a card interface does not replace the issuer's terms; * social popularity does not establish suitability. ## Progress measured by capability gates Progress is measured by evidence, not calendar promises. To move past planned, a product has to deliver: published specifications, a threat model, custody and issuer arrangements, jurisdictional review, test results, incident procedures and user-facing disclosures. **When the gates are met and availability is published, the product is live. Not before.**
Decentralized Social AppDiscovery and context. Let relationships enrich decisions without letting social pressure bypass control.Social
AI-Native PayFiThe second focus. Six stages from financial intent to execution evidence.PayFi
WalletFinancial home and control surface: state, permissions, staking access, decision support.Wallet
MarketplaceThe real-consumption leg. Payment and delivery are two different facts.Marketplace
Stablecoin CardEveryday acceptance, resting on a licensed issuer/operator.Stablecoin Card
*Previous:* [*Data & Oracles*](/nexon-docs/part-iii-architecture/03-architecture/data-and-oracles.md) *· Next:* [*Decentralized Social App*](/nexon-docs/part-iv-products/04-product-stack/social.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.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.