Did you temporarily lose the ability to accept credit and debit card payments? This may be why.

 

Delayed - TLS v1.2 security upgrade Express Flickering of the lights event delayed The Express platform 'flickering of the lights' event scheduled for today, Wednesday February 17, has been delayed until Monday, February 24 at 2:30 p.m. ET due to the winter storm impacting many cities across the U.S. We apologize for any inconvenience this may have caused. Worldpay from FIS is ending support of TLS 1.0 and 1.1 on our MercuryPay and Express platforms.   As a follow up to the communication below, Worldpay from FIS will be flickering the lights for merchants still processing on TLS 1.0 and 1.1. “Flicker the light” events, where Worldpay proactively ‘turns off’ the no longer compliant TLS 1.0 and 1.1 for a brief period will take place to identify potentially impacted merchants. The dates and platforms impacted are: MercuryPay: February 16 at 2:30 p.m. ET - COMPLETE Express: February 24 at 2:30 p.m. ET - DELAYED The flickers will last for 30 minutes and merchants using TLS 1.0 or 1.1 will be unable to process during the flicker window. You are receiving this notice because you may have merchants that are utilizing the outdated security protocols known as Transport Layer Security (TLS) 1.0 and 1.1 to submit transaction to Worldpay from FIS on our MercuryPay or Express platforms. The PCI Security Standards Council has declared that TLS 1.0 or 1.1 no longer meet minimum security standards due to security vulnerabilities for which there are no fixes. Worldpay from FIS will end all support for TLS 1.0 and 1.1 after February 28, 2021 on our MercuryPay and Express platforms. Customers who are still using TLS 1.0 and 1.1 and who have not updated their system by that date will no longer be able to process transactions with Worldpay from FIS. Worldpay from FIS will be emailing merchants who may be utilizing these outdated protocols with common steps to prepare for the end of support for TLS 1.0 and 1.1. The merchants’ required actions will vary, and these steps are outlined in the attached document. (note from Kevin - if you were effected by this, you need to look at updating your computer and possibly your point of sale software ASAP. The quickest and least expensive solution is to put in stand alone payment terminals that do not connect to your point of sale system. I realize that stand alone payment terminals mean lost revenue due to miss-keyed payment totals but it will at least be a temporary solution while you see what hardware and software needs to be update so you are TLS 1.2 compliant).

Now Offering Support for the Vantiv / Mercury Microsoft RMS Integration

Due to demand, we are now able to provide support to Microsoft Dynamics RMS point of sale software users who also use the Vantiv/Mercury/WorldPay payment integration along with the VX805 payment terminals (other payment terminals may be supported as well - so far we've only seen the ICS 250's and the VX 805's being used).

I've had around a half dozen retailers contact me as their current provider could not, or would not, provide support. Here are the stipulations:

• This is paid support (can choose pay as you go or pre-purchase discounted labor which lowers the hourly rate from $125/hour to under $100/hour - billed in 15 minute increments).
• A Dealer Change form must be completed in order for our support techs to have access to the information needed to support the system.

Please contact me at 208-340-5632 or kevinantosh@gmail.com for more information. You can also use my work contact information if that is easier for you: 208-994-9404 or kevina@rite.us

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".

Important MasterCard Mandate Deadlines for WorldPay Customers

Update 3/23/2017: I was actually onsite installing Card Defender for a customer here in Idaho when she received a letter from Heartland addressing the same card number issues noted below. It was very comforting for the retailer to know that Card Defender meets or exceeds industry requirements for payment processing.

Another credit card compliance mandate - this time from WorldPay specific to 2 MasterCard Mandate Deadlines. Do contact your WorldPay  salesperson and your point of sale hardware and software provider to verify compliance if you received the communication below.

If you are orphaned, please contact me at 208-340-5632 or kevinantosh@gmail.com and I will do my best to assess your situation.

If you would rather contact me at RITE, I can be reached at  208-994-9404 or kevina@rite.us

 

Dec 20, 2016

Important MasterCard Mandates 

Action Required
At Worldpay, our valued customers and partner relationships are our highest priority. We are committed to providing trusted and reliable payments processing and are sending this important reminder requiring action with your point of sale partner.
MasterCard has issued two upcoming changes that may affect you, the MasterCard Unique Terminal Identification (TID) Mandate and the New 2-Series Bank Identification Numbers (BIN). While each update is very different, it is important to note the deadlines to comply are January 1, 2017 and May 1, 2017 respectively. You have been identified as a merchant that may be affected by these changes and may not already be compliant.

MASTERCARD UNIQUE TERMINAL ID MANDATE
What is happening?
Effective January 1, 2017, merchants who do not adhere to the MasterCard Unique Terminal ID mandate which requires unique terminal identifiers for each independent card reading device in a single location, will fall into a status of noncompliance with MasterCard. For each transaction that violates this mandate, you may be assessed a fine by MasterCard.
All merchants with multiple card-reading devices, such as PIN pads, connected to a single host terminal are required to have each of their devices identifiable with a unique Device ID number to remain compliant and avoid fines from MasterCard.
What do you need to do?
To ensure you comply with the mandate, contact your point of sale partner immediately. Card reading devices are required to send separate and Unique Device ID numbers by January 1, 2017. 
If you would like to learn more about this mandate, click here to review MasterCard Unique Terminal ID Frequently Asked Questions (FAQs). For additional questions or concerns, contact your Worldpay Client Manager.

NEW 2-SERIES BANK IDENTIFICATION NUMBERS (BIN)
In order to support an expanding payments industry, MasterCard will begin issuing cards that utilize Bank Identification Numbers (BINs) beginning with a 2 in the range of 222100-272099. Effective May 1, 2017, merchants will be required to update BIN tables to support the new 2-Series BIN cards. If the appropriate actions are not taken, some MasterCard transactions will be declined at the point-of-sale (POS) and merchants in violation will be fined. 
What is happening?
Working with your respective partners, you will be required to update your POS terminal software in order to begin accepting and processing new 2-Series BIN transactions. If you do not update your software before the deadline, you will fall into a status of noncompliance. Each noncompliant merchant and/or ATM location may face fines in the as noted below.

• Up to $2,500 per occurrence for the first 30 days
• Up to $5,000 per occurrence for days 31-60
• Up to $10,000 per occurrence for days 61-90
• Up to $20,000 per occurrence for subsequent violations

A noncompliant occurrence is defined as any attempted and failed 2-Series BIN transaction that is confirmed as failed due to a merchant’s lack of readiness to support 2-Series BIN transactions.

What do you need to do?
Contact your point of sale partner immediately to make any necessary updates to BIN tables to support the new 2-Series BIN by the May 1, 2017 deadline.
If you would like to learn more about this mandate, click here to review MasterCard 2-Series BIN Implementation Frequently Asked Questions (FAQs). For additional questions or concerns, contact your Worldpay Client Manager.


© Worldpay 2016. All rights reserved. Worldpay, the logo and any associated brand names are trademarks of the Worldpay group of companies. Worldpay US, Inc. is a registered ISO/MSP of Citizens Bank, N.A., Wells Fargo Bank, N.A., and Eagle Bank, N.A.