Operation limits
Cap what a card may do per transaction, per day, per week and per month, by channel and operation type.
getCardLimitationParameterData
Retrieves the card limitation parameters for a debit card identified by ShadowCardNumber. Returns a list of CardLimitParameterData including daily, weekly, monthly, yearly transaction amounts and counts, per transaction amount limits, ratios, No-CVM consecutive transaction limits, profile code/description, and channel/network/event keys. Data is fetched from _dbtServiceProxy.GetCardLimitationParameterData.
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
getCardOperationLimit
Retrieves the operation limits for a debit card based on the CardRefNumber and Channel. Returns a list of GetCardOperationLimitResponseItem containing transaction limits by daily, weekly, monthly, and yearly amounts and counts, along with limit profile and event details. Uses _dbtServiceProxy.GetCardOperationLimit to fetch the data.
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 or updates operation limits for a specific debit card. Accepts card reference number, channel, and a list of operation limit items including daily, weekly, monthly, and yearly limits, per-transaction limits, and profile details. Returns the result of each operation with success status, errors, and updated operation limit data.
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 specific operation limits for a card. Accepts a list of operation limit keys and deletes them from the system, returning the result status and any associated errors.
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.
getCustomerOperationLimit
Returns customer operation limits for debit cards. Retrieves operation limits via CustomerService, filters by CardType = D and CustomLimitationChangeFlag = true, and returns profile information with per-transaction and period-based limits.
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 matches nothing and the list comes back empty.
getCustomerOperationLimit › Responses
Success
The limit rows the search matched.
setCustomerOperationLimit
Sets or updates operation limits for a customer. Accepts customer number, channel, and a list of operation limit definitions, applying them to the customer account.
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 specific operation limits for a customer. Accepts a list of operation limit keys and deletes them from the system, returning the result status and any associated errors.
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, 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
Returns customer limitation parameter data for debit cards. Retrieves limitation profiles via CustomerService, filters records by CardType = D, and returns profile, transaction limit ratios, period-based limits, and detailed limitation key information.
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