https://www.x-payments.com/help/api.php?action=feedcontributions&feedformat=atom&user=AnimaX-Payments Help - User contributions [en]2026-04-20T20:06:42ZUser contributionsMediaWiki 1.31.5https://www.x-payments.com/help/?title=X-Payments:V3.1.2_released&diff=1532X-Payments:V3.1.2 released2018-05-02T10:47:16Z<p>Anima: /* Upgrading Instructions */</p>
<hr />
<div>The new version comes with multiple improvements, security updates and several bug fixes. Here is a quick overview of the latest changes we've done in X-Payments:<br />
<br />
<br />
==Updates in Payment Gateways Integrations==<br />
<ul><br />
<li>'''Authorize.Net''': added a setting that enables the creation of the CIM profile before the transaction. In the previous versions, a profile either wasn't created at all (if the tokenization is turned off) or was created only after the transaction. As a result, due to Authorize.Net specific aspects, the first transaction was not tied to further transactions done with the token. Note: if you select to create the CIM profile before the payment, you'll need to pay a small commission for each authorization (a zero-dollar or one-cent) transaction .</li><br />
<li>'''Sage US''': renamed to Paya and got a new logo.</li><br />
<li>'''Elavon Converge''': updated endpoint URLs according to the latest changes on the Elavon side;</li><br />
<li>'''BlueSnap''': added support for phone fields and soft-descriptor. The soft-descriptor parameter lets you send transaction-specific data along with your request, which your buyers will see on their credit card statement.</li><br />
<li>'''eSelectPlus''': added a setting that allows disabling AVS check. You may want to disable it because it’s not compatible with particular merchant accounts and results in failed payments from them.</li><br />
<li>'''RBS Worldpay Corporate gateway''': fixed issues related to payments from modern merchant accounts.</li><br />
</ul><br />
<br />
==Other Improvements==<br />
<ul><br />
<li>New setting that allows enabling ‘Save card’ checkbox by default.</li><br />
<li>Ability to hide ‘Cardholder name’ entry on the payment form to simplify the checkout process for customers. X-Payments will still pass the cardholder name to the payment gateway, but it will use the one from the billing address.</li><br />
<li>Enabled logging of email sending attempts.</li><br />
<li>Ability to control the number of allowed payment attempts that a customer can take before X-Payments considers the order declined and returns it to the shopping cart. (New setting in X-Payments general settings -> Payments -> Maximum allowed payment attempts.)</li><br />
<li>New config setting that cleans line items names from special symbols. These symbols might result in failed transactions because not all payment gateways support them. The setting is enabled by default.</li><br />
<li>Detection of duplicate payments with same reference ID and total when creating a new payment via an API call. If the original payment was successful, X-Payments won’t allow the second one come through to avoid refunds and chargebacks.</li><br />
<li>Removed ‘developer’ mode for HTTP shopping cart connections for security purposes.</li><br />
<li>Support for PHP 7.2.</li><br />
<li>New X-Payments API 1.9 returns all important payment details in a single API request instead of multiple API calls. As a result, the whole payment process has become faster. X-Payments won't send callbacks with that data because the connector module gets them itself via the API. Now the callbacks are sent only if the payment is changed in X-Payments by the store admin or by a callback from a payment gateway.</li><br />
</ul><br />
<br />
==Fixed Bugs==<br />
<ul><br />
<li>SMS code re-sending didn’t work immediately after 30 seconds. Fixed.</li><br />
<li>Outdated Kount logs were not deleted by cron (automatically after certain period of time). Fixed.</li><br />
<li>In case of a connection error, a payment was considered as still being submitted in some cases. Fixed.</li><br />
<li>Administrators with access to edit payment configurations still couldn’t update antifraud settings for them. Fixed.</li><br />
</ul><br />
<br />
==Upgrading Instructions==<br />
<br />
If your X-Payments runs v1.x, v2.x or v3.0.x, you should first upgrade to v3.1.0 or v3.1.1 and only after this to v3.1.2. <br />
<br />
Our support team upgrades X-Payments Hosted accounts free of charge. They do it as soon as every new version is available. So, you don't have to think about it. If you are subscribed to any X-Payments Hosted plan, your account has already been upgraded.<br />
<br />
Owners of X-Payments Downloadable should upgrade their stores themselves following the instructions [https://www.x-payments.com/help/X-Payments:Upgrading here], or buy a support service in their [https://secure.x-cart.com Help Desk account] and have it upgraded by our support team.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.2_released&diff=1494X-Payments:V3.1.2 released2018-04-24T06:11:06Z<p>Anima: /* Updates in Payment Gateways Integrations */</p>
<hr />
<div>The new version comes with multiple improvements, security updates and several bug fixes. Here is a quick overview of the latest changes we've done in X-Payments:<br />
<br />
<br />
==Updates in Payment Gateways Integrations==<br />
<ul><br />
<li>'''Authorize.Net''': added a setting that enables the creation of the CIM profile before the transaction. In the previous versions, a profile either wasn't created at all (if the tokenization is turned off) or was created only after the transaction. As a result, due to Authorize.Net specific aspects, the first transaction was not tied to further transactions done with the token. Note: if you select to create the CIM profile before the payment, you'll need to pay a small commission for each authorization (a zero-dollar or one-cent) transaction .</li><br />
<li>'''Sage US''': renamed to Paya and got a new logo.</li><br />
<li>'''Elavon Converge''': updated endpoint URLs according to the latest changes on the Elavon side;</li><br />
<li>'''BlueSnap''': added support for phone fields and soft-descriptor. The soft-descriptor parameter lets you send transaction-specific data along with your request, which your buyers will see on their credit card statement.</li><br />
<li>'''eSelectPlus''': added a setting that allows disabling AVS check. You may want to disable it because it’s not compatible with particular merchant accounts and results in failed payments from them.</li><br />
<li>'''RBS Worldpay Corporate gateway''': fixed issues related to payments from modern merchant accounts.</li><br />
</ul><br />
<br />
==Other Improvements==<br />
<ul><br />
<li>New setting that allows enabling ‘Save card’ checkbox by default.</li><br />
<li>Ability to hide ‘Cardholder name’ entry on the payment form to simplify the checkout process for customers. X-Payments will still pass the cardholder name to the payment gateway, but it will use the one from the billing address.</li><br />
<li>Enabled logging of email sending attempts.</li><br />
<li>Ability to control the number of allowed payment attempts that a customer can take before X-Payments considers the order declined and returns it to the shopping cart. (New setting in X-Payments general settings -> Payments -> Maximum allowed payment attempts.)</li><br />
<li>New config setting that cleans line items names from special symbols. These symbols might result in failed transactions because not all payment gateways support them. The setting is enabled by default.</li><br />
<li>Detection of duplicate payments with same reference ID and total when creating a new payment via an API call. If the original payment was successful, X-Payments won’t allow the second one come through to avoid refunds and chargebacks.</li><br />
<li>Removed ‘developer’ mode for HTTP shopping cart connections for security purposes.</li><br />
<li>Support for PHP 7.2.</li><br />
<li>New X-Payments API 1.9 returns all important payment details in a single API request instead of multiple API calls. As a result, the whole payment process has become faster. X-Payments won't send callbacks with that data because the connector module gets them itself via the API. Now the callbacks are sent only if the payment is changed in X-Payments by the store admin or by a callback from a payment gateway.</li><br />
</ul><br />
<br />
==Fixed Bugs==<br />
<ul><br />
<li>SMS code re-sending didn’t work immediately after 30 seconds. Fixed.</li><br />
<li>Outdated Kount logs were not deleted by cron (automatically after certain period of time). Fixed.</li><br />
<li>In case of a connection error, a payment was considered as still being submitted in some cases. Fixed.</li><br />
<li>Administrators with access to edit payment configurations still couldn’t update antifraud settings for them. Fixed.</li><br />
</ul><br />
<br />
==Upgrading Instructions==<br />
<br />
If your X-Payments runs v1.x, v2.x or v3.0.x, you should first upgrade to v3.1.0 or v3.1.1 and only after this to v3.1.2. <br />
<br />
Our support team upgrades X-Payments Hosted accounts free of charge. Just create a ticket in your [https://secure.x-cart.com Help Desk account] and request the upgrade.<br />
<br />
Owners of X-Payments Downloadable can upgrade their stores themselves following the instructions [https://www.x-payments.com/help/X-Payments:Upgrading here], or buy a support service in their [https://secure.x-cart.com Help Desk account] and have it upgraded by our support team.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.2_released&diff=1493X-Payments:V3.1.2 released2018-04-24T06:10:06Z<p>Anima: </p>
<hr />
<div>The new version comes with multiple improvements, security updates and several bug fixes. Here is a quick overview of the latest changes we've done in X-Payments:<br />
<br />
<br />
==Updates in Payment Gateways Integrations==<br />
<ul><br />
<li>'''Authorize.Net''': added a setting that enables the creation of the CIM profile before the transaction. In the previous versions, a profile either wasn't created at all (if the tokenization is turned off) or was created only after the transaction. As a result, due to Authorize.Net specific aspects, the first transaction was not tied to further transactions done with the token. Note: if you select to create the CIM profile before the payment, you'll need to pay the commission for the authorization transaction (a zero-dollar or one-cent transaction).</li><br />
<li>'''Sage US''': renamed to Paya and got a new logo.</li><br />
<li>'''Elavon Converge''': updated endpoint URLs according to the latest changes on the Elavon side;</li><br />
<li>'''BlueSnap''': added support for phone fields and soft-descriptor. The soft-descriptor parameter lets you send transaction-specific data along with your request, which your buyers will see on their credit card statement.</li><br />
<li>'''eSelectPlus''': added a setting that allows disabling AVS check. You may want to disable it because it’s not compatible with particular merchant accounts and results in failed payments from them.</li><br />
<li>'''RBS Worldpay Corporate gateway''': fixed issues related to payments from modern merchant accounts.</li><br />
</ul><br />
<br />
==Other Improvements==<br />
<ul><br />
<li>New setting that allows enabling ‘Save card’ checkbox by default.</li><br />
<li>Ability to hide ‘Cardholder name’ entry on the payment form to simplify the checkout process for customers. X-Payments will still pass the cardholder name to the payment gateway, but it will use the one from the billing address.</li><br />
<li>Enabled logging of email sending attempts.</li><br />
<li>Ability to control the number of allowed payment attempts that a customer can take before X-Payments considers the order declined and returns it to the shopping cart. (New setting in X-Payments general settings -> Payments -> Maximum allowed payment attempts.)</li><br />
<li>New config setting that cleans line items names from special symbols. These symbols might result in failed transactions because not all payment gateways support them. The setting is enabled by default.</li><br />
<li>Detection of duplicate payments with same reference ID and total when creating a new payment via an API call. If the original payment was successful, X-Payments won’t allow the second one come through to avoid refunds and chargebacks.</li><br />
<li>Removed ‘developer’ mode for HTTP shopping cart connections for security purposes.</li><br />
<li>Support for PHP 7.2.</li><br />
<li>New X-Payments API 1.9 returns all important payment details in a single API request instead of multiple API calls. As a result, the whole payment process has become faster. X-Payments won't send callbacks with that data because the connector module gets them itself via the API. Now the callbacks are sent only if the payment is changed in X-Payments by the store admin or by a callback from a payment gateway.</li><br />
</ul><br />
<br />
==Fixed Bugs==<br />
<ul><br />
<li>SMS code re-sending didn’t work immediately after 30 seconds. Fixed.</li><br />
<li>Outdated Kount logs were not deleted by cron (automatically after certain period of time). Fixed.</li><br />
<li>In case of a connection error, a payment was considered as still being submitted in some cases. Fixed.</li><br />
<li>Administrators with access to edit payment configurations still couldn’t update antifraud settings for them. Fixed.</li><br />
</ul><br />
<br />
==Upgrading Instructions==<br />
<br />
If your X-Payments runs v1.x, v2.x or v3.0.x, you should first upgrade to v3.1.0 or v3.1.1 and only after this to v3.1.2. <br />
<br />
Our support team upgrades X-Payments Hosted accounts free of charge. Just create a ticket in your [https://secure.x-cart.com Help Desk account] and request the upgrade.<br />
<br />
Owners of X-Payments Downloadable can upgrade their stores themselves following the instructions [https://www.x-payments.com/help/X-Payments:Upgrading here], or buy a support service in their [https://secure.x-cart.com Help Desk account] and have it upgraded by our support team.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.2_released&diff=1488X-Payments:V3.1.2 released2018-04-20T07:43:12Z<p>Anima: </p>
<hr />
<div>The new version comes with multiple improvements, security updates and several bug fixes. Here is a quick overview:<br />
<br />
<br />
==Updates in Payment Gateways Integrations==<br />
<ul><br />
<li>'''Authorize.Net''': added option to create CIM profile before the transaction.</li><br />
<li>'''Sage US''': renamed to Paya and got a new logo.</li><br />
<li>'''Elavon Converge''': updated endpoint URLs according to the new server name of the payment gateway;</li><br />
<li>'''BlueSnap''': added support for phone fields and soft-descriptor. The soft-descriptor parameter lets you send transaction-specific data along with your request, which your buyers will see on their credit card statement.</li><br />
<li>'''eSelectPlus''': added a setting that allows disabling AVS check. You may want to disable it because it’s not compatible with particular merchant accounts and results in failed payments from them.</li><br />
<li>'''RBS Worldpay Corporate gateway''': fixed issues related to payments from modern merchant accounts.</li><br />
</ul><br />
<br />
==Other Improvements==<br />
<ul><br />
<li>New setting that allows enabling ‘Save card’ checkbox by default.</li><br />
<li>Ability to hide ‘Cardholder name’ entry on the payment form to simplify the checkout process for customers. X-Payments will still pass the cardholder name to the payment gateway, but it will use the one from the billing address.</li><br />
<li>Enabled logging of email sending attempts.</li><br />
<li>Ability to control the number of allowed payment attempts that a customer can take before X-Payments considers the order declined and returns it to the shopping cart. (New setting in X-Payments general settings -> Payments -> Maximum allowed payment attempts.)</li><br />
<li>New config setting that cleans line items names from special symbols. These symbols might result in failed transactions because not all payment gateways support them. The setting is enabled by default.</li><br />
<li>Detection of duplicate payments with same reference ID and total when creating a new payment via an API call. If the original payment was successful, X-Payments won’t allow the second one come through to avoid refunds and chargebacks.</li><br />
<li>Removed ‘developer’ mode for HTTP shopping cart connections for security purposes.</li><br />
<li>Support for PHP 7.2.</li><br />
<li>New X-Payments API 1.9 processes the payment transactions with fewer callbacks to the X-Payments server. The shopping cart doesn’t require the callbacks, it gets the results itself. As a result, the whole process has become faster without deadlocks and errors in log files that used to be caused by the high number of the callbacks.</li><br />
<li>Other minor feature and security improvements and bugfixes.</li><br />
</ul><br />
<br />
==Fixed Bugs==<br />
<ul><br />
<li>SMS code re-sending didn’t work immediately after 30 seconds. Fixed.</li><br />
<li>Outdated Kount logs were not deleted by cron (automatically after certain period of time). Fixed.</li><br />
<li>In case of a connection error, a payment was considered as still being submitted in some cases. Fixed.</li><br />
<li>Administrators with access to edit payment configurations still couldn’t update antifraud settings for them. Fixed.</li><br />
</ul><br />
<br />
==Upgrading Instructions==<br />
<br />
If your X-Payments runs v1.x, v2.x or v3.0.x, you should first upgrade to v3.1.0 or v3.1.1 and only after this to v3.1.2. <br />
<br />
Our support team upgrades X-Payments Hosted accounts free of charge. Just create a ticket in your [https://secure.x-cart.com Help Desk account] and request the upgrade.<br />
<br />
Owners of X-Payments Downloadable can upgrade their stores themselves following the instructions [https://www.x-payments.com/help/X-Payments:Upgrading here], or buy a support service in their [https://secure.x-cart.com Help Desk account] and have it upgraded by our support team.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.2_released&diff=1487X-Payments:V3.1.2 released2018-04-20T07:42:08Z<p>Anima: </p>
<hr />
<div>The new version comes with multiple improvements, security updates and several bug fixes. Here is a quick overview:<br />
<br />
<br />
==Updates in Payment Gateways Integrations==<br />
<ul><br />
<li>'''Authorize.Net''': added option to create CIM profile before the transaction.</li><br />
<li>'''Sage US''': renamed to Paya and got a new logo.</li><br />
<li>'''Elavon Converge''': updated endpoint URLs according to the new server name of the payment gateway;</li><br />
<li>'''BlueSnap''': added support for phone fields and soft-descriptor. The soft-descriptor parameter lets you send transaction-specific data along with your request, which your buyers will see on their credit card statement.</li><br />
<li>'''eSelectPlus''': added a setting that allows disabling AVS check. You may want to disable it because it’s not compatible with particular merchant accounts and results in failed payments from them.</li><br />
<li>'''RBS Worldpay Corporate gateway''': fixed issues related to payments from modern merchant accounts.</li><br />
</ul><br />
<br />
==Other Improvements==<br />
<ul><br />
<li>New setting that allows enabling ‘Save card’ checkbox by default.</li><br />
<li>Ability to hide ‘Cardholder name’ entry on the payment form to simplify the checkout process for customers. X-Payments will still pass the cardholder name to the payment gateway, but it will use the one from the billing address.</li><br />
<li>Enabled logging of email sending attempts.</li><br />
<li>Ability to control the number of allowed payment attempts that a customer can take before X-Payments considers the order declined and returns it to the shopping cart. (New setting in X-Payments general settings -> Payments -> Maximum allowed payment attempts.)</li><br />
<li>New config setting that cleans line items names from special symbols. These symbols might result in failed transactions because not all payment gateways support them. The setting is enabled by default.</li><br />
<li>Detection of duplicate payments with same reference ID and total when creating a new payment via an API call. If the original payment was successful, X-Payments won’t allow the second one come through to avoid refunds and chargebacks.</li><br />
<li>Removed ‘developer’ mode for HTTP shopping cart connections for security purposes.</li><br />
<li>Support for PHP 7.2.</li><br />
<li>New X-Payments API 1.9 processes the payment transactions with fewer callbacks to the X-Payments server. The shopping cart doesn’t require the callbacks, it gets the results itself. As a result, the whole process has become faster without deadlocks and errors in log files that used to be caused by the high number of the callbacks.</li><br />
<li>Other minor feature and security improvements and bugfixes.</li><br />
</ul><br />
<br />
<br />
==Fixed Bugs==<br />
<ul><br />
<li>SMS code re-sending didn’t work immediately after 30 seconds. Fixed.</li><br />
<li>Outdated Kount logs were not deleted by cron (automatically after certain period of time). Fixed.</li><br />
<li>In case of a connection error, a payment was considered as still being submitted in some cases. Fixed.</li><br />
<li>Administrators with access to edit payment configurations still couldn’t update antifraud settings for them. Fixed.</li><br />
</ul><br />
<br />
==Upgrading Instructions==<br />
<br />
If your X-Payments runs v1.x, v2.x or v3.0.x, you should first upgrade to v3.1.0 or v3.1.1 and only after this to v3.1.2. <br />
<br />
Our support team upgrades X-Payments Hosted accounts free of charge. Just create a ticket in your [https://secure.x-cart.com Help Desk account] and request the upgrade.<br />
<br />
Owners of X-Payments Downloadable can upgrade their stores themselves following the instructions [https://www.x-payments.com/help/X-Payments:Upgrading here], or buy a support service in their [https://secure.x-cart.com Help Desk account] and have it upgraded by our support team.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.2_released&diff=1486X-Payments:V3.1.2 released2018-04-19T13:47:57Z<p>Anima: Created page with "The new version comes with multiple improvements and several bug fixes. Here is a quick overview: ==Updates in Payment Gateways Integrations== <ul> <li>'''Authorize.Net''':..."</p>
<hr />
<div>The new version comes with multiple improvements and several bug fixes. Here is a quick overview:<br />
<br />
<br />
==Updates in Payment Gateways Integrations==<br />
<ul><br />
<li>'''Authorize.Net''': added option to create CIM profile before the transaction.</li><br />
<li>'''Sage US''': renamed to Paya and got a new logo.</li><br />
<li>'''Elavon Converge''': updated endpoint URLs according to the new server name of the payment gateway;</li><br />
<li>'''BlueSnap''': added support for phone fields and soft-descriptor. The soft-descriptor parameter lets you send transaction-specific data along with your request, which your buyers will see on their credit card statement.</li><br />
<li>'''eSelectPlus''': added a setting that allows disabling AVS check. You may want to disable it because it’s not compatible with particular merchant accounts and results in failed payments from them.</li><br />
<li>'''RBS Worldpay Corporate gateway''': fixed issues related to payments from modern merchant accounts.</li><br />
</ul><br />
<br />
==Other Improvements==<br />
<ul><br />
<li>New setting that allows enabling ‘Save card’ checkbox by default.</li><br />
<li>Ability to hide ‘Cardholder name’ entry on the payment form to simplify the checkout process for customers. X-Payments will still pass the cardholder name to the payment gateway, but it will use the one from the billing address.</li><br />
<li>Enabled logging of email sending attempts.</li><br />
<li>Ability to control the number of allowed payment attempts that X-Payments will take before considering the order declined and returning it to the shopping cart. (New setting in X-Payments general settings -> Payments -> Maximum allowed payment attempts.)</li><br />
<li>New config setting that cleans line items names from special symbols. These symbols might result in failed transactions because not all payment gateways support them. The setting is enabled by default.</li><br />
<li>Detection of duplicate payments with same reference ID and total when creating a new payment via an API call. If the original payment was successful, X-Payments won’t allow the second one come through to avoid refunds and chargebacks.</li><br />
<li>Removed ‘developer’ mode for HTTP shopping cart connections for security purposes.</li><br />
<li>Support for PHP 7.2.</li><br />
<li>New X-Payments API 1.9 processes the payment transactions with fewer callbacks to the X-Payments server. The shopping cart doesn’t require the callbacks, it gets the results itself. As a result, the whole process has become faster without deadlocks and errors in log files that used to be caused by the high number of the callbacks.</li><br />
<li>Other minor feature and security improvements and bugfixes.</li><br />
</ul><br />
<br />
<br />
==Fixed Bugs==<br />
<ul><br />
<li>SMS code re-sending didn’t work immediately after 30 seconds. Fixed.</li><br />
<li>Outdated Kount logs were not deleted by cron (automatically after certain period of time). Fixed.</li><br />
<li>In case of a connection error, a payment was considered as still being submitted in some cases. Fixed.</li><br />
<li>Administrators with access to edit payment configurations still couldn’t update antifraud settings for them. Fixed.</li><br />
</ul><br />
<br />
==Upgrading Instructions==<br />
<br />
If your X-Payments runs v1.x, v2.x or v3.0.x, you should first upgrade to v3.1.0 or v3.1.1 and only after this to v3.1.2. <br />
<br />
Our support team upgrades X-Payments Hosted accounts free of charge. Just create a ticket in your [https://secure.x-cart.com Help Desk account] and request the upgrade.<br />
<br />
Owners of X-Payments Downloadable can upgrade their stores themselves following the instructions [https://www.x-payments.com/help/X-Payments:Upgrading here], or buy a support service in their [https://secure.x-cart.com Help Desk account] and have it upgraded by our support team.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.1_released&diff=1143X-Payments:V3.1.1 released2017-12-14T09:26:49Z<p>Anima: /* Other issues */</p>
<hr />
<div>The v3.1.1 is a bugfix release. Here is a list of bugs and errors that have been repaired:<br />
<br />
==Payment gateways integrations==<br />
<ul><br />
<li>Authorize.net: Refunds didn’t work;</li><br />
<li>eSelect Plus: Multiple payment attempts and addresses without numbers caused errors;</li><br />
<li>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;</li><br />
<li>Bambora: Failed payments and unstable 3d secure feature work;</li><br />
<li>Cybersource: 3D Secure results were passed incorrectly to the gateway;</li><br />
<li>SagePay: Old tokens (saved cards) saved before the integration update didn't work with the new integration;</li><br />
<li>Payeezy: Reference ID was not passed, making it difficult to find the transaction in the Payeezy dashboard;</li><br />
<li>Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.</li><br />
</ul><br />
<br />
==Other issues==<br />
<ul><br />
<li>X-Payments iframe showed up incorrectly in IE8 browser;</li><br />
<li>Built-in recurring payments feature didn’t work. <br><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 [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><br />
<li>Time in logs used to differ from the online store time zone;</li><br />
<li>'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.</li><br />
</ul><br />
<br />
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.<br />
<br />
<br />
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].<br />
<br />
==See also==<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><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]</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1141X-Payments:V3.1.0 released2017-12-12T11:37:02Z<p>Anima: /* Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade */</p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<br />
<li>JCB card type support in PayPal module;</li><br />
<br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
<br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<br />
<li>'''Browser-side JavaScript card data validation''' has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<br />
<li>'''Automatic update of the card expiration date for re-issued cards''' has been enabled on the side of Authorize.Net. This feature is fully supported in X-Payments. If it’s only the expiration date, that has changed, this info will automatically be updated in X-Payments when a customer makes the next purchase using previously saved card (no additional actions from customer or administrator required);</li><br />
<br />
<li>Expired '''[https://www.x-payments.com/help/X-Payments:Encryption_keys cardholder data keys]''' don’t require manual regeneration anymore. X-Payments does it '''automatically'''. </li><br />
<br />
<li>Starting from v3.1.0 the root admin can grant '''permissions for additional user accounts''' in X-Payments back-end to '''edit templates, languages and view logs'''. See the full list of permissions the additional accounts owners may have [https://www.x-payments.com/help/X-Payments:Managing_users here].</li><br />
<br />
<li>Improved support of '''2-series Mastercard BINs''' and updated '''BIN detection for Discover''' network cards.</li><br />
<br />
<li>'''Improved IP addresses determination for stores protected by CloudFlare'''. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<br />
<li>'''Developer mode is now available for test installations without SSL.''' It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<br />
<li>'''OpenSSL''' library is used now instead of deprecated mcrypt library.</li><br />
<br />
<li>'''Removed Solo, Switch, and Laser''' from supported card types as no longer valid.</li><br />
<br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==X-Payments Self-Hosted Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these [https://www.x-payments.com/help/X-Payments:Upgrading instructions].<br />
<br />
==New Cloud-based Infrastructure for X-Payments Hosted Accounts==<br />
<br />
We're moving to a new cloud-based infrastructure and need your assistance. Till the end of August, X-Payments Hosted accounts will be transferred to a new hosting environment. Here are the main reasons for it:<br />
<br />
<ul><br />
<li>Flexibility. No more "X-Payments development" and "X-Payments hosting" as separate entities. As of today, we are one team and feel the full benefits of working in close cooperation with virtually no time lag.</li><br />
<br />
<li>Security. We are moving to Amazon Web Services PCI DSS Level 1 certified data centers so you can be sure that your data is safer than ever.</li><br />
<br />
<li>Optimization. The entire server-side environment was deployed with X-Payments in mind. Therefore we can reach the desired level of performance and security.<br />
I firmly believe that all these changes will make a positive impact on our product and you will notice it yourself. Also, your instance will be upgraded to the latest version of X-Payments 3.1.0. Of course, at no cost.<br />
</li><br />
</ul><br />
<br />
<br />
'''Here's what you should do:'''<br />
<br />
<ul><br />
<li>To start the transition process, please choose the most convenient time for you between August 16 and August 31. We recommend scheduling it for the night-time so that you could avoid losing any transactions. </li><br />
<br />
<li>When the time is set, we will start the transition and notify you once it is complete. Until then, your shopping cart will be communicating with the previous X-Payments installation. </li><br />
<br />
<li>The last step is reconnecting. It is up to you whether you do it yourself or we do it for you. In the latter case, we will need the admin access to your shopping cart and X-Payments instances to get it done. You can post it [https://secure.x-cart.com/customer.php?target=create_access_info here].</li><br />
</ul><br />
<br />
Needless to say, we are not going to disable or delete your current account until you confirm that the new one works as expected.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of [https://www.pcisecuritystandards.org/ PCI-SSC]. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the [https://www.x-payments.com/help/X-Payments:PCI_DSS_implementation_guide PCI-DSS implementation guide] to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy Flexible Plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the [https://www.bambora.com/en/ca/blog/letter-to-beanstreams-customers/?mkt_tok=eyJpIjoiTURNek0ySTJPVEUwT0RBMyIsInQiOiJ1R3hjamV4Z3Z2c3M3anZFMFcycUxxbWJvY1l2SU1ybmpRNXp3MnhiMFJhdlR5V0lwWkZBRFh6RXVGU3VlMUZUTzVcL3R3S3o3OHFPQzNuWFdcLytRTTl0U0xaRG0zbll5OFVHZ0dCZE1NZ0xJNkxHRElCdERGUUkwemVCZ2pjOFpRIn0%3D open letter by their CEO, Johan Tjärnberg].<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
<br />
'''For Canadian clients (CAD)''' Gateway + Merchant account:<br />
<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
'''For Canadian clients (USD)''' Gateway + Merchant account:<br />
<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
'''For USA Clients (USD)''' Gateway + Merchant account:<br />
<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4<br />
<br />
<br />
For any questions and suggestions, you're welcome to contact us at support@x-payments.com.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.1_released&diff=1140X-Payments:V3.1.1 released2017-12-12T11:36:14Z<p>Anima: /* See also */</p>
<hr />
<div>The v3.1.1 is a bugfix release. Here is a list of bugs and errors that have been repaired:<br />
<br />
==Payment gateways integrations==<br />
<ul><br />
<li>Authorize.net: Refunds didn’t work;</li><br />
<li>eSelect Plus: Multiple payment attempts and addresses without numbers caused errors;</li><br />
<li>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;</li><br />
<li>Bambora: Failed payments and unstable 3d secure feature work;</li><br />
<li>Cybersource: 3D Secure results were passed incorrectly to the gateway;</li><br />
<li>SagePay: Old tokens (saved cards) saved before the integration update didn't work with the new integration;</li><br />
<li>Payeezy: Reference ID was not passed, making it difficult to find the transaction in the Payeezy dashboard;</li><br />
<li>Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.</li><br />
</ul><br />
<br />
==Other issues==<br />
<ul><br />
<li>X-Payments iframe showed up incorrectly in IE8 browser;</li><br />
<li>Built-in recurring payments feature didn’t work. <br><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 [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><br />
<li>Time in logs used to differ from the online store time zone;</li><br />
<li>'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.</li><br />
</ul><br />
<br />
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.<br />
<br />
Also, X-Payments v3.1.1 uses the latest version of jQuery.<br />
<br />
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].<br />
<br />
==See also==<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><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]</div>Animahttps://www.x-payments.com/help/?title=X-Payments:Upgrading&diff=1139X-Payments:Upgrading2017-12-12T11:35:11Z<p>Anima: </p>
<hr />
<div><noinclude>{{Template:XP manual TOC}}</noinclude><br />
Upgrading is done with the help of a special upgrade pack. If you are using a downloadable version of X-Payments, and your license allows you to upgrade to later versions, you will find this pack in the <u>File area</u> section of your {{QA}} (Look for a file named like '''upgrade.pack.xp.X.Y.Z.zip''' (ZIP-archive) or '''upgrade.pack.xp.X.Y.Z.tgz''' (TGZ-archive), where X, Y and Z are version numbers). <br />
<br /><br /><br />
'''To upgrade X-Payments, complete the following steps:'''<br />
# Download the X-Payments upgrade pack. <br />
# Connect to your X-Payments server via SSH.<br />
# Extract the X-Payments upgrade pack that you downloaded and upload the extracted pack contents to the root of your X-Payments installation. <br />
# Run the script '''<xpay-dir>/upgrade/upgrade.php''' via the command line as follows:<br />&nbsp;&nbsp;&nbsp;'''php upgrade.php'''<br />The upgrade script will detect your current version automatically and will offer an upgrade to the latest X-Payments version available to you. You will only need to confirm your request by entering "y" (Use "n" to cancel the operation).<br />If necessary, the following parameters may be specified:<br /><br />
#* -vX.X.X - the version to which you want to upgrade; for example, "-v2.2.0";<br />
#* -oY.Y.Y - the version from which you are upgrading; for example, "-o2.1.3" (This parameter should be used if, for example, the version in the config/config.ini.php file of your X-Payments installation is specified incorrectly);<br />
#* -y - specify this to skip the step where you need to confirm your intention to upgrade (where you need to enter y/n).<br />For example, to upgrade from version 1.0.4 to 1.0.6, you will need to use the command<br />&nbsp;&nbsp;&nbsp;'''php upgrade.php -o1.0.4 -v1.0.6'''<br />The upgrade script will recognize the following X-Payments versions: 1.0.3, 1.0.4, 1.0.5, 1.0.6, 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.2.0, 2.2.1, 2.2.2, 3.0.0, 3.0.1.<br />Note that for X-Payments versions 1.0.3 and 1.0.4 you ''must'' specify the version from which you are upgrading using the -o parameter, since the config/config.ini.php file of these versions does not contain the version information upgrade.php expects to find there.<br /><br />
Once the script is run, it will create a backup of your X-Payments installation and carry out the upgrade for you. <br />
After upgrading has been completed, be sure to remove the directory '''<xpay-dir>/upgrade/''' (That is done for security purposes; remember that X-Payments must be a stand alone service on a separate server, so you must not keep other applications - including the upgrade script - on the same server while using it).<br />
<br />
In case of any issues, you can find your backup in the directory '''<xpay-dir>/var/backup/'''.<br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of [https://www.x-payments.com/help/X-Payments:Two-factor_authentication 2-factor authentication] for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
<br />
<br />
<noinclude>{{pdf_single}}</noinclude><br />
<br />
<br />
[[Category:X-Payments User Manual]]</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.1_released&diff=1138X-Payments:V3.1.1 released2017-12-12T11:27:55Z<p>Anima: /* Other issues */</p>
<hr />
<div>The v3.1.1 is a bugfix release. Here is a list of bugs and errors that have been repaired:<br />
<br />
==Payment gateways integrations==<br />
<ul><br />
<li>Authorize.net: Refunds didn’t work;</li><br />
<li>eSelect Plus: Multiple payment attempts and addresses without numbers caused errors;</li><br />
<li>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;</li><br />
<li>Bambora: Failed payments and unstable 3d secure feature work;</li><br />
<li>Cybersource: 3D Secure results were passed incorrectly to the gateway;</li><br />
<li>SagePay: Old tokens (saved cards) saved before the integration update didn't work with the new integration;</li><br />
<li>Payeezy: Reference ID was not passed, making it difficult to find the transaction in the Payeezy dashboard;</li><br />
<li>Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.</li><br />
</ul><br />
<br />
==Other issues==<br />
<ul><br />
<li>X-Payments iframe showed up incorrectly in IE8 browser;</li><br />
<li>Built-in recurring payments feature didn’t work. <br><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 [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><br />
<li>Time in logs used to differ from the online store time zone;</li><br />
<li>'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.</li><br />
</ul><br />
<br />
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.<br />
<br />
Also, X-Payments v3.1.1 uses the latest version of jQuery.<br />
<br />
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].<br />
<br />
==See also==<br />
[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><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]</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.1_released&diff=1137X-Payments:V3.1.1 released2017-12-12T11:27:16Z<p>Anima: </p>
<hr />
<div>The v3.1.1 is a bugfix release. Here is a list of bugs and errors that have been repaired:<br />
<br />
==Payment gateways integrations==<br />
<ul><br />
<li>Authorize.net: Refunds didn’t work;</li><br />
<li>eSelect Plus: Multiple payment attempts and addresses without numbers caused errors;</li><br />
<li>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;</li><br />
<li>Bambora: Failed payments and unstable 3d secure feature work;</li><br />
<li>Cybersource: 3D Secure results were passed incorrectly to the gateway;</li><br />
<li>SagePay: Old tokens (saved cards) saved before the integration update didn't work with the new integration;</li><br />
<li>Payeezy: Reference ID was not passed, making it difficult to find the transaction in the Payeezy dashboard;</li><br />
<li>Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.</li><br />
</ul><br />
<br />
==Other issues==<br />
<ul><br />
<li>X-Payments iframe showed up incorrectly in IE8 browser;</li><br />
<li>Built-in recurring payments feature didn’t work. <br><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 [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><br />
<li>Time in logs used to differ from the online store time zone;</li><br />
<li>'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.</li><br />
</ul><br />
<br />
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.<br />
<br />
Also, X-Payments v3.1.0 uses the latest version of jQuery.<br />
<br />
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].<br />
<br />
==See also==<br />
[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><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]</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.1_released&diff=1136X-Payments:V3.1.1 released2017-12-12T10:43:51Z<p>Anima: /* Other issues */</p>
<hr />
<div>The v3.1.0 is a bugfix release. Here is a list of bugs and errors that have been repaired:<br />
<br />
==Payment gateways integrations==<br />
<ul><br />
<li>Authorize.net: Refunds didn’t work;</li><br />
<li>eSelect Plus: Multiple payment attempts and addresses without numbers caused errors;</li><br />
<li>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;</li><br />
<li>Bambora: Failed payments and unstable 3d secure feature work;</li><br />
<li>Cybersource: 3D Secure results were passed incorrectly to the gateway;</li><br />
<li>SagePay: Old tokens (saved cards) saved before the integration update didn't work with the new integration;</li><br />
<li>Payeezy: Reference ID was not passed, making it difficult to find the transaction in the Payeezy dashboard;</li><br />
<li>Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.</li><br />
</ul><br />
<br />
==Other issues==<br />
<ul><br />
<li>X-Payments iframe showed up incorrectly in IE8 browser;</li><br />
<li>Built-in recurring payments feature didn’t work. <br><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 [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><br />
<li>Time in logs used to differ from the online store time zone;</li><br />
<li>'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.</li><br />
</ul><br />
<br />
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.<br />
<br />
Also, X-Payments v3.1.0 uses the latest version of jQuery.<br />
<br />
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].<br />
<br />
==See also==<br />
[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><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]</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.1_released&diff=1135X-Payments:V3.1.1 released2017-12-12T10:37:54Z<p>Anima: </p>
<hr />
<div>The v3.1.0 is a bugfix release. Here is a list of bugs and errors that have been repaired:<br />
<br />
==Payment gateways integrations==<br />
<ul><br />
<li>Authorize.net: Refunds didn’t work;</li><br />
<li>eSelect Plus: Multiple payment attempts and addresses without numbers caused errors;</li><br />
<li>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;</li><br />
<li>Bambora: Failed payments and unstable 3d secure feature work;</li><br />
<li>Cybersource: 3D Secure results were passed incorrectly to the gateway;</li><br />
<li>SagePay: Old tokens (saved cards) saved before the integration update didn't work with the new integration;</li><br />
<li>Payeezy: Reference ID was not passed, making it difficult to find the transaction in the Payeezy dashboard;</li><br />
<li>Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.</li><br />
</ul><br />
<br />
==Other issues==<br />
<ul><br />
<li>X-Payments iframe showed up incorrectly in IE8 browser;</li><br />
<li>Built-in recurring payments feature didn’t work. <br><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 [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><br />
<li>Time in logs used to differ from the online store time zone;</li><br />
<li>'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.</li><br />
</ul><br />
<br />
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.<br />
<br />
Also, X-Payments v3.1.0 uses the latest version of jQuery.<br />
<br />
If you are a subscriber of X-Payments Hosted solution, please create a ticket in your [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 [secure.x-cart.com Help Desk].<br />
<br />
==See also==<br />
[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><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]</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.1_released&diff=1134X-Payments:V3.1.1 released2017-12-12T10:18:50Z<p>Anima: </p>
<hr />
<div>The v3.1.0 is a bugfix release. Here is a list of bugs and errors that have been repaired:<br />
<br />
==Payment gateways integrations==<br />
<ul><br />
<li>Authorize.net: Refunds didn’t work;</li><br />
<li>eSelect Plus: Multiple payment attempts and addresses without numbers caused errors;</li><br />
<li>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;</li><br />
<li>Bambora: Failed payments and unstable 3d secure feature work;</li><br />
<li>Cybersource: 3D Secure results were passed incorrectly to the gateway;</li><br />
<li>SagePay: Old tokens (saved cards) saved before the integration update didn't work with the new integration;</li><br />
<li>Payeezy: Reference ID was not passed, making it difficult to find the transaction in the Payeezy dashboard;</li><br />
<li>Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.</li><br />
</ul><br />
<br />
==Other issues==<br />
<ul><br />
<li>X-Payments iframe showed up incorrectly in IE8 browser;</li><br />
<li>Built-in recurring payments feature didn’t work. <br><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 [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><br />
<li>Time in logs used to differ from the online store time zone;</li><br />
<li>'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.</li><br />
</ul><br />
<br />
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.<br />
<br />
Also, X-Payments v3.1.0 uses the latest version of jQuery.<br />
<br />
==See also==<br />
[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><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]</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.1_released&diff=1133X-Payments:V3.1.1 released2017-12-12T10:16:06Z<p>Anima: 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..."</p>
<hr />
<div>The v3.1.0 is a bugfix release. Here is a list of bugs and errors that have been repaired:<br />
<br />
==Payment gateways integrations==<br />
<ul><br />
<li>Authorize.net: Refunds didn’t work;</li><br />
<li>eSelect Plus: Multiple payment attempts and addresses without numbers caused errors;</li><br />
<li>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;</li><br />
<li>Bambora: Failed payments and unstable 3d secure feature work;</li><br />
<li>Cybersource: 3D Secure results were passed incorrectly to the gateway;</li><br />
<li>SagePay: Old tokens (saved cards) saved before the integration update didn't work with the new integration;</li><br />
<li>Payeezy: Reference ID was not passed, making it difficult to find the transaction in the Payeezy dashboard;</li><br />
<li>Payflow Pro: Address Verification System didn’t work if the merchant account used FDMS processor.</li><br />
</ul><br />
==Other issues==<br />
<ul><br />
<li>X-Payments iframe showed up incorrectly in IE8 browser;</li><br />
<li>Built-in recurring payments feature didn’t work. <br><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><br />
<li>Time in logs used to differ from the online store time zone;</li><br />
<li>'From' field in email notifications from X-Payments contained a wrong value when using sendmail instead of SMTP.</li><br />
</ul><br />
<br />
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.<br />
<br />
Also, X-Payments v3.1.0 uses the latest version of jQuery.<br />
<br />
==See also==<br />
[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><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]</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1036X-Payments:V3.1.0 released2017-08-23T07:00:50Z<p>Anima: /* Enjoy Flexible Plans from Bambora */</p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<br />
<li>JCB card type support in PayPal module;</li><br />
<br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
<br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<br />
<li>'''Browser-side JavaScript card data validation''' has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<br />
<li>'''Automatic update of the card expiration date for re-issued cards''' has been enabled on the side of Authorize.Net. This feature is fully supported in X-Payments. If it’s only the expiration date, that has changed, this info will automatically be updated in X-Payments when a customer makes the next purchase using previously saved card (no additional actions from customer or administrator required);</li><br />
<br />
<li>Expired '''[https://www.x-payments.com/help/X-Payments:Encryption_keys cardholder data keys]''' don’t require manual regeneration anymore. X-Payments does it '''automatically'''. </li><br />
<br />
<li>Starting from v3.1.0 the root admin can grant '''permissions for additional user accounts''' in X-Payments back-end to '''edit templates, languages and view logs'''. See the full list of permissions the additional accounts owners may have [https://www.x-payments.com/help/X-Payments:Managing_users here].</li><br />
<br />
<li>Improved support of '''2-series Mastercard BINs''' and updated '''BIN detection for Discover''' network cards.</li><br />
<br />
<li>'''Improved IP addresses determination for stores protected by CloudFlare'''. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<br />
<li>'''Developer mode is now available for test installations without SSL.''' It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<br />
<li>'''OpenSSL''' library is used now instead of deprecated mcrypt library.</li><br />
<br />
<li>'''Removed Solo, Switch, and Laser''' from supported card types as no longer valid.</li><br />
<br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these [https://www.x-payments.com/help/X-Payments:Upgrading instructions].<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of [https://www.x-payments.com/help/X-Payments:Two-factor_authentication 2-factor authentication] for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==New Cloud-based Infrastructure for X-Payments Hosted Accounts==<br />
<br />
We're moving to a new cloud-based infrastructure and need your assistance. Till the end of August, X-Payments Hosted accounts will be transferred to a new hosting environment. Here are the main reasons for it:<br />
<br />
<ul><br />
<li>Flexibility. No more "X-Payments development" and "X-Payments hosting" as separate entities. As of today, we are one team and feel the full benefits of working in close cooperation with virtually no time lag.</li><br />
<br />
<li>Security. We are moving to Amazon Web Services PCI DSS Level 1 certified data centers so you can be sure that your data is safer than ever.</li><br />
<br />
<li>Optimization. The entire server-side environment was deployed with X-Payments in mind. Therefore we can reach the desired level of performance and security.<br />
I firmly believe that all these changes will make a positive impact on our product and you will notice it yourself. Also, your instance will be upgraded to the latest version of X-Payments 3.1.0. Of course, at no cost.<br />
</li><br />
</ul><br />
<br />
<br />
'''Here's what you should do:'''<br />
<br />
<ul><br />
<li>To start the transition process, please choose the most convenient time for you between August 16 and August 31. We recommend scheduling it for the night-time so that you could avoid losing any transactions. </li><br />
<br />
<li>When the time is set, we will start the transition and notify you once it is complete. Until then, your shopping cart will be communicating with the previous X-Payments installation. </li><br />
<br />
<li>The last step is reconnecting. It is up to you whether you do it yourself or we do it for you. In the latter case, we will need the admin access to your shopping cart and X-Payments instances to get it done. You can post it [https://secure.x-cart.com/customer.php?target=create_access_info here].</li><br />
</ul><br />
<br />
Needless to say, we are not going to disable or delete your current account until you confirm that the new one works as expected.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of [https://www.pcisecuritystandards.org/ PCI-SSC]. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the [https://www.x-payments.com/help/X-Payments:PCI_DSS_implementation_guide PCI-DSS implementation guide] to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy Flexible Plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the [https://www.bambora.com/en/ca/blog/letter-to-beanstreams-customers/?mkt_tok=eyJpIjoiTURNek0ySTJPVEUwT0RBMyIsInQiOiJ1R3hjamV4Z3Z2c3M3anZFMFcycUxxbWJvY1l2SU1ybmpRNXp3MnhiMFJhdlR5V0lwWkZBRFh6RXVGU3VlMUZUTzVcL3R3S3o3OHFPQzNuWFdcLytRTTl0U0xaRG0zbll5OFVHZ0dCZE1NZ0xJNkxHRElCdERGUUkwemVCZ2pjOFpRIn0%3D open letter by their CEO, Johan Tjärnberg].<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
<br />
'''For Canadian clients (CAD)''' Gateway + Merchant account:<br />
<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
'''For Canadian clients (USD)''' Gateway + Merchant account:<br />
<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
'''For USA Clients (USD)''' Gateway + Merchant account:<br />
<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4<br />
<br />
<br />
For any questions and suggestions, you're welcome to contact us at support@x-payments.com.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1035X-Payments:V3.1.0 released2017-08-23T07:00:17Z<p>Anima: /* Enjoy Flexible Plans from Bambora */</p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<br />
<li>JCB card type support in PayPal module;</li><br />
<br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
<br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<br />
<li>'''Browser-side JavaScript card data validation''' has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<br />
<li>'''Automatic update of the card expiration date for re-issued cards''' has been enabled on the side of Authorize.Net. This feature is fully supported in X-Payments. If it’s only the expiration date, that has changed, this info will automatically be updated in X-Payments when a customer makes the next purchase using previously saved card (no additional actions from customer or administrator required);</li><br />
<br />
<li>Expired '''[https://www.x-payments.com/help/X-Payments:Encryption_keys cardholder data keys]''' don’t require manual regeneration anymore. X-Payments does it '''automatically'''. </li><br />
<br />
<li>Starting from v3.1.0 the root admin can grant '''permissions for additional user accounts''' in X-Payments back-end to '''edit templates, languages and view logs'''. See the full list of permissions the additional accounts owners may have [https://www.x-payments.com/help/X-Payments:Managing_users here].</li><br />
<br />
<li>Improved support of '''2-series Mastercard BINs''' and updated '''BIN detection for Discover''' network cards.</li><br />
<br />
<li>'''Improved IP addresses determination for stores protected by CloudFlare'''. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<br />
<li>'''Developer mode is now available for test installations without SSL.''' It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<br />
<li>'''OpenSSL''' library is used now instead of deprecated mcrypt library.</li><br />
<br />
<li>'''Removed Solo, Switch, and Laser''' from supported card types as no longer valid.</li><br />
<br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these [https://www.x-payments.com/help/X-Payments:Upgrading instructions].<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of [https://www.x-payments.com/help/X-Payments:Two-factor_authentication 2-factor authentication] for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==New Cloud-based Infrastructure for X-Payments Hosted Accounts==<br />
<br />
We're moving to a new cloud-based infrastructure and need your assistance. Till the end of August, X-Payments Hosted accounts will be transferred to a new hosting environment. Here are the main reasons for it:<br />
<br />
<ul><br />
<li>Flexibility. No more "X-Payments development" and "X-Payments hosting" as separate entities. As of today, we are one team and feel the full benefits of working in close cooperation with virtually no time lag.</li><br />
<br />
<li>Security. We are moving to Amazon Web Services PCI DSS Level 1 certified data centers so you can be sure that your data is safer than ever.</li><br />
<br />
<li>Optimization. The entire server-side environment was deployed with X-Payments in mind. Therefore we can reach the desired level of performance and security.<br />
I firmly believe that all these changes will make a positive impact on our product and you will notice it yourself. Also, your instance will be upgraded to the latest version of X-Payments 3.1.0. Of course, at no cost.<br />
</li><br />
</ul><br />
<br />
<br />
'''Here's what you should do:'''<br />
<br />
<ul><br />
<li>To start the transition process, please choose the most convenient time for you between August 16 and August 31. We recommend scheduling it for the night-time so that you could avoid losing any transactions. </li><br />
<br />
<li>When the time is set, we will start the transition and notify you once it is complete. Until then, your shopping cart will be communicating with the previous X-Payments installation. </li><br />
<br />
<li>The last step is reconnecting. It is up to you whether you do it yourself or we do it for you. In the latter case, we will need the admin access to your shopping cart and X-Payments instances to get it done. You can post it [https://secure.x-cart.com/customer.php?target=create_access_info here].</li><br />
</ul><br />
<br />
Needless to say, we are not going to disable or delete your current account until you confirm that the new one works as expected.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of [https://www.pcisecuritystandards.org/ PCI-SSC]. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the [https://www.x-payments.com/help/X-Payments:PCI_DSS_implementation_guide PCI-DSS implementation guide] to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy Flexible Plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the [https://www.bambora.com/en/ca/blog/letter-to-beanstreams-customers/?mkt_tok=eyJpIjoiTURNek0ySTJPVEUwT0RBMyIsInQiOiJ1R3hjamV4Z3Z2c3M3anZFMFcycUxxbWJvY1l2SU1ybmpRNXp3MnhiMFJhdlR5V0lwWkZBRFh6RXVGU3VlMUZUTzVcL3R3S3o3OHFPQzNuWFdcLytRTTl0U0xaRG0zbll5OFVHZ0dCZE1NZ0xJNkxHRElCdERGUUkwemVCZ2pjOFpRIn0%3D open letter by their CEO, Johan Tjärnberg].<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
<br />
'''For Canadian clients (CAD)''' Gateway + Merchant account:<br />
<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
'''For Canadian clients (USD)''' Gateway + Merchant account:<br />
<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
'''For USA Clients (USD)''' Gateway + Merchant account:<br />
<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4<br />
<br />
For any questions and suggestions, you're welcome to contact us at support@x-payments.com.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1034X-Payments:V3.1.0 released2017-08-23T06:14:23Z<p>Anima: </p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<br />
<li>JCB card type support in PayPal module;</li><br />
<br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
<br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<br />
<li>'''Browser-side JavaScript card data validation''' has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<br />
<li>'''Automatic update of the card expiration date for re-issued cards''' has been enabled on the side of Authorize.Net. This feature is fully supported in X-Payments. If it’s only the expiration date, that has changed, this info will automatically be updated in X-Payments when a customer makes the next purchase using previously saved card (no additional actions from customer or administrator required);</li><br />
<br />
<li>Expired '''[https://www.x-payments.com/help/X-Payments:Encryption_keys cardholder data keys]''' don’t require manual regeneration anymore. X-Payments does it '''automatically'''. </li><br />
<br />
<li>Starting from v3.1.0 the root admin can grant '''permissions for additional user accounts''' in X-Payments back-end to '''edit templates, languages and view logs'''. See the full list of permissions the additional accounts owners may have [https://www.x-payments.com/help/X-Payments:Managing_users here].</li><br />
<br />
<li>Improved support of '''2-series Mastercard BINs''' and updated '''BIN detection for Discover''' network cards.</li><br />
<br />
<li>'''Improved IP addresses determination for stores protected by CloudFlare'''. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<br />
<li>'''Developer mode is now available for test installations without SSL.''' It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<br />
<li>'''OpenSSL''' library is used now instead of deprecated mcrypt library.</li><br />
<br />
<li>'''Removed Solo, Switch, and Laser''' from supported card types as no longer valid.</li><br />
<br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these [https://www.x-payments.com/help/X-Payments:Upgrading instructions].<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of [https://www.x-payments.com/help/X-Payments:Two-factor_authentication 2-factor authentication] for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==New Cloud-based Infrastructure for X-Payments Hosted Accounts==<br />
<br />
We're moving to a new cloud-based infrastructure and need your assistance. Till the end of August, X-Payments Hosted accounts will be transferred to a new hosting environment. Here are the main reasons for it:<br />
<br />
<ul><br />
<li>Flexibility. No more "X-Payments development" and "X-Payments hosting" as separate entities. As of today, we are one team and feel the full benefits of working in close cooperation with virtually no time lag.</li><br />
<br />
<li>Security. We are moving to Amazon Web Services PCI DSS Level 1 certified data centers so you can be sure that your data is safer than ever.</li><br />
<br />
<li>Optimization. The entire server-side environment was deployed with X-Payments in mind. Therefore we can reach the desired level of performance and security.<br />
I firmly believe that all these changes will make a positive impact on our product and you will notice it yourself. Also, your instance will be upgraded to the latest version of X-Payments 3.1.0. Of course, at no cost.<br />
</li><br />
</ul><br />
<br />
<br />
'''Here's what you should do:'''<br />
<br />
<ul><br />
<li>To start the transition process, please choose the most convenient time for you between August 16 and August 31. We recommend scheduling it for the night-time so that you could avoid losing any transactions. </li><br />
<br />
<li>When the time is set, we will start the transition and notify you once it is complete. Until then, your shopping cart will be communicating with the previous X-Payments installation. </li><br />
<br />
<li>The last step is reconnecting. It is up to you whether you do it yourself or we do it for you. In the latter case, we will need the admin access to your shopping cart and X-Payments instances to get it done. You can post it [https://secure.x-cart.com/customer.php?target=create_access_info here].</li><br />
</ul><br />
<br />
Needless to say, we are not going to disable or delete your current account until you confirm that the new one works as expected.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of [https://www.pcisecuritystandards.org/ PCI-SSC]. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the [https://www.x-payments.com/help/X-Payments:PCI_DSS_implementation_guide PCI-DSS implementation guide] to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy Flexible Plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the [https://www.bambora.com/en/ca/blog/letter-to-beanstreams-customers/?mkt_tok=eyJpIjoiTURNek0ySTJPVEUwT0RBMyIsInQiOiJ1R3hjamV4Z3Z2c3M3anZFMFcycUxxbWJvY1l2SU1ybmpRNXp3MnhiMFJhdlR5V0lwWkZBRFh6RXVGU3VlMUZUTzVcL3R3S3o3OHFPQzNuWFdcLytRTTl0U0xaRG0zbll5OFVHZ0dCZE1NZ0xJNkxHRElCdERGUUkwemVCZ2pjOFpRIn0%3D open letter by their CEO, Johan Tjärnberg].<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
<br />
'''For Canadian clients (CAD)''' Gateway + Merchant account:<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
'''For Canadian clients (USD)''' Gateway + Merchant account:<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
'''For USA Clients (USD)''' Gateway + Merchant account:<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4<br />
<br />
For any questions and suggestions, you're welcome to contact us at support@x-payments.com.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1033X-Payments:V3.1.0 released2017-08-22T09:34:20Z<p>Anima: /* New Cloud-based Infrastructure for X-Payments Hosted accounts */</p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<br />
<li>JCB card type support in PayPal module;</li><br />
<br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
<br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<br />
<li>'''Browser-side JavaScript card data validation''' has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<br />
<li>'''Automatic update of the card expiration date for re-issued cards''' has been enabled on the side of Authorize.Net. This feature is fully supported in X-Payments. If it’s only the expiration date, that has changed, this info will automatically be updated in X-Payments when a customer makes the next purchase (no additional actions from customer or administrator end required);</li><br />
<br />
<li>Expired '''[https://www.x-payments.com/help/X-Payments:Encryption_keys cardholder data keys]''' don’t require manual regeneration anymore. X-Payments does it '''automatically'''. </li><br />
<br />
<li>Starting from v3.1.0 the root admin can grant '''permissions for additional user accounts''' in X-Payments back-end to '''edit templates, languages and view logs'''. See the full list of permissions the additional accounts owners may have [https://www.x-payments.com/help/X-Payments:Managing_users here].</li><br />
<br />
<li>Improved support of '''2-series Mastercard BINs''' and updated '''BIN detection for Discover''' network cards.</li><br />
<br />
<li>'''Improved IP addresses determination for stores protected by CloudFlare'''. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<br />
<li>'''Developer mode is now available for test installations without SSL.''' It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<br />
<li>'''OpenSSL''' library is used now instead of deprecated mcrypt library.</li><br />
<br />
<li>'''Removed Solo, Switch, and Laser''' from supported card types as no longer valid.</li><br />
<br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these [https://www.x-payments.com/help/X-Payments:Upgrading instructions].<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of [https://www.x-payments.com/help/X-Payments:Two-factor_authentication 2-factor authentication] for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==New Cloud-based Infrastructure for X-Payments Hosted accounts==<br />
<br />
We're moving to a new cloud-based infrastructure and need your assistance. Till the end of August, X-Payments Hosted accounts will be transferred to a new hosting environment. Here are the main reasons for it:<br />
<br />
<ul><br />
<li>Flexibility. No more "X-Payments development" and "X-Payments hosting" as separate entities. As of today, we are one team and feel the full benefits of working in close cooperation with virtually no time lag.</li><br />
<br />
<li>Security. We are moving to Amazon Web Services PCI DSS Level 1 certified data centers so you can be sure that your data is safer than ever.</li><br />
<br />
<li>Optimization. The entire server-side environment was deployed with X-Payments in mind. Therefore we can reach the desired level of performance and security.<br />
I firmly believe that all these changes will make a positive impact on our product and you will notice it yourself. Also, your instance will be upgraded to the latest version of X-Payments 3.1.0. Of course, at no cost.<br />
</li><br />
</ul><br />
<br />
<br />
'''Here's what you should do:'''<br />
<br />
<ul><br />
<li>To start the transition process, please choose the most convenient time for you between August 16 and August 31. We recommend scheduling it for the night-time so that you could avoid losing any transactions. </li><br />
<br />
<li>When the time is set, we will start the transition and notify you once it is complete. Until then, your shopping cart will be communicating with the previous X-Payments installation. </li><br />
<br />
<li>The last step is reconnecting. It is up to you whether you do it yourself or we do it for you. In the latter case, we will need the admin access to your shopping cart and X-Payments instances to get it done. You can post it [https://secure.x-cart.com/customer.php?target=create_access_info here].</li><br />
</ul><br />
<br />
Needless to say, we are not going to disable or delete your current account until you confirm that the new one works as expected.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of [https://www.pcisecuritystandards.org/ PCI-SSC]. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the [https://www.x-payments.com/help/X-Payments:PCI_DSS_implementation_guide PCI-DSS implementation guide] to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy Flexible Plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the [https://www.bambora.com/en/ca/blog/letter-to-beanstreams-customers/?mkt_tok=eyJpIjoiTURNek0ySTJPVEUwT0RBMyIsInQiOiJ1R3hjamV4Z3Z2c3M3anZFMFcycUxxbWJvY1l2SU1ybmpRNXp3MnhiMFJhdlR5V0lwWkZBRFh6RXVGU3VlMUZUTzVcL3R3S3o3OHFPQzNuWFdcLytRTTl0U0xaRG0zbll5OFVHZ0dCZE1NZ0xJNkxHRElCdERGUUkwemVCZ2pjOFpRIn0%3D open letter by their CEO, Johan Tjärnberg].<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
<br />
'''For Canadian clients (CAD)''' Gateway + Merchant account:<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
'''For Canadian clients (USD)''' Gateway + Merchant account:<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
'''For USA Clients (USD)''' Gateway + Merchant account:<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4<br />
<br />
For any questions and suggestions, you're welcome to contact us at support@x-payments.com.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1032X-Payments:V3.1.0 released2017-08-22T09:29:45Z<p>Anima: </p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<br />
<li>JCB card type support in PayPal module;</li><br />
<br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
<br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<br />
<li>'''Browser-side JavaScript card data validation''' has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<br />
<li>'''Automatic update of the card expiration date for re-issued cards''' has been enabled on the side of Authorize.Net. This feature is fully supported in X-Payments. If it’s only the expiration date, that has changed, this info will automatically be updated in X-Payments when a customer makes the next purchase (no additional actions from customer or administrator end required);</li><br />
<br />
<li>Expired '''[https://www.x-payments.com/help/X-Payments:Encryption_keys cardholder data keys]''' don’t require manual regeneration anymore. X-Payments does it '''automatically'''. </li><br />
<br />
<li>Starting from v3.1.0 the root admin can grant '''permissions for additional user accounts''' in X-Payments back-end to '''edit templates, languages and view logs'''. See the full list of permissions the additional accounts owners may have [https://www.x-payments.com/help/X-Payments:Managing_users here].</li><br />
<br />
<li>Improved support of '''2-series Mastercard BINs''' and updated '''BIN detection for Discover''' network cards.</li><br />
<br />
<li>'''Improved IP addresses determination for stores protected by CloudFlare'''. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<br />
<li>'''Developer mode is now available for test installations without SSL.''' It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<br />
<li>'''OpenSSL''' library is used now instead of deprecated mcrypt library.</li><br />
<br />
<li>'''Removed Solo, Switch, and Laser''' from supported card types as no longer valid.</li><br />
<br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these [https://www.x-payments.com/help/X-Payments:Upgrading instructions].<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of [https://www.x-payments.com/help/X-Payments:Two-factor_authentication 2-factor authentication] for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==New Cloud-based Infrastructure for X-Payments Hosted accounts==<br />
<br />
We're planning to move to a new cloud-based infrastructure and need your assistance. Till the end of August, X-Payments Hosted accounts will be transferred to a new hosting environment. Here are the main reasons for it:<br />
<br />
<ul><br />
<li>Flexibility. No more "X-Payments development" and "X-Payments hosting" as separate entities. As of today, we are one team and feel the full benefits of working in close cooperation with virtually no time lag.</li><br />
<br />
<li>Security. We are moving to Amazon Web Services PCI DSS Level 1 certified data centers so you can be sure that your data is safer than ever.</li><br />
<br />
<li>Optimization. The entire server-side environment was deployed with X-Payments in mind. Therefore we can reach the desired level of performance and security.<br />
I firmly believe that all these changes will make a positive impact on our product and you will notice it yourself. Also, your instance will be upgraded to the latest version of X-Payments 3.1.0. Of course, at no cost.<br />
</li><br />
</ul><br />
<br />
<br />
'''Here's what you should do:'''<br />
<br />
<ul><br />
<li>To start the transition process, please choose the most convenient time for you between August 16 and August 31. We recommend scheduling it for the night-time so that you could avoid losing any transactions. </li><br />
<br />
<li>When the time is set, we will start the transition and notify you once it is complete. Until then, your shopping cart will be communicating with the previous X-Payments installation. </li><br />
<br />
<li>The last step is reconnecting. It is up to you whether you do it yourself or we do it for you. In the latter case, we will need the admin access to your shopping cart and X-Payments instances to get it done. You can post it [https://secure.x-cart.com/customer.php?target=create_access_info here].</li><br />
</ul><br />
<br />
Needless to say, we are not going to disable or delete your current account until you confirm that the new one works as expected.<br />
<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of [https://www.pcisecuritystandards.org/ PCI-SSC]. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the [https://www.x-payments.com/help/X-Payments:PCI_DSS_implementation_guide PCI-DSS implementation guide] to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy Flexible Plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the [https://www.bambora.com/en/ca/blog/letter-to-beanstreams-customers/?mkt_tok=eyJpIjoiTURNek0ySTJPVEUwT0RBMyIsInQiOiJ1R3hjamV4Z3Z2c3M3anZFMFcycUxxbWJvY1l2SU1ybmpRNXp3MnhiMFJhdlR5V0lwWkZBRFh6RXVGU3VlMUZUTzVcL3R3S3o3OHFPQzNuWFdcLytRTTl0U0xaRG0zbll5OFVHZ0dCZE1NZ0xJNkxHRElCdERGUUkwemVCZ2pjOFpRIn0%3D open letter by their CEO, Johan Tjärnberg].<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
<br />
'''For Canadian clients (CAD)''' Gateway + Merchant account:<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
'''For Canadian clients (USD)''' Gateway + Merchant account:<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
'''For USA Clients (USD)''' Gateway + Merchant account:<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4<br />
<br />
For any questions and suggestions, you're welcome to contact us at support@x-payments.com.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1028X-Payments:V3.1.0 released2017-08-21T08:19:26Z<p>Anima: </p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<br />
<li>JCB card type support in PayPal module;</li><br />
<br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
<br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<br />
<li>'''Browser-side JavaScript card data validation''' has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<br />
<li>'''Automatic update of the card expiration date for re-issued cards''' has been enabled on the side of Authorize.Net. This feature is fully supported in X-Payments. If it’s only the expiration date, that has changed, this info will automatically be updated in X-Payments when a customer makes the next purchase (no additional actions from customer or administrator end required);</li><br />
<br />
<li>Expired '''[https://www.x-payments.com/help/X-Payments:Encryption_keys cardholder data keys]''' don’t require manual regeneration anymore. X-Payments does it '''automatically'''. </li><br />
<br />
<li>Starting from v3.1.0 the root admin can grant '''permissions for additional user accounts''' in X-Payments back-end to '''edit templates, languages and view logs'''. See the full list of permissions the additional accounts owners may have [https://www.x-payments.com/help/X-Payments:Managing_users here].</li><br />
<br />
<li>Improved support of '''2-series Mastercard BINs''' and updated '''BIN detection for Discover''' network cards.</li><br />
<br />
<li>'''Improved IP addresses determination for stores protected by CloudFlare'''. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<br />
<li>'''Developer mode is now available for test installations without SSL.''' It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<br />
<li>'''OpenSSL''' library is used now instead of deprecated mcrypt library.</li><br />
<br />
<li>'''Removed Solo, Switch, and Laser''' from supported card types as no longer valid.</li><br />
<br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these [https://www.x-payments.com/help/X-Payments:Upgrading instructions].<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of [https://www.x-payments.com/help/X-Payments:Two-factor_authentication 2-factor authentication] for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of [https://www.pcisecuritystandards.org/ PCI-SSC]. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the [https://www.x-payments.com/help/X-Payments:PCI_DSS_implementation_guide PCI-DSS implementation guide] to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy Flexible Plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the [https://www.bambora.com/en/ca/blog/letter-to-beanstreams-customers/?mkt_tok=eyJpIjoiTURNek0ySTJPVEUwT0RBMyIsInQiOiJ1R3hjamV4Z3Z2c3M3anZFMFcycUxxbWJvY1l2SU1ybmpRNXp3MnhiMFJhdlR5V0lwWkZBRFh6RXVGU3VlMUZUTzVcL3R3S3o3OHFPQzNuWFdcLytRTTl0U0xaRG0zbll5OFVHZ0dCZE1NZ0xJNkxHRElCdERGUUkwemVCZ2pjOFpRIn0%3D open letter by their CEO, Johan Tjärnberg].<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
<br />
<br />
'''For Canadian clients (CAD)''' Gateway + Merchant account:<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
'''For Canadian clients (USD)''' Gateway + Merchant account:<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
'''For USA Clients (USD)''' Gateway + Merchant account:<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1023X-Payments:V3.1.0 released2017-08-03T06:19:59Z<p>Anima: </p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<br />
<li>JCB card type support in PayPal module;</li><br />
<br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
<br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<br />
<li>'''Browser-side JavaScript card data validation''' has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<br />
<li>Expired '''[https://www.x-payments.com/help/X-Payments:Encryption_keys cardholder data keys]''' don’t require manual regeneration anymore. X-Payments does it '''automatically'''. </li><br />
<br />
<li>Starting from v3.1.0 the root admin can grant '''permissions for additional user accounts''' in X-Payments back-end to '''edit templates, languages and view logs'''. See the full list of permissions the additional accounts owners may have [https://www.x-payments.com/help/X-Payments:Managing_users here].</li><br />
<br />
<li>Improved support of '''2-series Mastercard BINs''' and updated '''BIN detection for Discover''' network cards.</li><br />
<br />
<li>'''Improved IP addresses determination for stores protected by CloudFlare'''. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<br />
<li>'''Developer mode is now available for test installations without SSL.''' It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<br />
<li>'''OpenSSL''' library is used now instead of deprecated mcrypt library.</li><br />
<br />
<li>'''Removed Solo, Switch, and Laser''' from supported card types as no longer valid.</li><br />
<br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these [https://www.x-payments.com/help/X-Payments:Upgrading instructions].<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of [https://www.x-payments.com/help/X-Payments:Two-factor_authentication 2-factor authentication] for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of [https://www.pcisecuritystandards.org/ PCI-SSC]. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the [https://www.x-payments.com/help/X-Payments:PCI_DSS_implementation_guide PCI-DSS implementation guide] to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy Flexible Plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the [https://www.bambora.com/en/ca/blog/letter-to-beanstreams-customers/?mkt_tok=eyJpIjoiTURNek0ySTJPVEUwT0RBMyIsInQiOiJ1R3hjamV4Z3Z2c3M3anZFMFcycUxxbWJvY1l2SU1ybmpRNXp3MnhiMFJhdlR5V0lwWkZBRFh6RXVGU3VlMUZUTzVcL3R3S3o3OHFPQzNuWFdcLytRTTl0U0xaRG0zbll5OFVHZ0dCZE1NZ0xJNkxHRElCdERGUUkwemVCZ2pjOFpRIn0%3D open letter by their CEO, Johan Tjärnberg].<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
<br />
<br />
'''For Canadian clients (CAD)''' Gateway + Merchant account:<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
'''For Canadian clients (USD)''' Gateway + Merchant account:<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
'''For USA Clients (USD)''' Gateway + Merchant account:<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1022X-Payments:V3.1.0 released2017-08-03T06:18:26Z<p>Anima: </p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<br />
<li>JCB card type support in PayPal module;</li><br />
<br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
<br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<br />
<li>'''Browser-side JavaScript card data validation''' has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<br />
<li>Expired '''[https://www.x-payments.com/help/X-Payments:Encryption_keys cardholder data keys]''' don’t require manual regeneration anymore. X-Payments does it '''automatically'''. </li><br />
<br />
<li>Starting from v3.1.0 the root admin can grant '''permissions for additional user accounts''' in X-Payments back-end to '''edit templates, languages and view logs'''. See the full list of permissions the additional accounts owners may have [https://www.x-payments.com/help/X-Payments:Managing_users here].</li><br />
<br />
<li>Improved support of '''2-series Mastercard BINs''' and updated '''BIN detection for Discover''' network cards.</li><br />
<br />
<li>'''Improved IP addresses determination for stores protected by CloudFlare'''. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<br />
<li>'''Developer mode is now available for test installations without SSL.''' It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<br />
<li>'''OpenSSL''' library is used now instead of deprecated mcrypt library.</li><br />
<br />
<li>'''Removed Solo, Switch, and Laser''' from supported card types as no longer valid.</li><br />
<br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these [https://www.x-payments.com/help/X-Payments:Upgrading instructions].<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of [https://www.x-payments.com/help/X-Payments:Two-factor_authentication 2-factor authentication] for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of [https://www.pcisecuritystandards.org/ PCI-SSC]. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the [https://www.x-payments.com/help/X-Payments:PCI_DSS_implementation_guide PCI-DSS implementation guide] to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy Flexible Plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the open letter by their CEO, Johan Tjärnberg.<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
<br />
<br />
'''For Canadian clients (CAD)''' Gateway + Merchant account:<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
'''For Canadian clients (USD)''' Gateway + Merchant account:<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
'''For USA Clients (USD)''' Gateway + Merchant account:<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1021X-Payments:V3.1.0 released2017-08-03T06:12:34Z<p>Anima: </p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<br />
<li>JCB card type support in PayPal module;</li><br />
<br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
<br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<br />
<li>'''Browser-side JavaScript card data validation''' has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<br />
<li>Expired '''[https://www.x-payments.com/help/X-Payments:Encryption_keys cardholder data keys]''' don’t require manual regeneration anymore. X-Payments does it '''automatically'''. </li><br />
<br />
<li>Starting from v3.1.0 the root admin can grant '''permissions for additional user accounts''' in X-Payments back-end to '''edit templates, languages and view logs'''. See the full list of permissions the additional accounts owners may have [https://www.x-payments.com/help/X-Payments:Managing_users here].</li><br />
<br />
<li>Improved support of '''2-series Mastercard BINs''' and updated '''BIN detection for Discover''' network cards.</li><br />
<br />
<li>'''Improved IP addresses determination for stores protected by CloudFlare'''. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<br />
<li>'''Developer mode is now available for test installations without SSL.''' It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<br />
<li>'''OpenSSL''' library is used now instead of deprecated mcrypt library.</li><br />
<br />
<li>'''Removed Solo, Switch, and Laser''' from supported card types as no longer valid.</li><br />
<br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these [https://www.x-payments.com/help/X-Payments:Upgrading instructions].<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of [https://www.x-payments.com/help/X-Payments:Two-factor_authentication 2-factor authentication] for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of [https://www.pcisecuritystandards.org/ PCI-SSC]. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the [https://www.x-payments.com/help/X-Payments:PCI_DSS_implementation_guide PCI-DSS implementation guide] to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy Flexible Plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the open letter by their CEO, Johan Tjärnberg.<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
<br />
----<br />
<br />
<br />
'''For Canadian clients (CAD)''' Gateway + Merchant account:<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
'''For Canadian clients (USD)''' Gateway + Merchant account:<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
'''For USA Clients (USD)''' Gateway + Merchant account:<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1020X-Payments:V3.1.0 released2017-08-03T06:01:34Z<p>Anima: </p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<li>JCB card type support in PayPal module;</li><br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
</ul><br />
<br />
==UX and Security Improvements==<br />
<br />
<ul><br />
<li>'''[https://www.signifyd.com/x-cart-fraud-protection-partner/ Signifyd] anti fraud screening service''' is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<li>Browser-side JavaScript card data validation has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<li>Expired cardholder data keys don’t require manual regeneration anymore. X-Payments does it automatically. </li><br />
<li>Starting from v3.1.0 the root admin can grant permissions for additional user accounts in X-Payments back-end to edit templates, languages and view logs. See the full list of permissions the additional accounts owners may have here.</li><br />
<li>Improved support of 2-series Mastercard BINs and updated BIN detection for Discover network cards.</li><br />
<li>Improved IP addresses determination for stores protected by CloudFlare. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<li>Developer mode is now available for test installations without SSL. It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<li>OpenSSL library is used now instead of deprecated mcrypt library.</li><br />
<li>Removed Solo, Switch, and Laser from supported card types as no longer valid.</li><br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these instructions.<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
'''Note!''' After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of 2-factor authentication for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of PCI-SSC. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the PCI-DSS implementation guide to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<br />
==Enjoy flexible plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the open letter by their CEO, Johan Tjärnberg.<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
For Canadian clients (CAD) Gateway + Merchant account:<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
For Canadian clients (USD) Gateway + Merchant account:<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
For USA Clients (USD) Gateway + Merchant account:<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1019X-Payments:V3.1.0 released2017-08-03T05:52:46Z<p>Anima: </p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, [https://www.x-payments.com/help/X-Payments:V3.1.0_released#Enjoy_flexible_plans_from_Bambora Bambora] (Beanstream), QuickPay;</li><br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<li>JCB card type support in PayPal module;</li><br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
</ul><br />
<br />
==New UX and Security Goodies==<br />
<br />
<ul><br />
<li>Signifyd anti fraud screening service is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<li>Browser-side JavaScript card data validation has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<li>Expired cardholder data keys don’t require manual regeneration anymore. X-Payments does it automatically. </li><br />
<li>Starting from v3.1.0 the root admin can grant permissions for additional user accounts in X-Payments back-end to edit templates, languages and view logs. See the full list of permissions the additional accounts owners may have here.</li><br />
<li>Improved support of 2-series Mastercard BINs and updated BIN detection for Discover network cards.</li><br />
<li>Improved IP addresses determination for stores protected by CloudFlare. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<li>Developer mode is now available for test installations without SSL. It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<li>OpenSSL library is used now instead of deprecated mcrypt library.</li><br />
<li>Removed Solo, Switch, and Laser from supported card types as no longer valid.</li><br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these instructions.<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
Note! After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of 2-factor authentication for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of PCI-SSC. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the PCI-DSS implementation guide to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<a id="bambora"></a><br />
==Enjoy flexible plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the open letter by their CEO, Johan Tjärnberg.<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
For Canadian clients (CAD) Gateway + Merchant account:<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
For Canadian clients (USD) Gateway + Merchant account:<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
For USA Clients (USD) Gateway + Merchant account:<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4</div>Animahttps://www.x-payments.com/help/?title=X-Payments:V3.1.0_released&diff=1018X-Payments:V3.1.0 released2017-08-03T05:51:13Z<p>Anima: Created page with "Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixe..."</p>
<hr />
<div>Our devs never stop working on making X-Cart Payments maximum convenient and efficient for you. So, here is X-Payments 3.1.0 with multiple improvements, new features, and fixes.<br />
<br />
==Payment Gateways ==<br />
<br />
<ul><br />
<li>New payment gateways added: Worldpay Total US, BlueSnap, <a href="https://www.x-payments.com/help/?title=X-Payments:V3.1.0_released#bambora”>Bambora</a> (Beanstream), QuickPay;</li><br />
<li>Virtual Merchant module renamed to Elavon Converge;</li><br />
<li>Tokenization (a PCI compliant method to store credit cards) added for iTransact, Elavon Converge and fixed for Payflow Pro;</li><br />
<li>Support for fraud management and other improvements in Authorize.net integration;</li><br />
<li>JCB card type support in PayPal module;</li><br />
<li>Fixed issues related to Heidelpay module test/live mode.</li><br />
</ul><br />
<br />
==New UX and Security Goodies==<br />
<br />
<ul><br />
<li>Signifyd anti fraud screening service is now available in X-Payments in addition to Kount and NoFraud. So, now you can choose the one which better meets your needs.</li><br />
<li>Browser-side JavaScript card data validation has been developed. Sounds complicated but, in fact, it’s simple. Due to this update, if there is a typo in the submitted card info, the page won’t reload after validation losing the entered data. Your buyers will see a warning and will only need to edit the card number, but not waste time filling in the fields anew.</li><br />
<li>Expired cardholder data keys don’t require manual regeneration anymore. X-Payments does it automatically. </li><br />
<li>Starting from v3.1.0 the root admin can grant permissions for additional user accounts in X-Payments back-end to edit templates, languages and view logs. See the full list of permissions the additional accounts owners may have here.</li><br />
<li>Improved support of 2-series Mastercard BINs and updated BIN detection for Discover network cards.</li><br />
<li>Improved IP addresses determination for stores protected by CloudFlare. In previous versions, the IP addresses could be determined incorrectly due to CloudFlare operational aspect.</li><br />
<li>Developer mode is now available for test installations without SSL. It means that you don’t need to have your site accessible by https and pay for SSL while testing. X-Payments will work in this case, however, there will be a watermark on checkout, that it’s a developer mode.</li><br />
<li>OpenSSL library is used now instead of deprecated mcrypt library.</li><br />
<li>Removed Solo, Switch, and Laser from supported card types as no longer valid.</li><br />
<li>Numerous minor design changes and improvements to make X-Payment as much convenient for you as it’s possible.</li><br />
</ul><br />
<br />
==Important Info on X-Payments Self-Hosted v2.x/1.x Upgrade==<br />
<br />
Users of X-Payments Hosted may skip this paragraph as our team handles all the upgrades for them upon request. Those who use self-hosted solutions should upgrade X-Cart Payments 3.1.0 follow these instructions.<br />
<br />
To prevent data loss caused by any possible issues that may happen during the upgrade, be sure to make backup copies of your X-Cart Payments files and database before you start. Thus, you’ll be able to revert back to your current X-Cart Payments version, if something goes wrong.<br />
<br />
Note! After you upgrade your X-Cart Payments from v1.x or v2.x to v3.1.0, you will be requested to change your password and set up a new method of 2-factor authentication for your user account. The authentication process is much handier. It doesn’t require generating dozens of pin codes at once, storing them and then searching for a correct one each time you need to log in. Instead, you’ll get a new code with the help of your smartphone each time, you need to log in.<br />
<br />
==PA-DSS Implementation Guide==<br />
<br />
X-Payments is a PA-DSS certified software, to help minimize your efforts securing your store according to the rules of PCI-SSC. While subscribers of any X-Payments Hosted plans can sleep peacefully, totally sure that their customer data is safe, merchants who preferred going with X-Payments downloadable solutions have something else to take care of. The case is that not only the software should comply with the council requirements, but the server environment, too.<br />
<br />
So, we’ve created the PCI-DSS implementation guide to help you configure your servers, where you’re going to host X-Payments software, in the right way.<br />
<br />
<a id="bambora"></a><br />
==Enjoy flexible plans from Bambora==<br />
<br />
Beanstream, a secure payment gateway supported by X-Payments, has passed rebranding and now is known as Bambora. Read the full announcement in the open letter by their CEO, Johan Tjärnberg.<br />
<br />
In honor of this exciting occasion, they've got something interesting for you to offer:<br />
<br />
For Canadian clients (CAD) Gateway + Merchant account:<br />
CAD = $0 setup, $0 monthly, $0.30 per transaction, 2.8% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=067ecda5-03d4-4f48-b070-c8e1d735c7ce<br />
<br />
For Canadian clients (USD) Gateway + Merchant account:<br />
USD = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=88f6f872-6ede-4885-824d-78ce907ced10<br />
<br />
For USA Clients (USD) Gateway + Merchant account:<br />
USA (USD) = $0 setup, $0 monthly, $0.30 per transaction, 2.9% processing rate<br />
Apply at https://onboarding.beanstream.com/?id=7f0a2313-d8fe-4582-9405-1fd164e00bd4</div>Animahttps://www.x-payments.com/help/?title=X-Payments:X-Cart_4.7.8_Connector_and_Subscriptions_updates&diff=995X-Payments:X-Cart 4.7.8 Connector and Subscriptions updates2017-06-21T08:02:07Z<p>Anima: /* X-Payments Connector Improvements and Fixes */</p>
<hr />
<div>Recently we’ve added multiple updates to X-Payments Connector for X-Cart Classic. Most likely you’ve read about a couple of most significant of them in [https://www.x-cart.com/blog/x-cart-4-7-8.htmlX-Cart 4.7.8 release] announcement. This article is to tell you about all the new changes.<br />
<br />
==X-Payments Connector Improvements and Fixes==<br />
<br />
The new connector comes with the following issues fixed:<br />
<br />
<ul><br />
<li>PHP error when iframe is disabled;</li><br />
<li>Charge instead of authorization when saving a card in customer’s profile;</li><br />
<li>Problems related to address book editing from the administrator back-end side;</li><br />
<li>Checkout freezing when switching between shipping methods with the same fee;</li><br />
<li>Redirect to empty cart after failed recharge.</li><br />
</ul><br />
<br />
Also, now it supports API 1.7 to get the payment fraud check data (from NoFraud/ Signifyd) and made some security updates.<br />
<br />
Starting from X-Payments 3.1.0 the allowed callback IP address will be included in the Configuration bundle. The new connector will be able to recognize this data and use accordingly in X-Cart.<br />
<br />
==X-Payments Subscriptions and Installments Module Update==<br />
<br />
We’ve optimized the process of assigning credit cards to subscriptions. Now your customers can pick a credit card among those saved in their profile to be used for a new subscription instead of adding the card details manually. Besides, they can update the credit card used for the existing subscription at any time without the need to stop it and re-subscribe with the new card.<br />
<br />
Previously, a subscription started only after the payment was captured. If you want it to start as soon as the payment is authorized, you can do so due to the additional new setting.<br />
<br />
If and anonymous customer adds a subscription product to cart, he will be able to complete an order only after login or signup. <br />
<br />
The update of this feature includes a couple of fixes, too: the one related to extra pending orders upon Subscriptions cron execution and another one related to subscription failed payments issues.<br />
<br />
In order to start using the new features, make sure you upgrade the modules. You’re welcome to contact us at support@x-payments.com for assistance.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:X-Cart_4.7.8_Connector_and_Subscriptions_updates&diff=994X-Payments:X-Cart 4.7.8 Connector and Subscriptions updates2017-06-21T08:01:24Z<p>Anima: Created page with "Recently we’ve added multiple updates to X-Payments Connector for X-Cart Classic. Most likely you’ve read about a couple of most significant of them in [https://www.x-cart..."</p>
<hr />
<div>Recently we’ve added multiple updates to X-Payments Connector for X-Cart Classic. Most likely you’ve read about a couple of most significant of them in [https://www.x-cart.com/blog/x-cart-4-7-8.htmlX-Cart 4.7.8 release] announcement. This article is to tell you about all the new changes.<br />
<br />
==X-Payments Connector Improvements and Fixes==<br />
<br />
The new connector comes with the following issues fixed:<br />
<br />
<ul><br />
<li>PHP error when iframe is disabled;</li><br />
<li>Charge instead of authorization when saving a card in customer’s profile;</li><br />
<li>Problems related to address book editing from the administrator back-end side;</li><br />
<li>Checkout freezing when switching between shipping methods with the same fee;</li><br />
<li>Redirect to empty cart after failed recharge.</li><br />
</ul><br />
<br />
Besides, it supports API 1.7 to get the payment fraud check data (from NoFraud/ Signifyd) and made some security updates.<br />
<br />
Starting from X-Payments 3.1.0 the allowed callback IP address will be included in the Configuration bundle. The new connector will be able to recognize this data and use accordingly in X-Cart.<br />
<br />
<br />
==X-Payments Subscriptions and Installments Module Update==<br />
<br />
We’ve optimized the process of assigning credit cards to subscriptions. Now your customers can pick a credit card among those saved in their profile to be used for a new subscription instead of adding the card details manually. Besides, they can update the credit card used for the existing subscription at any time without the need to stop it and re-subscribe with the new card.<br />
<br />
Previously, a subscription started only after the payment was captured. If you want it to start as soon as the payment is authorized, you can do so due to the additional new setting.<br />
<br />
If and anonymous customer adds a subscription product to cart, he will be able to complete an order only after login or signup. <br />
<br />
The update of this feature includes a couple of fixes, too: the one related to extra pending orders upon Subscriptions cron execution and another one related to subscription failed payments issues.<br />
<br />
In order to start using the new features, make sure you upgrade the modules. You’re welcome to contact us at support@x-payments.com for assistance.</div>Animahttps://www.x-payments.com/help/?title=X-Payments:New_Connector_1.8.0_for_Magento_released_%E2%80%93_more_flexible_and_user-friendly&diff=984X-Payments:New Connector 1.8.0 for Magento released – more flexible and user-friendly2017-05-04T09:21:21Z<p>Anima: </p>
<hr />
<div>It’s a known fact that fine-tuned checkout is a basic premise for conversions growth. With that in mind, we started working on the 1.8.0 Connector for Magento and designed it with care about the store administrator, buyers, and developers.<br />
<br />
You’ll love the convenience of payments setup and management, while your customer will appreciate the enhanced shopping experience.<br />
<br />
==Handy payments management for administrator==<br />
<br />
<ul><br />
<li>The whole X-Payments connection and configuration process now on the same page in your Magento back-end instead of multiple pages. It’s much quicker and clearer. See it for yourself in this [https://www.youtube.com/watch?v=OVN8acj45ic video].</li><br />
<li>Saving credit cards into customer profiles on behalf of customers to simplify their future purchases in the store.</li><br />
<li>Entering new credit cards on behalf of customers to pay for new orders created in Magento back-end – another great feature to help buyers complete their orders then and there.</li><br />
<li>Access to ‘Saving credit card’ setup”: set authorized amount and the transaction description.</li><br />
<li>Redesigned “X-Payments Order State” page allows doing partial refunds/voids and capturing authorized funds right in your store back-end.</li><br />
<li>Full support of the Magento’s Roles and Permissions tool allows partial or complete restriction of access to X-Payments Connector features.</li><br />
<li>New "Developer Mode" (use HTTP protocol) for testing/development environment without SSL support.</li><br />
</ul><br />
<br />
==Smooth checkout for your customers to get more completed orders==<br />
<br />
<ul><br />
<li>Ability to configure up to 3 payment gateways at a time – offer a wider choice of payment options to your customers on checkout. </li><br />
<li>Clear credit cards saving process and improved errors handling. </li><br />
<li>Reserved discount coupons if the transaction is declined. Previously such transactions consumed the coupon.</li><br />
<li>Full support of [https://marketplace.magento.com/aheadworks-onestepcheckout.html One Step Checkout module by AheadWorks] (beta).</li><br />
<li>Corrected free shipping calculation for [https://www.magentocommerce.com/magento-connect/one-page-checkout-extension.html FireCheckout].</li><br />
<li>Faster callback requests processing followed by significant speed up of X-Payments checkout routine in your Magento store.</li><br />
<li>No more errors after switching the X-Payments Connector extension off.</li><br />
</ul><br />
<br />
==Code re-factoring to help developers easier extend the module features==<br />
<br />
<ul><br />
<li>Decomposed common extension helper. This update made it possible to separate different features such as API communication, preparing cart data, address processing and module settings by different isolated helpers.</li><br />
<li>Re-worked functionality handled by the observer. We’ve changed it according to the MVC design, e.g. it’s a special API request from the certain controller that executes requests to charge the card again.</li><br />
<li>Corrected and simplified the inheritance tree. Internal quote model controls data transportation during payment processing, and it doesn’t affect quote class extensions made by other modules.</li><br />
<li>Removed unused legacy code and improved the code-style.</li><br />
<li>Corrected version in the internal config file.</li><br />
<li>Made other minor bug-fixes and improvements to ensure hassle-free work with X-Payments.</li><br />
</ul><br />
<br />
You’re welcome to download and try the new connector now. It’s already available in your Magento Connect. For any questions and suggestions do not hesitate to email at support@x-payments.com</div>Animahttps://www.x-payments.com/help/?title=X-Payments:New_Connector_1.8.0_for_Magento_released_%E2%80%93_more_flexible_and_user-friendly&diff=982X-Payments:New Connector 1.8.0 for Magento released – more flexible and user-friendly2017-05-04T09:19:21Z<p>Anima: Anima moved page X-Payments:X-Payments Connector 1.8.0 for Magento released – more flexible and user-friendly to X-Payments:New Connector 1.8.0 for Magento released – more flexible and user-friendly</p>
<hr />
<div><p>It’s a known fact that fine-tuned checkout is a basic premise for conversions growth. With that in mind, we started working on the 1.8.0 Connector for Magento and designed it with care about the store administrator, buyers, and developers. </p><br />
<br />
<p>You’ll love the convenience of payments setup and management, while your customer will appreciate the enhanced shopping experience.</p><br />
<br />
<br />
==Handy payments management for administrator==<br />
<br />
<ul><br />
<li>The whole X-Payments connection and configuration process now on the same page in your Magento back-end instead of multiple pages. It’s much quicker and clearer. See it for yourself in this [https://www.youtube.com/watch?v=OVN8acj45ic video].</li><br />
<li>Saving credit cards into customer profiles on behalf of customers to simplify their future purchases in the store.</li><br />
<li>Entering new credit cards on behalf of customers to pay for new orders created in Magento back-end – another great feature to help buyers complete their orders then and there.</li><br />
<li>Access to ‘Saving credit card’ setup”: set authorized amount and the transaction description.</li><br />
<li>Redesigned “X-Payments Order State” page allows doing partial refunds/voids and capturing authorized funds right in your store back-end.</li><br />
<li>Full support of the Magento’s Roles and Permissions tool allows partial or complete restriction of access to X-Payments Connector features.</li><br />
<li>New "Developer Mode" (use HTTP protocol) for testing/development environment without SSL support.</li><br />
</ul><br />
<br />
==Smooth checkout for your customers to get more completed orders==<br />
<br />
<ul><br />
<li>Ability to configure up to 3 payment gateways at a time – offer a wider choice of payment options to your customers on checkout. </li><br />
<li>Clear credit cards saving process and improved errors handling. </li><br />
<li>Reserved discount coupons if the transaction is declined. Previously such transactions consumed the coupon.</li><br />
<li>Full support of [https://marketplace.magento.com/aheadworks-onestepcheckout.html One Step Checkout module by AheadWorks] (beta).</li><br />
<li>Corrected free shipping calculation for [https://www.magentocommerce.com/magento-connect/one-page-checkout-extension.html FireCheckout].</li><br />
<li>Faster callback requests processing followed by significant speed up of X-Payments checkout routine in your Magento store.</li><br />
<li>No more errors after switching the X-Payments Connector extension off.</li><br />
</ul><br />
<br />
==Code re-factoring to help developers easier extend the module features==<br />
<br />
<ul><br />
<li>Decomposed common extension helper. This update made it possible to separate different features such as API communication, preparing cart data, address processing and module settings by different isolated helpers.</li><br />
<li>Re-worked functionality handled by the observer. We’ve changed it according to the MVC design, e.g. it’s a special API request from the certain controller that executes requests to charge the card again.</li><br />
<li>Corrected and simplified the inheritance tree. Internal quote model controls data transportation during payment processing, and it doesn’t affect quote class extensions made by other modules.</li><br />
<li>Removed unused legacy code and improved the code-style.</li><br />
<li>Corrected version in the internal config file.</li><br />
<li>Made other minor bug-fixes and improvements to ensure hassle-free work with X-Payments.</li><br />
</ul><br />
<br />
<p>You’re welcome to download and try the new connector now. It’s already available in your Magento Connect. For any questions and suggestions do not hesitate to email at support@x-payments.com</p></div>Animahttps://www.x-payments.com/help/?title=X-Payments:New_Connector_1.8.0_for_Magento_released_%E2%80%93_more_flexible_and_user-friendly&diff=980X-Payments:New Connector 1.8.0 for Magento released – more flexible and user-friendly2017-05-04T09:17:51Z<p>Anima: Anima moved page Magento-connector-180-released to X-Payments:X-Payments Connector 1.8.0 for Magento released – more flexible and user-friendly</p>
<hr />
<div><p>It’s a known fact that fine-tuned checkout is a basic premise for conversions growth. With that in mind, we started working on the 1.8.0 Connector for Magento and designed it with care about the store administrator, buyers, and developers. </p><br />
<br />
<p>You’ll love the convenience of payments setup and management, while your customer will appreciate the enhanced shopping experience.</p><br />
<br />
<br />
==Handy payments management for administrator==<br />
<br />
<ul><br />
<li>The whole X-Payments connection and configuration process now on the same page in your Magento back-end instead of multiple pages. It’s much quicker and clearer. See it for yourself in this [https://www.youtube.com/watch?v=OVN8acj45ic video].</li><br />
<li>Saving credit cards into customer profiles on behalf of customers to simplify their future purchases in the store.</li><br />
<li>Entering new credit cards on behalf of customers to pay for new orders created in Magento back-end – another great feature to help buyers complete their orders then and there.</li><br />
<li>Access to ‘Saving credit card’ setup”: set authorized amount and the transaction description.</li><br />
<li>Redesigned “X-Payments Order State” page allows doing partial refunds/voids and capturing authorized funds right in your store back-end.</li><br />
<li>Full support of the Magento’s Roles and Permissions tool allows partial or complete restriction of access to X-Payments Connector features.</li><br />
<li>New "Developer Mode" (use HTTP protocol) for testing/development environment without SSL support.</li><br />
</ul><br />
<br />
==Smooth checkout for your customers to get more completed orders==<br />
<br />
<ul><br />
<li>Ability to configure up to 3 payment gateways at a time – offer a wider choice of payment options to your customers on checkout. </li><br />
<li>Clear credit cards saving process and improved errors handling. </li><br />
<li>Reserved discount coupons if the transaction is declined. Previously such transactions consumed the coupon.</li><br />
<li>Full support of [https://marketplace.magento.com/aheadworks-onestepcheckout.html One Step Checkout module by AheadWorks] (beta).</li><br />
<li>Corrected free shipping calculation for [https://www.magentocommerce.com/magento-connect/one-page-checkout-extension.html FireCheckout].</li><br />
<li>Faster callback requests processing followed by significant speed up of X-Payments checkout routine in your Magento store.</li><br />
<li>No more errors after switching the X-Payments Connector extension off.</li><br />
</ul><br />
<br />
==Code re-factoring to help developers easier extend the module features==<br />
<br />
<ul><br />
<li>Decomposed common extension helper. This update made it possible to separate different features such as API communication, preparing cart data, address processing and module settings by different isolated helpers.</li><br />
<li>Re-worked functionality handled by the observer. We’ve changed it according to the MVC design, e.g. it’s a special API request from the certain controller that executes requests to charge the card again.</li><br />
<li>Corrected and simplified the inheritance tree. Internal quote model controls data transportation during payment processing, and it doesn’t affect quote class extensions made by other modules.</li><br />
<li>Removed unused legacy code and improved the code-style.</li><br />
<li>Corrected version in the internal config file.</li><br />
<li>Made other minor bug-fixes and improvements to ensure hassle-free work with X-Payments.</li><br />
</ul><br />
<br />
<p>You’re welcome to download and try the new connector now. It’s already available in your Magento Connect. For any questions and suggestions do not hesitate to email at support@x-payments.com</p></div>Animahttps://www.x-payments.com/help/?title=X-Payments:New_Connector_1.8.0_for_Magento_released_%E2%80%93_more_flexible_and_user-friendly&diff=979X-Payments:New Connector 1.8.0 for Magento released – more flexible and user-friendly2017-05-04T08:33:23Z<p>Anima: Created page with "<p>It’s a known fact that fine-tuned checkout is a basic premise for conversions growth. With that in mind, we started working on the 1.8.0 Connector for Magento and designe..."</p>
<hr />
<div><p>It’s a known fact that fine-tuned checkout is a basic premise for conversions growth. With that in mind, we started working on the 1.8.0 Connector for Magento and designed it with care about the store administrator, buyers, and developers. </p><br />
<br />
<p>You’ll love the convenience of payments setup and management, while your customer will appreciate the enhanced shopping experience.</p><br />
<br />
<br />
==Handy payments management for administrator==<br />
<br />
<ul><br />
<li>The whole X-Payments connection and configuration process now on the same page in your Magento back-end instead of multiple pages. It’s much quicker and clearer. See it for yourself in this [https://www.youtube.com/watch?v=OVN8acj45ic video].</li><br />
<li>Saving credit cards into customer profiles on behalf of customers to simplify their future purchases in the store.</li><br />
<li>Entering new credit cards on behalf of customers to pay for new orders created in Magento back-end – another great feature to help buyers complete their orders then and there.</li><br />
<li>Access to ‘Saving credit card’ setup”: set authorized amount and the transaction description.</li><br />
<li>Redesigned “X-Payments Order State” page allows doing partial refunds/voids and capturing authorized funds right in your store back-end.</li><br />
<li>Full support of the Magento’s Roles and Permissions tool allows partial or complete restriction of access to X-Payments Connector features.</li><br />
<li>New "Developer Mode" (use HTTP protocol) for testing/development environment without SSL support.</li><br />
</ul><br />
<br />
==Smooth checkout for your customers to get more completed orders==<br />
<br />
<ul><br />
<li>Ability to configure up to 3 payment gateways at a time – offer a wider choice of payment options to your customers on checkout. </li><br />
<li>Clear credit cards saving process and improved errors handling. </li><br />
<li>Reserved discount coupons if the transaction is declined. Previously such transactions consumed the coupon.</li><br />
<li>Full support of [https://marketplace.magento.com/aheadworks-onestepcheckout.html One Step Checkout module by AheadWorks] (beta).</li><br />
<li>Corrected free shipping calculation for [https://www.magentocommerce.com/magento-connect/one-page-checkout-extension.html FireCheckout].</li><br />
<li>Faster callback requests processing followed by significant speed up of X-Payments checkout routine in your Magento store.</li><br />
<li>No more errors after switching the X-Payments Connector extension off.</li><br />
</ul><br />
<br />
==Code re-factoring to help developers easier extend the module features==<br />
<br />
<ul><br />
<li>Decomposed common extension helper. This update made it possible to separate different features such as API communication, preparing cart data, address processing and module settings by different isolated helpers.</li><br />
<li>Re-worked functionality handled by the observer. We’ve changed it according to the MVC design, e.g. it’s a special API request from the certain controller that executes requests to charge the card again.</li><br />
<li>Corrected and simplified the inheritance tree. Internal quote model controls data transportation during payment processing, and it doesn’t affect quote class extensions made by other modules.</li><br />
<li>Removed unused legacy code and improved the code-style.</li><br />
<li>Corrected version in the internal config file.</li><br />
<li>Made other minor bug-fixes and improvements to ensure hassle-free work with X-Payments.</li><br />
</ul><br />
<br />
<p>You’re welcome to download and try the new connector now. It’s already available in your Magento Connect. For any questions and suggestions do not hesitate to email at support@x-payments.com</p></div>Anima