View source for X-Payments:V. 3.1.3 Released

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

==Bug Fixes== 

<ul><li><strong>3-D secure.</strong> In some cases, the trigger used to miscount payment attempts and cause issues placing an order again after one unsuccessful payment attempt. <strong>Fixed.</strong></li>
<li><strong>Duplicate payments issue.</strong> In some cases, payments that were detected as duplicate and removed from the system used to show up again. <strong>Fixed.</strong></li>
<li><strong>Cardholder data key regeneration.</strong> 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 <strong>fixed</strong> the issue and the key regeneration process is now fully automated. </li>
<li><strong>Expired authorization issue.</strong> Records of expired authorizations for a disabled or deleted shopping cart remained in the system and used to prevent cron from completing. <strong>Fixed.</strong></li>	
<li><strong>State field issue in Bluesnap.</strong> 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. <strong>Fixed. </strong></li>
<li><strong>Bambora:</strong> bugs in 3-D Secure process. <strong>Fixed.</strong></li>
<li><strong>NMI.</strong> The system did not receive CVV check results. <strong>Fixed. </strong></li>
<li><strong>Realex, Elavon (Realex API), Global Iris:</strong> issues with tokenization. <strong>Fixed. </strong></li>
<li><strong>Bundle configuration.</strong> Clicking the button used to create a copy of bundle configuration. <strong>Fixed.</strong></li>
 </ul>

Apart from fixing bugs we are constantly working on enhancing X-Payments. 

==Improvements==

<ul>
<li><strong>Expired authorization.</strong> 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.  </li>
<li><strong>NMI:</strong> improved response parsing. </li>
<li><strong>Worldpay Direct:</strong> we added GBP to the supported currencies list. </li>
<li><strong>API.</strong> 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. </li>
</ul>


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

<strong>IMPORTANT:</strong> We will be performing software upgrades for <strong>X-Payments Hosted</strong> users starting July,16 – free of charge, of course. 

If you use <strong>X-Payments Enterprise v. 3.x</strong>, please find the upgrade pack in the File Area section in [https://secure.x-cart.com/ HelpDesk]. [https://www.x-payments.com/help/X-Payments:Upgrading Upgrade Instructions.] You are always welcome to [https://secure.x-cart.com/ submit a request for our support team], should you need any help performing the upgrade.

If you use <strong>X-Payments Enterprise v. 1.x - 2.x</strong>, you will need to upgrade your X-Payments license first. Please [https://www.x-payments.com/contact-us.html contact our specialists] for assistance.