> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/vault/developer-tools/vgs-show/overview.md).

# Overview

VGS Show is the way to display sensitive data to an “end-user” without needing to pass through your systems. While securely showing the data, you can fully control the look and feel of the UI. VGS Show also offloads the PCI compliance burden (for specific use cases) by enabling the encrypted transmission of sensitive card data from Very Good Security directly to your cardholder or a PCI-compliant processor.

VGS Show is intended to display sensitive data back to end users, and not to your internal team. Revealing data to your internal teams puts you into PCI scope.

<figure><img src="https://www.verygoodsecurity.com/docs/vgs_theme/static/img/vgs-show-diagram.png" alt=""><figcaption></figcaption></figure>

### Advantages <a href="#advantages" id="advantages"></a>

* PCI Compliant
* Fully customizable styles
* Value formatting and masking
* Image reveal (mobile coming soon)
* Copy to clipboard button
* Flexible data structure
* Fast integration<br>

Also, check out [VGS Collect](/vault/developer-tools/vgs-collect.md) for securely collecting sensitive data.

<br>


---

# 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.verygoodsecurity.com/vault/developer-tools/vgs-show/overview.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.