Overview

We support a wide range of spend controls that enable you to control the usage of your cards for appropriate expenses. Enfuce supports the implementation of spend control through rules and rulesets.

What are Rules?

A rule determines whether a card transaction will be approved, partially approved, or declined, based on the regulation configured. For example, the DAILY AMOUNT ATM rule specifies a limit on the total ATM withdrawals allowed per day — any withdrawal that exceeds this limit is declined.

What are Rulesets?

A ruleset is a collection of rules. You can link a ruleset to a card program, which associates every card in the program with the ruleset. However, a card can also be linked directly to a ruleset,when there is a need to support multiple rulesets within the same program.

During project onboarding, your customer support representative will share with you the rule and the ruleset IDs.

By default, a ruleset is linked to a card program. If you want to link a ruleset with a specific card, mention the following parameters:

entities.id: Unique identifier of the entity (card).
entities.type: This implies that the entity is a specific card type (credit/debit).

Related API Endpoint: Create Entity Bindings

Types of Spend Controls

Spending Limit Per Transaction

You can set a maximum limit per transaction. Examples of spending limits per transaction are:

1000: SINGLE AMOUNT ALL
1010: SINGLE AMOUNT ATM (applicable only ATM transactions)
1020: SINGLE AMOUNT RETAIL (applicable only for retail transactions)

Cumulative Spending Limits

You can set spending limits for specific time periods, such as, daily,weekly,monthly, or yearly. You can also configure rolling amounts applicable for specific periods, such as, 1500: ROLLING_HOURLY_24 AMOUNT ALL AMOUNT — a cumulative spending limit that is calculated over a 24 hour period; hence after every transaction processed during the preceding 24 hour period, the total remaining amount is recalculated.

Example of how a rolling cumulative spending limit is calculated:

1610: ROLLING_DAILY_365 ATM AMOUNT

Where:

AMOUNT: Cumulative transaction amount (for example, €1000)
365 days: Total calculation period; the count can start at any time within a 365 day period.
ATM: Allowed transaction type
ROLLING_DAILY: After every day, the cumulative amount is recalculated, based on the amount spent in the preceding period.

Examples of pre-configured cumulative rules are:

1320: MONTHLY RETAIL AMOUNT
1600: ROLLING_DAILY_365 ALL AMOUNT
1610: ROLLING_DAILY_365 ATM AMOUNT
1611: ROLLING_DAILY_365 ATM COUNT

Regional Spending Limits

You can set a couple of location specific rules — allowed and/or blocked countries. Transactions occurring at the specific geographic locations are either approved or declined, based on what you have configured. Examples of location-specific rules are:

1700: ALLOWED_COUNTRIES
1701: BLOCKED_COUNTRIES

Card Usage Specific Spending Limits

You can configure rules that approve or decline a transaction, based on the type of card usage (card entry modes). Example of card entry mode specific rules:

1710: ALLOWED_CARD_ENTRY_MODES
1720: BLOCK_CARD_PRESENT

Transaction Type Spending Limits

You can set a spending rule that declines a transaction of specific types. Example of transaction type specific rule is:

1730: BLOCKED_TRANSACTION_TYPES

To comply with fraud regulations, Enfuce provides you with specific spend controls that are configured during onboarding. As per the current implementation, you cannot override them. Discuss with your customer support representative to discuss the details.

Rule IDs

Here is the entire list of rules pre-configured for your usage:

The third column represents the parameters that you can override for each rule.

Code	Rule Name	Parameters Allowed for Overrides
1000	SINGLE AMOUNT ALL	Specific amount (for example, 100) allowed for all transaction types
1010	SINGLE AMOUNT ATM	Specific amount (for example, 100) allowed for ATM transactions
1020	SINGLE AMOUNT RETAIL	Specific amount (for example, 100) allowed for Retail transactions
1100	DAILY ALL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: DAILY
1101	DAILY ALL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: DAILY
1110	DAILY ATM AMOUNT	First parameter: specific amount (for example, 100) Second parameter: DAILY
1111	DAILY ATM COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: DAILY
1120	DAILY RETAIL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: DAILY
1121	DAILY RETAIL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: DAILY
1200	WEEKLY ALL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: WEEKLY
1201	WEEKLY ALL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: WEEKLY
1210	WEEKLY ATM AMOUNT	First parameter: specific amount (for example, 100) Second parameter: WEEKLY
1211	WEEKLY ATM COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: WEEKLY
1220	WEEKLY RETAIL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: WEEKLY
1221	WEEKLY RETAIL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: WEEKLY
1300	MONTHLY ALL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: MONTHLY
1301	MONTHLY ALL COUNT	First parameter: specific number of transactions (for example, 10) (for example, 10) Second parameter: MONTHLY
1310	MONTHLY ATM AMOUNT	First parameter: specific amount (for example, 100) Second parameter: MONTHLY
1311	MONTHLY ATM COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: MONTHLY
1320	MONTHLY RETAIL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: MONTHLY
1321	MONTHLY RETAIL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: MONTHLY
1400	YEARLY ALL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: YEARLY
1401	YEARLY ALL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: YEARLY
1410	YEARLY ATM AMOUNT	First parameter: specific amount (for example, 100) Second parameter: MONTHLY
1411	YEARLY ATM COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: YEARLY
1420	YEARLY RETAIL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: YEARLY
1421	YEARLY RETAIL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: YEARLY
1500	ROLLING_HOURLY_24 ALL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: ROLLING_HOURLY Third parameter: Duration of the rolling period (for example, 24 hours)
1501	ROLLING_HOURLY_24 ALL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: ROLLING_HOURLY Third parameter: Duration of the rolling period
1510	ROLLING_HOURLY_24 ATM AMOUNT	First parameter: specific amount (for example, 100) Second parameter: ROLLING_HOURLY Third parameter: Duration of the total period
1511	ROLLING_HOURLY_24 ATM COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: ROLLING_HOURLY Third parameter: Duration of the total period
1520	ROLLING_HOURLY_24 RETAIL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: ROLLING_HOURLY Third parameter: Duration of the total period
1521	ROLLING_HOURLY_24 RETAIL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: ROLLING_HOURLY Third parameter: Duration of the total period
1600	ROLLING_DAILY_365 ALL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: ROLLING_DAILY Third parameter: Duration of the total period
1601	ROLLING_DAILY_365 ALL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: ROLLING_DAILY Third parameter: Duration of the total period (for example, 365 days)
1610	ROLLING_DAILY_365 ATM AMOUNT	First parameter: specific amount (for example, 100) Second parameter: ROLLING_DAILY Third parameter: Duration of the total period (for example, 365 days)
1611	ROLLING_DAILY_365 ATM COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: ROLLING_DAILY Third parameter: Duration of the total period (for example, 365 days)
1620	ROLLING_DAILY_365 RETAIL AMOUNT	First parameter: specific amount (for example, 100) Second parameter: ROLLING_DAILY Third parameter: Duration of the rolling period (for example, 365 days)
1621	ROLLING_DAILY_365 RETAIL COUNT	First parameter: specific number of transactions (for example, 10) Second parameter: ROLLING_DAILY Third parameter: Duration of the rolling period (for example, 365 days)
1700	ALLOWED_COUNTRIES	ISO 3166-1 numeric codes to denote allowed countries
1701	BLOCKED_COUNTRIES	ISO 3166-1 numeric codes to denote countries where transactions are not allowed
1710	ALLOWED_CARD_ENTRY_MODES	Mention specific allowed card entry modes. Values are: UNKNOWN MANUAL_ENTRY MAGNETIC_STRIPE CHIP CHIP_CONTACTLESS ECOMMERCE WALLET_CONTACTLESS WALLET_ECOMMERCE CREDENTIALS_ON_FILE
1720	BLOCK_CARD_PRESENT	No specific parameter to mention
1730	BLOCKED_TRANSACTION_TYPES	Mention specific transaction types that are not allowed. Values are: RETAIL ATM UNIQUE CASH_DISBURSEMENT BALANCE_INQUIRY P2P_DEBIT P2P_CREDIT CREDIT CASHBACK AFT

Use Cases

Override Monthly ATM Spend

Rule ID and Name: 1310 MONTHLY ATM AMOUNT
Operation: Mention a specific monthly limit allowed for ATM transactions.

Send a request to the Add Parameters by Rule ID Endpoint:

 POST /v1/rules/1310/parameters
 
  "entity" : {
  "id" : "<cardId>",
  "type" : "card"
  },
  "parameters" : [
 "1000", "MONTHLY"
 ]

Override to Block ATM and Cash Disbursements

Rule ID and Name: 1730 BLOCKED_TRANSACTION_TYPES
Operation: Block ATM and cash withdrawal transaction types.

Send a request to the Add Parameters by Rule ID Endpoint:

 POST /v1/rules/1730/parameters
 
  "entity" : {
  "id" : "<cardId>",
  "type" : "card"
   },
  "parameters" : [
  "ATM", "CASH_DISBURSEMENT"
  ]

Retrieve Ruleset Details by Ruleset ID

Send a request to the Get Ruleset by Ruleset ID Endpoint. Here is the endpoint response that you receive:

 {
 "id" :  "<rule-set-id>",
 "name" : "Standard Spend Control",
 "operatorType": "ALL",
 "rules" : [
   {
   "id" : 1310,
   "name" : "Monthly ATM cumulative amount",
   "type" : "CUMULATIVE_AMOUNT",
   "defaultParameters" : [
   "500", "MONTHLY"
   ],
    "filterType" : "ANY",
   "filters" : [
    {
     "id" : "<atm-filter-id>",
     "type" : "TRANSACTION_TYPE",
     "parameters" : [
       "ATM", "CASH_DISBURSEMENT"
     ],
     "reversed" : false
    }
   ]
 },
{
 "id" : 1730,
 "name" : "Blocked transaction types",
 "type" : "BLOCKED_TRANSACTION_TYPES",
 "defaultParameters" : [],
 "filterType" : "ANY",
 "filters" : []
}
...
...
...
]
}

Additional Reference Information | Filters

Filters

Filters determine the conditions when a rule is applicable, such as the transaction type. A rule can have multiple filters (filters object).

filterType determines whether a transaction must pass all filters or any filter (enums: ANY/ALL).
filters.type: This determines the type of a specific filter, such as TRANSACTION_TYPE.

Parameters

Filters include parameters. Parameters define the limits, thresholds, and configuration values. A rule can have a default set of parameters (parameters).

filters.parameters: Based on the type of each filter, it includes a list of parameters, such as , if the filter.type is TRANSACTION_TYPE, the filters.parameters can be RETAIL and ATM.
defaultParameters: A rule can have a default set of parameters (defaultParameters).
You can add, update, or delete the parameters included in a rule. The relevant endpoints are:
parameters.entity: A parameter can either be associated with a card or a card program.

When you are retrieving details of a rule, in the endpoint response, you can view details relevant to filters. However, these values are applicable only for Advanced Spend Control.

Example:1210: WEEKLY ATM AMOUNT

id: 1210
type: AMOUNT
filters.type: TRANSACTION_TYPE
filters.parameters: ATM

You can send a request to the Add Parameters by Rule ID Endpoint to mention a specific weekly amount allowed for ATM transactions, such as €100.

Getting Started

Cards

Cardholders

PIN

Digital Wallets

Transaction Lifecycle

Spend Controls

Exchange Rates

What are Rules?

What are Rulesets?

Types of Spend Controls

Rule IDs

Use Cases

Additional Reference Information | Filters

​What are Rules?

​What are Rulesets?

​Types of Spend Controls

​Rule IDs

​Use Cases

​Additional Reference Information | Filters

What are Rules?

What are Rulesets?

Types of Spend Controls

Rule IDs

Use Cases

Additional Reference Information | Filters