Register cards via API

The registration is a backend-to-backend process between your issuer backend and the D1 backend. It can be done at any time before the card is used in a D1 service. You can also combine card registration with card creation for the same end user.

As part of this registration, the issuer backend must provide the following information:

• cardId: A technical unique identifier of the card used to identify the card in the D1 API and D1 SDK, and for troubleshooting. The cardId must not be the PAN or derived from the PAN (for example, a hash or digest of the PAN).

• cardProductId: Identifies the card product definition to which the card is linked.

• PAN and expiry date: Provided encrypted using JWE.

• consumerId: The issuer backend identifier for the end user who owns the card.

Note : If the End User is not already register to D1 then D1 will automaticaly create and register a End User from the provided consumerId with any personal information associated. Then D1 will call the Get Consumer Info API each time it needs one or serveral personal information.

Unlike card creation, card registration does not require an account list, because D1 does not orchestrate calls to the Core Banking system (CBS).

Card registration depends on how you use D1:

• Card can be Explicitly register via the D1 API

• Or Card can be Implicitly register in some particular cases (based on cardId and consumerId):

  • If an unregistered card is Tokenize successfully .

  • If a unregistered card is Ordered from Physical Issuance

Sequence diagram

Card registration flow between the issuer backend and the D1 backend

After registration, you can use this card across different D1 Digital services:

• Transaction Control

• Secure Card Display

• Tokenization

• Push Provisioning