Spilt Settlements

1. Introduction

Split Settlements solution offered by BillDesk is a convenient way to manage merchant receivables in case the merchant has multiple settlement accounts. Eliminate the extra effort in payment reconciliation & accounting with BillDesk's Split Settlement solution.


2. Salient Features

  • Configure multiple settlement accounts - No cap on the number of the settlement accounts which can be configured allowing merchant flexibility in managing their business
  • Plug and play integration - Integration supported across BillDesk Neo – Full Redirect options, Ace – SDK and CX+ – Deep API ensuring a consistent experience

3. API Orchestration of Split Settlements

For split settlements, BillDesk will provide the merchant with one primary and multiple (depending on the requirement) child merchant IDs. These child merchant id's are linked to individual settlement accounts.

Split Settlements can be used with multiple BillDesk workflows. The below table outlines the steps involved in each of these. A detailed explanation of the Split Settlement object is available in the API Explorer section of the BillDesk documentation section and the link to the same has been referenced in the relevant section below:

Workflows

Workflow

API Reference

Steps

Neo – Full Redirect and Ace – SDK

Create Order

• Include the Split Settlement object in the Create Order API request.
• Specify the distribution of the transaction amount among the child merchant id's.
• Launch the BillDesk Neo – Full Redirect/ Ace – SDK.
• The customer will complete the transaction.
• BillDesk will settle the transaction amount to the individual settlement accounts as specified in the Create Order API request.

BillDesk CX+ – Deep API

Create Transaction

• Include the Split Settlement object in the Create Transaction API request body.
• Provide the relevant page for the customer to complete the payment.
• The customer will complete the transaction.
• BillDesk will settle the transaction amount to the individual settlement accounts as specified in the Create Order API request.

See also

💬

Review the associated workflows

Quick links to access the workflows which support AVS.