> 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/split-payments.md).

# Split Settlement

Unify your marketplace settlement logic across multiple processors through a single configuration.

### Overview

Split settlement refers to the process of dividing a single transaction into multiple parts, ensuring that funds are automatically distributed among different parties in real-time or through scheduled settlements.

This is essential for marketplaces, platforms, and businesses handling multi-party transactions, enabling seamless revenue sharing, commission deductions, and vendor settlements while maintaining accuracy and compliance.

### Hyperswitch Implementation

Juspay Hyperswitch provides payment functionality with connector-specific implementations supporting three major payment processors: Stripe, Adyen, and Xendit.

Each connector has distinct validation rules, data structures, and split models tailored to their specific requirements. This abstraction allows you to manage multi-party flows through a single orchestration layer.

### Configuration Requirements

* Business Profile: Split Settlement must be enabled at the business profile level through the `split_txns_enabled` flag. This allows merchants to configure this functionality per profile.
* Account Setup: Proper merchant connector account (MCA) setup is required before split settlement can be utilized.

### Connector-Specific Split Models

The table below outlines the specific capabilities supported by each processor integration:

| Processor                                                                               | Key Capabilities                                                                                                                                |
| --------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| [Xendit](/integrations/connectors-integrations/split-payments/xendit-split-payments.md) | Supports both single splits and multiple route distributions, with flexible routing options including flat amounts and percentage-based splits. |
| [Adyen](/integrations/connectors-integrations/split-payments/adyen-split-payments.md)   | Provides various split types including balance accounts, commissions, and fees with detailed charge response tracking.                          |
| [Stripe](/integrations/connectors-integrations/split-payments/stripe-split-payments.md) | Implements application fees and destination accounts for revenue sharing scenarios.                                                             |


---

# 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/split-payments.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.