Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Update profiles by D1 SDK

Overview

This page explains how the issuer application can update Click to Pay profile data by using the D1 SDK.

The issuer application can call updateConsumer to update end user profile data, or updateCard to update card-level data for one card.

Use this SDK flow when you want the end user to review and update Click to Pay data directly in the issuer application, while D1 orchestrates the backend update with the Click to Pay directories.

Choose the right SDK API

updateConsumer

Use updateConsumer when consumer data stored in Click to Pay must change.

Provide all consumer fields, even if only one value changed.

If you also provide a billing address, D1 updates the billing address for all cards linked to the consumer profile.

updateCard

Use updateCard when only one enrolled card must change.

This API updates the billing address for the selected card and, for Visa only, the cardholder name.

Flow

The SDK update flow follows these steps:

  1. The issuer application initializes D1 SDK and logs in the end user.

  2. The issuer application retrieves the current Click to Pay profiles.

  3. The end user updates the required data in the issuer application.

  4. The issuer application calls updateConsumer or updateCard.

  5. D1 sends the request to the D1 backend by using the authenticated end user context.

  6. The D1 backend updates the relevant Click to Pay directories.

  7. D1 returns the operation status to the issuer application.

Sequence diagram

The SDK flow has the same functional behavior as the backend update flow, but it is initiated directly from the issuer application.

For the detailed sequence diagrams, refer to Update Click to Pay profiles.

Key points

  • Both operations are asynchronous.

  • The immediate result contains a status of SUCCESSFUL or PENDING, plus an operationID.

  • Use Retrieve profiles by D1 SDK to prefill the issuer application user interface with the current Click to Pay data.

  • Use updateConsumer only when you want to update Click to Pay data specifically.

  • If the issuer backend stores the end user profile in D1, prefer Update consumer information when you want all channels, including Click to Pay, to stay synchronized.

  • For Mastercard, when you provide a billing address, provide the complete address object.

Handle Click to Pay push notifications

Refer to Handle Click to Pay push notifications in the enrollment by D1 SDK documentation for the implementation details.

SDK API for updateConsumer

Use updateConsumer when the issuer application updates end user profile data in Click to Pay.

This API updates the end user profile in all relevant Click to Pay directories. If you provide a billing address, D1 also updates the billing address for each enrolled card.

Always send the full consumer data set.

Do not send only the changed field.

SDK API for updateCard

Use updateCard when the issuer application updates one enrolled card in Click to Pay.

This API updates card-level data only. Use it for the billing address, or for the cardholder name when the card belongs to Visa.

Use updateCard only for data attached to one card.

If the end user profile changes, use updateConsumer instead.

Last updated

Was this helpful?