> 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/release-notes/backend/readme-2/apr-22.md).

# Apr 22

| Environment    | Date         |
| -------------- | ------------ |
| Pre-Production | Apr 16, 2026 |
| Production     | Apr 22, 2026 |

### Click to Pay

#### New Features

* Add a [Click to Pay opt-out at consumer level API](https://docs.payments.thalescloud.io/click-to-pay/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/click-to-pay-api#post-issuers-issuerid-consumers-consumerid-operations-clicktopayoptout).
  * Allow the issuer backend to opt out an end user and all associated cards in a single API call.
  * Add a `CLICK_TO_PAY_OPTOUT` consumer-level operation in [Get consumer operations](https://docs.payments.thalescloud.io/click-to-pay/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/consumer-api#get-issuers-issuerid-consumers-consumerid-operations).
  * Send the related consumer-level notification through [Send consumer notifications](https://docs.payments.thalescloud.io/click-to-pay/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/consumer-api#post-notifications-d1-v2-issuers-issuerid-consumers).

#### Improvements

* Update the Delete consumer API to use the new Click to Pay opt-out at consumer level API internally. This will generate a consumer-level `CLICK_TO_PAY_OPTOUT` operation and notification instead of card-level events.

### E-commerce enablement

#### New Features

* Add the [Create merchant API](https://docs.payments.thalescloud.io/ecom/integrate-the-d1-api/d1-api-reference/inbound-apis-to-thales-d1#post-merchant-gateways-merchantgatewayid-merchants) to register a merchant for a merchant gateway.
* Add the [Create token API](https://docs.payments.thalescloud.io/ecom/integrate-the-d1-api/d1-api-reference/inbound-apis-to-thales-d1#post-merchant-gateways-merchantgatewayid-merchants-merchantid-tokens) to create a token for a card on the merchant gateway domestic scheme.
* Add the [Get token metadata API](https://docs.payments.thalescloud.io/ecom/integrate-the-d1-api/d1-api-reference/inbound-apis-to-thales-d1#get-merchant-gateways-merchantgatewayid-merchants-merchantid-tokens-tokenid-metadata) to retrieve token status and the linked card details.
* Add the [Delete token API](https://docs.payments.thalescloud.io/ecom/integrate-the-d1-api/d1-api-reference/inbound-apis-to-thales-d1#delete-merchant-gateways-merchantgatewayid-merchants-merchantid-tokens-tokenid) to delete a token. Continue to support metadata retrieval after deletion.
* Add the [Create transaction API](https://docs.payments.thalescloud.io/ecom/integrate-the-d1-api/d1-api-reference/inbound-apis-to-thales-d1#post-merchant-gateways-merchantgatewayid-merchants-merchantid-tokens-tokenid-transactions) to generate a payment cryptogram for the authorization request and TSP Detokenization.
* Add the [token update notification API](https://docs.payments.thalescloud.io/ecom/integrate-the-d1-api/d1-api-reference/outbound-apis-from-thales-d1#post-merchant-gateways-merchantgatewayid-merchants-merchantid-tokens-tokenid-notify-update) to notify a merchant gateway when a token changes state or when the linked card is renewed or replaced.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/release-notes/backend/readme-2/apr-22.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.