What Microsoft Dynamics RMS Users are Doing: 2017 Edition

***Video did not render correctly - yet another problem with my Surface Pro 4***

I will attempt to edit and re-upload  but the video is watchable - just the right side content is cutoff.

I'm in the midst of travel visiting retailers using the Microsoft Dynamics RMS point of sale software to advise what, if anything, they need to do between now and July 2021. The options are fairly clear cut between Card Defender, Cloud Retailer, Retail Management Hero, Retailer Realm Essentials, Microsoft Dynamics AX and Microsoft Dynamics 365 which are all covered briefly in this video:

If your store or chain is using RMS, I'm happy to consult with you on options (both short and long term). I can be reached at kevinantosh@gmail.com or 208-340-5632

MasterCard May 1st 2017 Mandate for New Numbers - Will RMS Process the New Cards?

As retailers report receiving more letters and emails from WorldPay, Heartland and other merchant services companies related to the MasterCard 2 Series Bank Identification Number (BIN) Mandate, the biggest question is "will I be able to accept and process the new cards if I am using the Microsoft Dynamics RMS point of sale software?"

A quick reminder that this mandate goes in to effect on May 1st, 2017. Not being able to accept and process the new number sequence on these MasterCard credit cards means fines of up to $20,000 per the letters and emails that have been shared with us.

As for the question, the short answer is "yes, but...". We've done some testing and RMS appears to handle the new card numbers. However, there are quite a few variables at play related to the version of RMS being used and any add-ons being used with RMS.

There is also the reality that new payment processing requirements are being introduced on a fairly regular basis and RMS is not being updated to accommodate these requirements. A better solution is looking at Card Defender which integrates with RMS but assumes all the payment processing liability using the latest in payment processing terminals as well as being updatable to meet or exceed present as well as future payment processing requirements.

Because of the variables involved, as well as future payment processing requirements, the best answer to the question is "Yes, but please contact RITE at 888-267-7483 or sales@rite.us in order to discuss your specific situation and look at the best course of action".

Possible Issues with Mercury/Vantiv Magtek IPAD for Microsoft RMS

Wanted to make everyone aware of a potential issue specific to the Mercury/Vantiv Magtek "IPAD" payment processing add-on for the Microsoft Dynamics RMS point of sale software.

I arrived at a customers site last week only to find that the entire system was down due to the Microsoft Dynamics RMS database being "full". The cause was a large amount of transaction data being put in to the RMS database from the Mercury/Vantiv Magtek "IPAD" payment processing add-on. The customer had only been using the add-on for just over 2 years and is a single lane RMS users.

Obviously, retailers can't have their system go down due to the RMS database being full so here are the possible resolutions:

1. Purchase SQL Server which allows for a larger database size ($1100 - $2000 depending on version and license options).
2. Have your point of sale partner/VAR/dealer monitor your RMS database and delete/archive old data as needed ($125-$250 per occurrence if needed).
3. Consider switching to Card Defender which does not populate your RMS database with as much transaction data as the MagTek IPAD solution does (Card Defender does not presently work with Mercury/Vanticv but this will change in the coming months).
4. Look at a different integration that RITE offers using an Vantiv ICS250 payment terminal with Microsoft Dynamics RMS.

Do contact me at 208-340-5632 or kevinantosh@gmail.com with any questions or contact your RMS Partner to have them check the size of your RMS database (or your IT staff can check the size fo the database as well - just takes about 5 minutes).