> 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/integrations/connectors-integrations/payouts.md).
# Payout Processors
Distribute funds programmatically to bank accounts, cards, and wallets via Hyperswitch's unified payout infrastructure, with smart routing, bulk operations, and independent tokenization.
### Overview
The Juspay Hyperswitch Payouts infrastructure allows you to programmatically distribute funds to third parties, including affiliates, contractors, and merchants, across a variety of payment methods. By integrating with global processors, Hyperswitch helps you manage the entire payout lifecycle from a single point of control.
* **Automate at scale:** Orchestrate high-volume bulk payouts. Schedule when each payout is created from your application.
* **Optimize reliability:** Use [smart retries](https://docs.hyperswitch.io/explore-hyperswitch/connectors/payouts/smart-retries-in-payout) and routing to minimize failed transfers.
* **Maintain compliance:** Reduce your PCI burden with secure, [processor-agnostic tokenization](https://docs.hyperswitch.io/explore-hyperswitch/payment-orchestration/quickstart/tokenization-and-saved-cards/network-tokenisation).
* **Unified visibility:** Track every payout across different regions and connectors in one dashboard.
### Key Features
#### High-velocity distribution
Move funds to bank accounts, cards, or digital wallets through your preferred connectors. Whether you are using funds collected through Hyperswitch or external sources, our API ensures a seamless transfer experience.
#### Intelligence and routing
Maximize payout success with [Smart Retries](https://docs.hyperswitch.io/explore-hyperswitch/connectors/payouts/smart-retries-in-payout). If a payout fails due to a temporary connector error, Hyperswitch automatically retries the transaction through the most viable path, ensuring your partners get paid on time without manual intervention.
#### Flexible data handling
* **Independent Tokenization:** Securely store card and bank data using our processor-independent vault. This gives you the flexibility to switch payout partners without losing your users' payment credentials.
* **Bulk Operations:** Effortlessly manage large-scale disbursements by uploading `.xlsx` or `.csv` files directly via the dashboard.
* **Account Verification:** Ensure the validity of recipient bank accounts through Stripe or other supported verification providers.
### Supported payout connectors
The payout connector enum defines **22** wire values: `adyen`, `adyenplatform`, `cybersource`, `deutschebank`, `ebanx`, `gigadat`, `gotyme_sanlam`, `loonio`, `mifinity`, `nomupay`, `nuvei`, `payone`, `paypal`, `stripe`, `truelayer`, `trustly`, `wise`, `worldpay`, `worldpayxml`, `envoy`, `itaubank`, and `santander`. See the [`PayoutConnectors` enum and its `snake_case` serialization](https://github.com/juspay/hyperswitch/blob/04ac0042fc99a2d305540a7c7ed9167279ce7052/crates/api_models/src/enums.rs#L46-L71).
Helcim is not a payout processor in this list. Connector-specific payment methods can differ, so check the relevant payout processor page before integration.
### Supported connectors
The router accepts 22 payout connector values. The names below are the variants of [`PayoutConnectors`](https://github.com/juspay/hyperswitch/blob/04ac0042fc99a2d305540a7c7ed9167279ce7052/crates/api_models/src/enums.rs#L46-L71), so the list is exactly what the router accepts.
| Connector | Regions | Cards | Bank Rails | Wallets |
| ------------------ | ------------ | --------------------------------------------------------------------- | ------------------------------ | ------------------------------ |
| **Adyen** | Global | - | SEPA | PayPal |
| **Adyen Platform** | Global | Visa, Mastercard | SEPA | - |
| **Cybersource** | Global | Major Networks | - | - |
| **Deutsche Bank** | Europe | - | SEPA | - |
| **Ebanx** | Brazil | - | Pix (Key)\* | - |
| **Envoy** | UK, EU & US | - | SEPA, BACS, ACH | - |
| **Gigadat** | Canada | - | Interac | - |
| **GotymeSanlam** | South Africa | - | PayShap, PayShap Proxy | - |
| **Itaubank** | Brazil | - | Pix, Pix Key, Pix EMV | - |
| **Loonio** | Canada | - | Interac | - |
| **Mifinity** | - | - | Declared only, not implemented | Declared only, not implemented |
| **Nomupay** | Europe | - | SEPA | - |
| **Nuvei** | Global | Visa, Mastercard, Amex, Discover, Diners Club, JCB, UnionPay, Interac | - | - |
| **Payone** | Europe | Major Networks | - | - |
| **PayPal** | Global | - | - | PayPal, Venmo\*\* |
| **Santander** | Brazil | - | Pix, Pix Key, Pix EMV | - |
| **Stripe** | Global | Debit Cards | ACH | - |
| **Truelayer** | UK & Europe | - | Open Banking | - |
| **Trustly** | Europe | - | Trustly (A2A) | - |
| **Wise** | Global | - | ACH, BACS, SEPA | - |
| **Worldpay** | Global | - | - | Apple Pay |
| **Worldpay XML** | Global | Visa, Mastercard | - | Apple Pay, Google Pay |
The regions and method columns are maintained by hand and are not derived from the connector declarations, so treat them as a guide and confirm with your connector. The connector names are the part tied to the source.
### Payout fields and wire values
Use these request values when you create or update a payout:
* `payout_type`: `card`, `bank`, `wallet`, or `bank_redirect`. These values come from [`PayoutType` with `snake_case` serialization](https://github.com/juspay/hyperswitch/blob/04ac0042fc99a2d305540a7c7ed9167279ce7052/crates/common_enums/src/enums.rs#L9216-L9224).
* `payout_method_data`: `card`, `bank`, `wallet`, `bank_redirect`, `passthrough`, or `bank_transfer`. These values come from [`PayoutMethodData` with `snake_case` serialization](https://github.com/juspay/hyperswitch/blob/04ac0042fc99a2d305540a7c7ed9167279ce7052/crates/api_models/src/payouts.rs#L254-L261). `bank` is deprecated in the source, which directs new integrations to `bank_transfer` instead; prefer `bank_transfer` unless you are maintaining an existing integration.
* For `bank_transfer`, `payout_method_type`: `ach`, `bacs`, `sepa`, `pix`, `pix_key`, `pix_emv`, `trustly`, `open_banking`, `payshap`, `payshap_proxy`, or `ted`. The field is the tagged discriminator on [`BankTransfer`](https://github.com/juspay/hyperswitch/blob/04ac0042fc99a2d305540a7c7ed9167279ce7052/crates/api_models/src/payouts.rs#L425-L438).
```json
"payout_type": "bank",
"payout_method_data": {
"bank_transfer": {
"payout_method_type": "ach",
"bank_account_number": "",
"bank_routing_number": ""
}
}
```
`payout_type` is a plain string. `payout_method_data` is not: it is an object keyed by the method name, because [`PayoutMethodData`](https://github.com/juspay/hyperswitch/blob/04ac0042fc99a2d305540a7c7ed9167279ce7052/crates/api_models/src/payouts.rs#L254-L261) carries the method's details and is externally tagged. Sending `"payout_method_data": "bank_transfer"` is not a valid request. Inside `bank_transfer`, the method type is a field rather than another level of nesting, because [`BankTransfer`](https://github.com/juspay/hyperswitch/blob/04ac0042fc99a2d305540a7c7ed9167279ce7052/crates/api_models/src/payouts.rs#L425-L438) is tagged on `payout_method_type`.
Crypto assets are not modeled as payout methods. This includes USDT. The payout method enums have no crypto or USDT wire value.
### FAQ
**Can I use Hyperswitch solely for payouts without payments?**
Yes. Hyperswitch is modular. You can use our infrastructure to handle payouts independently of your payment collection. You can initiate payouts via direct payment info or by using an existing Token ID.
**Can Hyperswitch schedule recurring payouts?**
The payout service can reuse a saved payout method for a later payout, but your application must decide when to create each payout. The create validator treats a request with `payout_method_id` as a recurring payout and requires `confirm: true`; it does not define a schedule or recurrence interval. See the [`validate_create_request` check](https://github.com/juspay/hyperswitch/blob/04ac0042fc99a2d305540a7c7ed9167279ce7052/crates/router/src/core/payouts/validator.rs#L136-L152). Follow [Payouts with Saved Payment Methods](/integrations/connectors-integrations/payouts/get-started-with-payouts/process-payouts-using-saved-payment-methods.md) for method reuse.
**What is the benefit of independent tokenization?**
It prevents vendor lock-in. By tokenizing sensitive data independently of the underlying processor, you retain ownership of your data and can route payouts to any supported connector without asking your users to re-enter their information.
---
# 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/integrations/connectors-integrations/payouts.md?ask=&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.
