X-Payments:V. 3.1.3 Released

From X-Payments Help
Revision as of 13:32, 16 July 2018 by Nastya (talk | contribs) (Created page with "We have released a fresh X-Payments v. 3.1.3. We’ve addressed a few annoying bugs, so update is strongly recommended. These are the issues that have been fixed: <ul><li>...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

We have released a fresh X-Payments v. 3.1.3. We’ve addressed a few annoying bugs, so update is strongly recommended.

These are the issues that have been fixed:

  • 3-D secure. In some cases, the trigger used to miscount payment attempts and cause issues placing an order again after one unsuccessful payment attempt. Fixed.
  • Duplicate payments issue. In some cases, payments that were detected as duplicate and removed from the system used to show up again. Fixed.
  • Cardholder data key regeneration. In one of the previous versions we implemented automatic cardholder key regeneration but the system used to send out numerous reminder emails of expired data key. We fixed the issue and the key regeneration process is now fully automated.
  • Expired authorization issue. Records of expired authorizations for a disabled or deleted shopping cart remained in the system and used to prevent cron from completing. Fixed.
  • State field issue in Bluesnap. The system used to send information from the state field regardless of the country causing errors in processing payments for countries that do not have any state. Fixed.
  • Bambora: bugs in 3-D Secure process. Fixed.
  • NMI. The system did not receive CVV check results. Fixed.
  • Realex, Elavon (Realex API), Global Iris: issues with tokenization. Fixed.
  • Bundle configuration. Clicking the button used to create a copy of bundle configuration. Fixed.

Apart from fixing bugs we are constantly working on enhancing X-Payments. Here are the improvements that we included in this release:

  • Expired authorization. In previous versions of X-Payments, payments that were in ‘Authorized’ status for 30 days were automatically marked as ‘Void’. Now it checks the status of the payment with the issuing bank before considering it void.
  • NMI: improved response parsing.
  • Worldpay Direct: we added GBP to the supported currencies list.
  • API. Providing shipping address is now not required to initiate a payment or can be partially filled in. Also we corrected minor issues with response for API recharge request.

We implemented a number of other minor changes and improvements as well.

IMPORTANT: We will be performing software upgrades for X-Payments Hosted users during this week – free of charge, of course.

If you use X-Payments Enterprise, please find the upgrade pack in the File Area section in HelpDesk. Upgrade Instructions.

You are always welcome to submit a request for our support team if you need any help performing the upgrade.