10.3 and 3.1 How to test PlugNPay with TLS 1.2 mandate before deadline May 31, 2018
Problem
From the PlugNPay gateway status website: http://www.gatewaystatus.com/CipherModificationNotice.htm:
SOURCE: Plug & Pay Technologies Inc.
Modification To Permitted Ciphers
Hauppauge, NY - March 26, 2018
REDUCING RISK
Solution
REDUCING RISK
Migration from SSL and Early TLS Deadline
Effective May 14th 2018
The Payment Card Industry Security Standards Council (PCI SSC) announced a mandate for transitioning from all versions of SSL and TLS 1.0 communication protocols to a more secure version of TLS (currently TLS v1.1 or higher).
Plug and Pay has established a compliance deadline for all transaction traffic to update to TLS 1.1+ by May 14th 2018.
For most merchants running modern software, merchants that have not upgraded by this date will experience service outages and will not be able to process transactions until an upgrade to TLS 1.1 or higher is performed.
We're requesting that said API based integrations be tested with our test domain ('https://pay2.plugnpay.com/'), to determine if your given system/integration will have difficulties connecting to the payment gateway after May 1st.
Tests can easily be performed, by changing the domain name within the URL you're calling to 'pay2.plugnpay.com' & then make the API requests to the gateway normally.
Test all your gateway accounts.
If everything works normally, then you can be sure your API integration to the payment gateway will continue to function after the given deadline.
**** You can now change back to https://pay1.plugnpay.com. ****
However, if you run into any troubles while testing, please contact support@plugnpay.com so we may work with you &/or your staff on the matter.
RecTrac 3.1 users on 3.1.07.02 or higher should have gotten the change already so there is nothing to test.
Testing should be done in the demo database with a cloned profile(3.1) or device (10.3)