> 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/core-protocol/multi-token-settlement.md).

# Multi-Token Settlement

### **Overview**

**Multi-Token Settlement** gives users and service providers freedom to transact in the token they prefer **$402G**, **USDC**, or **SOL** without friction.\
The protocol routes payments automatically and settles them instantly, ensuring stable and efficient micropayments regardless of currency volatility.

#### **Flow**

1. User selects token → pays via connected wallet.
2. Protocol verifies and records transaction on Solana.
3. Merchant receives value in their preferred token.
4. Optional on-chain conversion occurs (via Jupiter / Raydium).

#### **Core Benefits**

* **Token Flexibility** – Users can pay in any supported token.
* **Auto Routing** – Smart contract ensures recipient gets correct asset.
* **Transparent Analytics** – Each transaction categorized per token on dashboard.

#### **Developer Controls**

Developers can:

* Set preferred settlement token.
* Define conversion thresholds.
* Enable auto-conversion or direct transfers.

Example:

```json
{
  "acceptedMints": ["402G","USDC","SOL"],
  "settlementToken": "USDC",
  "autoConversion": true
}
```

#### **Why It Matters**

This model ensures **interoperability, token neutrality, and efficiency**, allowing 402Gate to function across multiple ecosystems while keeping its own native token **$402G** at the protocol’s core.


---

# 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/core-protocol/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.