> 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/opt-out-cards-from-click-to-pay.md).

# Opt out cards from Click to Pay

## Overview

Click to Pay allows an end user to **opt a card out** so that it is no longer available during Click to Pay checkout.

To opt a card out of Click to Pay, the issuer uses the D1 API [Click to Pay opt-out card](/click-to-pay/integrate-the-d1-api/d1-api-summary.md).

Opting out a card has the following effects:

* The card is removed from the Click to Pay directory.
* The payment network deletes the associated digital card.
* The card no longer appears as a means of payment during Click to Pay checkout for that end user.

D1 also exposes another API to **opt out a consumer** from Click to Pay entirely. This removes the consumer details and all tokenized cards. Refer to [Click to Pay opt-out consumer](/click-to-pay/integrate-the-d1-api/d1-api-summary.md).

The opt-out is a definitive operation. If needed, the issuer can make the card available again by re-enrolling it in Click to Pay. For details, see [Enroll cards in Click to Pay](/click-to-pay/implement-click-to-pay-issuers/enroll-cards-in-click-to-pay.md).

{% 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)
* [Retrieve Click to Pay profiles](/click-to-pay/implement-click-to-pay-issuers/retrieve-click-to-pay-profiles.md)
* [Opt out by D1 API](/click-to-pay/implement-click-to-pay-issuers/opt-out-cards-from-click-to-pay/opt-out-by-d1-api.md)
* [Opt out by D1 SDK](/click-to-pay/implement-click-to-pay-issuers/opt-out-cards-from-click-to-pay/opt-out-by-d1-sdk.md)
  {% endhint %}

## Choose how to opt out

D1 provides two integration options for opting out a card from Click to Pay:

* **Opt out via issuer backend (D1 API)** – the issuer backend calls the [Click to Pay opt-out card](/click-to-pay/integrate-the-d1-api/d1-api-summary.md) API to remove a card from Click to Pay, or the [Click to Pay opt-out consumer](/click-to-pay/integrate-the-d1-api/d1-api-summary.md) API to fully remove the consumer from Click to Pay. See [Opt out by D1 API](/click-to-pay/implement-click-to-pay-issuers/opt-out-cards-from-click-to-pay/opt-out-by-d1-api.md).
* **Opt out via issuer application (D1 SDK)** – the issuer application uses the D1 SDK (`D1ClickToPay.optOutCard` or `D1ClickToPay.optOutConsumer`) to initiate the same backend flow from within the mobile experience. See [Opt out by D1 SDK](/click-to-pay/implement-click-to-pay-issuers/opt-out-cards-from-click-to-pay/opt-out-by-d1-sdk.md).

Both approaches trigger the same backend operation on D1 and on the Click to Pay directories. Choose the one that best fits your user experience and technical architecture.

{% hint style="info" %}
**When to use backend vs SDK opt-out**

Use **backend opt-out (D1 API)** when:

* Opt-out is triggered by the issuer backend (for example, card closure, fraud, or chargeback handling).
* Customer care agents perform opt-out from a customer care interface.
* You need to bulk-opt-out multiple cards without any issuer application interaction.

Use **SDK opt-out (D1 SDK)** when:

* You want the end user to initiate opt-out directly from the issuer application (for example, a "Remove from Click to Pay" action in card details).
* You want to show immediate feedback in the issuer application while D1 orchestrates the backend process.
* You already use the D1 SDK for Click to Pay enrollment and want a consistent user experience.
  {% endhint %}


---

# 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/opt-out-cards-from-click-to-pay.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.