> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/click-to-pay/implement-click-to-pay-issuers/retrieve-click-to-pay-profiles.md).

# Retrieve Click to Pay profiles

### Overview

The issuer backend might need to retrieve the Click to Pay data previously enrolled for an end user. Typical use cases include:

* Displaying Click to Pay details to the end user in the issuer application.
* Verifying the information stored in Click to Pay before allowing the end user to update it.

D1 exposes the [Click to Pay get consumer profiles API](/click-to-pay/integrate-the-d1-api/d1-api-summary.md), which retrieves all Click to Pay profiles that the issuer has enrolled in the Click to Pay directories.

When multiple Click to Pay directories are configured, D1 aggregates the data and returns at most one profile per directory. The response contains a `clickToPayProfiles[]` array, where each entry represents the consumer profile stored in a given directory.

{% hint style="info" %}
**Quick links**

* [Enroll cards in Click to Pay](/click-to-pay/implement-click-to-pay-issuers/enroll-cards-in-click-to-pay.md)
* [Update Click to Pay profiles](/click-to-pay/implement-click-to-pay-issuers/update-click-to-pay-profiles.md)
* [Opt out cards from Click to Pay](/click-to-pay/implement-click-to-pay-issuers/opt-out-cards-from-click-to-pay.md)
  {% endhint %}

#### When to use this API

Use **Click to Pay get consumer profiles** when the issuer backend needs a current snapshot of the consumer information stored in Click to Pay directories. Typical situations include:

* Showing the consumer which cards and profile data are registered in Click to Pay.
* Comparing the data stored in Click to Pay with the data stored in the issuer backend before deciding whether an update is required.
* Troubleshooting differences between what is stored in the issuer backend and what is stored in Click to Pay.

Do **not** use this API to update consumer or card details. To modify the data stored in Click to Pay, use the update APIs described in [Update Click to Pay profiles](/click-to-pay/implement-click-to-pay-issuers/update-click-to-pay-profiles.md).

### Flow

The diagram below shows the overall flow to retrieve Click to Pay consumer profiles through D1:

<figure><img src="/files/Qxg1qe8DRUgLY7yM56Qu" alt=""><figcaption></figcaption></figure>

## Sequence diagram

### Prerequisites

Please refer to [prerequisites](/click-to-pay/implement-click-to-pay-issuers/enroll-cards-in-click-to-pay.md#prerequisites).

The sequence diagram below illustrates the detailed behavior when retrieving Click to Pay consumer profiles. When several directories are available, D1 queries each directory and consolidates the profiles in a single response.

<figure><img src="/files/wahmXSbd7FUxrKLzHvvU" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/click-to-pay/implement-click-to-pay-issuers/retrieve-click-to-pay-profiles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.