The scope of the card spending control.
Card creation & servicing (1.0)
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/
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.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/lists
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
{ "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "inclusion": { "type": "MERCHANT_CATEGORY", "dimension": [ … ] }, "exclusion": { "type": "MERCHANT_CATEGORY", "dimension": [ … ] } }
The card controls list was successfully created.
ID of the created card controls list.
The scope of the card spending control.
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.
Indicates whether the card spending control was created by Solarisbank or by you.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
{ "id": "7a911b90-0109-11ec-9a03-0242ac130003", "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "origin": "SOLARISBANK", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "inclusion": { "type": "MERCHANT_CATEGORY", "dimension": [ … ] }, "exclusion": { "type": "MERCHANT_CATEGORY", "dimension": [ … ] } }
Filter the results by the type of scope.
Filter the results by a specific scope (e.g., the ID of an account
or the person
ID of a cardholder).
Using this filter, the API will return all card controls lists that were defined at the ACCOUNT
, BUSINESS
, or PARTNER
level that apply to a specific card. You can only use this filter in combination with the scope
and scope_id
filters. The scope
must be set to CARD
and the scope_id
must be set to a card ID.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/lists
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
Successful result of the operation
ID of the created card controls list.
The scope of the card spending control.
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.
Indicates whether the card spending control was created by Solarisbank or by you.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
[ { "id": "7a911b90-0109-11ec-9a03-0242ac130003", "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "origin": "SOLARISBANK", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "inclusion": { … }, "exclusion": { … } } ]
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/lists/{id}
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
The operation was successful.
ID of the created card controls list.
The scope of the card spending control.
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.
Indicates whether the card spending control was created by Solarisbank or by you.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
{ "id": "7a911b90-0109-11ec-9a03-0242ac130003", "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "origin": "SOLARISBANK", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "inclusion": { "type": "MERCHANT_CATEGORY", "dimension": [ … ] }, "exclusion": { "type": "MERCHANT_CATEGORY", "dimension": [ … ] } }
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/lists/{id}
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
The scope of the card spending control.
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.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
Amount or count limit - only one could be used.
The dimension of transactions to be restricted.
The type of transactions to be included/excluded.
The time period in which to restrict transactions.
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.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/spending_limits
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
{ "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "limit": { "type": "MERCHANT_CATEGORY", "dimension": [ … ], "period": "HOURLY", "amount": 10000, "count": 0 } }
The card spending limit control was successfully created.
ID of the created card spending limit control.
The scope of the card spending control.
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.
Indicates whether the card spending control was created by Solarisbank or by you.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
Amount or count limit - only one could be used.
The dimension of transactions to be restricted.
The type of transactions to be included/excluded.
The time period in which to restrict transactions.
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.
{ "id": "7a911b90-0109-11ec-9a03-0242ac130003", "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "origin": "SOLARISBANK", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "limit": { "type": "MERCHANT_CATEGORY", "dimension": [ … ], "period": "HOURLY", "amount": 10000, "count": 0 } }
Filter the results by the type of scope.
Filter the results by a specific scope (e.g., the ID of an account
or the person
ID of a cardholder).
Using this filter, the API will return all card spending limit controls that were defined at the ACCOUNT
, BUSINESS
, or PARTNER
level that apply to a specific card. You can only use this filter in combination with the scope
and scope_id
filters. The scope
must be set to CARD
and the scope_id
must be set to a card ID.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/spending_limits
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
Successful result of the operation
ID of the created card spending limit control.
The scope of the card spending control.
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.
Indicates whether the card spending control was created by Solarisbank or by you.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
Amount or count limit - only one could be used.
The dimension of transactions to be restricted.
The type of transactions to be included/excluded.
The time period in which to restrict transactions.
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.
[ { "id": "7a911b90-0109-11ec-9a03-0242ac130003", "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "origin": "SOLARISBANK", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "limit": { … } } ]
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/spending_limits/{id}
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
Successful result of the operation
ID of the card spending limit control.
The scope of the card spending control.
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.
Indicates whether the card spending control was created by Solarisbank or by you.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
Amount or count limit - only one could be used.
The dimension of transactions to be restricted.
The type of transactions to be included/excluded.
The time period in which to restrict transactions.
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.
{ "id": "7a911b90-0109-11ec-9a03-0242ac130003", "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "origin": "SOLARISBANK", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "limit": { "type": "MERCHANT_CATEGORY", "dimension": [ … ], "period": "HOURLY", "amount": 10000, "count": 0 }, "utilized_limit": { "amount": 10000, "count": 5 } }
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/spending_limits/{id}
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
Request
Creates a card spending limit control and applies it to all cards defined in the scope
and scope_id
of the request.
Important This endpoint replaces the old version. 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.
The scope of the card spending control.
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.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
Object containing the properties of the spending limit control. Note that you must set either amount
or count
; you cannot set both.
The time period in which to restrict transactions.
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.
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.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/spending_limits(use api-version-header to consume this endpoint)
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
{ "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "limit": { "period": "HOURLY", "amount": 10000, "count": 0, "conditions": [ … ] }, "positive_balance_limit": true }
The card spending limit control was successfully created.
ID of the created card spending limit control.
The scope of the card spending control.
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.
Indicates whether the card spending control was created by Solarisbank or by you.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
Object containing the properties of the spending limit control. Note that you must set either amount
or count
; you cannot set both.
The time period in which to restrict transactions.
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.
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.
{ "id": "7a911b90-0109-11ec-9a03-0242ac130003", "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "origin": "SOLARISBANK", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "limit": { "period": "HOURLY", "amount": 10000, "count": 0, "conditions": [ … ] }, "positive_balance_limit": true }
Request
Returns all active card spending limit controls.
Important This endpoint replaces the old version. 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 an Api-Version
, then the API will return the older version of the response.
Filter the results by the type of scope.
Filter the results by a specific scope (e.g., the ID of an account
or the person
ID of a cardholder).
Using this filter, the API will return all card spending limit controls that were defined at the ACCOUNT
, BUSINESS
, or PARTNER
level that apply to a specific card. You can only use this filter in combination with the scope
and scope_id
filters. The scope
must be set to CARD
and the scope_id
must be set to a card ID.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/spending_limits(use api-version-header to consume this endpoint)
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
Successful result of the operation
ID of the created card spending limit control.
The scope of the card spending control.
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.
Indicates whether the card spending control was created by Solarisbank or by you.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
Object containing the properties of the spending limit control. Note that you must set either amount
or count
; you cannot set both.
The time period in which to restrict transactions.
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.
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.
It is set to true if the limit field represents positive balance limit. It is an optional field. Default value is false.
[ { "id": "7a911b90-0109-11ec-9a03-0242ac130003", "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "origin": "SOLARISBANK", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "limit": { … }, "positive_balance_limit": true } ]
Request
Returns information about the card spending limit control specified in the request URL.
Important This endpoint replaces the old version. 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 an api-version
, then the API will return the older version of the response.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/spending_limits/{id}(use api-version-header to consume this endpoint)
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
Successful result of the operation
ID of the card spending limit control.
The scope of the card spending control.
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.
Indicates whether the card spending control was created by Solarisbank or by you.
A randomly generated UUID which the server uses to recognize subsequent retries of the same request.
Object containing the properties of the spending limit control. Note that you must set either amount
or count
; you cannot set both.
The time period in which to restrict transactions.
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.
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.
{ "id": "7a911b90-0109-11ec-9a03-0242ac130003", "scope": "CARD", "scope_id": "54e06604b0cf825810bec508cc1f2dc7mcrd", "origin": "SOLARISBANK", "idempotency_key": "504f6816-f7b5-4965-bc35-69acadc9f5c7", "limit": { "period": "HOURLY", "amount": 10000, "count": 0, "conditions": [ … ] }, "utilized_limit": { "amount": 10000, "count": 5 }, "positive_balance_limit": true }
Request
Deletes the card spending limit control specified in the request URL..
Important This endpoint replaces the old version. 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 an api-version
, then the API will return the older version of the response.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/cards/v1/card_controls/spending_limits/{id}(use api-version-header to consume this endpoint)
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload