> 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/default-fallback-routing.md).

# Default Fallback Routing

Configure the backup processor order used when no routing rule applies or the selected processor is not eligible

{% embed url="<https://youtu.be/5ymPEkOf-BQ>" %}

Default Fallback Routing is the priority order of configured processors for a merchant profile. Hyperswitch can use this order on its own, or as the backup path when another routing strategy does not return a usable processor.

## When It Applies

Default fallback can be used in the following situations:

* No routing configuration is active.
* A rule or volume split points to a processor that does not support the payment method.
* A processor is temporarily unavailable.
* A dynamic routing result cannot be used safely.

## Setup

{% hint style="info" %}
If your account still shows the older routing interface, open `Workflow` > `Routing` and click `Manage` for Default Fallback. The steps below describe the Decision Engine Routing interface.
{% endhint %}

1. Select your merchant account and **Profile** in the dashboard.
2. Go to **Decision Engine Routing** > **Default Fallback**.
3. Confirm the **Profile** on the fallback page and review its configured processors.
4. Drag and drop processors into your preferred priority order, from top to bottom.
5. Click **Save Changes**, then confirm with **Yes, save it**.

<figure><img src="https://1943537505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf7BGdsPkCw9nalhAIlE%2Fuploads%2Fgit-blob-a5076cf083bb7d027cfdb9694d416a32447e1ee9%2Fdecision-engine-default-fallback.png?alt=media" alt="Decision Engine Routing > Default Fallback page showing the selected profile, Stripe first and Adyen second, drag handles, priority positions, and Save Changes."><figcaption><p>Drag processors into your preferred fallback order, then click Save Changes.</p></figcaption></figure>

When no Rule-Based block matches a payment routed through Hyperswitch, this profile-level order is used instead of the rule builder's **Default Fallback Gateway**, provided the profile has a fallback list. Review this order whenever you change your routing configuration.

## Good Practices

Put your most reliable general-purpose processor first, followed by processors that support the broadest set of payment methods and currencies. Review this list whenever you add or remove a connector.


---

# 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/default-fallback-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.
