Card issuance models

D1 supports two card issuance models:

• Card creation model: D1 creates the card, allocates the PAN, expiry date, and other card credentials. D1 can optionally synchronize these credentials with the issuer’s CMS.

• Card registration model: The issuer creates the card in its CMS and then registers the existing card and its credentials in D1.

Once the card exists in D1 (through creation or registration), you can use services such as Tokenization, Push provisioning, and Secure Card Display.

You can also configure D1 to participate in payment authorization based on the workflow defined on the card product:

• Authorization orchestration workflow: D1 orchestrates the complete authorization process.

• Authorization control workflow: D1 performs a subset of authorization checks.

• No authorization mode: D1 does not participate in authorization.

These models and workflows are described in detail in D1 authorization.

Prerequisites

Before you create or register a card in D1, make sure that:

• A card product is configured in D1 with the help of the Thales delivery team. The card product is identified by a unique cardProductId.

• The end user who owns the card is registered in D1. See Register end users via API.

Card creation model

In the card creation model:

• D1 is responsible for creating the card.

• D1 allocates the PAN, expiry date, and other card attributes.

• D1 can optionally synchronize the card credentials with the issuer’s CMS.

Choose this model when you want D1 to own the full card creation process while keeping your CMS synchronized.

Card registration model

In the card registration model:

• The issuer’s CMS is responsible for creating the card.

• The issuer then registers the existing card in D1 through the registration APIs.

• D1 stores the card credentials received from the issuer.

Choose this model when your CMS remains the system of record for cards and D1 acts as the digital enablement.

Account configuration

As part of card creation or registration, D1 needs the list of accounts linked to the card whenever D1 is expected to perform fund checks during authorization (for example, in the authorization orchestration workflow).

D1 uses these accounts to query the Core Banking system (CBS) for available funds.

Each account is defined by:

• default: Set to true if this is the default account for the card.

• type: The account type. D1 supports CHECKING and SAVING.

• number: The account number that D1 uses to reference the account when checking funds with the CBS.

• currencyCode: The currency of the account.