# Split Settlement & Partner Fees

Distribute a single payment across multiple settlement recipients using predefined allocation instructions.

Split Settlement allows a single payment transaction to distribute funds to multiple settlement destinations.

Instead of depositing the entire transaction amount into a single settlement account, Deluxe accepts settlement instructions that allocate portions of the transaction to different recipients during settlement processing.

The customer sees a single payment transaction while Deluxe distributes the proceeds according to the provided allocations.

### Why Use Split Settlement?

Use Split Settlement when transaction proceeds belong to more than one party.

Common use cases include:

- Merchant revenue sharing
- Platform commissions
- Partner compensation
- Franchise distribution models
- Marketplace payments


Instead of receiving funds into a single account and manually transferring money later, Deluxe distributes funds according to the allocation instructions supplied with the transaction.

### How Split Settlement Works

#### High-Level Process

The platform provides settlement instructions as part of the payment request.

The payment authorizes and processes normally. During settlement, Deluxe uses the allocations to distribute funds into the configured recipient accounts.

**Business Transaction - Customer Transaction**
A customer initiates a transaction, beginning the payment process.

**Processing - Create Payment API**
The Create Payment API is used to create and submit the payment for processing.

**Authorization - Transaction Authorization**
The transaction proceeds through the authorization process to determine whether the payment can be approved.

**Outcome - Approved Transaction**
The transaction receives approval and advances to settlement.

**Settlement - Settlement Instructions Applied**
Settlement instructions are applied to determine how the approved transaction's funds will be allocated and distributed.

**Funding - Funds Distributed to Recipients**
Following settlement, funds are distributed through three separate payment allocations:

- **Payment Allocation 1** → Recipient Account 1
- **Payment Allocation 2** → Recipient Account 2
- **Payment Allocation 3** → Recipient Account 3


Each payment allocation directs funds to its corresponding recipient account, completing the illustrated payment workflow.

### Prerequisites

Before a transaction can be split:

- Split Settlement must be enabled.
- Recipient settlement accounts must exist.
- Settlement accounts must be configured and approved.
- Each destination account must have a valid disbursement identifier.


Supported account configuration is managed through merchant onboarding, bank profile configuration, and split funding setup.

### Configure Settlement Recipients

Split Settlement distributes funds using pre-configured settlement recipients.

Each recipient is associated with a settlement account and assigned a unique disbursement identifier that can later be referenced in payment requests.

#### Example Recipient Types

| Type | Purpose |
|  --- | --- |
| Primary Deposit | Main merchant funding account |
| Partner Fee | Partner settlement account |
| Other | Additional approved settlement account |


Banking profiles for Split Settlement are configured by Deluxe a part of the merchant setup. Work with your Deluxe Implementation or partner support team to provide the required settlement account information and obtain a Split Settlement-enabled merchant account and disbursement IDs before processing Split Settlement transactions.

Partner Support →
  
### Creating a Split

#### How Do I Tell Deluxe Where To Send Funds?

Include a `disbursement` array when creating the payment.

Each disbursement identifies:

- The recipient (`disbursementId`)
- The allocation purpose (`typeId`)
- The amount to allocate


Documented examples show split instructions supplied as part of the original payment request.

**For exact request and response schemas, see API Reference → Split Settlement.**

### Example Flow

#### Scenario

| Allocation | Amount |
|  --- | --- |
| Customer Purchase Amount | $100.00 |
| Merchant Allocation | $75.00 |
| Platform Fee | $20.00 |
| Partner Commission | $5.00 |
| **Total Allocations** | **$100.00** |


#### Flow of Funds

A $100.00 customer payment moves through payment creation, authorization, and settlement processing before the funds are divided among three settlement accounts according to predefined split instructions.

**Customer Checkout**
The customer initiates a **$100.00** payment during checkout.

**Platform Creates Payment**
The platform creates the payment and begins the payment processing flow.

**Payment Request**
A payment request for **$100.00** is submitted for authorization.

**Deluxe Authorization**
Deluxe processes the authorization request to determine whether the transaction can be approved.

**Approved Transaction**
After authorization is successful, the transaction is approved and proceeds to settlement processing.

**Split Instructions**
Split instructions define how the **$100.00** payment is distributed during settlement:

- **Primary deposit:** $75.00
- **Partner fee:** $20.00
- **Other:** $5.00


**Settlement Processing**
Settlement processing applies the split instructions to the approved transaction and distributes the funds to the designated settlement accounts.

**Funds Distribution**
The payment is distributed across three settlement accounts:

- **$75.00** → Primary Deposit Settlement Account
- **$20.00** → Partner Fee Settlement Account
- **$5.00** → Other Settlement Account


The three allocations total **$100.00**, matching the original customer payment.

#### Key Takeaway

The customer is charged **$100.00 once**.

Split Settlement does not create multiple payments or multiple authorizations.

Instead, the platform supplies allocation instructions that Deluxe uses during settlement to distribute proceeds to the configured recipient accounts.

### Core Disbursement Rules

1. **Disbursement is Optional, but Fields are Required and Atomic When Used**
  - The disbursement object in general is optional.
  - If disbursement instructions are provided, each object in the list must include the `disbursementId`, `amount`, `typeId`, and `description`.
  - If included, it must be treated as a single, atomic instruction tied to the transaction.
2. **Amounts Must Fully Reconcile**
  - The sum of all `disbursement.amount` values must equal the total transaction amount (payment or refund).
  - Partial, over, or under-allocation is not permitted.
3. **Applies Consistently Across Payment Types**
  - The same disbursement rules apply to:
    - Credit Card payments
    - ACH payments
    - Refunds
    - Complete Payment calls
  - No payment-type-specific exceptions exist.
  - Authorize does not support Disbursement instructions. Instructions should be sent in on the associated Complete Payment request after initial Authorization.
4. **Disbursement IDs Must Be Valid and Pre-Provisioned**
  - Each `disbursementId` must reference a valid, pre-configured disbursement account.
  - Invalid or unknown IDs should result in request rejection.
  - `TypeID` and `Description` should both match what is on file for the disbursement account.
5. **No Implicit or System-Derived Splits**
  - Splits are not inferred or automatically calculated.
  - All disbursement logic and math must be explicitly provided by the caller.
6. **Refunds Must Respect Original Allocation Logic**
  - When disbursement is supplied on a refund, the same reconciliation rule applies.
  - Refund disbursement amounts must total the refund amount exactly.
  - Refunding an original Create Payment that had disbursement instructions requires that the refund also has disbursement instructions, even if they are different from the original ones.
7. **Complete Payment Still Enforces Reconciliation**
  - Even in `/payments/complete`, disbursement totals must match the completion amount.
  - Multiple disbursement entries are allowed, but totals must still reconcile 1:1.


### Refunds

Split Settlement supports refunds. When submitting a refund with split instructions, the full refund amount must be allocated across the specified disbursements.

#### Refund Workflow

A refund for a previously settled split transaction is processed using the refund amount and refund split instructions to determine how the refunded funds are distributed.

**Original Split Transaction**
The refund process begins with the original split transaction.

**Settlement Completed**
The original split transaction has completed settlement before the refund is initiated.

**Refund Request**
A refund request is submitted for the settled transaction.

**Refund Amount and Split Instructions**
The refund request includes the amount to be refunded and the split instructions that define how the refund should be distributed.

**Refund Processing**
The refund amount and split instructions are used to process the refund.

**Refund Distribution**
The refund is distributed according to the specified split instructions.

As with payment requests, refund allocation instructions should account for the full refund amount.

### Error Handling

The below errors indicate a configuration issue:

- Split Settlement not enabled
- Invalid recipient reference
- Invalid disbursement identifier
- Recipient account not configured


Most Split Settlement issues can be resolved by validating merchant configuration, recipient setup, and disbursement identifiers before submitting the payment request.

### Best Practices

- Configure and validate recipient accounts before processing production transactions.
- Store and manage disbursement identifiers securely.
- Ensure allocation amounts equal the total transaction amount.
- Validate allocation instructions before submitting payment requests.
- Test split funding scenarios in Sandbox before Production deployment.
- Confirm recipient configuration during merchant onboarding.


### Related Resources

Reporting & Reconciliation
Review reporting data and reconcile distributed settlement activity.

Merchant Onboarding
Configure merchants, funding accounts, and recipient relationships required for Split Settlement.