> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integration-guide/workflows/intelligent-routing/routing-strategies.md).

# Routing Strategies

Choose the routing strategy based on the problem you are solving. Static strategies give you deterministic control. Dynamic strategies use observed performance or cost data and should be rolled out after you have enough traffic and monitoring.

| Strategy                                                                                                                    | Use it when                                                                                                        | Requires                                        |
| --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------- |
| [Rule-Based Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/rule-based-routing.md)             | A business condition must force a processor, split, or fallback list.                                              | Processor setup and rule conditions.            |
| [Volume-Based Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/volume-based-routing.md)         | You want a fixed traffic allocation or a controlled ramp to a new processor.                                       | Processor setup and percentage allocation.      |
| [Auth-Rate Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/auth-rate-based-routing.md)         | Multiple processors can handle the same traffic and you want routing to adapt to recent authorization performance. | Outcome feedback and enough volume for scoring. |
| [Multi-Objective Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/multi-objective-routing.md)   | You want to reduce processing cost without ignoring authorization performance.                                     | Auth-Rate Routing and cost coverage.            |
| [Least Cost Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/least-cost-routing.md)             | You process supported debit card traffic where local debit networks can reduce cost.                               | Debit support and enabled local networks.       |
| [Default Fallback Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/default-fallback-routing.md) | You need the backup processor order for unmatched or ineligible routing results.                                   | At least one configured processor.              |

## Recommended Starting Point

1. Configure [Default Fallback Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/default-fallback-routing.md).
2. Use [Rule-Based Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/rule-based-routing.md) for known business constraints.
3. Use [Volume-Based Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/volume-based-routing.md) to ramp new processors.
4. Use [Auth-Rate Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/auth-rate-based-routing.md) when multiple processors can handle the same traffic.
5. Add [Multi-Objective Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/multi-objective-routing.md) once processor cost data is available.
6. Use [Least Cost Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/least-cost-routing.md) for supported debit network optimization.

{% hint style="info" %}
Screenshot placeholder: Routing strategy selection page with available strategy cards.
{% endhint %}


---

# 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.hyperswitch.io/integration-guide/workflows/intelligent-routing/routing-strategies.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.