Blog Home

PCI compliant with neapay switch

Posted on 11th Nov 2021 189 views

PCI compliant with neapay switch

What are the requirements for becoming PCI compliant?

In order to become PCI DSS compliant, there are 12 requirements a business must adhere to. Each requirement falls into a ‘goal’ or category that, according to the PCI SSC, “help merchants and other organizations incrementally protect against the highest risk factors and escalating threats while on the road to PCI DSS compliance.”

The PCI validation requirements and goals are: 

  1. Build and maintain a secure network
    Install and maintain a firewall configuration to protect data
    Do not use vendor-supplied defaults for system passwords and other security parameters

  2. Protect cardholder data
    Protect stored cardholder data
    Encrypt transmission of cardholder data across open, public networks

  3. Create a vulnerability management program
    Use and regularly update anti-virus software or programs
    Develop and maintain secure systems and applications

  4. Implement strong access control measures
    Restrict access to cardholder data by business need-to-know
    Assign a unique ID to each person with computer access
    Restrict physical access to cardholder data

  5. Monitor and test networks regularly
    Track and monitor all access to network resources and cardholder data
    Regularly test security systems and processes

  6. Develop an information security policy
    Maintain a policy that addresses information security for employees and contractors

These categories are intended “to provide the following benefits” for businesses:

  • Roadmap to assess, address, and report on prioritised risks

  • Objective and measurable indicators of progress

  • Consistency among assessors

How do I get PCI DSS Certified?

Here are the below steps you should take once you are ready to become PCI DSS certified: 

  • Identify your compliance ‘level’ 

  • Complete a self-assessment questionnaire (SAQ) or Complete an annual Report on Compliance (ROC) 

  • Complete a formal attestation of compliance (AOC)

  • Complete a quarterly network scan by an Approved Scanning Vendor (ASV)

  • Submit the document

Please note: When dealing with PCI DSS requirements, you can either go through the process yourself or get help from a PCI SSC Qualified Security Assessor (QSA) 

  •  Identify your compliance ‘level’ 

Identify where your business sits within the compliance levels. There are varying levels depending on the size of a business, based on how they handle transactions and data, what credit cards they work with and how many transactions they process. 

Level 1 
A business that processes over six million transactions annually.

Level 2 
A business that processes one to six million transactions annually. 

Level 3  
A business which processes 20,000 to one million transactions online over 12 months. 

Level 4
A business that processes less than 20,000 transactions online annually and processes up to one million transactions annually.

For Level 2-4 merchants:

  • Complete a self-assessment questionnaire (SAQ) 

The self-assessment questionnaire (SAQ) is a guidebook you can use to assess your current compliance level. It takes you through the requirements (as listed above) to help you identify your company’s payment security and if you should make changes to your business.

For Level 1 merchants:

  • Complete an annual Report on Compliance (ROC) - an external audit performed by a Qualified Security Assessor (QSA)

As part of the audit the assessor will:

  • Validate the scope of the assessment;

  • Review documentation and technical information;

  • Determine whether the PCI DSS’s requirements are being met;

  • Evaluate compensating controls.

The RoC (Report on Compliance) will then be submitted to the organisation’s acquiring banks to demonstrate compliance.

  • Complete a formal attestation of compliance (AOC)

Once you’ve made any changes necessary and have updated your SAQ, you can fill out a formal attestation of compliance (AOC) in which a qualified security assessor reviews your work and officially validates if your business is fully compliant with all relevant PCI standards. 

  • Complete a quarterly network scan by an Approved Scanning Vendor (ASV)

An Approved Scanning Vendor (ASV) is an organisation that is qualified by the PCI SSC, to complete external vulnerability scanning services using specialist security tools find any weaknesses or holes in your systems that hackers may attempt to exploit. These must be completed every 90 days. For further information click here

  •  Submit the documents 

Finally, you must submit your documents such as your SAQ, AOC and ASV scan report to your acquirer bank and to the relevant credit card/payment brands as requested.

PCI compliance is a vital part of your business and should not be overlooked. By being PCI DSS compliant, you will protect not only your brand but your customers. 

As a reminder, to become PCI compliant you should:

  • Identify your compliance ‘level’ 

  • Complete a self-assessment questionnaire (SAQ) or Complete an annual Report on Compliance (ROC) 

  • Complete a formal attestation of compliance (AOC)

  • Complete a quarterly network scan by an Approved Scanning Vendor (ASV)

  • Submit the documents 

Although this checklist might look daunting at first it is actually fairly straightforward. However, it might be best to seek assistance from your payment service provider should you need it. 

Remember, if you fail to become PCI compliant you could incur steep fines, a loss of credibility and customers and lose the ability to accept future credit card payments. For further information about failing to comply, see our Failure to Comply with PCI article.


Top Read Articles

Read smart card chip data with APDU commands ISO 7816 27292 views

BIN List & Range for MasterCard, Visa, Amex, Diners, Discover, JCB, CUP 20322 views

Deploy, run and generate with neaPay Card Data Generator 11467 views

Run the neaPay ISO8583 simulator 10618 views

ISO8583 payments message format, programmers guide 9986 views

ISO8583 Response Codes for Transaction processing 8863 views

MCC Codes - Merchant Category Codes to use in ISO8583 Field 18 7470 views

ISO8583 message: The list of ISO 4217 currency codes for data elements 49 and 52 7462 views

ISO8583 Message Converter JSON and XML interface specification mapping 7104 views

ISO8583 Message Types for Transaction Processing 6048 views

ISO8583 Processing Codes for Transaction Processing 5949 views

Deploy the neaPay ISO8583 simulator - video guide 5264 views

Create a new test case in the neaPay ISO8583 simulator Video guide 4720 views

Log Files in BASE24 classic 4360 views

BASE24 classic interview questions 3856 views

BASE24 documentation to read 3777 views

Performance testing at 500, 1000 and 1500 TPS 3763 views

BASE24 classic vs BASE24-eps 3689 views

Connect the neaPay ISO8583 Acquirer simulator to your own host or Issuer 3515 views

Asking for defects support for the neaPay products: converter, switch, issuer, simulator 3341 views

ISO8583 converter to JSON XML SQL to HTTP host - message flow - video guide - Part.2 3193 views

Regression Testing in 1 click with instant Analytics and CSV report 3099 views

Load Test enabling and performance testing at 1TPS and 100TPS 3078 views

BASE24 classic screens examples explained 3073 views

Run the neaPay ISO8583 converter to JSON, XML, SQL, in a test environment 2902 views

Card readers supported by neaPay payments simulator, CHIP and NFC 2894 views

ISO8583 converter to JSON XML SQL to HTTP host - start& run - video guide - Part.1 2893 views

Sample Recommended design for an Acquirer test cases suite, Scenarios and Regression 2869 views

ISO8583 converter to JSON XML SQL to HTTP Host - host unavailable - video guide- Part.3 2862 views

Adding your own card to the Payments simulator to test your system 2778 views

Enabling traces in the payments simulator 2775 views

EMV explained for programmers 2775 views

Altering test cases in Excel for the ISO8583 simulator 2773 views

How the fingerprint reader works in the ISO8583 payments simulator 2772 views

Run One, Run Scenario, Run All, Run Load in the neaPay ISO8583 Simulator - Use guide 2771 views

Deploy the neaPay ISO8583 Payments converter in a test environment 2771 views

Changing fields definitions in the ISO8583 simulator and message converter 2770 views

BASE24-eps interview questions 2689 views

BASE24 classic ATM configuration Tutorial in ATD and XPNET with examples 2596 views

Deploy the neaPay HSM simulator in a test environment 2480 views

Cards and Banks Training 2434 views

Deploy the Payments Switch Router in a test environment 2377 views

BASE24 classic cards configuration tutorial with Examples 2245 views

Add extra custom fields to the ISO8583 simulator 2162 views

ISO8583 ATM POS Crypto API integration with exchanges like Coinbase or Binance 2133 views

BASE24-EPS ACI DESKTOP tutorial - Getting started 1964 views

Getting started with BASE24. Compiling your first TAL program 1907 views

BASE24 classic prefix configuration tutorial CPF with examples 1824 views

BASE24 classic tracing of transactions. Audits, configuration, enabling and opening 1715 views

BASE24 classic Institution configuration Tutorial with example 1607 views

BASE24 classic interchange configuration with examples 1590 views

Working with Base24-eps vs BASE24 Classic 1562 views

BASE24 classic balance file configuration PBF with example 1551 views

ACI BASE24 classic automatic extract configuration 1543 views

BASE24 classic routing in IDF 1347 views

Base24-eps how to create journals with esbldjnl 1322 views

Getting started with Base24 development. TAL tutorial 1299 views

BASE24 classic External Message File configuration EMF with examples 1209 views

Getting started with using Prognosis for BASE24 and BASE24-eps 1135 views

First steps with BASE24 Classic 1113 views

What to expect when installing Base24-eps 1048 views

BASE24 classic host configuration tutorial HCF with examples 1047 views

Managing BASE24-eps implementation projects 980 views

PCI compliant with neapay switch 190 views

ISO8583 Message Converter to XML SQL CSV interface specification mapping 25 views

Ask a question, get advice and help


Read related articles - Iso8583

Are you ready to start or need help?

Ready to start your next project with us? Give us a call or send us an email and we will get back to you as soon as possible!

Get a free quote, Ask for details, Get guidance

Contact us

Download and Use the software yourself

Download software

Follow a getting started guide to deploy and use the software

Get started