Issuin icon

Create and manage rules

Use transaction rules to automatically approve or decline a transaction.

Before you begin

Before you create a transaction rule, make sure you're familiar with how transaction rules work.

Create a transaction rule

When you have defined your business logic and requirements, turn your requirements into a transaction rule.

Make a POST /transactionRules request, specifying the following parameters:

Parameter Required Description
description -white_check_mark- Your description for the rule. Maximum length: 300 characters. This description is shown in the Balance Platform Customer Area.
entityKey -white_check_mark- Contains the ID and type of resource to which the rule is applied.
interval -white_check_mark- The time period or duration when the rule applies.
reference -white_check_mark- Your reference for the rule. Maximum length: 150 characters.
type -white_check_mark- Set to blockList, maxUsage, or velocity.
ruleRestrictions -white_check_mark- Object that contains key-value objects with the key as the condition and the value containing values and operations.
startDate Specify a date and time in the future when the rule must be evaluated. For example, 2022-02-25T07:00:00+01:00. When you specify a start date, the rule is created with a status set to active.
endDate Specify a date and time in the future when the rule evaluation must stop. For example, 2022-12-18T10:15:30+01:00. If not provided, the rule is evaluated until the status is set to inactive.
status Set to active if you want to start evaluating the rule. When you set the status to active, we automatically set the startDate to the current time.

Let's take the following requirements for example.

  • Only allow payments from the Netherlands.
  • Apply the rule to paymentInstrumentId PI3227C223222B59KGTXP884R.
  • Apply the rule starting from 2022-03-20 at 00:00 CET.

Here is an example of how to create a transaction rule for the requirements above.

The response contains the new transactionRule resource, identified by its unique id. The transaction rule will be applied on the specified startDate for all payments made with payment instrument PI3227C223222B59KGTXP884R. If the country where the transaction is processed does not match any of the values (NL), then the transaction is blocked.

Allowed combinations

The following are the allowed combinations when creating rules. To learn about the specific rule restriction, select the link to see the objects on API Explorer.

Rule restrictions Rule type Operation Interval type
activeNetworkTokens blockList, velocity equals, notEquals, greaterThanOrEqualTo, greaterThan, lessThanOrEqualTo, lessThan perTransaction, daily, weekly, monthly, rolling, sliding
brandVariants blockList, maxUsage, velocity anyMatch, noneMatch perTransaction, daily, weekly, monthly, rolling, sliding
countries blockList, velocity anyMatch, noneMatch perTransaction, daily, weekly, monthly, rolling, sliding
differentCurrencies blockList, velocity equals, notEquals perTransaction, daily, weekly, monthly, rolling, sliding
entryModes blockList, velocity anyMatch, noneMatch perTransaction, daily, weekly, monthly, rolling, sliding
internationalTransaction blockList, velocity equals, notEquals perTransaction, daily, weekly, monthly, rolling, sliding
matchingTransactions maxUsage, velocity equals, notEquals, greaterThanOrEqualTo, greaterThan, lessThanOrEqualTo, lessThan daily, weekly, monthly, lifetime, rolling, sliding
mccs blockList, velocity anyMatch, noneMatch perTransaction, daily, weekly, monthly, rolling, sliding
merchants blockList, velocity anyMatch, noneMatch perTransaction, daily, weekly, monthly, rolling, sliding
processingTypes blockList, velocity anyMatch, noneMatch perTransaction, daily, weekly, monthly, rolling, sliding
timeOfDay blockList, velocity equals, notEquals perTransaction
totalAmount maxUsage, velocity equals, notEquals, greaterThanOrEqualTo, greaterThan, lessThanOrEqualTo, lessThan perTransaction, daily, weekly, monthly, lifetime, rolling, sliding

View transaction rules

You can see the transaction rules that you created on the Balance Platform Customer Area or by making API requests.

To view transaction rules, you can make the following API requests.

Update a transaction rule

You can update transaction rules by making a PATCH /transactionRules/{id} request, specifying the id in the path.

For example, to add the US the previous transaction rule, send the request below:

The response returns the updated transaction rule, along with the NL and US in the list of countries. If the country where the transaction is processed does not match any of NL or US, then the transaction is blocked.

Activate or deactivate a transaction rule

You can activate or deactivate transaction rules using the Balance Platform Customer Area or by making API requests.

To deactivate a transaction rule, make a PATCH /transactionRules/{id} request and set the status to inactive.

The rule status changes to inactive and the rule is no longer applied.

Next steps