> 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/rule-based-routing.md).

# Rule-Based Routing

{% embed url="<https://youtu.be/Zs6H1vAKTJM>" %}

Rule-Based Routing lets you configure one or more rules, where each rule has a condition and a processor preference. When a payment matches a condition, Hyperswitch uses the processor preference attached to that rule.

## How It Works

Rules are evaluated from top to bottom in the same order shown in the dashboard. The first matching rule is applied. If no rule matches, Hyperswitch uses your [Default Fallback Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/default-fallback-routing.md).

**Condition:** A condition is built from payment dimensions and logical operators. Common dimensions include payment method, payment method type, amount, currency, country, card type, and card network. Operators include equal to, greater than, lesser than, is, is not, contains, and not contains.

**Processor preference:** The processor, split, or fallback list Hyperswitch should use when the condition matches.

## Processor Preference Types

Every rule can use one of these processor preference types:

1. **Single choice of processor:** Route matching payments to one processor, such as `Stripe`.
2. **Split payments across processors:** Distribute matching traffic across processors, such as `Stripe: 70%` and `PayPal: 30%`.
3. **Single choice with fallback:** Route to one processor first, with one or more fallback processors if the first processor cannot process the payment.

## When To Use It

Use Rule-Based Routing when you need deterministic control, for example:

* Route a country or currency to a local acquirer.
* Send high-value payments to a processor with stronger risk handling.
* Route a payment method to a processor that has better support for it.
* Keep a processor preference tied to a commercial agreement.

## Setup In Smart Router

1. Go to `Workflow` > `Routing`.
2. Click `Setup` for Rule-Based Routing.
3. Save the rule name and description.
4. Use the no-code UI to configure conditions for your business logic.
5. Select the processor preference and click `Configure Rule`.
6. In the confirmation popup, choose whether to save the rule or save and activate it for payments.
7. Review your active routing algorithm and previously configured algorithms on the [Hyperswitch Dashboard](https://app.hyperswitch.io/routing).

<figure><img src="/files/E4s83sMEGG1fyDo0xHt7" alt=""><figcaption></figcaption></figure>

## Good Practices

Keep the most specific rules at the top and broad rules lower in the list. Always configure Default Fallback Routing so payments have a backup path when a rule output is not eligible for the payment.

## How Rule-Based Routing Works

{% embed url="<https://hyperswitch.io/video/Rule_Based_video.mp4>" %}


---

# 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/rule-based-routing.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.