Difference between revisions of "X-Payments:V3.1.0 released"
| Line 12: | Line 12: | ||
</ul> | </ul> | ||
| − | == | + | ==UX and Security Improvements== |
<ul> | <ul> | ||
| − | <li>Signifyd anti fraud screening service is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li> | + | <li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li> |
<li>Browser-side JavaScript card data validation has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li> | <li>Browser-side JavaScript card data validation has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li> | ||
<li>Expired cardholder data keys don’t require manual regeneration anymore. X-Payments does it automatically. </li> | <li>Expired cardholder data keys don’t require manual regeneration anymore. X-Payments does it automatically. </li> | ||
| Line 33: | Line 33: | ||
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong. | To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong. | ||
| − | Note! After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of 2-factor authentication for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in. | + | '''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of 2-factor authentication for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in. |
==PA-DSS Implementation Guide== | ==PA-DSS Implementation Guide== | ||
| Line 41: | Line 41: | ||
So, we’ve created the PCI-DSS implementation guide to help you configure your servers, where you’re going to host X-Payments software, in the right way. | So, we’ve created the PCI-DSS implementation guide to help you configure your servers, where you’re going to host X-Payments software, in the right way. | ||
| − | + | ||
==Enjoy flexible plans from Bambora== | ==Enjoy flexible plans from Bambora== | ||
Revision as of 10:01, 3 August 2017
Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.
Contents
Payment Gateways
- New payment gateways added: Worldpay Total US, BlueSnap, Bambora (Beanstream), QuickPay;
- Virtual Merchant module renamed to Elavon Converge;
- Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;
- Support for fraud management and other improvements in Authorize.net integration;
- JCB card type support in PayPal module;
- Fixed issues related to Heidelpay module test/live mode.
UX and Security Improvements
- Signifyd anti fraud screening service is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.
- Browser-side JavaScript card data validation has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.
- Expired cardholder data keys don’t require manual regeneration anymore. X-Payments does it automatically.
- Starting from v3.1.0 the root admin can grant permissions for additional user accounts in X-Payments back-end to edit templates, languages and view logs. See the full list of permissions the additional accounts owners may have here.
- Improved support of 2-series Mastercard BINs and updated BIN detection for Discover network cards.
- Improved IP addresses determination for stores protected by CloudFlare. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.
- Developer mode is now available for test installations without SSL. It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.
- OpenSSL library is used now instead of deprecated mcrypt library.
- Removed Solo, Switch, and Laser from supported card types as no longer valid.
- Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.
Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these instructions.
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.
Note! After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of 2-factor authentication for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.
PA-DSS Implementation Guide
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of PCI-SSC. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.
So, we’ve created the PCI-DSS implementation guide to help you configure your servers, where you’re going to host X-Payments software, in the right way.
Enjoy flexible plans from Bambora
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the open letter by their CEO, Johan Tjärnberg.
In honor of this exciting occasion, they've got something interesting for you to offer:
For Canadian clients (CAD) Gateway + Merchant account: CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce
For Canadian clients (USD) Gateway + Merchant account: USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10
For USA Clients (USD) Gateway + Merchant account: USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4
