Skip to main content

Update a transaction rule

patch/transactionRules/{transactionRuleId}

Updates a transaction rule.

  • To update only the status of a transaction rule, send only the status parameter. All other parameters not provided in the request are left unchanged.

  • When updating any other parameter, you need to send all existing resource parameters. If you omit a parameter in the request, that parameter is removed from the resource.

Endpoint destination URL
https://balanceplatform-api-test.adyen.com/bcl/v1/transactionRules/{transactionRuleId}
Click to copy
transactionRuleIdstringRequired

The unique identifier of the transaction rule.

amountobject

The maximum amount that a payment instrument can be used for in the period specified in the interval.type.

balancePlatformIdstring

The unique identifier of the balance platform to which the rule applies.

countriesarray[string]

List of countries to which the rule applies. For example: ["NL","US"].

descriptionstringRequired
Max length: 300

Your description for the transaction rule, maximum 300 characters.

endDatestring

The date when the rule will stop being evaluated, in ISO 8601 extended offset date-time format. For example, 2020-12-18T10:15:30+01:00.

If not provided, the rule will be evaluated until the rule status is set to inactive.

entryModesarray[string]

List of point-of-sale entry modes to which the rule applies.

Possible values: manual, chip, magstripe, contactless, cof, token, server, barcode, ocr.

intervalobjectRequired

The time interval when the rule conditions apply.

maxTransactionsinteger

The maximum number of transactions that a payment instrument can be used for in the period specified in the interval.type.

mccsarray[string]

List of Merchant Category Codes (MCCs) to which the rule applies.

paymentInstrumentGroupIdstring

The unique identifier of the payment instrument group to which the rule applies.

paymentInstrumentIdstring

The unique identifier of the payment instrument to which the rule applies.

processingTypesarray[string]

List of processing types to which the rule applies.

Possible values: atmWithdraw, pos, ecommerce, moto, recurring, balanceInquiry.

referencestringRequired
Max length: 150

Your reference for the transaction rule, maximum 150 characters.

startDatestring

The date when the rule will start to be evaluated, in ISO 8601 extended offset date-time format. For example, 2020-12-18T10:15:30+01:00.

If not provided when creating a transaction rule, the startDate is set to the date when the rule status is set to active.

statusstring

The status of the transaction rule. If you provide a startDate in the request, the rule is automatically created with an active status.

Possible values: active, inactive.

typestringRequired

Type of conditions provided in the rule.

Possible values:

  • allowList: The rule provides categories (such as country and MCC) where payments must be allowed.
  • blockList: The rule provides categories (such as country and MCC) where payments must be blocked.
  • maxUsage: The rule sets limits for the maximum amount or maximum number of transactions for the lifetime of the payment instrument.
  • velocity: The rule sets limits for the maximum amount or maximum number of transactions for a given time interval.

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.

  • 400 - Bad Request

    A problem reading or understanding the request.

  • 401 - Unauthorized

    Authentication required.

  • 403 - Forbidden

    Insufficient permissions to process the request.

  • 422 - Unprocessable Entity

    A request validation error.

  • 500 - Internal Server Error

    The server could not process the request.