POS-n-go - Android POS Manual

POS-n-go Android POS Manual

The information on this page provides general guidance when using a wired Nuvei payment terminal connected to a POS-n-go router. Your implementation may be different. POS-n-go Solutions Inc. does not accept any responsibility or liability for the accuracy, content, completeness, legality, or reliability of the information contained on this website. No warranties, promises and/or representations of any kind, expressed or implied, are given as to the nature, standard, accuracy or otherwise of the information provided in this website nor to the suitability or otherwise of the information to your particular circumstances.

For additional information contact support@pcitoolkit.com or 855-251-0151.

Visit https://nuvei.pcitoolkit.com/version3
Login using either the temporary credentials mailed to you or your updated permanent credentials.
Select Start.

Confirm your business contact information.
Select your type of business (example Retailer) and Card-Present for transaction processing.
Select the Stand Alone Terminal.
Select No for specialized terminal.
Select Network Cable, Ingenico, and your terminal model ICT250.
Select No to storing credit card data electronically.
Select No to processing on behalf of other merchants.
Select No to payment applications.
Select No to sharing card holder data.
Select Yes to network segmentation if your payment terminal is connected to a POS-n-go router which enhances security.

Select No to a written policy for credit card information. One will be provided.
Select No to a written policy for administrative accounts. One will be provided.
Select Yes to a separate password for each person.
Select No to remote access.
Select No to printed mterial with credit card data.
Select No to an awareness training program. One will be provided.
Select Yes to vendor supplied passwords changed.
Select No to web based administrative access.
Select Yes to prohibit storage of full contents of track data.
Select Yes to prohibit storage of card security code.
Select Yes to prohibit storage of PIN.
Select Yes to terminal software up to date.
Select Yes to restrict credit card numbers printed.
Select Yes to strong cryptography.
Select Yes to restrict access to minimum people.
Select No to a written policy for employee logging of access. One will be provided.
Select No to a written policy for managing policies. One will be provided.
Select Yes to a policies reviewed every year.
Select No to a written policy for incidents. One will be provided.
Select No to a written policy for hardware and software. One will be provided.
Select No to a written policy for acceptable use of devices. One will be provided.
Select No to a written policy for firewalls. One will be provided.
Select Yes to a network diagram.
Select Yes to a firewall required and implemented.
Select Yes to the firewall configuration denying traffic.
Select Yes to the IP traffic limited within DMZ.
Select Yes to the firewall dynamic packet filtering.
Select Yes to the firewall restricted traffic.
Select Yes to the removal of unnecessary functionality.
Select Yes to insecure services identified.
Select Yes to systems and components on the internal network.
Select No to a scan performed yet, no passing documentation in possession.
Select Yes to all systems up to date.
Select Yes to a process to identify security vulnerabilities.
Select Yes to a wireless network.
Select No to a written policy for wireless access. One will be provided.
Select Yes to a wireless network implementation requirements.
Select Yes to a perimeter firewall.
Select Yes to WPA encryption.
Select Yes to an inventory of wireless access points.
Select No to a written policy for physical security. One will be provided.
Select Yes to public network jack access restricted.
Select Yes to a list of terminal devices.
Select Yes to inpection of terminal devices.
Select No to devices that connect with SSL.
Select Yes to contractually require third parties.
Select Yes to a list of PCI DSS requirements.
Select Yes to reading the PCI DSS specification.
Select Yes to isolating equipment.
Select Yes to PCI DSS scope.
Select Yes to penetration covers all conduits.
Select Yes to penetration vefifies segmentation.
Select No to implementation after Jan 1, 2017.

Download, review and implement all the policies in the tasks list. Mark as completed when done.
Schedule a network scan using the 403Labs tool in the dashboard. Mark as completed when passed.
Sign your name and position to attest to the successful PCI completion in step 5 in the dashboard.
Download and read the PCI DSS specification: PCI_DSS_v3-2.pdf
The 11 policies from the tasks list are also available here: pci_policies.zip