Update spend rules for a card
Updates the card-level spend rules of the managed card identified by the id path parameter. Use this once the card has rules; to set them for the first time, use Create spend rules.
The same fields are accepted as on create: merchant, MCC, and country allow and block lists, the allow* transaction-type switches, transaction size bounds, and spendLimit.
Updating spend limits
updateSpendLimitMethod controls how the spendLimit you send is applied:
| Method | Effect |
|---|---|
| OVERWRITE | Replaces the existing limits with the ones supplied. This is the default. |
| INCREMENT | Adds the supplied value to the existing limit for that interval. |
INCREMENT combined with an ALWAYS interval is how you top a card up on your own schedule. Incrementing a lifetime limit monthly, for instance, leaves any unused allowance from earlier periods available to spend, which a fixed MONTHLY limit would not.
Rollover
Set rolloverPolicy.rolloverNegative to true on a spend limit to carry overspend into subsequent intervals. This applies per card; to change it across many cards at once, use Update spend rules in bulk.
Request
- Base URL: https://sandbox.weavr.io/multi
- URL: https://sandbox.weavr.io/multi/managed_cards/{id}/spend_rules
- Auth: HTTP bearer and API key in header api-key
Path parameters
The unique identifier of the managed card.
Headers
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 body
Example request
{
"allowContactless": true,
"allowAtm": true,
"allowECommerce": true,
"allowCashback": true,
"allowCreditAuthorisations": true,
"spendLimit": [
{
"startTimestamp": 1767225600000,
"value": {
"currency": "GBP",
"amount": 1250
}
}
],
"minTransactionAmount": 100,
"maxTransactionAmount": 50000
}Response
Success - No Content.
Changes
No recorded changes to this operation across all 1 revision of this API.