> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/marketplace-pricing-and-checkout.md).

# Marketplace pricing & checkout

SONIC Marketplace is **SOL-first in presentation and checkout**, while each listing preserves exactly one authoritative atomic commercial price.

## Listing authority

A listing owns its authoritative price identity and references the creative asset, creator, optional project, rights policy and active license offer. It does not persist independent SOL and USDC prices.

```ts
type MarketplaceListingPrice = {
  quoteCurrency: "SOL" | "USDC" | "EURC" | "SONIC";
  amountAtomic: bigint;
  decimals: number;
};
```

## Display and quote

Cards may render SOL as primary with the USDC estimate underneath. A short-lived server quote converts the authoritative listing price into the chosen payment currency and expires. Re-quote occurs before transaction preparation; material movement returns a fresh quote instead of silently changing the signing amount.

## Durable order state machine

`CREATED → QUOTE_LOCKED → PAYMENT_PENDING → SUBMITTED → CONFIRMING → PAID → LICENSE_ISSUED → FULFILLED`

Exceptional states include `EXPIRED`, `FAILED`, `REFUND_PENDING`, `REFUNDED`, and `DISPUTED`. Arbitrary transitions are rejected.

## Immutable order snapshot

Before wallet authorization, SONIC creates a durable Marketplace order snapshot containing:

* listing/asset identity;
* title and creator snapshots;
* authoritative price atomic amount, currency and decimals;
* license ID and version;
* immutable license-terms hash;
* Marketplace fee basis points;
* creator-settlement policy;
* settlement split snapshots.

Edits to a listing, project collaborators, license offer or fee policy after order creation cannot rewrite old economics.

## Rights and entitlements

Marketplace rights are modeled as:

`ASSET → RIGHTS POLICY → LICENSE OFFER → ORDER SNAPSHOT → VERIFIED PAYMENT → ENTITLEMENT`

A listing must reference an active license offer. A browser purchase response does not issue rights. Entitlement issuance occurs only after the payment has reached the required trusted settlement state.

## Settlement splits

Settlement splits are snapshotted per order and may include creator, collaborator, platform and treasury recipients. Settlement never reads today's collaboration configuration when paying an older order.

## Financial ledger

Verified payment records financial-ledger entries such as payment, fee and creator payable. Refund/settlement operations use their own idempotent ledger movements instead of rewriting one balance field.

## SOL-first hierarchy

Marketplace discovery remains SOL-primary, with USDC as the smaller estimated reference and EURC as an additional settlement option. SONIC appears only where explicitly denominated or enabled. AI Credits are not part of the Marketplace currency-conversion hierarchy.


---

# 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://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/marketplace-pricing-and-checkout.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.