Update split conditions

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

Changes the conditions of the split configuration rule 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}
Click to copy

Path parameters

ruleId string Required

The unique identifier of the split configuration rule.

splitConfigurationId string Required

The identifier of the split configuration.

merchantId string Required

The unique identifier of the merchant account.

Request parameters

currency string Required

The currency condition that defines whether the split logic applies. Its value must be a three-character ISO currency code.

fundingSource string

The funding source condition of the payment method (only for cards).

Possible values: credit, debit, or ANY.

paymentMethod string Required

The payment method condition that defines whether the split logic applies.

Possible values:

  • Payment method variant: Apply the split logic for a specific payment method.
  • ANY: Apply the split logic for all available payment methods.
shopperInteraction string Required

The sales channel condition that defines whether the split logic applies.

Possible values:

  • Ecommerce: Online transactions where the cardholder is present.
  • ContAuth: Card on file and/or subscription transactions, where the cardholder is known to the merchant (returning customer).
  • Moto: Mail-order and telephone-order transactions where the customer is in contact with the merchant via email or telephone.
  • POS: Point-of-sale transactions where the customer is physically present to make a payment using a secure payment terminal.
  • ANY: All sales channels.

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