X-Payments:What's New in X-Payments 3.1
- X-Payments:General information
- What's New
- System requirements
- Installation
- Two-factor user authentication
- Configuring X-Payments
- Managing users
- Customizing the interface
- Managing payments
- Unistalling X-Payments
- Upgrading
- Moving X-Payments from one host to another
- Viewing X-Payments logs
- FAQ
- Troubleshooting
- Glossary
- Supported payment gateways
- Popular Payment Methods Configuration Instructions
In this section:
- X-Payments 3.1.0 key features
- News of X-Payments 3.1.x releases in our blog
- Previous X-Payments versions
Contents
X-Payments 3.1.0 key features
- Support for some new payment gateways has been added:
- Worldpay Total US,
- BlueSnap,
- Bambora (Beanstream),
- QuickPay.
- For a complete list of payment gateways supported by X-Payments 3.1, see Payment_gateways supported by X-Payments 3.1.
- The module Virtual Merchant has been renamed and is now called Elavon Converge.
- Tokenization feature has been for added for the iTransact and Elavon Converge payment methods and fixed for Payflow Pro.
- Authorize.net integration now supports fraud management and other improvements.
- Added JCB card type support for PayPal module.
- Fixed some issues related to Heidelpay module test/live mode.
UX and security improvements
- Signifyd antifraud screening service integrated
- Browser-side Javascript card data validation
- Automatic regeneration of [X-Payments:Encryption_keys | cardholder data keys]
- Improved support of 2-series Mastercard BINs
- Support of IP adresses passed by Cloudflare
- Developer mode is now available (for test installations without SSL)
- OpenSSL library is used now instead of the deprecated mcrypt library
- Updated BIN detection for Discover network cards
- Removed Solo, Switch and Laser from supported card types
- Shortened URLs for profile actions (password restoration, etc.) in emails
- Ability to grant permissions for admin users to edit templates, languages and view logs
- Minor design changes and improvements