> 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/september-2026/sep-22.md).

# Sep 22

D1 backend release version 5.45.

| Environment    | Date         |
| -------------- | ------------ |
| Pre-Production | Sep 22, 2026 |
| Production     | Sep 29, 2026 |

### Tokenization

#### New Features

* [Get Digital Card Operation API ](/tokenization/integrate-the-d1-api/d1-api-reference.md#browse-the-api-reference)updated in order to support in the response body a 'matchedRule' object with details on the Decision Engine processing result. This field is applicable only in case Issuer has opted for **NextGen DecisionEngine**.
* [**StepUpAuthResult API** ](https://docs.payments.thalescloud.io/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api#post-issuers-issuerid-digitalcards-digitalcardid-operations-stepupauthenticationresult)integrated in VTS In-App ID\&V [Device Binding ](/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only/device-binding-flow.md)flow 


---

# 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/september-2026/sep-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.