> 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/classic-tokenization/ja/ysuksu/deng-lu-hou/kdoraifusaikuru/kdometadtawosuru.md).

# カードメタデータを更新する

トークナイゼーションサービスは次のものを提供します [UpdateCard API](/classic-tokenization/ja/apirifarensu/ishuagtoweiapi/inbaundoishuakara.md) カードプロファイルのメタデータを更新または上書きするため。

イシュアのバックエンドは、カードがxPayウォレットにどのように表示されるかを更新する必要がある場合に通常このAPIを使用します。

### カードメタデータは何のために使われるか

カードメタデータはxPayウォレットで使用される情報です。例えば：

* カードの詳細を表示する（例：カードプログラム名）。
* 取引通知および履歴のエンドポイントを構成する。
* イシュアのアプリケーションの連絡先情報やリンクを表示する。

メタデータフィールドを次の中で送信します `metadata` リクエストボディのオブジェクト。

リクエストボディの例：

```json
{
  "issuerCardRefId": "string",
  "metadata": {
    "foregroundColor": "rgb(223355)",
    "backgroundColor": "rgb(223355)",
    "labelColor": "rgb(223355)",
    "shortDescription": "ACME Gold Card",
    "longDescription": "ACME Bank Gold card",
    "contactWebsite": "https://acme.com/contacts",
    "contactEmail": "contacts@acme.com",
    "contactNumber": "+33645878741",
    "privacyPolicyURL": "https://acme.com/contacts"
  }
}
```

<figure><img src="https://26142420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OvNtPk6hurTTvkKLzkK%2Fuploads%2FHuL8uzaT3zS7vGvBKgSZ%2Fcard-metadata.png?alt=media&amp;token=45d3a9f1-1ec1-4291-9039-63d43571c439" alt=""><figcaption><p>カードメタデータフィールドを含むUpdateCardリクエストの例。</p></figcaption></figure>


---

# 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/classic-tokenization/ja/ysuksu/deng-lu-hou/kdoraifusaikuru/kdometadtawosuru.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.
