Customers
Read the customer behind the cards — portfolio summary, corporate relationships and total assets.
Where this is used
Implemented on 4 programmes. A capability is one business idea, built once per card programme, so these are the programmes it applies to.
- 2 operationsCredit Digital Channels Integration APIOpen this capability’s operations in the reference.
- 4 operationsDebit Digital Channels Integration APIOpen this capability’s operations in the reference.
- 2 operationsPrepaid Digital Channels Integration APIOpen this capability’s operations in the reference.
- 4 operationsCommon MethodsOpen this capability’s operations in the reference.
Journeys that walk through it
Guides about it
- General InformationCore card management features including card number generation, status management, PIN handling, transaction restrictions, and notification services.
Operations
credit-digital-channels-integration
debit-digital-channels-integration
/debit/api/getCorporateCustomerInfoByIndividualCustomer
Retrieves corporate customer information (shadow card numbers, masked numbers, main customer number) for an individual customer who is part of a corporate program.
POST/debit/api/getCustomerAsset
Retrieves asset information (cards and accounts) for a customer, providing a portfolio view.
POST/debit/api/isCustomerConvertToRipper
Checks whether customer or card data exists in "Ripper" system (likely a legacy or external system).
POST/debit/api/getCustomerAssetsSummaryDebit
Retrieves a summary of debit card assets for a customer, optimized for display and reporting.
prepaid-digital-channels-integration
integration-corebanking-indoor
/Indoor/api/getAssetByShadowCardNumber
Retrieves asset information (card account relationship) for a card.
POST/Indoor/api/getCustomerDetail
Retrieves comprehensive customer information.
POST/Indoor/api/createCustomer
Registers a customer from the bank's core system on the card platform and returns the customerNumber every later call is keyed on. The customer is mirrored rather than created here: externalCustomerNumber holds the identifier the core system already knows them by, and an omitted customerNumber makes the platform generate one.
POST/Indoor/api/updateCustomer
Updates a registered customer's identity, corporate, segment and preference data. Limits are not changed here — they move through the customer limit operations.
integration-corebanking-outdoor · not published
/Outdoor/api/customerDataReplicationFromCoreBanking
Copies a customer's core banking record into the platform's customer store
/Outdoor/api/getCustomerInformationAsCustomerMasterByCustomerNumber
Reads a customer by customer number and maps the answer onto the platform's own customer master shape
/Outdoor/api/getCustomerInformationByCustomerNumber
Reads a customer's core banking record by customer number
/Outdoor/api/getCustomerInformationByCustomerOid
Reads a customer's core banking record by customer OID