> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/self-hosting/guides-for-self-hosting/going-live/for-on-prem-setup/pci-compliance.md).

# PCI compliance

It's no rocket science

{% hint style="info" %}
The complexity around PCI compliance is often exaggerated, creating closed systems and walled gardens. This section aims to simplify the process of obtaining PCI compliance and includes a project tracker, documentation templates & automation scripts
{% endhint %}

***

### PCI Compliance - Why and What?

The current payment networks are built on a chain of trust between banks, card networks, payment processors and merchants. And the result is that *"everyone needs to take responsibility"* for secure handling of card information.

> PCI compliance is not determined not enforced by any Government body. It is a set of standards created by the Payment Card Industry Security Standards Council.

Payment Card Industry Security Standards Council (PCI-SSC), was an independent body created by the card networks in 2006. The independent body publishes and manages PCI security standards. However, the enforcement of these standards falls to the card networks and payment processors.

We have open sourced our PCI certified card vault application code along with the deployment scripts which you can self-host. By the time you complete this guide, you will be running a PCI complaint card vault on your server and also be ready to get PCI certification.

{% embed url="<https://docs.google.com/presentation/d/1inTRp-yvIUjiIuo1f-FBFd1zbUq5IxIbUMzEYpAAUNI/edit?usp=sharing>" fullWidth="false" %}

Understand PCI compliance requirements with respect to your application and complete the Self Assessment Questionnaire to obtain PCI compliance:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Understanding PCI compliance requirements</strong></td><td>Understand PCI compliance requirements with respect to your application and transaction volumes</td><td></td><td><a href="/self-hosting/guides-for-self-hosting/going-live/for-on-prem-setup/pci-compliance/its-no-rocket-science.md">Get started</a></td><td></td></tr><tr><td><strong>Completing the SAQ</strong></td><td>A simplified recipe to fast track obtaining PCI compliance. This includes a project tracker, documentation templates and automation scripts</td><td></td><td></td><td></td></tr></tbody></table>


---

# 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.hyperswitch.io/self-hosting/guides-for-self-hosting/going-live/for-on-prem-setup/pci-compliance.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.