> For the complete documentation index, see [llms.txt](https://docs.reloadsol.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reloadsol.app/trade/order-execution-and-mechanics.md).

# Order execution, slippage & fees

How reloadSol quotes swaps, enforces dynamic slippage (0.50%–10.00%) and 15% price-impact caps, handles fees, and verifies on-chain receipts.

**TL;DR:** Every swap is quoted fresh at click time, guarded against > **15%** price impact, simulated with exact bytes before signing, and marked **Confirmed** only after an on-chain receipt succeeds.

[Open reloadSol Sell →](https://reloadsol.app/sell/solana)

***

## Execution parameters

| Setting                    | Default                           | What it does                                                                                                                             |
| -------------------------- | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| **Dynamic slippage**       | **0.50% – 10.00%** (50–1,000 bps) | Scales automatically with token volatility; manual overrides are respected.                                                              |
| **Max price impact**       | **15%**                           | Routes above 15% [price impact](https://docs.reloadsol.app/start-here/trading-terms.md#quote-and-execution) are rejected before signing. |
| **Solana managed landing** | **Jupiter Swap V2** (\~1.5s–2.1s) | Falls back to Shyft/Helius RPC if managed landing is unavailable.                                                                        |
| **Platform fee**           | **0.25%** (25 bps, when active)   | Built into the same batch approval—**fail-open** so a fee issue never blocks your swap.                                                  |

***

## Receipt-gated confirmation lifecycle

```mermaid
sequenceDiagram
    actor Trader
    participant UI as reloadSol UI
    participant Chain as Solana / Robinhood
    Trader->>UI: Click Confirm
    UI->>Trader: Wallet signature prompt (after exact-bytes simulation)
    Trader->>Chain: Broadcast signed transaction
    Chain-->>UI: On-chain receipt (success or reverted)
    alt Receipt succeeded
        UI->>Trader: Confirmed + Solscan / Blockscout link
    else Reverted or rejected
        UI->>Trader: Failed (exact leg attribution)
    end
```

A trade is **never** marked confirmed simply because you clicked approve. If a transaction reverts on-chain or expires, your history reflects **Failed** with the exact failing leg.

{% hint style="warning" %}
**Slippage vs. price impact:** Slippage protects you from price movement *while your transaction is in flight*. Price impact is caused by *your own order size* against pool liquidity. Raising slippage will not fix an illiquid pool.
{% endhint %}

***

## Related

* [What is checked before you sign](https://docs.reloadsol.app/start-here/paper-trading-and-safety.md)
* [Trading terms in 5 minutes](https://docs.reloadsol.app/start-here/trading-terms.md)
* [Troubleshooting & FAQ](https://docs.reloadsol.app/help/troubleshooting-and-faq.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reloadsol.app/trade/order-execution-and-mechanics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
