Spend controls
Enfuce supports a range of spend controls that are used to provide the customer with the possibility to control the use of the card and improve trust and a sense of safety. It’s also possible to set product-level spend controls which are often implemented to mitigate risk. Additionally, there are some controls that are set to comply with regulations and card scheme mandates.
- Enfuce spend blocks and spend counters can be set on an individual card level and they are updated in real-time via the Card API. They can also be set on a product-level, in which case they by default apply to all cards within the your portfolio. A product-level control can be overruled by personal settings if necessary.
- Regulatory and fraud spend controls are based on regulatory requirements and card scheme mandates and are by default set for all cards. Deviation from these is evaluated case by case.
Anti Money Laundering (AML) limits are set for prepaid cards to limit the top-ups done to the card account in order to comply with the AML regulation and mitigate the risk of money laundering.
Enfuce spend blocks
| Spend control | Description |
|---|---|
| E-commerce block | When the ecom block is active, all e-commerce transactions will be declined. |
| Regional block | With the regional block, you can limit card use to a predefined area (e.g. Europe). The spend control is valid only for card present transactions, i.e., e-commerce transactions can happen outside the regional block. Enfuce uses the M49 standard of the United Nations for the area definition. |
Enfuce spend counters
| Spend control | Description |
|---|---|
| 24H_ALL | Spend counter that includes all transaction types. 24H rolling, i.e. accumulates transactions from the last 24h. Example of 24H rolling usage limiter (24H spend limit is 400 EUR): – Day 1 – 1st purchase at 11:30 for 300 EUR. – Day 1 – 2nd purchase at 18.00 for 100 EUR. – Spend counter blocks usage until +24H has passed from 1st purchase – Day 2 – 3rd purchase at 11.31 for 200 EUR. – Day 2 – at 18.01 available usage is 200 EUR as 2nd purchase is +24H old. singleAmount, count and/or sumAmount of this spend counter can be set on product level (applies to all customers) by Enfuce or on user level via our standard APIs. Personal settings will overrule any settings on product level. |
| 24H_ATM | Spend counter that includes ATM transactions. 24H rolling, i.e. accumulates transactions from the last 24h. singleAmount, count, sumAmount of this spend counter can be set on product level (applies to all customers) by Enfuce or on user level via Enfuce standard APIs. Personal settings will overrule any settings on product level. |
| 24H_RETAIL | Spend counter that includes Retail transactions . 24H rolling, i.e. accumulates transactions from the last 24h. singleAmount, count, sumAmount of this spend counter can be set on product level (applies to all customers) by Enfuce or on user level via Enfuce standard APIs. Personal settings will overrule any settings on product level. |
| WEEKLY_ALL | Spend counter that includes all transaction types. Weekly, i.e. accumulates transactions from one calendar week (Mon-Sun). Week breaks Mondays at 00:00 UCT. singleAmount, count, sumAmount of this spend counter can be set on product level (applies to all customers) by Enfuce or on user level via Enfuce standard APIs. Personal settings will overrule any settings on product level. |
| WEEKLY_ATM | Spend counter that includes ATM transactions. Weekly, i.e. accumulates transactions from one calendar week (Mon-Sun). Week breaks Mondays at 00:00 UCT. singleAmount, count, sumAmount of this spend counter can be set on product level (applies to all customers) by Enfuce or on user level via Enfuce standard APIs. Personal settings will overrule any settings on product level. |
| WEEKLY_RETAIL | Spend counter that includes Retail transactions. Weekly, i.e. accumulates transactions from one calendar week (Mon-Sun). Week breaks Mondays at 00:00 UCT. singleAmount, count, sumAmount of this spend counter can be set on product level (applies to all customers) by Enfuce or on user level via Enfuce standard APIs. Personal settings will overrule any settings on product level. |
| MONTHLY_ALL | Spend counter that includes all transaction types. Monthly, i.e. accumulates transactions from current calendar month. Month breaks at 00:00 on the first day on the month. singleAmount, count, sumAmount of this spend counter can be set on product level (applies to all customers) by Enfuce or on user level via Enfuce standard APIs. Personal settings will overrule any settings on product level. |
| MONTHLY_ATM | Spend counter that includes ATM transactions. Monthly, i.e. accumulates transactions from current calendar month. Month breaks at 00:00 on the first day on the month.singleAmount, count, sumAmount of this spend counter can be set on product level (applies to all customers) by Enfuce or on user level via Enfuce standard APIs. Personal settings will overrule any settings on product level. |
| MONTHLY_RETAIL | Spend counter that includes Retail transactions. Monthly, i.e. accumulates transactions from current calendar month. Month breaks at 00:00 on the first day on the month. singleAmount, count, sumAmount of this spend count can be set on product level (applies to all customers) by Enfuce or on user level via Enfuce standard APIs. Personal settings will overrule any settings on product level. |
Regulatory and Fraud Spend controls
| Spend control | Description |
|---|---|
| PSD2 Contactless counter | According to PSD2 requirements the issuer should require authentication if the single amount, cumulative amount or number of consecutive contactless transactions exceed predefined limits. By default this is active on all products. The limits are:
|
| PSD2 Transport SCA exemption | According to PSD2 requirements, Parking and Transit fare transactions are exempted from strong customer authentication. By default this is active on all products. This means that parking or transit related authorisations will be approved even when they are not strongly authenticated and these transactions will also not increase the contactless counter. Merchant Category Codes (MCC) that are considered to be in scope of this exemption:
|
| Decline magnetic stripe transactions (“Disable Fallback”) | Enfuce will decline purchases done with magnetic stripe if the terminal is capable of reading chip cards. This is required by the card schemes to reduce fraud. |
| Block of high risk merchant categories | Enfuce blocks transactions from high risk merchant categories (e.g. money transfers, gambling, crypto) that are related to potential financial crime. These are restricted by default and transactions are declined accordingly. Issuers operating under their own licence and scheme membership may opt-out or add merchant categories per their risk analysis and internal decision. Any changes are subject to a change request to Enfuce. High risk merchant categories are:
|
| Block of sanctioned countries | The blocked countries are based on assessment of compliance by EU sanction lists and US Office of Foreign Assets Control (as Visa and Mastercard are required to follow US sanctions). These are restricted by default and transactions are declined accordingly.
Enfuce reserves the right to update the countries immediately when changes are introduced by the officials. Any deviation from the above needs to be aligned separately with Enfuce. |
Anti Money Laundering (AML) controls
| Spend control | Description |
|---|---|
| Prepaid Balance Threshold | Maximum amount of money allowed on the card’s account |
| Top-Up Usage – Daily | Daily maximum amount of money allowed to load on the card’s account |
| Top-Up Usage – Monthly | Monthly maximum amount of money allowed to load on the card’s account |