Enroll cards by auto enrollment

Automatic Click to Pay enrollment lets the issuer enable enrollment without calling the explicit Click to Pay enrollment API.

Issuers that do not have specific constraints on the data to enroll (for example, consent management or additional data validation) can enable Click to Pay enrollment directly when consumer and card data is registered in D1.

Please note that the auto enrollment option must be chosen by the issuer at the project kickoff.

Auto enrollment during D1 registration

Automatic Click to Pay enrollment is driven by the Manage end users and Manage cards process.

When auto enrollment is enabled, the consumer and card data provided during registration is used to automatically trigger a Click to Pay enrollment request.

As described in the Manage end users and Manage cards sections, registration can be performed through:

• D1 API

• Batch file (see section Integrate batch files for more details)

Key points

• Auto enrollment relies entirely on the data sent in the D1 registration flow. If any required consumer details are missing or invalid, the Click to Pay enrollment will fail.

• Auto enrollment is suitable only when the issuer does not require additional controls during enrollment (such as explicit consent management or extra data validation).

• The issuer can still use Notifications and the Get Operation APIs to verify the final status of the auto enrollment operation (check API summary section).

The issuer must provide all required consumer details through the D1 API or batch files. Otherwise, the Click to Pay enrollment will fail and the platform may be overloaded with unnecessary retries.

Do not enable auto enrollment if you are not confident in the quality and completeness of the consumer details, or if you require explicit consent management as part of enrollment.