Skip to main content
Version: multi-v3

Spend Controls

Learn how to set rules on cards and card profiles to control spending.

Spend rules can be used to block certain card purchases. You can configure them at either the card profile level in the Multi Portal or at individual card level by using the APIs below.

Supported Card Spend Rules

Merchant Rules

You can use merchant rules to block or allow merchant categories (e.g. shoe stores) or specific merchants.

FieldDescription
allowedMerchantCategoriesA list of merchant categories from where purchases are allowed. All other categories will be blocked.
blockedMerchantCategoriesA list of merchant categories from where purchases should be blocked. All other categories will be allowed.
allowedMerchantIdsA list of merchant IDs from where purchases should be allowed. All other merchants will be blocked.
blockedMerchantIdsA list of merchant IDs from where purchases should be blocked. All other merchants will be allowed.
allowedMerchantCountriesA list of countries from where merchants should be allowed. All other countries will be blocked.
blockedMerchantCountriesA list of countries from where merchants should be blocked. All other countries will be blocked.
minTransactionAmountThe minimum transaction amount in the card currency that is allowed. Transactions with an amount that is less than the value set, will be declined.
maxTransactionAmountThe maximum transaction amount in the card currency that is allowed. Transactions with an amount that is greater than the value set, will be declined.
info

If you set the same category or ID in the allowed and blocked lists, the purchase will be denied.

Transaction Type Rules

Cardholders can initiate different types of transactions (e.g. ATM withdrawals) using their cards. You can use spend controls to limit allowed transaction types.

FieldDescription
allowContactlessPurchases can be authorised without the need for the cardholder to swipe the card, enter the PIN, and/or sign for the transaction. If not set, contactless transactions are allowed.
allowATMCardholders can withdraw funds from the card using an ATM. If not set, ATM withdrawals are allowed.
allowECommerceCardholders can initiate purchases from online e-commerce portals. If not set, e-commerce transactions are allowed.
allowCashbackCardholders can ask for a cashback transaction at a point-of-sale. If not set, cashback transactions are allowed.
allowCreditAuthorisationsCardholders can receive funds directly on the card. If not set, credit transactions are allowed.

Spend Limits

You can set spend limits for debit mode cards to limit the amount that can be spend for the card. Spend limits can be configured for different intervals

FieldDescription
DAILYThe daily total spend allowed starting at 00:00:00 UTC.
WEEKLYThe weekly total spend allowed starting on Monday 00:00:00 UTC.
MONTHLYThe monthly total spend allowed starting on the first day of the month at 00:00:00 UTC.
QUARTERLYThe quarterly total spend allowed starting on the first day of the first month in the quarter at 00:00:00 UTC.
YEARLYThe yearly total spend allowed starting on the first day of the year at 00:00:00 UTC.
ALWAYSThe total spend allowed in the lifetime of the card.

Spend Rules Levels

There are three levels of spend rules each one having priority over the ones below starting from the Identity then Profile and lastly the Card level spend rules.

Spend Rule LevelsDescription
IdentityThe highest level of spend rules that is applied on the user identity and it is decided based on the KYC results
ProfileThe profile spend rules is enforced on the profile level and all rules will have precetense over the rules the cards have under the profile
CardThe card rules are applied individually to each card assuming that there are no conflicts with the rules applied on the Identity and Profile level rules which have precedence over the card rules

Configure Card Spend Rules on individual cards

You can control the spend rules on individual cards in these 5 steps:

  1. Setup card spend rules
  2. Update card spend rules
  3. Retrieve all spend rules
  4. Reset card spend rules

1. Setup Card Spend Rules

When setting up spend rules on a card for the first time you need to use the Setup operation. Any number of spend rules can be added during this step but at least one spend rule needs to be set.

info

For subsequent changes to the spend rules of a card, you should use the update card spend rules operation.

2. Update Card Spend Rules

You should use this operation to update spend rules for cards which you have already configured rules for. When updating rules, you only need to include the rules that you want to set and can omit any rules which you are not interested in.

3. Retrieve all Spend Rules

Retrieve all spend rules associated with a card. The spend rules returned will include the ones configured in the setup card spend rules API and the update card spend rules API as well as spend rules configured in the card profile or identity.

note

Only the rules that have been set will be returned when retrieving spend rules.

4. Reset Card Spend Rules

Use the reset operation to remove all card level spend rules at once.

note

Spend rules configured in the card profile or at identity level will not be affected by this API and will continue to be checked accordingly.

Configure Spend Rules in Card Profiles

You can set spend rules at the card profile level on the Multi Portal > Settings page, in the card profile configuration section as shown in the screenshot below. All cards associated with a card profile will inherit the spend rules specified in its card profile.

Spend Controls

Spend rules set at the card profile level are effective for all cards linked to the profile. Weavr checks spend rules set at the card level at the same time that it checks card profile rules.

Review All Level Spend Rules

You can see all the spend rules applied on a card across all spend rule levels (Identity, Profile, Card) on the Multi Portal > Managed Cards_Settings page

Spend Controls

Rule Order

If any one of the rules rejects the card purchase, the transaction is declined.