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

# Volume-Based Routing

Distribute payment traffic across multiple processors by percentage

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

Volume-Based Routing distributes payment traffic across processors using fixed percentages, independent of transaction attributes. In the dashboard, this strategy is called **Volume Split**. The dashboard labels processors as gateways.

## How It Works

For each payment, Hyperswitch uses the configured percentages to choose the preferred processor. With Stripe at 70% and Adyen at 30%, each payment has a 70% chance of preferring Stripe and a 30% chance of preferring Adyen.

These percentages describe traffic allocation across many payments. They do not guarantee that exactly seven out of every ten payments go to Stripe. Processor eligibility and fallback can also affect the final distribution. Each payment is assigned a preferred processor. The split does not divide an individual payment amount.

The separate Volume Split strategy applies without payment conditions. To split only a subset of traffic, such as USD card payments, use **Volume Split** within a [Rule-Based Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/rule-based-routing.md) condition block.

## When To Use It

Use Volume-Based Routing to manage traffic allocation:

* Gradually move traffic to a new processor.
* Keep multiple processors active.
* Meet a planned traffic allocation.
* Run a simple production rollout before switching to a dynamic strategy.

## Setup In Decision Engine Routing

Before you start, connect the processors you want to use for the selected profile and review its [Default Fallback Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/default-fallback-routing.md). You need permission to manage routing to create or activate a rule.

{% hint style="info" %}
If your account still shows the older routing interface, open `Workflow` > `Routing` and select `Setup` for Volume-Based Routing. The steps below describe the Decision Engine Routing interface.
{% endhint %}

### 1. Open Volume Split

1. Select your merchant account and **Profile** in the dashboard.
2. Go to **Decision Engine Routing** > **Volume Split**.
3. Click **Create Rule**.
4. Enter a **Rule Name**, such as `Stripe 70 Adyen 30`, and an optional **Description**.

<figure><img src="https://1943537505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf7BGdsPkCw9nalhAIlE%2Fuploads%2Fgit-blob-7083f3a999248a98b10cf3fb7dcc8b58270c07ca%2Fdecision-engine-volume-split-overview.png?alt=media" alt="Decision Engine Routing > Volume Split page showing the selected profile, no configured volume split rules, and the Create Rule button."><figcaption><p>Open Volume Split for your selected profile and click Create Rule to configure a traffic split.</p></figcaption></figure>

### 2. Set The Traffic Distribution

For a 70% Stripe / 30% Adyen allocation, follow these steps.

1. Under **Traffic Distribution**, select your configured Stripe processor in the first row and Adyen in the second row. Selecting a configured processor fills its **Gateway ID**. If you have multiple accounts for a processor, choose the intended account.
2. Set Stripe's **Split %** to **70** using the percentage field or slider.
3. The last row automatically receives the remaining percentage. Adyen shows **30%** with an **Auto** label. You do not edit that percentage directly.
4. Check that **Total** shows **100%** and review the allocation in **Rule details**.

Use **Add Gateway** to include more processors, or remove a row you no longer need. The final row always receives the remainder. If the other rows exceed 100%, reduce their percentages before saving.

<figure><img src="https://1943537505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf7BGdsPkCw9nalhAIlE%2Fuploads%2Fgit-blob-7b45ad95c0fe679622c108dda8d9ecb3a0d317c9%2Fdecision-engine-volume-split-builder.png?alt=media" alt="Volume Split builder showing Stripe at 70%, Adyen at an automatically calculated 30%, a 100% total, and the Rule details allocation preview."><figcaption><p>Set Stripe to 70%. Adyen receives the remaining 30% automatically, with the full allocation shown in Rule details.</p></figcaption></figure>

### 3. Save And Activate

1. Click **Create Rule** to save the split.
2. Find the saved rule on the Volume Split list. Its status is **Inactive**. Saving alone does not change payment routing.
3. Open its actions menu and select **Activate**.
4. If a Rule-Based configuration is active, review the replacement confirmation and click **Yes, activate** to switch to Volume Split.
5. Confirm that the split's status is **Active**.

<figure><img src="https://1943537505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf7BGdsPkCw9nalhAIlE%2Fuploads%2Fgit-blob-bfe0ff4b8dc05b40965c30b497d2a7c609e87928%2Fdecision-engine-volume-split-activate.png?alt=media" alt="Saved Volume_Split_Rule marked Inactive with a Stripe 70% and Adyen 30% distribution, and its actions menu open to Activate."><figcaption><p>Saved splits remain inactive until you select Activate from the actions menu.</p></figcaption></figure>

{% hint style="warning" %}
Activating Volume Split replaces the active Rule-Based configuration for these payments. The Rule-Based conditions stop applying. Activating Rule-Based Routing later replaces the active Volume Split rule.
{% endhint %}

<figure><img src="https://1943537505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf7BGdsPkCw9nalhAIlE%2Fuploads%2Fgit-blob-978326d9d23791b93713f7dcad3f296337ef25e1%2Fdecision-engine-volume-split-active.png?alt=media" alt="Volume_Split_Rule marked Active with a Rule activated confirmation and an expanded Stripe 70% and Adyen 30% allocation."><figcaption><p>Confirm that the split is Active. Expand the row to review the configured 70% Stripe and 30% Adyen allocation.</p></figcaption></figure>

## Change Or Deactivate A Split

To update an inactive split, open its actions menu, select **Edit**, change the allocation, and click **Save Changes**. Activate it when you are ready to use it.

To adjust an active split while keeping it in use, select **Duplicate**, update the copy, and click **Create Rule**. The copy is saved as **Inactive**. Activate it when you are ready to replace the original split.

To stop using a split, select **Deactivate** and confirm. It remains saved and can be activated again.

## Notes

Choose processors that support the payment methods and currencies you intend to route. An ineligible preferred processor can change the final allocation. Keep [Default Fallback Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/default-fallback-routing.md) configured so payments have a backup path when the routing result does not provide an eligible processor.


---

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