X-Payments:What's New in X-Payments 3.0

From X-Payments Help
Revision as of 14:50, 1 August 2016 by Dohtur (talk | contribs)
Jump to: navigation, search
X-Payments user manual
  1. X-Payments:General information
  2. What's New
  3. System requirements
  4. Installation
  5. Two-factor user authentication
  6. Configuring X-Payments
  7. Managing users
  8. Customizing the interface
  9. Managing payments
  10. Unistalling X-Payments
  11. Upgrading
  12. Moving X-Payments from one host to another
  13. Viewing X-Payments logs
  14. FAQ
  15. Troubleshooting
  16. Glossary
  17. Supported payment gateways
  18. 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.
    We have come up with a completely new set of templates defining the look of the form for entering payment information. It is a totally new template system, so, after an upgrade to X-Payments 3.0, those of you who have used X-Payments 2.2 or earlier version with customized templates will have to implement the customization anew. The big plus of the new system, however, is that the templates are now responsive, which means that you only have to adjust your templates once, after which they will adapt automatically to any width of the screen or iframe, providing users with a neat-looking payment form on any type of computer or mobile device - for all the supported shopping carts.

  • Improved experience for mobile users (e.g. number pads to enter credit card numbers, etc.)



  • Browser auto-fill supported.
    We have implemented browser autofill support for the payment info entry form. Now when a user enters their payment card info to pay via X-Payments, they may choose to allow the web browser they are using to save this information. Alternatively, they may choose to add this information in advance via the browser's Autofill settings. On subsequent payments, the user will be able to allow the browser to autofill the payment form with the payment information stored by the browser.

  • Payment template customization and translation capabilities via the admin back end (no need for FTP any more).
    Starting with X-Payments 3.0, the templates defining the look of the X-Payments payment form can be adjusted via the Settings > Templates section. The process is point-and-click easy. It has also become possible to edit the wording of the X-Payments user interface via the Settings > Languages section.

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

  • Changes to payment modules:
    - New payment modules: NMI (Network Merchants Inc.), NAB (National Australia Bank), Bendigo 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).
    For the complete list of payment modules, see Payment gateways supported by X-Payments 3

  • Kount module updated.

  • 3-d secure form is now displayed on a separate page.

  • Automatic notifications about available X-Payments upgrades.

  • Back-end UI improvements.

  • Fixed several minor issues.

  • Security improvements