Skip to content

Bank or Payment Service Provider Requests PCI DSS Compliance: What Documents Should Businesses in Kazakhstan Prepare

  • by
Bank or Payment Service Provider Requests PCI DSS Compliance: What Documents Should Businesses in Kazakhstan Prepare

The integration is almost complete, but the bank requests "PCI DSS documentation", bringing the onboarding process to a halt. What should you provide: a questionnaire, an attestation of compliance or an auditor's report? If a bank requires PCI DSS compliance, the first step is to clarify the required form of validation and the assessment scope. Otherwise, the company risks preparing documentation that the partner will not accept.

PCI DSS in Kazakhstan: Where to Start

PCI DSS establishes requirements for protecting payment card data. Businesses in Kazakhstan, Uzbekistan, Georgia and Kyrgyzstan are subject to the same international standard, although the compliance validation process is determined by payment card scheme programmes and the requirements of the acquiring bank or other requesting party.

Start by obtaining a written request from the bank or payment service provider. Simply stating that a "certificate is required" is not sufficient. Ask them to specify the exact documents needed, the applicable version of the standard, the submission deadline and the legal entity for which compliance validation is required.

SAQ, AOC and ROC: What Is the Difference

SAQ, AOC and ROC: What Is the DifferenceSAQ (Self-Assessment Questionnaire) is a self-assessment tool. The company assesses its compliance with the applicable requirements and documents the results. Different SAQ types are available for different payment acceptance methods. Businesses cannot simply choose the shortest questionnaire: they must meet all the eligibility criteria for the selected SAQ type.

AOC (Attestation of Compliance) confirms the results of a compliance assessment. The document specifies the organisation, assessment scope and overall compliance status. An AOC is completed based on the results of an SAQ or ROC. Therefore, obtaining an AOC for PCI DSS in Kazakhstan does not mean that a company can receive a standalone certificate without undergoing a compliance assessment.

ROC (Report on Compliance) is a detailed assessment report. It describes the environment assessed, the procedures performed and the results obtained. Where a Qualified Security Assessor (QSA) is involved, the report is prepared by the qualified assessor. The ROC is accompanied by the corresponding AOC.

In summary, SAQ and ROC document the compliance assessment, while AOC attests to its results. These documents are interconnected but are not interchangeable.

SAQ or ROC: What Determines the Choice

The appropriate approach depends on the company's role — merchant or service provider — transaction volume, payment card scheme rules and the bank's requirements. The integration architecture determines the assessment scope and eligibility for a particular SAQ type.

For example, redirecting customers to a payment provider's hosted payment page and transmitting cardholder data through the merchant's server create different scopes of responsibility. Outsourcing payment processing to a third-party provider may reduce the number of applicable requirements, but it does not remove all compliance obligations from the business.

Engaging a QSA does not automatically mean that an ROC is required: a qualified assessor can also assist with self-assessment. The reporting format should be agreed with the requesting party, while the assessor verifies that the assessment scope and applicability of requirements have been correctly determined.

Which PCI DSS Documents Should You Prepare in Advance

For the initial discussion, it is more useful to prepare a description of the actual payment integration than to complete an arbitrary template. Gather the following information into a single package:

  • The bank's or payment service provider's request, deadlines and contact details of the responsible person;
  • Company details and a list of websites, applications and payment channels;
  • A cardholder data flow diagram showing where card details are entered, where they are transmitted and whether they are stored;
  • Information about service providers, their current AOCs and the allocation of responsibilities;
  • Previous SAQs, AOCs and ROCs, if an assessment has already been conducted;
  • Existing security policies and available vulnerability scanning and testing results.

This provides a starting point for determining the scope of work. Security policies, ASV scan reports and other supporting evidence will be required depending on the applicable requirements. However, it is not necessarily required to submit the entire internal documentation package to the bank.

PCI DSS for Online Payment Acquiring: The Freedom Pay Example

When searching for "Freedom Pay PCI DSS", it is important to consider the integration method. Freedom Pay's Gateway API documentation explicitly states that PCI DSS compliance validation is required when merchants collect cardholder data within their own systems and transmit it via the API.

However, this does not automatically determine which form of compliance reporting will be accepted for a particular company. Check with your account manager to clarify the requirements for your chosen integration method. The payment service provider's own PCI DSS compliance does not demonstrate that the merchant's systems are compliant.

What to Agree Before Starting the Process

Ask your partner to confirm in writing whether self-assessment is permitted, which SAQ type is appropriate, whether a QSA is required, whether an AOC alone is sufficient or an additional report is needed, and which supporting documents and signatures are mandatory. Agree separately on the submission deadline and a secure channel for transferring the documents.

You can contact System Management for a consultation to review the requirements, determine the assessment scope and agree on a preparation plan. The practical outcome of this review should be a clear list of required documents, assigned responsibilities and a sequence of actions to move the integration process forward.

EN