Operation limits
Cap what a card may do per transaction, per day, per week and per month, by channel and operation type.
getCardOperationLimit
Retrieves operation limits for a specific credit card by card reference and channel. Maps results from Lifecycle service to GetCardOperationLimitResponseItem objects including transaction limits, counts, amounts, and detailed limitation keys (channel, network, event codes, group codes, descriptions, and custom limitation flags) on a per-transaction, daily, weekly, monthly, and yearly basis.
Part of:
- Journey 02 · Managing a card product — step 1, Read current controls
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCardOperationLimit › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
cardRefNumberThe card whose limits are read.
getCardOperationLimit › Responses
Success
The limit rows the search matched.
setCardOperationLimit
Sets the card operation limits, including transaction amounts and counts for daily, weekly, monthly, and yearly limits, for a specified card.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
setCardOperationLimit › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
cardRefNumberThe card whose limits are set.
ListHasNoItem — The limits to write. Must be sent and must hold at least one entry.
setCardOperationLimit › Responses
Success.
Each entry is answered separately in listOfResult, with its own code and message — a limit the channel may not raise, or one that would exceed the customer's, is reported there rather than refusing the call. A 200 does not mean every entry was applied.
One entry per item the request asked about.
removeCardOperationLimit
Removes operation limits from a credit card. Accepts a card reference number and a list of operation limit keys. Invokes the lifecycle service proxy to process the removal and returns a list of results including action type, success flag, errors, and operation limit keys.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
removeCardOperationLimit › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
cardRefNumberThe card whose operation limits are removed.
ListHasNoItem — Which operation limits to remove. An empty list is refused rather than treated as nothing to do.
removeCardOperationLimit › Responses
Success
One entry per item the request asked about.
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.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCardLimitationParameterData › Request Body
shadowCardNumberThe platform's own handle for a card, and the identifier most operations take. It is returned by every operation that creates a card and by the card listings; a caller does not compose one.
getCardLimitationParameterData › Responses
Success
getCustomerOperationLimit
Retrieves a customer's operational limits for credit cards. The method calls the customer service proxy to get all operation limits for a customer and channel, filters the list to include only credit cards (CardType = "C") and those with CustomLimitationChangeFlag enabled, and maps the remaining data into a detailed response including daily, weekly, monthly, yearly, and per-transaction limits along with descriptive keys and profile information.
Part of:
- Journey 02 · Managing a card product — step 1, Read current controls
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCustomerOperationLimit › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
customerNumberRequired in practice — Customer whose operation limits are read. Not validated — the service's check on it is commented out, so a zero or negative value is not refused; it simply matches nothing and the list comes back empty.
getCustomerOperationLimit › Responses
Success
The limit rows the search matched.
setCustomerOperationLimit
Sets operation limits for a specific customer. Validates and updates transaction limits across various profiles, ensuring control over daily, weekly, monthly, and yearly transaction amounts and counts.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
setCustomerOperationLimit › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
customerNumberCustomer whose operation limits are set. Zero is refused; the service checks for zero rather than for absence, so the two arrive as the same failure.
ListHasNoItem — The limits to set. An empty list is refused rather than treated as nothing to do.
setCustomerOperationLimit › Responses
Success
One entry per item the request asked about.
removeCustomerOperationLimit
Removes operation limits at the customer level. Accepts a customer number and a list of operation limit keys. Invokes the customer service proxy to process the removal and returns a list of results including action type, success flag, errors, and operation limit keys.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
removeCustomerOperationLimit › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
customerNumberCustomer whose operation limits are removed. Negative and zero are refused separately, each with its own code, and the customer must then exist.
ListHasNoItem — Which limits to remove. An empty list is refused; a key naming no limit on this customer is refused as a business failure.
removeCustomerOperationLimit › Responses
Success
One entry per item the request asked about.
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.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCustomerLimitationParameterData › Request Body
customerNumberThe customer at the bank's core banking system, as a number. The platform stores it rather than issuing it, so it comes from the core.
getCustomerLimitationParameterData › Responses
Success