> 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/august-2025/aug-4.md).

# Aug 4

| Environment    | Date        |
| -------------- | ----------- |
| Pre-Production | Aug 4, 2025 |
| Production     | Aug 4, 2025 |

### Click to Pay

#### New Features

* Add an option to automatically enroll cards in Click to Pay during registration.
* Speed up Click to Pay enrollment for new end users and cards.
* Support the following endpoints:
  * [Register card v2](https://thales-dis-dbp.stoplight.io/docs/d1-caas/gxe4p2chcr1j2-register-card)
  * [Create card v2](https://thales-dis-dbp.stoplight.io/docs/d1-caas/mr1pghnxjjerd-create)
  * [Register end users with cards batch file v2](https://thales-dis-dbp.stoplight.io/docs/d1-caas/5k3mz1j8g10h8-register-consumers-with-cards-batch-file-definition)
* Contact the Thales delivery team to enable this option at card product level.

### Physical issuance

#### Improvements

* Add an optional `multiCardId` field to the [Produce physical card API](/central-issuance/integrate-d1-api/d1-api-reference/inbound-api-to-d1/order-card-api.md#post-issuers-issuerid-physicalcards-cardid-operations-production) to group cards under the same identifier in a single card carrier.

### Tokenization

#### New Features

* Add [Digital card binding approval](https://thales-dis-dbp.stoplight.io/docs/d1-caas/eda9525a16bf5-bind) to approve device-to-token binding for CTF yellow flows.
* Add [Digital card unbind](https://thales-dis-dbp.stoplight.io/docs/d1-caas/0337fa075b128-unbind) to remove a device previously bound to an e-commerce token.
* Add Visa wallet reason codes for Google Pay and Samsung Pay to the [Get digitize card operation API](https://thales-dis-dbp.stoplight.io/docs/d1-caas/300a477b6ed85-get-operation).


---

# 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/release-notes/backend/august-2025/aug-4.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.