Update the split logic

patch /merchants/{merchantId}/splitConfigurations/{splitConfigurationId}/rules/{ruleId}/splitLogic/{splitLogicId}

Changes the split logic specified in the path.

To make this request, your API credential must have the following role:

  • Management API - SplitConfiguration read and write

Endpoint destination URL

https://management-test.adyen.com/v1/merchants/{merchantId}/splitConfigurations/{splitConfigurationId}/rules/{ruleId}/splitLogic/{splitLogicId}
Click to copy

Path parameters

splitLogicId string Required

The unique identifier of the split configuration split.

ruleId string Required

The unique identifier of the split configuration rule.

splitConfigurationId string Required

The unique identifier of the split configuration.

merchantId string Required

The unique identifier of the merchant account.

Request parameters

additionalCommission object

Contains the logic used to calculate your user's commission, booked directly to their balance account.

chargeback string

Specifies the logic to apply when booking the chargeback amount.

Possible values: deductFromLiableAccount, deductFromOneBalanceAccount, deductAccordingToSplitRatio.

commission object Required

Contains the logic used to the calculate your platform's commission, booked to your liable balance account.

paymentFee string Required

Specifies the logic to apply when booking the transaction fees.

Possible values: deductFromLiableAccount, deductFromOneBalanceAccount.

remainder string

Specifies the logic to apply when booking the amount left over after currency conversion.

Possible values: addToLiableAccount, addToOneBalanceAccount.

surcharge string

Specifies the logic to apply when booking the surcharge amount.

Possible values: addToLiableAccount, addToOneBalanceAccount

tip string

Specifies the logic to apply when booking tips (gratuity).

Possible values: addToLiableAccount, addToOneBalanceAccount.

Response parameters

After submitting a call, you receive a response message to inform you that your request was received and processed.

Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.

HTTP Responses

  • 200 - OK

    The request has succeeded.

    Show more Show less
  • 204 - No Content

    The request has been successfully processed, but there is no additional content.

  • 400 - Bad Request

    A problem reading or understanding the request.

    Show more Show less
  • 401 - Unauthorized

    Authentication required.

    Show more Show less
  • 403 - Forbidden

    Insufficient permissions to process the request.

    Show more Show less
  • 422 - Unprocessable Entity

    A request validation error.

    Show more Show less
  • 500 - Internal Server Error

    The server could not process the request.

    Show more Show less
  • Request
  • Click to copy
  • Response
  • Click to copy