> 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/ja/bakkuendo/readme/jun-1.md).

# 6月1日

| 環境     | 日付         |
| ------ | ---------- |
| プレ本番環境 | 2026年5月25日 |
| 本番環境   | 2026年6月1日  |

### Click to Pay

#### 改善点

* 追加 `SCHEME_CARD_INELIGIBLE` トークナイゼーションが失敗したか、カードが対象外であることを示すエラーコード。
* 追加 `SCHEME_AMBIGUOUS_PROFILE` メールアドレスや電話番号などの消費者プロフィールデータの不一致を示すエラーコード。

### コア

#### 改善点

* 追加 `threeDSsupport` への [カード詳細取得API](https://docs.payments.thalescloud.io/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api#get-v2-issuers-issuerid-cards-cardid) および [カード一覧取得API](https://docs.payments.thalescloud.io/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/consumer-api#get-issuers-issuerid-consumers-consumerid-cards) のレスポンスに、カードがEMV 3-D Secure（3DS）フローをサポートしているかどうかを示します。

### トークナイゼーション

* 新規 **ステップアップ認証結果** イシュアアプリケーションに公開され、デバイスバインディング要求を承認/拒否するためのD1 Banking APIエンドポイント。現時点ではMDESのみ対応しており、まもなくVTSにも拡張される予定です
* 非推奨フィールド「**reasonCodesRecommendation**」は
  * [カード取得操作（DIGITIZE）](https://docs.payments.thalescloud.io/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api#get-issuers-issuerid-cards-cardid-operations-operationid)
  * [カード操作通知 V2（DIGITIZE）](https://app.gitbook.com/o/fwy1mtbRONGA2YDKDBr0/s/1anzKGkgnN7Yu0UiQZjY/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/card-api#post-notifications-d1-v2-issuers-issuerid-cards)


---

# 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/ja/bakkuendo/readme/jun-1.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.