Card lifecycle

Move a card through its states after issuance — status changes, replacement, renewal, blocking and closure.

Operations37DomainCardsStatedocumentedAPIs4

Operations

credit-digital-channels-integration

POST

/credit/api/getCardList

Retrieves a list of credit cards matching specified criteria.

POST

/credit/api/replaceCard

Replaces an existing card (e.g., due to expiration, loss, damage).

POST

/credit/api/getCardMemo

Retrieves memo/notes associated with a card.

POST

/credit/api/changeCardStatus

Changes the status of a credit card (activate, block, close, etc.).

POST

/credit/api/changeCustomerCreditCardStatus

Changes the credit card status for a given customer. Validates input parameters, calls the lifecycle service to update card statuses, and returns a list of shadow card numbers for cards that were closed. Supports optional activation of cards and ensures proper rollback and logging on failure.

POST

/credit/api/changeAndReplaceCard

Combines card status change and replacement in a single operation.

POST

/credit/api/getRenewCountByShadowCardNumber

Reads how many times a card has been renewed, broken down by emboss reason, with the maximum each reason allows. Replaces getRenewCountLostAndStolen, which counted only one reason and returned three flat figures rather than a list.

POST

/credit/api/getCreditCardInfo

Retrieves comprehensive card information including reward details.

POST

/credit/api/getCustomerCreditCardListByTenantId

Retrieves list of customer's credit cards filtered by tenant/product group.

POST

/credit/api/getCustomerCreditShadowCardsByTenantId

Retrieves shadow card numbers for a customer by tenant.

POST

/credit/api/getCustomerCreditCardListByTenantIdProductNumber

Retrieves cards filtered by tenant and product number.

POST

/credit/api/getCardListNew

Retrieves a list of credit cards based on various filters (card number, customer number, main customer number, barcode, account number, branch code, identification, courier status, etc.). Aggregates card product, branch, limit, debt, account info, annual fee, sensitive data (PAN/CVV2), and currency conversion details. Uses parallel async calls for efficiency and maps results to CreditCardModel objects.

debit-digital-channels-integration

POST

/debit/api/getCustomerDebitCardListByTenantId

Retrieves debit cards for a customer filtered by tenant ID, supporting multi-tenant architectures.

POST

/debit/api/getCustomerDebitShadowCardsByTenantId

Retrieves shadow card numbers (internal references) for a customer by tenant, supporting internal system integration.

POST

/debit/api/changeCardStatus

Changes the operational status of a debit card (e.g., Active, Blocked, Closed, Suspended).

POST

/debit/api/getCardList

Retrieves a list of debit cards matching various search criteria, supporting multiple query patterns for different use cases.

POST

/debit/api/getCardListNew

Retrieves the list of debit cards based on multiple filters such as ShadowCardNumber, CustomerNumber, MainCustomerNumber, Barcode, AccountNumber, BranchCode, CustomerNameSurname, IdentificationNumber, and CourierStatus. Supports corporate cards, active cards, and digital card flags. Returns a list of DebitCardModel including card details, sensitive data when applicable, account information via ListCardAccountByShadowCardNumber, card status logs, delivery information, and PIN setup status. Uses _dcidRepository.GetSearchByCustomernumberCardnumber for searching, _dbtServiceProxy for account and permission operations, _customerServiceProxy for card and PAN retrieval, and GetSensitiveData for retrieving sensitive card data such as CVV2.

POST

/debit/api/getCardInfo

Retrieves detailed information about a specific debit card, including status, linked accounts, and metadata.

POST

/debit/api/replaceCard

Replaces an existing card (due to expiration, loss, damage, or upgrade) while maintaining account relationships and card history.

POST

/debit/api/changeAndReplaceCard

Atomically changes card status (e.g., to closed) and initiates replacement in a single operation.

POST

/debit/api/isCardFoundIn

Checks whether a specific card exists in the system. Accepts a CardNumber and returns a flag (IsFound) along with the ServiceDomainId indicating where the card was found.

POST

/debit/api/addDebitCardLog

Adds a log entry for a debit card operation, supporting audit trails and debugging.

prepaid-digital-channels-integration

integration-corebanking-indoor