> 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/completing-the-saq.md).

# Completing the SAQ

Guide to completing the PCI DSS Self-Assessment Questionnaire (SAQ D) for merchant compliance certification

{% hint style="warning" %}
There are multiple [variants of SAQs](https://listings.pcisecuritystandards.org/documents/Understanding_SAQs_PCI_DSS_v3.pdf) applicable for Merchants willing to be PCI compliant. This document explains compliance to SAQ D only.

Examples of merchant environments that would use SAQ D includes but not limited to:

* **E-commerce merchants** who **accept cardholder data** on their website.
* Merchants with **electronic storage of cardholder data.**
* Merchants that don’t store cardholder data electronically but that do not meet the criteria of another SAQ type.
  {% endhint %}

The [Official SAQ D](https://listings.pcisecuritystandards.org/documents/SAQ_D_v3_Merchant.pdf) has approximately 300 questions to be answered. Most of the aspects are general infrastructure controls, access controls and organizational policies. Answering the questions will be a cake walk if you close few activities upfront. We have divided the activities into three categories.

<table><thead><tr><th>Type of Activity</th><th width="348.3333333333333">Description</th></tr></thead><tbody><tr><td>Organizational and People activities</td><td>Establish organizational policies and conduct staff training.</td></tr><tr><td>Infrastructure activities</td><td>Implement security measures in your cloud environment handling card data.</td></tr><tr><td>Access controls</td><td>Restrict infrastructure access to essential personnel.</td></tr></tbody></table>

{% hint style="info" %}
For further assistance, please contact us at <hyperswitch@juspay.in>
{% endhint %}

**Final Steps**

1. **Network Scan**: Select a PCI-approved scanning vendor from the official [list](https://listings.pcisecuritystandards.org/assessors_and_solutions/approved_scanning_vendors) and obtain a network scan report. This process, typically automated by Approved Scanning Vendors (ASVs), should be conducted quarterly and usually completes within a few hours.
2. **Complete SAQ D**: Fill out the SAQ D and retain a copy for your records.

{% hint style="success" %}
You are PCI compliant now!!
{% endhint %}

It's essential to submit your network scan report and Self-Assessment Questionnaire (SAQ) to your payment processor or acquirer.

**Submission methods vary;** some processors provide a dashboard for uploads, while others prefer email communication. Ensure you adhere to your processor's specific requirements and submission schedule, typically on a quarterly basis.


---

# 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/completing-the-saq.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.