> 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/other-features/connectors/payouts/smart-retries-in-payout.md).

# Smart Retries in Payout

Learn how Hyperswitch Smart Retries automatically recover failed payout attempts by re-routing transactions across connectors to maximize disbursement success rates.

Juspay Hyperswitch Smart Retries enable the automatic recovery of failed payout attempts by re-initiating transactions based on specific error types and connector availability. This mechanism optimizes the success rate of disbursements by evaluating whether a retry is likely to resolve the initial failure.

### How Smart Retries Work

Smart Retries are triggered based on connector-specific error configurations. A retry is only attempted if the error is categorized as recoverable and the configuration suggests a high probability of success upon re-attempt.

#### Retry Strategies

Hyperswitch employs two primary strategies for payout recovery:

* **Single Connector Retry:** If only one connector is configured for a specific payout method, eligible errors are retried through that same connector.
* **Multi-Connector Retry:** If multiple connectors are available for a payout method, Hyperswitch attempts the retry using the next available connector in your priority list.

#### Supported Payout Methods by Connector

Smart Retries are available for the following connector and method combinations:

| Connector   | Payout Methods           |
| ----------- | ------------------------ |
| Adyen       | Cards, Banks and Wallets |
| CyberSource | Cards                    |
| EBANX       | Banks                    |
| PayPal      | Wallets                  |
| Stripe      | Cards and Banks          |
| Wise        | Banks                    |

### Conditions and Constraints

The execution of a Smart Retry is governed by the following logic:

* **Method Consistency:** The payout method remains unchanged during a retry. For example, a failed bank transfer will not be retried as a card payout.
* **Error Configuration:** Retries are only initiated for error codes that have been loaded into the Hyperswitch engine. Merchants can submit custom error configurations to the Hyperswitch team.
* **Retry Limits:**
  * The system continues retrying until the payout is successful, the retry count is exhausted, or all eligible connectors are exhausted.
  * The default retry count is 5 per connector, which can be customized based on merchant requirements.
* **Multi-Connector Eligibility:** Multi-connector retries require at least two active [payout connectors](https://github.com/juspay/hyperswitch-docs/tree/main/docs/payouts/connectors/README.md) to be configured for the same payout method.


---

# 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/other-features/connectors/payouts/smart-retries-in-payout.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.