PCI compliant with neapay switch

Posted on 11th Nov 2021 6108 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.


Docs Home ISO8583 Simulator Simulator Tutorials ISO8583 Converter Cards Issuer BASE24 Base24-eps Reference Guide ISO8583 Switch HSM Simulator POS Simulator Products Switch

Top Read Articles

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

ISO8583 Response Codes for Transaction processing 73638 views

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

ISO8583 Processing Codes for Transaction Processing 33353 views

ISO8583 Message Types for Transaction Processing 32889 views

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

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

Run the neaPay ISO8583 simulator 21485 views

ISO8583 payments message format, programmers guide 19032 views

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

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

ISO8583 Message Converter JSON and XML interface specification mapping 14657 views

Cards and Banks Training 14307 views

Java version for neapay products Simulator Converter Switch Authorization Cards Issuer 12083 views

Support for the neaPay products: Authorization, Switch, Converter, Simulator, Issuer 10552 views

Log Files in BASE24 classic 10408 views

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

BASE24 classic vs BASE24-eps 9312 views

BASE24 documentation to read 9112 views

BASE24 classic interview questions 8946 views

Deploy the neaPay ISO8583 simulator - video guide 8769 views

EMV explained for programmers 8671 views

ISO8583 Simulator neapay- Performance testing at 500, 1000 and 1500 Transactions per second 8431 views

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

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

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

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

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

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

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

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

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

BASE24 classic screens examples explained 7363 views

BASE24-eps interview questions 7284 views

Enabling traces in the payments simulator 7253 views

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

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

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

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

Altering test cases in Excel for the ISO8583 simulator 7229 views

Deploy the neaPay HSM simulator in a test environment 7218 views

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

Deploy the Payments Switch Router in a test environment 6844 views

Trace configuration in neaPay Simulator, Converter, Switch, Authorization and Cards Issuer 6725 views

BASE24 classic cards configuration tutorial with Examples 6626 views

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

Add extra custom fields to the ISO8583 simulator 6533 views

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

PCI compliant with neapay switch 6109 views

BASE24-EPS ACI DESKTOP tutorial - Getting started 5957 views

BASE24 classic prefix configuration tutorial CPF with examples 4348 views

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

POS simulator format SPDH HPDH Verifone and custom 4037 views

BASE24 classic Institution configuration Tutorial with example 3865 views

ACI BASE24 classic automatic extract configuration 3836 views

BASE24 classic balance file configuration PBF with example 3742 views

First steps with BASE24 Classic 3556 views

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

ISO8583 Load Balancer with neapay Switch Router 725 views

ISO8583 Card Transaction BIN Prefix Router with neapay Switch 724 views

ISO8583 simulator scheduling tasks and test regressions 704 views

Swift Message Structure ISO 15022 and ISO 20022 703 views

ISO8583 simulator Visa MasterCard Amex CUP configuration demo video 659 views

SWIFT Message types complete list reference 578 views

SWIFT Common Message Type List with examples 421 views

POS Transaction types explained 381 views

Recent Articles on Iso8583

Choose the product you need

ISO8583 Converter

Convert ISO8583 to JSON XML SQL

ISO8583 Interface

ISO8583 Interface Handler

ISO20022 Converter

Convert ISO20022 to ISO8583 ...

ISO8583 Builder

Build ISO8583 from scratch

ISO8583 Switch

ISO8583 Router by criteria

ISO8583 Authorization

Authorize cards and ledger

Payments Acquirer

Acquiring host from devices

Cards Issuing

Generate and issue cards

ISO8583 Simulator

ISO8583 HISO98 HISO87 simulator

ISO20022 Simulator

ISO20022 & SWIFT simulator

POS Simulator

POS protocols simulator

Web Api Simulator

Web API tester Performance


Get a free quote, Ask for details
Get help

Contact us

Try the software yourself

Download software

Read Documentation and Start guides


Online Tools Overview

Online Tools