Enroll cards in Click to Pay

Overview

To enroll an end user and an associated card in the Click to Pay service, D1 provides three options:

• Through the issuer backend (D1 API).

• Through the issuer application (D1 SDK – in-app integration required).

• Automatic enrollment during card and end user registration (check Manage end users and Manage cards for details).

The issuer can choose the preferred method.

D1 exposes a Click to Pay enrol API that creates a consumer profile in the Click to Pay service the first time it is called.

For subsequent Click to Pay enrol API calls, only the card is added, because the consumer profile is already created during the first call.

Quick links

• Enroll cards by D1 API

• Enroll cards by D1 SDK

• Enroll cards by auto enrollment

• Retrieve Click to Pay profiles

• Update Click to Pay profiles

• Opt out cards from Click to Pay

When to use backend vs SDK vs auto enrollment

Use backend enrollment (D1 API) when:

• Enrollment is initiated from the issuer backend or customer care interface.

• You want to control Click to Pay enrollment centrally, without requiring the issuer application to call the API.

Use SDK enrollment (D1 SDK) when:

• You want the end user to initiate Click to Pay enrollment directly from the issuer application.

• You want to show immediate feedback in the issuer application while D1 orchestrates the backend process.

Use auto enrollment when:

• You want cards to be enrolled in Click to Pay automatically during D1 registration.

• You do not need additional checks such as explicit consent management or extra data validation during enrollment.

• The Click to Pay enrol API is generic; it can be used to enroll data across any payment network (for example, Visa or Mastercard).

• The D1 model identifies the payment network type using cardId.

• Because D1 does not store the personal data used for the Click to Pay service, the issuer is responsible for ensuring that the same end user data is kept in the profiles stored within the payment network directories. This can be done through the Update Click to Pay profiles feature.

Prerequisites

The following prerequisites must be satisfied before calling the Click to Pay enrol API:

1

Have full end user and card details

The issuer must have the full details of the end user and the associated card. If needed, see D1 concepts.

2

Register card and end user

The D1 model requires registering both the card and the end user before enrollment. See Register end users via API and Register cards via API.

If the end user details have changed, do not call the Click to Pay enrol API.

Instead, call the Click to Pay update consumer API or Click to Pay update card API, according to the data that has changed. See Update Click to Pay profiles for details.

This allows the issuer backend to synchronize the Click to Pay directories.