---
title: "Create card spending limit control (V2)"
method: POST
path: "/v1/card_controls/spending_limits(v2)"
tags: ["Card spending controls"]
---

# Create card spending limit control (V2)

`POST /v1/card_controls/spending_limits(v2)`

Creates a card spending limit control and applies it to all cards defined in the `scope` and `scope_id` of the request. <br> **Important** This endpoint replaces the [old version](https://docs.solarisgroup.com/api-reference/digital-banking/cards/#operation/createCardControlSpendingLimit). However, please note that you have to set the `Api-Version` header to the version you want (e.g., `2024-01-01`). If you do not specify a version, then the API will return the older version of the response.

## Request body

- CreateCardControlSpendingLimitRequestV2
  - `scope` 'CARD' | 'CARDHOLDER' | 'ACCOUNT' | 'BUSINESS' | 'PARTNER' | 'PARTNER_CARDS' | 'BUSINESS_CARDS' | 'ACCOUNT_CARDS' | 'CARDHOLDER_CARDS' | 'NON_BUSINESS_CARDS' | 'PARTNER_CARDHOLDERS', required — The scope of the card spending control.
  - `scope_id` string, required — ID of the resource that corresponds with the `scope`. For example, if the `scope` is `PARTNER`, then the `scope_id` would be your partner ID. For `business`, it would be the business ID.
  - `idempotency_key` string, uuid, required — A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
  - `limit` SpendingLimitRuleV2, required — Object containing the properties of the spending limit control. Note that you must set either `amount` or `count`; you cannot set both.
    - `period` 'HOURLY' | 'DAILY' | 'WEEKLY' | 'MONTHLY' | 'MINUTES_60' | 'HOURS_24' | 'DAYS_7' | 'DAYS_30' | 'TRANSACTION', required — The time period in which to restrict transactions.
    - `amount` integer — The maximum amount (in Euro cents) that customers may spend under this card spending limit control. **Note**: You cannot set `amount` and `count` together under the same scope ID.
    - `count` integer — The maximum number of transactions that customers may conduct under this card spending limit control. **Note**: You cannot set `amount` and `count` together under the same scope ID.
    - `conditions` DimensionCondition[] — Object containing the dimensions to either include or exclude in this control. Note that you must use either `dimension` or `excluded_dimension`; you cannot use both.
      - `type` 'MERCHANT_CATEGORY' | 'POS_ENTRY_MODE' | 'TRANSACTION_TYPE' | 'MERCHANT_COUNTRY' | 'ACQUIRER_ID' | 'MERCHANT_ID' | 'ALL_TYPES', required — The type of transactions to be included/excluded.
      - `dimension` string[] — Array containing dimensions to include in the spending limit control. See the [guide](https://docs.solarisgroup.com/guides/cards/card-spending-controls/#list-of-dimensions) for more information about dimensions.
      - `excluded_dimension` string[] — Array containing dimensions to exclude from the spending limit control. See the [guide](https://docs.solarisgroup.com/guides/cards/card-spending-controls/#list-of-dimensions) for more information about dimensions.
  - `positive_balance_limit` boolean — It is set to true if the limit field represents positive balance limit. It is an optional field. Default value is false.

## Response `201`

The card spending limit control was successfully created.

- CardControlSpendingLimitResponseV2
  - `id` string, required — ID of the created card spending limit control.
  - `scope` 'CARD' | 'CARDHOLDER' | 'ACCOUNT' | 'BUSINESS' | 'PARTNER' | 'PARTNER_CARDS' | 'BUSINESS_CARDS' | 'ACCOUNT_CARDS' | 'CARDHOLDER_CARDS' | 'NON_BUSINESS_CARDS' | 'PARTNER_CARDHOLDERS', required — The scope of the card spending control.
  - `scope_id` string, required — ID of the resource that corresponds with the `scope`. For example, if the `scope` is `PARTNER`, then the `scope_id` would be your partner ID. For `business`, it would be the business ID.
  - `origin` 'SOLARISBANK' | 'PARTNER', required — Indicates whether the card spending control was created by Solaris SE or by you.
  - `idempotency_key` string, uuid, required — A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
  - `limit` SpendingLimitRuleV2, required — Object containing the properties of the spending limit control. Note that you must set either `amount` or `count`; you cannot set both.
    - `period` 'HOURLY' | 'DAILY' | 'WEEKLY' | 'MONTHLY' | 'MINUTES_60' | 'HOURS_24' | 'DAYS_7' | 'DAYS_30' | 'TRANSACTION', required — The time period in which to restrict transactions.
    - `amount` integer — The maximum amount (in Euro cents) that customers may spend under this card spending limit control. **Note**: You cannot set `amount` and `count` together under the same scope ID.
    - `count` integer — The maximum number of transactions that customers may conduct under this card spending limit control. **Note**: You cannot set `amount` and `count` together under the same scope ID.
    - `conditions` DimensionCondition[] — Object containing the dimensions to either include or exclude in this control. Note that you must use either `dimension` or `excluded_dimension`; you cannot use both.
      - `type` 'MERCHANT_CATEGORY' | 'POS_ENTRY_MODE' | 'TRANSACTION_TYPE' | 'MERCHANT_COUNTRY' | 'ACQUIRER_ID' | 'MERCHANT_ID' | 'ALL_TYPES', required — The type of transactions to be included/excluded.
      - `dimension` string[] — Array containing dimensions to include in the spending limit control. See the [guide](https://docs.solarisgroup.com/guides/cards/card-spending-controls/#list-of-dimensions) for more information about dimensions.
      - `excluded_dimension` string[] — Array containing dimensions to exclude from the spending limit control. See the [guide](https://docs.solarisgroup.com/guides/cards/card-spending-controls/#list-of-dimensions) for more information about dimensions.
  - `positive_balance_limit` boolean — It is set to true if the limit field represents positive balance limit. It is an optional field. Default value is false.

## Other responses

- `208` — The card spending limit control has already been created.
- `400` — The request validation failed.
- `403` — You are not authorized to perform this action.
- `500` — Internal server error.

---

[API](https://skmtc.net/solarisgroup/apis/card-creation-servicing.md) · [All operations](https://skmtc.net/solarisgroup/apis/card-creation-servicing/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/solarisgroup/card-creation-servicing/revisions/a772504dcc9e/schema)
