> For the complete documentation index, see [llms.txt](https://docs.402gate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.402gate.com/use-cases/multi-token-settlement.md).

# Multi-Token Settlement

The Web3 ecosystem is multi-asset by design.\
402Gate supports settlement in **$402G**, **USDC**, or **SOL**, allowing both users and providers to choose their preferred currency while maintaining instant finality.

#### **Use Case Points**

1. **User Choice, Provider Stability**\
   Users select any token they hold; providers still receive their chosen asset thanks to automatic on-chain conversion.
2. **Seamless Conversion**\
   Integration with Raydium/Jupiter ensures real-time swaps during settlement maintaining exact value parity.
3. **Transparent Reporting**\
   The dashboard logs all token types, conversion ratios, and volume metrics, ensuring full visibility for businesses and investors.

> *“Any token. Any user. One seamless settlement.”*


---

# 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.402gate.com/use-cases/multi-token-settlement.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.