Card issuance and personalisation

Create individual, corporate and virtual cards, and check which products a customer is eligible to hold before you issue.

Operations21DomainCardsStatedocumentedAPIs4

Where this is used

Implemented on 3 programmes. A capability is one business idea, built once per card programme, so these are the programmes it applies to.

Journeys that walk through it

Guides about it

  • Product IdentificationComprehensive card product definition and parametric management system for credit, debit, prepaid, digital, and virtual cards.
  • Credit Card ApplicationsComplete credit card lifecycle management including limits, statements, installments, interest calculation, payments, and delinquency tracking.
  • Debit Card ApplicationsDebit card management with bank account integration, On-Us and Off-Us transaction support, and real-time balance verification.
  • Debit card issuing, end to endCreate the card, get it to the cardholder, then run it — the three stages of a debit programme in the order you call them.
  • Prepaid Card ApplicationsComplete prepaid card management with wallet and balance operations, anonymous and registered cards, and multi-currency support.

How this behaves

Creating a card is the first of seven stages

The call that creates a card returns when the record exists. The cardholder is five stages away, and most of what happens between is not an operation anybody calls — which is worth knowing before a launch plan treats issuance as one step.

From order to in-life
  1. 1 · OrderOne card, or a bulk order into stockNot published
  2. 2 · GenerateCard record and candidate numbersNot published
  3. 3 · EmbossBatched to the bureauCancel and pending list only
  4. 4 · PersonaliseName, stripe and chip writtenNot published
  5. 5 · DeliverCourier file, movements, barcodePublished
  6. 6 · ActivateStatus change; requested limit appliedPublished
  7. 7 · In-lifeLimits, PIN, status, statementsPublished
Embossing is a batch, and that is why its surface looks thin.

Requests accumulate through the day and go to the production bureau in one session, so there is nothing to call per card. What is published around it is the pending list and a cancellation — which is exactly what an incident needs: a card ordered for an account that has since been compromised has to be stopped before it is printed.

The embossing reason is the business classification of why a card is being produced — new, renewal, lost, damaged, name change — and it decides both the fee and what becomes of the card being replaced. Read the permitted list rather than sending a remembered code.

A no-name card inverts the first four stages: the order is against stock rather than a person, and the card is bound to a customer at activation instead — see No-name cards.

The limit arrives at activation, not at creation

A limit asked for on the application is held rather than applied: it is assigned when the card is activated. So a card read between issuance and activation shows no limit, and that is correct rather than a failure of the create call.

Which is why resetting a card limit clears the stored request too.

Otherwise activating the physical card would hand the old limit straight back — see Card and customer limits.

Operations

credit-digital-channels-integration

POST

/credit/api/createIndividualCard

Creates a new individual credit card for a customer.

POST

/credit/api/createIndividualSupplementaryCard

Creates a new individual supplementary credit card for a customer. Supports digital and physical cards, multiple accounts, addresses, auto payment, permissions, and optional card miscellaneous options. Returns card reference, shadow card number, masked card number, and sensitive card data if applicable.

POST

/credit/api/createDummyCorporateCard

Creates a new dummy corporate credit card. Supports specifying addresses, accounts, statement preferences, card limits, virtual card relation, auto payment accounts, and permissions. Returns card reference, shadow numbers, masked card number, record ID, warnings, and sensitive card data if applicable.

POST

/credit/api/createCorporateCard

Creates a corporate credit card.

POST

/credit/api/createVirtualCard

Creates a virtual credit card linked to an existing physical card.

POST

/credit/api/getApplicableProductsByCustomerNumber

Retrieves credit card products that a customer is eligible to apply for.

POST

/credit/api/getApplicableProductsByMainCustomerPreControl

Checks applicable credit card products for a main customer before control. Returns a success flag indicating whether the pre-control check passed.

POST

/credit/api/createNoNameCard

Creates a card from a no-name envelope (pre-printed card stock with barcode).

POST

/credit/api/cancelCardEmbossByShadowCardNumber

Cancels a pending card embossing order.

POST

/credit/api/getPendingCardEmbossList

Retrieves list of cards pending embossing.

debit-digital-channels-integration

integration-corebanking-outdoor · not published

POST

/Outdoor/api/getVendorIssuanceCreditCard

Asks core banking to issue a vendor credit card