Customers
Read the customer behind the cards — portfolio summary, corporate relationships and total assets.
getCorporateCustomerInfoByIndividualCustomer
Retrieves corporate customer information for a given individual customer. Validates the request, fetches customer assets, and filters for corporate supplementary cards (ProductSegmentCode = "T"). Returns a GetCorporateCustomerInfoByIndividualCustomerResponse containing MainCustomerNumber, ShadowCardNumber, and MaskedCardNumber for each relevant card.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCorporateCustomerInfoByIndividualCustomer › 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.
customerNumberThe individual customer whose corporate relationships are read.
getCorporateCustomerInfoByIndividualCustomer › Responses
Success
getCustomerAsset
Retrieves all debit card assets for a given customer. Fetches card details, sensitive data, account info, status, and delivery info. Uses _dcidRepository.GetCustomerAssetByCustomernumber for card data, _dbtServiceProxy.ListCardAccountByShadowCardNumber for account info, _coreBankingIntegrationOutdoor.GetAccountInformation for balances, and GetSensitiveData for sensitive card info (CVV2, PAN). Returns a GetCustomerAssetResponse containing a list of DebitCardModel with all relevant information.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCustomerAsset › Request Body
channelCodeThree-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.
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.
purposegetCustomerAsset › Responses
Success.
Nothing in this request is validated. The facade passes the customer number, purpose and channel straight to a generated repository read, so an unknown customer, a zero customer number and an unrecognised purpose all return an empty result rather than a refusal.
channelCode is this operation's spelling of the channel field — it is not the channel the rest of the API carries, and it is not checked against the channel enumeration.
The cards the search matched.
isCustomerConvertToRipper
Checks whether a customer has any cards in the system. Accepts a CustomerNumber and returns flags indicating whether the customer has Credit, Debit, or Prepaid cards.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
isCustomerConvertToRipper › Request Body
customerNumberCustomer the question is asked about. The field is a non-nullable number, so omitting it is not the same as sending nothing: it arrives as zero and is refused as zero, naming CustomerNumber with the message CustomerNumber Invalid Value. A negative value is refused by a second check carrying the same message. There is no null check at all — absent and zero are one failure, not two.
isCustomerConvertToRipper › Responses
Success
haveAnyDebitCardAlways true. The service returns a constant here; it does not look at this customer's assets for this field.
haveAnyCreditCardThe only field computed from the customer. true whenever the platform is not running the old system. While it is, true needs all three: the ShowCreditCardInNewVersion parameter set to Y, at least one of the customer's cards in the credit service domain, and no suppressed conversion card among them — a card whose converted shadow number is set and which is either hidden on mobile or in status B forces this to false on its own, whatever else the customer holds.
haveAnyPrepaidCardAlways true. A constant, as haveAnyDebitCard is.
getCustomerAssetsSummaryDebit
Retrieves a summarized list of debit card assets for a customer. Fetches card details, status, and related accounts. Uses _dcidRepository.GetCustomerAssetsSummaryDebit for card info, _dbtServiceProxy.ListCardAccountByShadowCardNumber for accounts, _coreBankingIntegrationOutdoor.GetAccountInformation for balances, and _cache for product and status descriptions. Filters out invalid or expired reissue cards and orders the list according to sort rules. Returns GetCustomerAssetsSummaryDebitResponse containing a list of GetCustomerAssetsSummaryDebitCardModel with card and account info.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCustomerAssetsSummaryDebit › Request Body
channelCodeThree-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.
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.
getCustomerAssetsSummaryDebit › Responses
Success
The cards the search matched.