> For the complete documentation index, see [llms.txt](https://docs.aces.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aces.fun/rwa-marketplace/concierge-sales-process.md).
# Concierge Sales Process
On ACES.fun v1, Sellers and Buyers will handle the sales process between themselves. This version will only allow the Community Reward to be funded by the Seller. v2 will handle the payment processing and will allow the reward to be funded from the payment.
1. **Auction Listing & Initial Bidding**
* A seller submits their asset for listing on Aces.fun and sets a Reserve Price.
* Aces.fun team verifies the listing and gets the RWA ready for launch.
* As soon as the asset token launches on Aces.fun, buyers can start placing bids.
* After the token bonds, bidding continues for an additional week, allowing the community to drive price discovery.
2. **Claim Period**
* At the end of the week, the highest bid above the Reserve Price earns the first claim to purchase the asset and has 24 hours to complete payment.
* If this highest bidder fails to pay within that 24-hour window, any other bid above the Reserve Price then has 24 hours to purchase the asset.
* If there are no purchases within the second 24-hour period, the asset becomes available for anyone to purchase at the Reserve Price.
3. **Payment and Logistics**
* Funds are held at the payment processor until the buyer confirms receipt of the asset.
* The seller retains primary responsibility for arranging delivery and completing any required paperwork, but can also access additional services from the Aces.fun team and/or AI Agent for a smoother transaction.
* Both seller and buyer must complete the transaction verification process: seller confirms shipment details with tracking, buyer inspects the asset upon receipt, both parties verify the asset's condition matches the listing, buyer signs off on successful delivery, and seller confirms the completion - all steps are documented by the AI Agent.
4. **Transfer of Asset and Ecosystem**
* Upon payment confirmation, the buyer receives the physical RWA along with control of all the digital assets like the AI Concierge and associated social accounts.
* The buyer also inherits the NFT, which entitles them to a share of the asset token’s trading fees.
5. **Payment Distribution**
* Seller: Receives 90% of the sale price in crypto or fiat, based on preference minus the sales fee.
* Token Holders: Receive the sales fee up to 10% (in USDC, USDT, or wETH), allocated proportionally based on their share of the owned token supply.
6. **Fintech On/Offramp**
* An integrated on/offramp system enables buyers to pay in their preferred currency while allowing sellers to select their payout method, ensuring secure and efficient high-value transactions.
This streamlined sales process combines immediate bidding, a defined claim period, robust escrow, and seamless payment systems—creating a competitive, transparent environment.
---
# 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://docs.aces.fun/rwa-marketplace/concierge-sales-process.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.