Card and customer limits
Raise, lower and reverse the spending limit on a card or on the customer behind it. Every change returns a log id you can reverse with.
changeCustomerLimitDecrease
Decreases the customer limit. Sends CustomerNumber and NewCustomerLimit to _cisServiceProxy.ChangeCustomerLimit. Optionally uses CardProfileSetCode for customer profile adjustments.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
changeCustomerLimitDecrease › Request Body
customerNumberThe customer whose limit changes.
newCustomerLimitThe limit to set. An absolute figure, not a delta — and it is what decides the direction, because this operation does not read one from the path.
cardProfileSetCodeRead-only — Declared on the request and not passed on.
changeCustomerLimitDecrease › Responses
Success, and the body is empty.
Identical to changeCustomerLimitIncrease. The two operations call the same service method with the same two fields and discard the same response; there is no code path that distinguishes them. Which one a caller uses is a matter of naming, and the direction is decided by newCustomerLimit.
changeCustomerLimitIncrease
Increases the customer limit. Sends CustomerNumber and NewCustomerLimit to _cisServiceProxy.ChangeCustomerLimit. Optionally uses CardProfileSetCode for customer profile adjustments.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
changeCustomerLimitIncrease › Request Body
customerNumberThe customer whose limit changes.
newCustomerLimitThe limit to set. An absolute figure, not a delta — and it is what decides the direction, because this operation does not read one from the path.
cardProfileSetCodeRead-only — Declared on the request and not passed on.
changeCustomerLimitIncrease › Responses
Success, and the body is empty.
Two things to know, and neither is in the schema. The response the customer service returns is discarded — this operation always answers with an empty ChangeCustomerLimitResponse. And this operation and changeCustomerLimitDecrease do exactly the same thing: both call the same ChangeCustomerLimit with the same two fields, so the direction comes from whether newCustomerLimit is above or below the customer's current limit, not from which of the two paths was called. There is also no channel on this request, unlike almost every other operation here.