Operation limits
Cap what a card may do per transaction, per day, per week and per month, by channel and operation type.
Where this is used
Implemented on 3 programmes. A capability is one business idea, built once per card programme, so these are the programmes it applies to.
- 8 operationsCredit Digital Channels Integration APIOpen this capability’s operations in the reference.
- 8 operationsDebit Digital Channels Integration APIOpen this capability’s operations in the reference.
- 8 operationsPrepaid Digital Channels Integration APIOpen this capability’s operations in the reference.
Journeys that walk through it
How this behaves
An operation limit is keyed by five things at once
This is a different layer from the card and customer limits. Those say how much; these say where, how and how often — and they live in their own table with their own operations.
- Transaction groupPurchase, cash, transfer…
- Main groupIts parent band
- ChannelPOS, ATM, internet, mobile
- NetworkDomestic / international
- EventWhat triggered it
At customer level the key is wider still: the merchant category and its group join it, a limit profile detail can be named, and the periods run per transaction, daily, weekly, monthly and yearly.
One call, many rows, and each one answers for itself
- AppliedInsert, update or deleteDecided per row
- Refused — flagCustomisation is closed for that key in the parameter
- Refused — profileThe profile code sent does not match the card's
- DeletedEvery amount and count left emptyNot “leave unchanged”
A 200 means the call ran. Each row carries its own outcome, and at customer level each one also names what happened to it — insert, update or delete — so the caller learns the effect rather than being told its own request back.
- A dry run is supported. With the validation-only flag set, every check runs, nothing is written, and the result list still comes back — which is what a "show me before I save" screen needs.
- The description fields beside the key are not carried. They are absent from the integration's own mapping, so sending them changes nothing.
Operations
credit-digital-channels-integration
/credit/api/getCardOperationLimit
Retrieves operation limits configured for a card.
POST/credit/api/setCardOperationLimit
Sets or updates operation limits for a card.
POST/credit/api/removeCardOperationLimit
Removes operation limits, reverting to defaults.
POST/credit/api/getCardLimitationParameterData
Retrieves card-specific limitation parameter data, including per-transaction, daily, weekly, monthly, and yearly limits, along with associated keys and profile details. Maps lifecycle service response to structured CardLimitationParameterData objects.
POST/credit/api/getCustomerOperationLimit
Retrieves customer-level operation limits.
POST/credit/api/setCustomerOperationLimit
Sets customer-level operation limits.
POST/credit/api/removeCustomerOperationLimit
Removes customer-level operation limits.
POST/credit/api/getCustomerLimitationParameterData
Retrieves customer limitation parameter data for credit cards. It calls the customer service proxy to get all limitation parameters for a customer, filters the results to only include cards of type "C" (credit cards), and maps them into a detailed response including transaction limits, counts, profile codes, descriptions, and other key attributes.
debit-digital-channels-integration
/debit/api/getCardLimitationParameterData
Retrieves detailed limitation parameter data including both configured limits and system defaults.
POST/debit/api/getCardOperationLimit
Retrieves all operation limits configured for a specific card, showing transaction limits by type, channel, and time period.
POST/debit/api/setCardOperationLimit
Creates or updates operation limits for a card.
POST/debit/api/removeCardOperationLimit
Removes specific operation limits from a card, reverting to default or customer-level limits.
POST/debit/api/getCustomerOperationLimit
Manage operation limits at the customer level, applying to all cards for that customer.
POST/debit/api/setCustomerOperationLimit
Manage operation limits at the customer level, applying to all cards for that customer.
POST/debit/api/removeCustomerOperationLimit
Manage operation limits at the customer level, applying to all cards for that customer.
POST/debit/api/getCustomerLimitationParameterData
Retrieves customer-level limitation parameters, showing defaults and inheritance rules.
prepaid-digital-channels-integration
/prepaid/api/getCardLimitationParameterData
Retrieves all limitation parameters (operation limits) configured for a specific card.
POST/prepaid/api/getCustomerOperationLimit
Retrieves configured operation limits for a customer.
POST/prepaid/api/getCardOperationLimit
Retrieves configured operation limits for a card.
POST/prepaid/api/setCustomerOperationLimit
Sets or updates operation limits at the customer level.
POST/prepaid/api/setCardOperationLimit
Sets or updates operation limits for a specific card.
POST/prepaid/api/removeCustomerOperationLimit
Removes specific operation limits from a customer.
POST/prepaid/api/removeCardOperationLimit
Removes specific operation limits from a card.
POST/prepaid/api/getCustomerLimitationParameterData
Retrieves limitation parameters at the customer level, which may apply to all cards belonging to a customer.