Skip to main content

Conditional Residuals Splits

Updated

Overview

Conditional Splits allow ISOs and partners to define multiple residual split rules per user based on merchant attributes such as processor, group, custom properties, or lead source.

Instead of relying on a single default residual split per user, Conditional Splits provide:

  • Greater flexibility for complex compensation models
  • Deterministic rule evaluation with clear priority order
  • Automatic split calculation across assignment workflows
  • Auditable and consistent split logic across Merchant Central

This feature is ideal for larger organizations where compensation varies depending on merchant characteristics. Conditional Splits ensure the correct split is applied automatically — reducing manual adjustments and improving operational accuracy.

Prerequisites

Before using Conditional Splits:

  • You must be an Admin user
  • You must have Residuals Management permissions
  • The feature must be enabled for your organization

💡If you do not see the Conditional Splits page, contact your system administrator and ask them to enable the RESIDUAL_CONDITIONAL_SPLIT feature flag.

  1. Navigate to Manage → Residuals
  2. Click Conditional Splits 
    01.png

On the Manage Conditional Splits page, you will see:

  • A table listing all configured Conditional Splits
  • Split name
  • Number of rules
  • Edit and Delete actions
  • Add New Conditional Split button 
    02.png

How Conditional Splits Work

Conditional Splits use rule-based logic to determine the correct residual split for a specific User–Merchant pair.

Each user may have:

  • Multiple conditional rules
  • Explicit rule priority (position-based ordering)
  • A fallback default residual split

Supported Conditions

Rules can be based on merchant attributes such as:

  • Processor (e.g., First Data, TSYS)
  • Merchant Group
  • Custom Properties
  • Lead Source or Campaign
  • Other merchant-level attributes

Deterministic First-Match Logic

Rules are evaluated in ascending priority order.

  • The first rule that matches all conditions is applied.
  • If no rules match, the system falls back to the user’s default residual split.
  • Rules do not merge or stack.
  • Only one rule is applied per evaluation.

This ensures predictable and auditable split determination.

How to Create a Conditional Split Configuration

  1. Navigate to Conditional Splits
  2. Click Add New Conditional Split
  3. Enter a name for the configuration
  4. Click Add 
    03.png

Once created, you can configure rules and assign users.

How to Add and Configure Rules

  1. Open a Conditional Split configuration
  2. In the configuration popup, go to the Rules tab
  3. Click Add Rule
    05.png
  4. In the popup window that appears, define:
    • Match Mode (AND or OR): AND requires all conditions to match (such as group, processor, campaign, etc.), while OR requires at least one condition to match
    • Conditions (processor, group, property, etc.)
    • Split percentage, split structure, and pay order
  5. Save the rule
    06.png

Reordering Rules

Rules are evaluated by priority order.

  • Move rules up or down to adjust evaluation order.
  • The top rule is evaluated first.
    07.png

Overriding Split Information Per User

When a configuration is assigned to a user, split percentages can be adjusted per user if needed.

This allows reuse of rule logic while maintaining flexible compensation percentages.

How to Assign Conditional Splits to Users

  1. Open a Conditional Split configuration
  2. Navigate to the Assign Users tab in the popup
  3. Use the filters above the user tables to narrow down the list of users
  4. Select users to assign the configuration (using checkboxes to the left of user names)
  5. Click Apply 
    08.png

Once assigned:

  • The system will evaluate conditional rules whenever a merchant is linked to that user.
  • The user’s default split remains as a fallback.

How Split Evaluation Works (Priority & Fallback)

When a merchant is assigned to a user:

  1. The system retrieves the user’s assigned conditional rules.
  2. Rules are evaluated in ascending priority order.
  3. The first matching rule is applied.
  4. If no rules match, the user’s default residual split is used.

This evaluation occurs server-side to ensure performance, auditability, and consistency across all workflows.

The system logs the applied rule for auditability and transparency.

Processes That Use Conditional Splits

Conditional splits are automatically applied in the following workflows:

  • Manual User–Merchant Assignment
  • Merchant Import (when split is not explicitly provided)
  • Merchant Updater (Mass Actions)
  • Create Merchant from Lead
  • TurboApp Boarding
  • REST API assignment endpoints
  • Residuals Import (ASSIGN function)

If a split is explicitly provided during import, that value will be used. Otherwise, the system computes the split using conditional rules.