> For the complete documentation index, see [llms.txt](https://stablemesh.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stablemesh.gitbook.io/docs/home/stablemesh-doc/zhong-wen-wen-dang/cards/sensitive-info.md).

# 查看敏感信息

出于安全考虑，完整卡号、有效期和 CVV 默认处于隐藏状态。需要消费时可随时查看。

***

## 查看卡片详情的步骤

1. 进入**卡片**页面，点击您要查看的卡片。
2. 在详情面板中，点击**眼睛图标**（查看详情）。
3. 面板将显示：
   * **完整卡号**
   * **有效期**
   * **CVV**
4. 如需重新隐藏，再次点击眼睛图标（隐藏详情）。

***

## 在线消费

获取卡片详情后，您可以：

* 在任意在线结账页面输入卡片信息
* 将卡片添加到 **Apple Pay** 或 **Google Pay**
* 在任何支持 Mastercard 的服务中使用

***

{% hint style="danger" %}
**请妥善保管您的 CVV。** 切勿向任何人泄露完整卡号、有效期或 CVV。Stable Mesh 客服人员绝不会索取这些信息。
{% endhint %}


---

# 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://stablemesh.gitbook.io/docs/home/stablemesh-doc/zhong-wen-wen-dang/cards/sensitive-info.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.