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

X-Payments user manual

1. X-Payments:General information
   • How It Works
   • Key features
2. What's New
   • What's New in X-Payments 3.1
   • What's New in X-Payments 3.0
3. System requirements
   • System requirements for X-Payments 3
   • System requirements for X-Payments 2.2
4. Installation
   • Installing X-Payments
   • Setting up file permissions for X-Payments
   • Getting started with X-Payments
5. Two-factor user authentication
   • Two-factor authentication (X-Payments 3)
   • Managing PIN codes (X-Payments 2.2 and earlier)
6. Configuring X-Payments
   • General settings
   • Online stores
   • Payment configurations
   • Encryption keys
   • 3D-Secure settings
   • KOUNT Antifraud screening
   • NoFraud fraud prevention
   • Signifyd fraud protection and chargeback prevention
7. Managing users
8. Customizing the interface
   • Customizing the interface (X-Payments 3)
   • Customizing the interface (X-Payments 2.2 and earlier)
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
    • Payment gateways supported by X-Payments 3.1
    • Payment gateways supported by X-Payments 3.0
    • Payment gateways supported by X-Payments 2.2
18. Popular Payment Methods Configuration Instructions
    • PayPal Payments Pro (PayPal API), PayPal Payments Pro (Payflow API), Payflow Pro
    • PayPal REST API
    • First Data Payeezy Gateway (ex- Global Gateway e4)
    • CyberSource - SOAP toolkit API

• 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