Difference between revisions of "X-Payments:V3.1.1 released"

From X-Payments Help
Jump to: navigation, search
(Created page with "The v3.1.0 is a bugfix release. Here is a list of bugs and errors that have been repaired: ==Payment gateways integrations== <ul> <li>Authorize.net: Refunds didn’t work;</l...")
 
(Other issues)
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
The v3.1.0 is a bugfix release. Here is a list of bugs and errors that have been repaired:
+
The v3.1.1 is a bugfix release. Here is a list of bugs and errors that have been repaired:
  
 
==Payment gateways integrations==
 
==Payment gateways integrations==
Line 12: Line 12:
 
<li>Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.</li>
 
<li>Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.</li>
 
</ul>
 
</ul>
 +
 
==Other issues==
 
==Other issues==
 
<ul>
 
<ul>
 
<li>X-Payments iframe showed up incorrectly in IE8 browser;</li>
 
<li>X-Payments iframe showed up incorrectly in IE8 browser;</li>
 
<li>Built-in recurring payments feature didn’t work. <br>
 
<li>Built-in recurring payments feature didn’t work. <br>
BTW, this feature is deprecated now though still work. If you want to set recurring payments and sell subscription products, consider special free addons for X-Cart 5 and X-Cart Classic;</li>
+
BTW, this feature is deprecated now though still work. If you want to set recurring payments and sell subscription products, consider special free addons for [https://market.x-cart.com/addons/x-payments-subscriptions-and-installements.html X-Cart 5] and [https://market.x-cart.com/addons/xpayments_subscriptions.html X-Cart Classic];</li>
 
<li>Time in logs used to differ from the online store time zone;</li>
 
<li>Time in logs used to differ from the online store time zone;</li>
 
<li>'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.</li>
 
<li>'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.</li>
 
</ul>
 
</ul>
  
If you’ve faced any of the bugs and errors mentioned above, upgrade to v3.1.0 and forget about the inconveniences caused by these issues.
+
If you’ve faced any of the bugs and errors mentioned above, upgrade to v3.1.1 and forget about the inconveniences caused by these issues.
 +
 
  
Also, X-Payments v3.1.0 uses the latest version of jQuery.
+
If you are a subscriber of X-Payments Hosted solution, please create a ticket in your [https://secure.x-cart.com Help Desk account] and we'll apply the update for you for free. If you use a downloadable X-Payments solution, you should update it yourself following the instructions [https://www.x-payments.com/help/X-Payments:Upgrading here] or we can do it for you within our support services upon your request in [https://secure.x-cart.com Help Desk].
  
 
==See also==
 
==See also==
[https://www.x-payments.com/help/X-Payments:V3.1.0_released#Important_Info_on_X-Payments_Self-Hosted_v2.x.2F1.x_Upgrade Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade] <br>
+
[https://www.x-payments.com/help/X-Payments:Upgrading#Important_Info_on_X-Payments_Self-Hosted_v2.x.2F1.x_Upgrade Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade] <br>
 
[https://www.x-payments.com/help/X-Payments:PA-DSS_implementation_guide_for_X-Cart_Payments_3 PA-DSS implementation guide for X-Cart Payments 3]
 
[https://www.x-payments.com/help/X-Payments:PA-DSS_implementation_guide_for_X-Cart_Payments_3 PA-DSS implementation guide for X-Cart Payments 3]

Latest revision as of 13:26, 14 December 2017

The v3.1.1 is a bugfix release. Here is a list of bugs and errors that have been repaired:

Payment gateways integrations

  • Authorize.net: Refunds didn’t work;
  • eSelect Plus: Multiple payment attempts and addresses without numbers caused errors;
  • Intuit Quickbooks: If a customer had saved any credit cards data in his/her account but attempted to use a new card at checkout, it resulted in errors;
  • Bambora: Failed payments and unstable 3d secure feature work;
  • Cybersource: 3D Secure results were passed incorrectly to the gateway;
  • SagePay: Old tokens (saved cards) saved before the integration update didn't work with the new integration;
  • Payeezy: Reference ID was not passed, making it difficult to find the transaction in the Payeezy dashboard;
  • Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.

Other issues

  • X-Payments iframe showed up incorrectly in IE8 browser;
  • Built-in recurring payments feature didn’t work.
    BTW, this feature is deprecated now though still work. If you want to set recurring payments and sell subscription products, consider special free addons for X-Cart 5 and X-Cart Classic;
  • Time in logs used to differ from the online store time zone;
  • 'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.

If you’ve faced any of the bugs and errors mentioned above, upgrade to v3.1.1 and forget about the inconveniences caused by these issues.


If you are a subscriber of X-Payments Hosted solution, please create a ticket in your Help Desk account and we'll apply the update for you for free. If you use a downloadable X-Payments solution, you should update it yourself following the instructions here or we can do it for you within our support services upon your request in Help Desk.

See also

Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade
PA-DSS implementation guide for X-Cart Payments 3