Difference between revisions of "X-Payments:What's New in X-Payments 3.0"
m |
m |
||
| Line 1: | Line 1: | ||
<noinclude>{{XP_manual_TOC}}</noinclude> | <noinclude>{{XP_manual_TOC}}</noinclude> | ||
| − | * [[X-Payments:Two-factor_authentication | | + | * Two-factor authentication [[X-Payments:Two-factor_authentication | via SMS or Google authenticator app]]. Instead of PIN codes that were used for the second step of admin user authentication in X-Payments versions 2.2 and earlier, we have enabled the administrator to choose either an authentication method based on using one-time passwords from Google Authenticator or a method based on using passwords sent via SMS/text messages. Authentication via backup codes is also available. |
* New optimized and responsive HTML5 payment templates for all the supported shopping cart engines. | * New optimized and responsive HTML5 payment templates for all the supported shopping cart engines. | ||
* Improved experience for mobile users (e.g. number pads to enter credit card numbers, etc.) | * Improved experience for mobile users (e.g. number pads to enter credit card numbers, etc.) | ||
Revision as of 20:55, 31 July 2016
- 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
- Two-factor authentication via SMS or Google authenticator app. Instead of PIN codes that were used for the second step of admin user authentication in X-Payments versions 2.2 and earlier, we have enabled the administrator to choose either an authentication method based on using one-time passwords from Google Authenticator or a method based on using passwords sent via SMS/text messages. Authentication via backup codes is also available.
- New optimized and responsive HTML5 payment templates for all the supported shopping cart engines.
- Improved experience for mobile users (e.g. number pads to enter credit card numbers, etc.)
- Browser auto-fill supported.
- Payment template customization and translation capabilities via the admin back end (no need for FTP any more).
- Simplified interface for the management of individual store configurations.
- Ability to download logs from the admin back end (no need for FTP).
- Get/update tokenized card feature implemented for Chase Paymentech Orbital and Authorize.Net modules.
- MySQL 5.7 support.
- IPv6 support.
- Support for new Mastercard BINs.
- After a payment error, customers can now make another attempt to pay - without returning to the Shopping cart error page and starting checkout anew (Better conversion rates for your site).
- Multiple Authorize.net modules are now merged into a single module with tokenization support.
- New payment modules: NMI (Network Merchants Inc.), NAB (National Australia Bank), Bendigo Bank, Suncorp (Suncorp Bank), Suncorp (Suncorp Bank), Sage (US).
- Updates for existing payment modules: eWay, ANZ, USA ePay.
- Added tokenization support for the following modules: Netbilling, eProcessingNetwork, USA ePay.
- 3-d secure support for eProcessingNetwork and Payeezy (FirstData e4).
- 3-d secure form is now displayed on a separate page.
- Kount module updated.
- Automatic notifications about available X-Payments upgrades.
- Back-end UI improvements.
- Fixed several minor issues.
- Security improvements
