Purging History to Update Faster

Posted on by ccsretail

 

Preparing To Update From CPSQL 8.5.3 and lower.

If you are planning to update your NCR Counterpoint System and are running version 8.5.3 or lower and have a lot of sales history, purging some of that history will make the update take less time.

I get asked quite a bit on how long an update will take. For most systems that keep up to date, it can be anywhere from 1 to 2 hours. But, if you have skipped a couple of updates, this can turn into 3 to 4 hours to complete to the whole process.

The reason for this is that during the upgrade, your history files go through a conversion process to add/remove changed fields. Although the main system itself will be useable after the initial update, the history will not be there right away.

Depending on how much history you keep on file will determine how long the rest of the update will take. If you rely on sales history to do validated returns, or to help make decisions about purchasing or running reports, this will unavailable until the conversion process is complete.

So, when you decide to upgrade your system, take a look at how much sales history you have on file and purge (there are utilities that make this easy) whatever is not necessary. As a reference, most companies keep about 3 years’ worth of history, but you should check with your accounting team for how much may be required.

-Bryan

Using Proper Physical Count Procedures

Posted on by ccsretail

Using Proper Physical Count Procedures

It’s always a good idea to make copious notes about physical count configuration and usage issue and to review them prior to doing the actual work.

Typically, this process would include:

  • Making backups of current data. – Typically, this would involve backing-up the full database.
  • Archiving old count files for previous periods or years. – This would ensure that old files are not accidentally imported.
  • Making sure that PDT’s (Physical count device) batteries are fully charged, and that any old count data is cleared from the devices.
  • Training staff who will actually be doing the work to properly use both the software and hardware functions.

Taking this proactive approach is vitally important, especially if you only do inventories once a year or less frequently. Failing to do this can mean a potential disaster waiting to happen…

As an example…

An end-user who had just completed a physical count determined that ALL of the adjusted inventory levels were wrong for all of their locations.

In working with the counter staff, the following was later determined:

  • When importing the count file into the default PDT’s (Physical count device) software directory, the file downloaded was named the same as what it was last year and downloaded to PDT software’s default directory.
  • However, their default NCR Counterpoint parameter was pointing to a different import folder than the PDT software default. When the staff imported the count file, they were actually importing the previous year’s physical count file. – No one had checked the date of the file or the content before importing it.
  • After importing the count file, the user did a blind post the count data without checking any of the data, and just let the system to adjust all items not counted to zero.

To compound matters…

  • No backup of the existing CounterPoint data files was done prior to the start of the import process. – This means that they had no recourse but to restart the physical count process.
  • The count file had obvious errors in it (Barcodes scanned into the quantity field; Quantities input into the barcode field; Blank Quantities; etc.). – The NCR Counterpoint software has both a verify function that can be used prior to importing data and various worksheets that can be used for reviewing and validating data.
  • Other users had started multiple physical count snap-shots that involved many of the same items. Some of these has been open for as long as a year.
  • On detecting the initial problem, the staff repeated the exact same import/post process (using the wrong file) at least twice, before finally creating a new physical count, and without doing any imports, then zeroed-out

the entire inventory for that location.

The one saving grace here was the current year’s count file uploaded not been deleted, nor had the PDT been purged after the upload.

If you are unsure of any part of the physical count process, CCS Retail Systems can provide both training and technical assistance prior to starting the count, as well as ongoing process support during the actual count.

– John

Monitoring your NCR Secure Pay activity.

Posted on by ccsretail

Monitoring your NCR Secure Pay activity.

By, default, when one signs-up for the NCR Secure Pay Service, the notification email address that you provided will be used to automatically notify you of the success or failure of your regularly scheduled overnight credit card settlements.  You can also access the NCR Secure Pay Portal in order to check on the real-time open activity as well as the settlement history 24/7/365 from any location that allows you access to the Internet access.

Site access will require the link information, the NCR Secure Pay User ID and the required password to access the site. This Portal location information was provided in your original NCR Secure Pay sign-up email, however, if you no longer have this access information, please contact CCS.  The site has a built-in access limitation that will temporarily disable your login account if more than (3) three failed back-to-back failed access attempts have been made.

Currently, NCR Secure Pay keeps detailed Settlement History online on their servers for 2 years, after which time the site automatically purges the older data. You can also extract transaction detail to an ASCII CSV file for use in importing into other products such as MS Excel.

In the set-up and configuration area, the site allows you to change both the settlement status email address and time of day that the auto-settlement happens. Additionally, detailed information about your current merchant information and configuration, and options will be displayed.

If you have any question regarding NCR Secure Pay or need assistance with accessing the NCR Secure Pay Portal, please contact the CCS Retail Systems Support Department.

– John

NCR Silver Essentials Cloud-based POS Solution

Posted on by ccsretail

Supercharge Your Business with a Total NCR Silver Essentials Bundle Solution 

This bundle combines all the software and hardware you need – in a monthly fee, with no money down* – and will save you up to 20 percent. 

What Features are Available with NCR Silver?

NCR Silver is a complete POS system that can improve customer retention, manage your business, and help you grow

Inventory management

Know which items are selling, and which ones aren’t, to make informed decisions.

Employee management

Assign roles and track employee time with clock-in/clock-out functionality.

Consolidated reporting

Track sales and cash — for all locations — from anywhere, thanks to the cloud.

You’ve Got People

24/7 support + Silver Concierge = an entire team at your disposal

NCR Silver chat on an iPhone.
  • Unlike other POS providers, you’ll get LIVE support — every day of the week, any hour of the day.
  • Save time by letting your Silver Concierge team maintain your menus every month.
  • Experience peace of mind knowing that select hardware is supported if something goes wrong.
  • Get your back office up quicker by letting a Silver Concierge agent set it up for you.
  • Attend ongoing training sessions on new features.
  • Reach an agent by phone, email, chat or text.

NCR Silver EMV: A Chip off the New Block

EMV chip technology from NCR Silver is a cut above

When you opt for NCR Silver EMV, you can choose just about any card processor you want. In addition, NCR Silver chip readers and EMV stands are built to withstand the rigors of your restaurant, mobile environment or shop.  If that isn’t enough, you’ll also have more than 130 years of NCR financial technology know-how in your corner.

Learn More

EMV chip card reader with stand.

Have More Questions About NCR Silver?

Choosing the right POS system can be a challenge. We hope the decision is made easier with these FAQs

  • What devices does NCR Silver work with?

    NCR Silver apps work on Apple iOS 8.0 mobile devices, Apple iOS 9.0 mobile devices and the NCR Silver Quantum.

  • What’s included in my NCR Silver subscription?

    Your app, 24/7 LIVE customer support, the award-winning Silver Concierge service, regular software updates, integrated loyalty, email marketing, inventory management and more.

  • What third-party software works with NCR Silver?

    We’re constantly working with the best software providers — from accounting to mobile payments — to offer your small business or franchise an all-in-one experience. To name just a few: Xero, PassMarket, Paychex, LevelUp.

  • What is Silver Console?

    Silver Console, formerly known as CimpleBox, is an NCR-owned add-on service that offers advanced reporting and management features in one time-saving dashboard. It is fully integrated with NCR Silver.

  Silver Special Promotion For 2018.  Act NOW! 

 

CCS Retail Systems
Your Bridge With Technology  

Contact CCS Retail Sales …

 

Quick Chip

Posted on by ccsretail

Quick Chip.

NCR Counterpoint now supports “Quick Chip”!

What is Quick Chip?

Quick Chip for EMV allows customers to insert (dip) and remove their EMV chip card at checkout in about 2 seconds. They can even do so before the transaction is complete. This is similar to the “Swipe Any Time” feature in NCR Counterpoint.

Quick Chip is also meant to help the payment industry’s transition to EMV chip.

In order to use Quick Chip with NCR Counterpoint, you will need to be running version 8.5.4.1, have an Ingenico ISC250 payment terminal with the required firmware version, and an account setup and configured with NCR Secure Pay.

So if you are already processing EMV chip cards through your NCR Counterpoint software, all that should need to be done is update your software to 8.5.4.1 and update your payment terminal to the required firmware.

With the update to 8.5.4.1, you will also be able to accept Pin Debit transactions using the EMV technology as well. There are some processor specific restrictions for Pin Debit, so be sure to ask CCS about your current configuration.

As always, if you have any questions or concerns, please contact the CCS Retail Systems Support Department at 800.672.4806 or email us at support.

-Bryan

Testing Updates and Changes

Posted on by ccsretail

Testing updates and Changes.

With the recent changes in requirements for credit card processors, NCR Retail Online going away, and others, there are a large number of people going through updates and changes. Many of these changes are quite significant. With that in mind, a word about testing those changes is in order.

The most common thing that I see is a lack of sufficient testing. For example, if you are changing your web store provider, there will be changes in how orders flow in and out of your ticketing system. It is not enough to test that orders come into your system. You also need to check that you can process those orders. It does not do any good to receive orders, and then not be able to process and complete them. The testing process needs to incorporate all aspects of the workflow.

  • Does the order come in with the correct information?
  • How about taxes?
  • Are the tax amounts correct when appropriate?
  • How about when taxes do not apply so that there is a zero
  • tax amount?

Those are all important, but that is just the beginning.

If that information is importing correctly, what about going forward.

You should test printing picking tickets, generating invoices, and everything all the way through posting those invoices. When that all goes through without a hitch, there is still more to do. Test canceling orders, and partial shipments. If you ever edit orders to add or remove lines, change a line quantity, or anything else, then those functions need to be tested also.

It takes some time and needs to be included in your schedule for everything else, but the more time spent testing changes and updates ahead of time, the smoother it will be when it comes time to implement those changes in your live system.

Dave

Signature Capture Devices

Posted on by ccsretail

 

 

Signature Capture Devices.

Would you like to have your customers signature show up on Invoices and Order printouts?

There are a couple devices that can be used to do this.

One is the Ingenico ISC250 Pin Pad, it combines a signature capture device, along with a Pin Pad and MSR for processing credit/debit card payments. It will capture the customers signature, which can then be used to print on receipts, invoice and order forms and also be looked up in ticket history without printing.

There is also the Topaz signature capture device. It will only capture the customer signature that can then be printed on receipts, invoices, and order forms.

The signature will not automatically print on the forms with these devices and will need to be added to the form of your choice.

The Topaz is a useful device if you are processing payments outside of Counterpoint (i.e. Standalone Credit Card Terminal), or would still like to capture signatures for A/R charge type sales/returns or any transaction that you set as requiring a signature.

There is a little setup required, and there are specific device models that can be used, so if you are interested, please contact the CCS Retail Systems Support or Sales Department at 800.672.4806 for help determining the right model for your system.

-Bryan

Getting Ready For Transport Security Layer (TLS) 1.2

Posted on by ccsretail

GETTING READY FOR TLS 1.2

Payment Card Industry Data Security Standards (PCI DSS) require all PA-DSS validated payment applications to discontinue the use of “early TLS” (i.e., all versions of SSL and TLS 1.0) by June 30th, 2018.

To comply with this requirement, NCR Secure Pay will no longer accept early TLS connections after 2:30 A.M. on June 5th, 2018. In addition, updates to NCR Counterpoint V8.5.4 and V8.4.6 that will require the use of TLS 1.2 for payment transactions processed through NCR Secure Pay will be released as follows:

  • V8.5.4 Patch 002: Scheduled for 2/20/2018
  • V8.4.6.19 Service Pack: Scheduled for 3/6/2018

We do not plan to release patches or Service Packs to support TLS 1.2 in other versions of NCR Counterpoint. To prepare for the transition to TLS 1.2, you must first ensure that TLS 1.2 is supported and enabled on your

workstations by following the appropriate steps for your operating system, as outlined below.

 Do NOT disable early TLS on your workstations, as NCR Counterpoint Services (CPServices) requires TLS 1.0 for internal communications. Because PCI DSS prohibits the use of early TLS for the external communication of payment transactions only, using TLS 1.0 with CPService does not violate PCI-DSS compliance.

CPServices will be updated to use TLS 1.2 in a future NCR Counterpoint release.

Once TLS 1.2 is enabled, you can install V8.5.4 Patch 002 or the V8.4.6.19 Service Pack—depending on which version of NCR Counterpoint you are using—to begin using TLS 1.2 for all communications with NCR Secure Pay.

  V8.5.4 Patch 002 and the V8.4.6.19 Service Pack will only work with TLS 1.2. If you install these updates on a workstation for which TLS 1.2 is not supported and enabled, NCR Counterpoint will be unable to connect to NCR Secure Pay and you will be unable to process payments.

W I N D O WS 8. 1/ W I N D O W S 1 0 / W I N D O W S  S E R V E R 2 01 2 R 2

By default, TLS 1.2 is supported and enabled in Windows 8.1, Windows 10, and Windows Server 2012 R2. Thus,

no additional configuration is required to use TLS 1.2 with these operating systems.

W I N D O W S 7/ W I N D O W S  E M B E D D E D  P O S  R EA D Y  7 / W I N D O W S  S E R V E R  2 0 0 8 R 2

If your NCR Counterpoint workstations are running Windows 7, Windows Embedded POSReady 7, or Windows

Server 2008 R2, first ensure that you have installed all current Service Packs, updates, and security patches.

To enable TLS 1.2, create the registry setting entries (in the Client subkey) that are specified in the TLS 1.2

section of the Transport Security Layer (TLS) registry settings page in the Microsoft documentation library

(https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings#tls-12).

Every effort has been made to ensure the accuracy of this document. NCR makes no representations or warranties with respect to any of the information contained in this document and specifically disclaims any express or implied warranties of merchantability or fitness for a particular purpose with respect to such information. NCR shall not be liable for any errors or for incidental, indirect or consequential damages in connecting with the furnishing, performance or use of this document.

V E R I FY I N G  T H A T  T L S 1 .2  I S  E N A B L E D

If you are using Windows 7, Windows Embedded POSReady 7, or Windows Server 2008 R2, you can verify whether TLS 1.2 is supported and enabled on each of your NCR Counterpoint workstations by using Microsoft Internet Explorer to access the How’s My SSL? Website (https://howsmyssl.com).

Only use Internet Explorer to verify that your workstation is using TLS 1.2; other browsers do not use the Windows TLS system and may display incorrect results.

The Version section of the page should indicate that your client is using TLS 1.2, as illustrated below.

W I N D O W S  E M B E D D E D  P O S  R E A D Y  2 0 0 9

NCR does not currently plan to test or support TLS 1.2 with Windows Embedded POSReady 2009. Although Microsoft has indicated that an update will be made available to support TLS 1.2 with Windows POSReady 2009 (https://cloudblogs.microsoft.com/microsoftsecure/2017/10/05/announcing-support-for-tls-1-1-and-tls-1-2-in- xp-posready-2009/), merchants who wish to continue using POSReady 2009 must do so at their own risk.

We strongly recommend upgrading any workstation that is running Windows POSReady 2009 to a newer, supported operating system.

Marilyn.

Benefits of NCR Secure Pay

Posted on by ccsretail

Benefits of NCR Secure Pay

Without P2PE Hardware

NCR Secure Pay offers added security even when it is employed without Point-to-Point Encrypting (P2PE) Hardware.

Tokenization
The way card information is stored in your retail location is a key component of security. You need to ensure that you are storing cardholder information securely at all locations in your retail environment.

NCR Secure Pay utilizes tokenization, which is the most secure method of credit card data storage, also known as a token replacement. Tokenization allows NCR Counterpoint to store a token instead of an actual card number. If your system were breached, unauthorized users would only find the token information and not the actual card information, which is stored in a token vault hosted by NCR. With
the token, you can access the transaction information as needed for returns and other operations, including a card on file billing, while maintaining a secure system.

Host-Based Settlement
NCR Secure Pay uses host-based settlement, which stores transaction information at NCR’s host, rather than your NCR Counterpoint installation, until settlement. This provides flexibility allowing a settlement to be easily automated from the host or initiated from any web browser by using the NCR Secure Pay merchant portal.

In addition, with a host-based settlement, POS workstations running in “offline” mode can are still able to settle their transactions. This is a great benefit when offline workstations are disconnected for an extended period, such as during large upgrades.

With P2PE Hardware

Point-to-Point Encryption
Transmission of cardholder data between your system and the payment processor can be an area of a weakness that cyber payment criminals target.

To get an approval from a credit processor, card information must travel from the MSR (card reader) through the Point of Sale (POS) application and operating system (OS) to an application which communicates with the credit processor in order to get an authorization. Most systems pass the card data from the MSR unencrypted through the OS to the POS application and encrypt before sending the
approval communication to the credit processor.

With the addition of P2PE Hardware, NCR Secure Pay enables you to encrypt directly by the MSR hardware at the time the card is swiped, rather than solely during the transmission to the credit processor. The encryption happens in the hardware on the MSR device, not inside your NCR Counterpoint system and unencrypted data never exists on your POS network. This ensures sensitive cardholder information is encrypted throughout its lifecycle in your environment, limiting your risk of an unauthorized user scraping that data from memory.
Benefits of NCR Secure Pay

Another difference worth noting with P2PE as compared to traditional encryption is that the encryption and decryption processes use different keys. Even if you have the encrypting key, you can’t decrypt the data because the key to unlock the data is not the same. When using P2PE with NCR Secure Pay, the decryption key does not exist in the store environment, again reducing the risk that sensitive data could
be stolen from the system.

Contact CCS Retail Systems to get started with your NCR Secure Pay Systems.

Marilyn.

NOTICE: PCI DSS Requires Transition to Secure Pay Before April 30th, 2018!

Posted on by ccsretail

PCI DSS Requires Transition to Secure Pay Before April 30th, 2018!

TSYS and WorldPay Ending CPGateway Support

TSYS will discontinue support for the NCR Counterpoint Gateway (CPGateway) platform on April 30th, 2018. Merchants who are currently processing EDC payments through TSYS via CPGateway are advised to migrate to NCR Secure Pay before this date to ensure they can continue processing without interruption.

In addition, Worldpay will discontinue support for CPGateway within a similar time frame (we will announce the actual date on which CPGateway support will end for Worldpay merchants as soon as it is confirmed). Again, we strongly encourage merchants who are currently processing EDC payments through Worldpay via CPGateway to migrate to a Worldpay (TCMP) account for NCR Secure Pay to avoid any interruptions.

TLS (Transaction Level Security) 1.2 Transition

Getting Ready for TLS 1.2 (Check My TLS Status)

Payment Card Industry Data Security Standards (PCI DSS) require all PA-DSS validated payment applications to discontinue the use of “early TLS” (i.e., all versions of SSL and TLS 1.0) by June 30th, 2018.

To comply with this requirement, NCR Secure Pay will no longer accept early TLS connections after 2:30 A.M. on June 5th, 2018. In addition, updates to NCR Counterpoint V8.5.4 and V8.4.6 that will require the use of TLS 1.2 for payment transactions processed through NCR Secure Pay will be released as follows:

  • V8.5.4 Patch 002: Scheduled for 2/20/2018
  • V8.4.6.19 Service Pack: Scheduled for 3/6/2018

NCR does not plan to release patches or Service Packs to support TLS 1.2 in other versions of NCR Counterpoint.

To sign up for an NCR Secure Pay account, Contact CCS Retail Systems  ASAP.

Marilyn.