Update - since this blog post went up, I have also been contacted by TSYS users reporting a 11.5 cent/transaction non-compliance surcharge so its extremely clear that the credit card industry is cracking down on PCI/SHA-2/EMV requirements.
It has been reported to me that some First Data customers have started seeing $20 to $25 monthly fees on their statements for not being PCI compliant and/or not having the hardware in place to accept EMV/Chip Cards. While this may not sound like much, paying $240 to $300 per store location annually adds up quickly.
Microsoft Dynamics RMS users may want to take a look at Card Defender which is hardware and software for Microsoft Dynamics RMS that is PCI compliant, works with First Data, and also allows you to accept EMV/Chip Cards as payment.
More information on Card Defender can be found here: http://www.pospondering.com/p/card-defender-emv-for-rms.html
You can also contact me at 208-340-5632 or kevinantosh@gmail.com for more information.
Offering general point of sale advice, consulting, and sales/service to independently owned beer, wine, and liquor stores in the United States.
Showing posts with label first data. Show all posts
Showing posts with label first data. Show all posts
Wednesday, January 18, 2017
Friday, December 16, 2016
Critical Deadline for First Data, SHA-256, and Microsoft RMS
A quick reminder that if you are using First Data for merchant services along with the Microsoft Dynamics RMS software that the deadline for being SHA-256 compliant is December 28th, 2016 (next week!).
If you have not yet taken steps to replace outdated credit and debit card processing equipment, it needs to be taken care of now as First Data has indicated that they will not allow processing via Datawire starting December 29th, 2016.
If you are unsure, it would be smart to contact your First Data merchant salesperson and/or your Microsoft Dynamics RMS Partner to confirm that your system is SHA-256 compliant.
The most common situation involves still using "old school style" credit card swipes that connect to a USB port or use a keyboard wedge style interface.
The good news is that there are multiple solutions to upgrade to SHA-256 compliant equipment AND still use the Microsoft RMS software. These options may include using a separate payment terminal or installing Card Defender for Microsoft RMS.
As always, contact me at 208-340-5632 or kevinantosh@gmail.com - I do work for a Microsoft RMS Partner so I can offer advice and solutions.
If you have not yet taken steps to replace outdated credit and debit card processing equipment, it needs to be taken care of now as First Data has indicated that they will not allow processing via Datawire starting December 29th, 2016.
If you are unsure, it would be smart to contact your First Data merchant salesperson and/or your Microsoft Dynamics RMS Partner to confirm that your system is SHA-256 compliant.
The most common situation involves still using "old school style" credit card swipes that connect to a USB port or use a keyboard wedge style interface.
The good news is that there are multiple solutions to upgrade to SHA-256 compliant equipment AND still use the Microsoft RMS software. These options may include using a separate payment terminal or installing Card Defender for Microsoft RMS.
As always, contact me at 208-340-5632 or kevinantosh@gmail.com - I do work for a Microsoft RMS Partner so I can offer advice and solutions.
Thursday, October 27, 2016
TSYS SHA2 Deadline: What Microsoft RMS Users Need to Know
Wow - lots of calls and emails the last couple of days asking about the looming January 1st, 2017 SHA2 compliance deadline and what options are available for retailers using the Microsoft RMS point of sale software. It appears that TSYS and possibly First Data are pushing for compliance via the companies that use the TSYS and First Data platforms for merchant services.
First off - this is actually a good thing from a security standpoint as many retailers have held off on implementing EMV/Chip Card solutions and/or are still using Windows XP. Given the calls that I have been receiving about EMV fraud, the time has come to move forward with putting in the equipment to process EMV/Chip Cards.
I would strongly recommend that retailers using the Microsoft RMS point of sale software move to Windows 7. Windows 10 is possible with some help from myself or another Microsoft Dynamics RMS Partner. Skip Windows 8 or 8.1.
When it comes to retailers using the Microsoft RMS point of sale software, you have several options to meet the SHA2 deadline. My, advice (in order of preference) is the following:
First off - this is actually a good thing from a security standpoint as many retailers have held off on implementing EMV/Chip Card solutions and/or are still using Windows XP. Given the calls that I have been receiving about EMV fraud, the time has come to move forward with putting in the equipment to process EMV/Chip Cards.
I would strongly recommend that retailers using the Microsoft RMS point of sale software move to Windows 7. Windows 10 is possible with some help from myself or another Microsoft Dynamics RMS Partner. Skip Windows 8 or 8.1.
When it comes to retailers using the Microsoft RMS point of sale software, you have several options to meet the SHA2 deadline. My, advice (in order of preference) is the following:
- Implement Card Defender for Microsoft RMS: Card Defender solves your security issues and allows for both EMV/Chip Card processing and NFC (Apple Pay and Google Wallet) processing as an integrated add-on for Microsoft RMS . Card Defender does not add any gateway or per-transaction fees above what your merchant services company charges, is processor agnostic (TSYS, First Data, and Heartland), and requires no contracts. Visit this page on my blog for more information on Card Defender or contact me for more information - I've already had 5 retailers using RMS contact me in just the last 2 days about Card Defender so it is clear that the is upcoming deadline is being taken seriously.
- Vantiv/Mercury, Shift 4, Heartland and Cayan/Merchants Warehouse also offer some EMV/Chip Card add-ons/payment gateways/payment tunnels for Microsoft RMS. Generally I have found that these solutions are more expensive than Card Defender in the long run (1+ years) due to additional per-transaction fees and/or locking you into a contract using only one company for merchant services (which is another thing that I like about Card Defender - its keeps your merchant services provider honest when it comes to the rates and fees that they charge as they know that you can switch companies of you are unhappy while these other solutions basically lock you in).
- Use a separate credit card terminal that does not interface with the Microsoft RMS software. While this is the easiest and lowest cost option, keep in mind that you will be reconciling two reports at the end of each day and you open up the system to human error when entering the total on the credit card terminal (for example: a transaction totaling $15.20 could be entered as $1.52 or $152.00 - not fun to have have to track a customer down to correct the error).
All in all - there are plenty of options that allow Microsoft RMS point of sale software users to keep using RMS and meet the SHA2 deadline. Do contact me with any questions or clarifications.
Thursday, May 7, 2015
Continued Cover Complaints
As I don't always have time to post every time that someone is kind enough to provide me with feedback on their POS system, I did want to mention that I continue to receive regular negative feedback on Clover POS. Several folks have taken the time to call or email me with recent details about their negative experience with Clover.
The complaints similar to what I have posted about Clover in other posts (excessive fees, long term contracts, promised features/functions not available, etc). You can always contact me if you need more details but obviously Clover is not on my recommendation list when it comes to reliable and reputable point of sale systems.
Are you in the US and in need of no cost retail point of sale advice? I'm happy to help and can be reached on my cell at 208-340-5632 (I am on Mountain Time) or via email at kevinantosh@gmail.com. There is also a contact form to the right that can be used to reach me.
The complaints similar to what I have posted about Clover in other posts (excessive fees, long term contracts, promised features/functions not available, etc). You can always contact me if you need more details but obviously Clover is not on my recommendation list when it comes to reliable and reputable point of sale systems.
Are you in the US and in need of no cost retail point of sale advice? I'm happy to help and can be reached on my cell at 208-340-5632 (I am on Mountain Time) or via email at kevinantosh@gmail.com. There is also a contact form to the right that can be used to reach me.
Labels:
clover,
complaints,
first data,
point of sale,
POS,
reviews
Subscribe to:
Posts (Atom)