TSYS, Heartland and Wells Fargo Ending Support for Native Payment Processing in Microsoft Dynamics POS 2.0, 2007, 2009 and RMS / TLS Deadline

If you happen to be hanging on to old credit card swipes and are using TSYS, First Data or Heartland to process payments made via credit card or debit card in the Microsoft Dynamics POS 2.0, 2007, 2009 and RMS point of sale software programs, you will be in for a surprise when your processing is turned off starting June 1st, June 30th, or July 1st 2018. This also somewhat aligns with the TLS deadline for non-secure ways of processing credit cards.

It is simply just not secure or safe to use USB or Keyboard Wedge credit card swipes anymore.  You could be fined and/or lose the ability to accept payment via credit or debit card if caught.

There are multiple options available to you:

1. Look at Card Defender which takes the security risk out of RMS, uses integrated payment terminals to interface with RMS, and you even pick up cool stuff like signature capture and NFC for Apple Pay and Google Wallet.
2. Switch to using stand alone payment terminals. Quickest and least expensive option but leaves you open to entry errors that can cost you over $2080 annually in lost revenue.
3. Look at updating RMS to one of the low cost direct replacement programs like Cloud Retailer or Retail Management Hero 

Those are the main options - you should make a decision no late than the end of May.

***I've also been contact by users of Microsoft Dynamics POS 2007, 2009 and 2.0 stating that they are also losing the ability to process credit cards effective June 1st, 2018. In these cases, you have fewer options since Dynamics POS 2007, 2009 and 2.0 do not have any 3rd party processing interfaces and do not qualify for a low cost replacement program. Contact me as needed***

***New Heartland Deadline: June 1st, 2018. You will need to change hardware/software as need or your processing will be tuned off***

****Wells Fargo and Heartland have also communicated with retailers that they will no longer allow them to use RMS and native processing with USB/Keyboard Wedge credit card swipes****

*****If you are using Windows XP then you can not use any web-based or integrated processing solution as Windows XP does not meet security standards*****

Please contact me at 208-340-5632 or kevinantosh@gmail.com for more information. You should also contact your merchant services company to see which deadline applies to you.

TSYS, Heartland and Wells Fargo Ending Support for Native Payment Processing in Microsoft Dynamics POS 2.0, 2007, 2009 and RMS / TLS Deadline

***New Heartland Deadline: June 1st, 2018. You will need to change hardware/software as need or your processing will be tuned off***

If you happen to be hanging on to old credit card swipes and are using TSYS, First Data or Heartland to process payments made via credit card or debit card in the Microsoft Dynamics POS 2.0, 2007, 2009 and RMS point of sale software programs, you will be in for a surprise when your processing is turned off starting June 1st, June 30th, or July 1st 2018. This also somewhat aligns with the TLS deadline for non-secure ways of processing credit cards.

It is simply just not secure or safe to use USB or Keyboard Wedge credit card swipes anymore.  You could be fined and/or lose the ability to accept payment via credit or debit card if caught.

There are multiple options available to you:

1. Look at Card Defender which takes the security risk out of RMS, uses integrated payment terminals to interface with RMS, and you even pick up cool stuff like signature capture and NFC for Apple Pay and Google Wallet.
2. Switch to using stand alone payment terminals. Quickest and least expensive option but leaves you open to entry errors that can cost you over $2080 annually in lost revenue.
3. Look at updating RMS to one of the low cost direct replacement programs like Cloud Retailer or Retail Management Hero 

Those are the main options - you should make a decision no late than the end of May.

***I've also been contact by users of Microsoft Dynamics POS 2007, 2009 and 2.0 stating that they are also losing the ability to process credit cards effective June 1st, 2018. In these cases, you have fewer options since Dynamics POS 2007, 2009 and 2.0 do not have any 3rd party processing interfaces and do not qualify for a low cost replacement program. Contact me as needed***

****Wells Fargo and Heartland have also communicated with retailers that they will no longer allow them to use RMS and native processing with USB/Keyboard Wedge credit card swipes****

*****If you are using Windows XP then you can not use any web-based or integrated processing solution as Windows XP does not meet security standards*****

Please contact me at 208-340-5632 or kevinantosh@gmail.com for more information. You should also contact your merchant services company to see which deadline applies to you.

Pin Debit Error Message with TSYS and Microsoft Dynamics RMS

I've had reports of Microsoft Dynamics RMS point of sale software users receiving the following error message when try to process payments made using PIN Debit:

"Connection Error: Unable to Connect to remote host.  Unable to establish security context for this session  Num=0, Source="

In most cases, transactions run by credit card work fine.

TSYS is looking in to the issue but this is a good example of why RMS users should be looking at Card Defender since Card Defender takes out the old EDC settings in RMS (which is really not secure when it comes to protecting card holder information) and replaces EDC with payment terminals that meet or exceed payment industry security requirements (and still interface directly with RMS).

As a bonus, Card Defender also allows retailers to accept Chip Cards, NFC Payments like Apple Pay and Google Wallet, and even works with the low cost replacement point of sale programs for RMS like Cloud Retailer and Retail Management Hero.

More information on Card Defender can be found here or by contacting RITE at sales@rite.us or 888-267-7483.