Skip to main content

Spend Controls & Overspend

Overview​

An overspend may occur if a merchant clears more funds than authorised, or when a merchant clears funds without authorising, resulting in the availableToSpend value to go into negative. Rollover is relative to a spendLimit.interval.

If there is any overspend at the end of the spendLimit.interval, this overspend will be get deducted in the upcoming intervals until the availableToSpend is back to a positive value. It will be deducted from the availableToSpend at the beginning of the next interval.

Getting Started​

Enabling the Rollover Policy​

This feature is disabled by default and would need to be enabled on every managed card spend limit. It can be configured by setting rolloverPolicy.rolloverNegative to TRUE when calling either the create or update spend rule:

POST/managed_cards/{id}/spend_rulesTry it
PATCH/managed_cards/{id}/spend_rulesTry it

There is also information about the rollover policy, by looking at ProfileLevelSpendRule.rolloverPolicy.rolloverNegative when fetching the list of spend rules via

GET/managed_cards/{id}/spend_rulesTry it
note

The same endpoints are available through Weavr Multi Back-Office API that allow you, as an embedder, to perform various back-office operations concerning identities and their instruments, without requiring the users to be logged in.

How it works​

Consider the following scenario:

I have a Spend Rule with a MONTHLY interval and a £100 Spend Limit with rolloverNegative TRUE. We are in January.

  1. I start January with an Available To Spend of £100
  2. During January I made a £95 worth of purchases leaving me with an Available To Spend at £5
  3. On the last week of January, I receive a settlement of £15 that pushes my Available To Spend down to -£10
  4. When February starts, my Available To Spend should be reading £90 and not £100

Now consider the following scenario:

I have a Spend Rule with a MONTHLY interval and a £100 Spend Limit with rolloverNegative TRUE. We are in January.

  1. I start January with an Available To Spend of £100
  2. Close to the end of January I get a settlement of £190
  3. February starts, my Available To Spend is at -£90
  4. I cannot make any purchases during February given that my Available to Spend is in negative
  5. March starts my Available To Spend is at £10

Migrating existing cards to use the rollover policy​

The update of the rollover policy is applicable on a card by card basis. You can either update each card individually or use the bulk operation to update multiple cards at once.

Update cards individually​

You can specify the managed card id in the following patch end point and set rolloverPolicy.rolloverNegative to TRUE:

PATCH/managed_cards/{id}/spend_rulesTry it
note

The same endpoints are available through Weavr Multi Back-Office API that allows you, as an embedder, to perform various back-office operations concerning identities and their instruments, without requiring the users to be logged in.

Update multiple cards at once​

You can specify a list of managed cards in the following patch end point and set rolloverPolicy.rolloverNegative to TRUE:

PATCH/bulks/managed_cards/_id_/spend_rulesTry it

Further information on how to use bulk operations is available here.

In case you are still facing issues with using or implementing any of the above, please contact Weavr Support or your account manager to put you in touch with our technical team who can facilitate card migration.