# Asynchronous Routing ION Finance uses a unique system for routing, a staple in most AMM Dex platforms. This method allows the system to determine the most efficient pathway for a token swap, even if it means routing through multiple pools to get the best rate. Given the asynchronous nature of TON, a perfect rollback isn’t feasible. If a swap gets interrupted midway because of excessive slippage, the system will yield an intermediate result. **Example:** Suppose you want to swap token A for token C, but there's no direct pool for A to C. The system might route your swap from A to B and then B to C. However, if the A to B step faces too much slippage, the swap might stop there, and you'll receive token B instead of C. --- # Agent Instructions: 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: ``` GET https://ion-finance.gitbook.io/ion-finance/concepts/asynchronous-routing.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.