# Update spend rules for a managed card in bulk

Submit the details to update the spend rules of Managed Cards

The bulkId returned in the response can subsequently be used to launch the execution of the bulk process through Execute Bulk Process. A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any Authorised User of the same identity of the user that submits the details.

The status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.

The submission of data for a bulk process does not expire but it can be cancelled through Cancel Bulk Process.

The system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations

Each individual operation in this bulk will be processed via Update Spend Rules for a Managed Card.

Endpoint: PATCH /bulks/managed_cards/_id_/spend_rules
Version: 3.63.5
Security: auth_token, api-key

## Header parameters:

  - `idempotency-ref` (string)
    A unique call reference generated by the caller that, taking into consideration the payload as well as the operation itself, helps avoid duplicate operations. Idempotency reference uniqueness is maintained for at least 24 hours.

## Request fields (application/json):

  - `pathParams` (object)

  - `pathParams._id_` (string)

  - `requestBody` (object)

  - `requestBody.allowedMerchantCategories` (array)
    Whitelist MCC: A list of allowed merchant category codes (MCCs). If the MCC does not match, then the transaction will be declined. If an MCC is also in the blocked list, the blocked list will take precedence.

  - `requestBody.blockedMerchantCategories` (array)
    Blacklist MCC: A list of disallowed merchant category codes (MCCs). If the MCC matches, then the transaction will be declined. If an MCC is also in the allowed list, the blocked list will take precedence.

  - `requestBody.allowedMerchantIds` (array)
    Whitelist Merchant Id: A list of allowed merchant IDs. If the Merchant Id does not match, then the transaction will be declined. If a Merchant Id is also provided in the blocked list, the blocked list will take precedence.

  - `requestBody.blockedMerchantIds` (array)
    Blacklist Merchant Id: A list of disallowed merchant IDs. If the Merchant Id matches, then the transaction will be declined. If a Merchant Id is also in the allowed list, the blocked list will take precedence.

  - `requestBody.allowedMerchantCountries` (array)
    Whitelist Merchant Country: A list of allowed merchant countries, in ISO 3166-1 alpha-2 format. If the Merchant country does not match, then the transaction will be declined. If a Merchant Country is also provided in the blocked list, the blocked list will take precedence.

  - `requestBody.blockedMerchantCountries` (array)
    Blacklist Merchant Country: A list of disallowed merchant countries, in ISO 3166-1 alpha-2 format. If the Merchant country matches, then the transaction will be declined. If a Merchant Country is also in the allowed list, the blocked list will take precedence.

  - `requestBody.allowContactless` (boolean)
    Indicates if a contactless transaction is allowed on the card.

  - `requestBody.allowAtm` (boolean)
    Indicates if an ATM Withdrawal transaction is allowed on the card.

  - `requestBody.allowECommerce` (boolean)
    Indicates if an online transaction is allowed on the card.

  - `requestBody.allowCashback` (boolean)
    Indicates if a cashback transaction at a physical terminal is allowed on the card.

  - `requestBody.allowCreditAuthorisations` (boolean)
    Indicates if a the card can receive a credit transaction.

  - `requestBody.rolloverPolicy` (object)
    The rollover policy will dictate how Weavr handles any eventual overspending. This is possible 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

  - `requestBody.rolloverPolicy.rolloverNegative` (boolean, required)
    If set to true any overspend will keep rolling over and get deducted in the upcoming intervals until the availableToSpend is back to a positive value. Any overspend will be deducted from the availableToSpend at the beginning of the next interval.

  - `requestBody.spendLimit` (array)
    The total amount of funds that can be spent using this card, in a given time interval.

  - `requestBody.spendLimit.startTimestamp` (integer)
    The start timestamp of the spend limit, expressed in Epoch timestamp using millisecond precision.

  - `requestBody.spendLimit.value` (object, required)
    The spend limit, as amount and currency, (for the given interval).

  - `requestBody.spendLimit.value.currency` (string, required)
    The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.

  - `requestBody.spendLimit.value.amount` (integer, required)
    The monetary amount, scaled to the lowest denomination of the currency.

Example, an amount of 1000 for a EUR currency is actually 1000 Euro cents or EUR 10.00.

  - `requestBody.spendLimit.interval` (string, required)
    The time period for which the spendLimit is valid.
 - DAILY: starting from 00:00:00 UTC of current day to 23:59:59 UTC of current day
 - WEEKLY: 00:00:00 UTC Monday of current week to following Sunday 23:59:59 UTC
 - MONTHLY: 1st of current calendar month to end of current calendar month
 - QUARTERLY: starting from beginning of current quarter where quarters are defined as follows:
  - 1 January 00:00:00 UTC to 31 March 23:59:59 UTC
  - 1 April 00:00:00 UTC to 30 Jun 23:59:59 UTC
  - 1 July 00:00:00 UTC to 30 September 23:59:59 UTC
  - 1 October 00:00:00 UTC to 31 December 23:59:59 UTC

- YEARLY: 1 January 00:00:00 UTC of current calendar year to 31 December 23:59:59 UTC of current calendar year.
- ALWAYS: This indicates that the spendLimit is the total amount that can be spent through the card throughout the whole lifetime of the card.
    Enum: "DAILY", "WEEKLY", "MONTHLY", "QUARTERLY", "YEARLY", "ALWAYS"

  - `requestBody.minTransactionAmount` (integer)
    The minimum transaction amount, in card currency, that is allowed. If the transaction amount is less than this value, then the transaction will be declined.

  - `requestBody.maxTransactionAmount` (integer)
    The maximum transaction amount, in card currency, that is allowed. If the transaction amount is greater than this value, then the transaction will be declined.

  - `requestBody.updateSpendLimitMethod` (string)
    The spend limit update method to apply. Currently supported:
  - OVERWRITE: (default option if nothing selected). Overwrites the previous values for the spendLimit object i.e. sets new limits
  - INCREMENT : This will increase the existing value of the spend limit by the amount input the value field. If used in conjunction with an ALWAYS interval, this can be used to increment a spend limit on a periodic basis (controlled by you, e.g. monthly), and means that any 'unused' balance from the previous period will still available to spend. See examples in our documentation
    Enum: "OVERWRITE", "INCREMENT"

## Response 201 fields (application/json):

  - `bulkId` (string)

  - `operationCount` (integer)

  - `path` (string)