Hi!
1. Most likely we will release 4.4
2. X-Payments release is not tied to 4.4. Its release date depends on results of beta testing (will launch soon) and on results of PA-DSS certification
3. We plan to support the following payment methods in X-Payments v1.0:
- ANZ eGate - Virtual Payment Client (merchant hosted)
- Authorize.Net - Advanced Integration Method
- Beanstream - Process Transaction API
- Global Gateway - Direct model
- BluePay
- Caledon - Real-time interface
- DIBS - API integration
- DirectOne - Direct interface
- ECHOnline
- ePDQ - MPI XML
- eProcessing Network - Transparent Database Engine
- eSec - Web Direct Model
- eSelect - DirectPost
- eWay - Realtime Payments XML
- GoEmerchant - XML Gateway API
- HSBC Secure ePayments - API integration
- Innovative Gateway - PHP Connection
- iTransact - XML connection method
- Global Gateway - API (North America)
- Global Gateway - API (EMEA)
- Netbilling gateway - Direct Mode 3.1
- Netregistry eCommerce Gateway - HTTPS method
- Ogone e-Commerce - DirectLink integration
- PayPal - Website Payments Pro
- PayPal - Website Payments Pro Payflow Edition
- PayPal - Payflow Pro
- WebXpress - XML method
- Sage Pay - Direct protocol
- PSIGate - XML API
- Quantum Gateway - Transparent QGWdatabase Engine
- SecurePay - Non-recurring Interface
- SkipJack
- USA ePay - CGI Transaction Gateway API
- Virtual Merchant - Merchant Provided Form
- CyberSource - SOAP Toolkit API
- Manual credit card processing
4. X-Payments v1.0 requires the payment form to be displayed by X-Payments (on your domain) and doesn't allow the payment form to be integrated into a checkout page displayed by a shopping cart system. We will check (when will be certifying X-Payments by a PA-QSA) whether it is not against PCI DSS, and perhaps future X-Payments versions will support this feature.