X-Payments Help - User contributions [en]

X-Payments:Using X-Payments with Magento

2019-06-13T06:29:16Z

Nastya: /* What's New */

__NOTOC__
A Magento store can be connected to [[X-Payments:User_manual|X-Payments]] web-based payment application to process payments from customers and save their credit card data in a PCI DSS compliant way.

This section provides information on how to connect X-Payments to your Magento store and how to handle payments in your Magento store using X-Payments.

==Video tutorials==

:* [[X-Payments:Video_Tutotials_on_Using_X-Payments_with_Magento | Video Tutotials on Using X-Payments with Magento]]

==What's New==
:* [[X-Payments:What%27s_New_in_X-Payments_Connector_for_Magento | What's New in X-Payments Connector for Magento]]
:* [[X-Payments:Magento1-Connector-1.8.3 | X-Payments Connector for Magento v1.8.3]]
:* [[X-Payments:Magento_Connector_v1.8.4 | X-Payments Connector for Magento v1.8.4]]

==Connecting Magento to X-Payments==

:* [[X-Payments:Installing_the_X-Payments_connector_extension_for_Magento | Installing the X-Payments connector extension for Magento]]
:* [[X-Payments:Connecting_X-Payments_and_Magento | Connecting X-Payments and Magento]]
:* [[X-Payments:Updating_your_X-Payments_connector_for_Magento | Updating your X-Payments connector for Magento]]

==Using X-Payments with Magento: Customer experience==

:* [[X-Payments:Magento_checkout_routine_when_using_X-Payments | Magento checkout routine when using X-Payments]]
:* [[X-Payments:PCI_compliant_credit_card_saving_when_using_X-Payments_with_Magento | PCI compliant credit card saving when using X-Payments with Magento]]

==Using X-Payments with Magento: Administrator experience==

:* [[X-Payments:Control_of_access_to_X-Payments_connector_features_in_Magento | Control of access to X-Payments connector features in Magento]]
:* [[X-Payments:Capturing_payments_when_using_X-Payments_with_Magento | Capturing payments when using X-Payments with Magento]]
:* [[X-Payments:Issuing_refunds_when_using_X-Payments_with_Magento | Issuing refunds when using X-Payments with Magento]]
:* [[X-Payments:Canceling_payments_when_using_X-Payments_with_Magento | Canceling payments when using X-Payments with Magento]]
:* [[X-Payments:Finding_out_the_order_state_for_X-Payments_orders_when_using_X-Payments_with_Magento | Finding out the order state for X-Payments orders when using X-Payments with Magento]]
:* [[X-Payments:Capture,_Void_and_Refund_on_orders_modified_using_Magento%27s_default_Edit_feature_when_using_X-Payments_with_Magento | Capture, Void and Refund on orders modified using Magento's default Edit feature when using X-Payments with Magento]]
:* [[X-Payments:Capture,_Void_and_Refund_via_the_X-Payment_Order_State_tab_when_using_X-Payments_with_Magento | Capture, Void and Refund via the X-Payment Order State tab when using X-Payments with Magento]]
:* [[X-Payments:PCI_compliant_credit_card_saving_on_behalf_of_a_customer | PCI compliant credit card saving on behalf of a customer]]

==Recurring Billing in Magento with X-Payments==
:* [[X-Payments:Recurring_Billing_in_Magento_with_X-Payments | Recurring Billing in Magento with X-Payments]].

==Export of order information to StoneEdge Order Manager==
Starting with version 1.7.0, the X-Payments connector for Magento supports export of payment information (stuff like transaction IDs, the last four digits of the credit card number, etc.) to [http://stoneedge.com/ StoneEdge Order Manager]. If you use X-Payments with Magento and need to export information about payments conducted via X-Payments to StoneEdge Order Manager, contact the X-Payments team for help.

[[Category:X-Payments_Connection_Manuals]]

X-Payments:Using X-Payments with Zoey

2019-06-13T06:24:59Z

Nastya: /* What's New */

__NOTOC__
A Zoey store can be connected to [[X-Payments:User_manual|X-Payments]] web-based payment application to process payments from customers and save their credit card data in a PCI DSS compliant way.

This section provides information on how to connect and use X-Payments with your Zoey store.

==What's New==

:* [[X-Payments:What%27s_New_in_X-Payments_Connector_for_Zoey | What's New in X-Payments Connector for Zoey]]
:* [[X-Payments:X-Payments_Connector_for_Zoey_v1.8.12_Released | X-Payments Connector for Zoey v1.8.12]]
:* [[X-Payments:X-Payments_Connector_for_Zoey_v1.8.14_Released | X-Payments Connector for Zoey v1.8.14]]

==Zoey and X-Payments: Connection and Configuration==
Connecting your Zoey store to X-Payments includes two consecutive steps:
:* [[X-Payments:Configure the connection to your Zoey store in the X-Payments back end | Configure the connection to your Zoey store in the X-Payments back end]] (Instructions for X-Payments 2.1.1 and later)
:* [[X-Payments:Configure the connection to X-Payments in the Zoey store Control Panel | Configure the connection to X-Payments in the Zoey store Control Panel]] (Zoey Connector 1.8.4 or later )

Information on how to configure your store to accept payments in more than one currency is available in this article:
:* [[Zoey and X-Payments: Multi-Currency Configuration]]

Information on multi-address checkout and shipping can be found here:
:* [[Zoey and X-Payments: Multi-Address Checkout and Shipping]]

==Using X-Payments with Zoey: Customer experience==
:* [[X-Payments:Zoey checkout routine when using X-Payments | Zoey checkout routine when using X-Payments]]
:* [[X-Payments:PCI_compliant_credit_card_saving_when_using_X-Payments_with_Zoey | PCI compliant credit card saving when using X-Payments with Zoey]]

==Using X-Payments with Zoey: Administrator experience==
:* [[X-Payments:Finding out the order state for X-Payments orders when using X-Payments with Zoey | Finding out the order state for X-Payments orders when using X-Payments with Zoey]]
:* [[X-Payments:Capturing payments when using X-Payments with Zoey | Capturing payments when using X-Payments with Zoey]]
:* [[X-Payments:Issuing refunds when using X-Payments with Zoey | Issuing refunds when using X-Payments with Zoey]]
:* [[X-Payments:Canceling payments when using X-Payments with Zoey | Canceling payments when using X-Payments with Zoey]]
:* [[X-Payments:Editing X-Payments orders in Zoey|Editing X-Payments orders in Zoey]]
:* [[X-Payments:Capture, Void and Refund via the X-Payment Order State section when using X-Payments with_Zoey | Capture, Void and Refund via the X-Payment Order State section when using X-Payments with_Zoey]]
:* [[X-Payments:PCI compliant credit card saving on behalf of a customer (Zoey)|PCI compliant credit card saving on behalf of a customer (Zoey)]]

==Video tutorials (outdated)==

:* [[X-Payments:Video_Tutotials_on_Using_X-Payments_with_Zoey | Video Tutotials on Using X-Payments with Zoey]]

[[Category:X-Payments_Connection_Manuals]]

X-Payments:X-Payments Connector for Zoey v1.8.14 Released

2019-06-13T06:20:22Z

Nastya: Created page with "=X-Payments Connector v1.8.14 for Zoey= This time, we’re releasing a huge upgrade of X-Payments Connector for your Zoey store. New excellent features, API 1.9 support, bug..."

=X-Payments Connector v1.8.14 for Zoey=

This time, we’re releasing a huge upgrade of X-Payments Connector for your Zoey store. New excellent features, API 1.9 support, bug fixes and more. Let’s take a closer look here.

As always, the detailed overview of the updates is followed by the changelog for the techies.

==Updates and Improvements==

Maybe there are not so many of them but this is the situation when quality outweighs quantity a good deal.

===Admin Backend===

Mass-delete action used to fail for saved payment cards in some cases. We located the origin of the issue and fixed it.

There was an issue with the warning buttons at the order page – at times, they didn’t show up and the admin couldn’t accept or decline the payment. Sometimes, the warning message didn’t pop up, either, for suspicious transactions. Both of them were caused by the same bug – we took care of it, so now they work properly.

Another major issue was related to capturing payments in secondary currency.

For example, a customer places an order for 100 CAD, which equals 80 USD (I’m rounding up for convenience). The amount captured was 80 instead of 100, which caused wrong calculations and complicated matters if the payment had to be refunded. That was a complex issue with how Zoey handled currency conversion. We went ahead and fixed it so the amount captured is now calculated properly.

===Frontend===

Apart from the overall performance, security, and speed optimization, we addressed a number of issues that occurred in the previous versions.

The link to saved payment cards used to disappear in the customer profiles. We corrected the appearance.

We have improved cart/quote state for the declined payment. Previously, if a payment failed for some reason, the cart used to be cleaned and the customer redirected elsewhere. (Elsewhere, I swear!)

From now on the client will stay at checkout and can try and pay once more. Besides, the errors are logged properly for future investigation.

Further, we went on to correct shipping address processing. There was an issue with sending it to Signifyd the anti-fraud service, which resulted in wrong payment “suspiciousness” calculations.

===Internal and Processing===

First of all, we have added support for API 1.9.

Second of all, we optimized payment processing and order placing procedures. They now take less time and back-and-forth requesting.

Caching of the communication between X-Payments and your Zoey store was implemented, which allowed us to optimize it a little bit more.

Logging was improved, too. Well, in fact, we started logging more details so in case an error occurs (God forbid!), we’ll know at once what happened and how to fix it.

cc_trans_id for successful payment sent by the payment gateway or the bank – the one that follows the failed transaction – used to fail registering in the database. This, in turn, caused troubles with the third-party systems integrated with your store. They couldn’t get the necessary data and failed to work properly, too. As always, we defined the origin and fixed it.

Faulty responses for callback requests caused jams in communication between X-Payments Connector and X-Payments itself. We did our magic and it’s now flawless.

We have corrected occasional mis-reference with quotes and orders. To give you a clue of what happened, please imagine a rare situation. A client and the store admin create orders each on their end at the same time – without submitting the payment.

In such cases, the database couldn’t handle the flow of data and did crazy stuff.

We addressed the issue. Now you still can’t create the two orders simultaneously, but the database can now manage such situations without losing it.

And the last update for today is for us, developers, mainly. We removed the long unused PHP docs and corrected comments in code.

==Changelog 1.8.14==

Now you've scrolled down to the promised changelog (or jumped straight here :) ), so no more details, just facts.

'''Admin Backend:'''
* Corrected mass-delete action for saved payment cards.
* Corrected amount for capture and refund in secondary currency.
* Corrected appearance of the warning buttons on the order page.

'''Frontend:'''
* Security, performance optimizations and bug-fixes at checkout.
* Corrected appearance of the Payment Cards link and pages.
* Improved cart/quote state for the declined payment. Customer stays at checkout correctly in this case.
* Corrected shipping address processing (affects Signifyd anti-fraud service).

'''Internal and Processing:'''
* API 1.9 support.
* Optimization of the payment processing and order placing procedure.
* Caching of the communication between X-Payments and the Store implemented.
* Improved logging.
* Correct cc_trans_id for successful payment which follows the failed one.
* Fixed responding for callback requests (headers already sent error).
* Corrected occasional mis-reference with quotes and orders.
* Removed unused PHP-docs. Corrected comments.

==Bottomline==

We are proud of our work today with the updated version of X-Payments Connector for Zoey. Hope you appreciate the optimized performance and improved looks.

You are welcome to upgrade anytime now.

X-Payments:Magento Connector v1.8.4

2019-05-21T13:38:52Z

Nastya: /* To sum up */

=X-Payments connector for Magento 1 (v1.8.4)=

We’re releasing another update for X-Payments connector for Magento 1. If your Magento version is between '''1.6.x.x and 1.9.x.x''', this update is of interest for you. I am going to review all the major changes and a few minor ones. If you prefer the dry language of changelog, there’s one for you, too – at the end of this article.

==Improvements==

So let’s get the ball rolling. First of all, there’s a number of updates to the admin backend of your X-Payments instance.

===Admin backend===

For security purposes, only the HTTPS protocol is now allowed. For the same reasons, developer mode is no longer available as well.

"IP addresses for X-Payments callbacks" option and IP address check did little to improve security but took up a great deal of resources, so we decided to give them up in favor of smoother and faster processing.

We rearranged customers’ saved payment cards lists so they now look neater and more logical. We implemented payment cards in each buyer’s profile and a separate page where the admin can see all the payment cards.

The "X-Payments Order State" tab on the order details page saw some rearranging, too. Now the sections look cleaner and show the information from Anti-fraud service providers and internal X-Payments validation, which is handy. Besides, the tab itself loads faster because we reduced the number of requests to X-Payments to just one.

For situations when you need to charge a saved card, we added protection from accidental double (or triple or even multiple) form submits. It can happen to us all, I guess, and extra protection will certainly help reduce the admin’s work.

We also removed secondary actions (void, capture, refund) from this tab. And improved the looks of saved cards form.

In the new version, whenever a client’s profile is deleted, their associated saved cards will be deleted, too.

Some will find it handy that X-Payments now allows setting status for new orders.

We have updated the credit card logos – some of them changed since the last time. We also reorganized them a bit, so the whole page is more pleasant to look at. ''(We’re technicians all right, but who says we don’t like it pretty?)''

X-Payments can now work in maintenance mode. Most of you will never see the difference, but it’ll be much more convenient to support the software. Yes, this update is for us, developers, an egoistic one. :)

For you, we’ve added the ability to update payment status. The payment statuses are normally updated in your Magento store automatically from X-Payments. But in case anything goes wrong, you can now set the status manually according to what is shown in X-Payments backend.

If there are several stores, websites, or views within your Magento installation, you can set up specific parameters for each of them. This feature can be used in various situations. For example, you may use a different set of payment methods for each of your sites. Or if you have separate stores for selling in several countries, you may set a specific currency for each.

===Frontend===

Sure, the admin backend saw a lot of changes, because this is where you work and it’s important that your working environment is as intuitive as possible. However, we don’t forget about what your clients see, either.

So let’s see what’s new in the frontend.

First of all, we added support for multiple currencies. This is a must-have feature if you sell worldwide. Say, one of your clients from France chooses to pay with euro and another from Japan likes paying with yen. If you let that happen, your conversion rate will grow – that’s for sure.

Moreover, each of these two hypothetical clients will see different payment options at checkout – only those that can process payments in those currencies.

You can now force tokenization if you like. If you select this option, all your clients’ payment cards will be saved. Of course, the buyer will see a proper notice.

For cases when the order total is not final yet – for any reason – we’ve implemented the tokenization-only feature. In this case, the payment card is saved and the credit or debit card will be charged later when the order total is defined.

You’ll also like the improved looks of the AJAX loader.

We’ve also corrected some issues in the frontend but let’s finish up with the improvements first.

===Internal and Processing===

The most important change here is that we started to associate a callback request with the customer’s session. Say, a client belongs in a special user group in your Magento store and you defined special prices or discounts to its members. From now on, X-Payments will “know” it from the associated session and show the correct total.

X-Payments now supports decimal product quantity. This feature will be useful if you sell products that are measured in pounds / feet / square feet (or kilograms / meters / square meters, accordingly – if you use the metric system).

This way, you can sell, say, 1½ lbs of melted gold or 5.7 linear meters of finest intricate nun-made lace for a wedding dress. :)

We’ve also implemented a lot of improvements code-wise but that’s mainly for us, developers, too.

==Bug fixes==

===Admin backend===

The table of payment cards used to work weird whenever a card was deleted. It now behaves itself.

If X-Payments is not configured, it should not be possible to add new cards. Of course, X-Payments did not allow that but the error message did not look good. It now does.

Your smart Magento store automatically captures/voids payments when an order is changed. For example, if an order gets canceled, it’s normal to void the payment.

There were occasional issues with secondary actions, and we took good care of them.

Whenever an order is edited, the system used to cancel the order, create a new one and consequently, void the payment. This is not necessary in a lot of cases, so now you can manually void payments if need be.

===Frontend===

We corrected error handling for the situations when a customer returns from the payment page. The error (if there was one, of course) is handled properly and logged for easier troubleshooting.

In some cases, the Payment Cards link did not show up and the admin could not view an existing card. We corrected that issue.

===Internal and Processing===

We have fixed a possible issue with rounding. It could have caused critical issues with tax calculation, you wouldn’t want that.

The auto-capture feature could fail in some cases, we will not let that happen again. The issue’s fixed.

We have corrected the processing of the "sumbitPaymentForm" event from X-Payments, it used to fail sometimes.

There was an issue with subscription prices not calculating properly – we corrected it.

==To sum up==

There have been a lot of minor improvements and a few major ones. Regardless of the importance, they will improve your overall X-Payments experience, and we hope you’re already enjoying them.

If not, [http://www.pjtra.com/t/TUJGRkxNTkJGTU5IRUpCRktJTEpO?url=https%3A%2F%2Fmarketplace.magento.com%2Fcdev-cdev-xpaymentsconnector.html get the updated version from the Magento Marketplace] now.

==Changelog 1.8.4==

Now for the promised changelog.

'''Admin Backend:'''
* Removed "Developer mode", only HTTPS protocol is now allowed
* Removed "IP addresses for X-Payments callbacks" option and the IP address check
* Improved page listing customers' saved payment cards. Implemented separate page to list saved cards from all customers
* Corrected card delete action
* Corrected add new card page if X-Payments is not configured
* Delete associated saved cards when a customer is deleted
* Reorganized appearance of the "X-Payments Order State" tab on the order details page. Added information about anti-fraud check
* Added protection from double form submits at the "X-Payments Order State" tab. Removed secondary actions. Improved saved cards form
* Added some corrections for the core payment secondary actions on order changes
* Do not void payment after edit order
* Corrected "Manual review required" text for the errors in internal validation
* Ability to set status for new orders
* Corrected saved cards form validation at order creation
* Corrected credit card logos
* Added maintenance mode
* "Update payment status" feature, which allows updating payment status according to the info from X-Payments
* Support of the Multi-store configuration

'''Frontend:'''
* Support of multi-address checkout and multi-currencies
* Improved error handling when a customer returns from the payment page
* Added ability to force tokenization
* Added tokenization-only feature when order is placed
* Changed default payment method name to "Credit or Debit Card"
* Corrected appearance of the AJAX loader at checkout
* Corrected appearance of the Payment Cards link and pages

'''Internal and Processing:'''
* Corrected occasional mis-reference with quotes and orders
* Corrected possible rounding issue
* Start customer's session for callback request for correct cart calculation
* Payment token TTL is now 900 seconds
* Corrected auto-capture feature
* Corrected processing of the "sumbitPaymentForm" event from XP
* Corrected subscription prices
* Decimal product quantity support
* Code-style improvements
* Removed unused PHP docs. Corrected comments

X-Payments:Magento Connector v1.8.4

2019-05-17T10:34:22Z

Nastya: Created page with "=X-Payments connector for Magento 1 (v1.8.4)= We’re releasing another update for X-Payments connector for Magento 1. If your Magento version is between '''1.6.x.x and 1.9.x..."

=X-Payments connector for Magento 1 (v1.8.4)=

We’re releasing another update for X-Payments connector for Magento 1. If your Magento version is between '''1.6.x.x and 1.9.x.x''', this update is of interest for you. I am going to review all the major changes and a few minor ones. If you prefer the dry language of changelog, there’s one for you, too – at the end of this article.

==Improvements==

So let’s get the ball rolling. First of all, there’s a number of updates to the admin backend of your X-Payments instance.

===Admin backend===

For security purposes, only the HTTPS protocol is now allowed. For the same reasons, developer mode is no longer available as well.

"IP addresses for X-Payments callbacks" option and IP address check did little to improve security but took up a great deal of resources, so we decided to give them up in favor of smoother and faster processing.

We rearranged customers’ saved payment cards lists so they now look neater and more logical. We implemented payment cards in each buyer’s profile and a separate page where the admin can see all the payment cards.

The "X-Payments Order State" tab on the order details page saw some rearranging, too. Now the sections look cleaner and show the information from Anti-fraud service providers and internal X-Payments validation, which is handy. Besides, the tab itself loads faster because we reduced the number of requests to X-Payments to just one.

For situations when you need to charge a saved card, we added protection from accidental double (or triple or even multiple) form submits. It can happen to us all, I guess, and extra protection will certainly help reduce the admin’s work.

We also removed secondary actions (void, capture, refund) from this tab. And improved the looks of saved cards form.

In the new version, whenever a client’s profile is deleted, their associated saved cards will be deleted, too.

Some will find it handy that X-Payments now allows setting status for new orders.

We have updated the credit card logos – some of them changed since the last time. We also reorganized them a bit, so the whole page is more pleasant to look at. ''(We’re technicians all right, but who says we don’t like it pretty?)''

X-Payments can now work in maintenance mode. Most of you will never see the difference, but it’ll be much more convenient to support the software. Yes, this update is for us, developers, an egoistic one. :)

For you, we’ve added the ability to update payment status. The payment statuses are normally updated in your Magento store automatically from X-Payments. But in case anything goes wrong, you can now set the status manually according to what is shown in X-Payments backend.

If there are several stores, websites, or views within your Magento installation, you can set up specific parameters for each of them. This feature can be used in various situations. For example, you may use a different set of payment methods for each of your sites. Or if you have separate stores for selling in several countries, you may set a specific currency for each.

===Frontend===

Sure, the admin backend saw a lot of changes, because this is where you work and it’s important that your working environment is as intuitive as possible. However, we don’t forget about what your clients see, either.

So let’s see what’s new in the frontend.

First of all, we added support for multiple currencies. This is a must-have feature if you sell worldwide. Say, one of your clients from France chooses to pay with euro and another from Japan likes paying with yen. If you let that happen, your conversion rate will grow – that’s for sure.

Moreover, each of these two hypothetical clients will see different payment options at checkout – only those that can process payments in those currencies.

You can now force tokenization if you like. If you select this option, all your clients’ payment cards will be saved. Of course, the buyer will see a proper notice.

For cases when the order total is not final yet – for any reason – we’ve implemented the tokenization-only feature. In this case, the payment card is saved and the credit or debit card will be charged later when the order total is defined.

You’ll also like the improved looks of the AJAX loader.

We’ve also corrected some issues in the frontend but let’s finish up with the improvements first.

===Internal and Processing===

The most important change here is that we started to associate a callback request with the customer’s session. Say, a client belongs in a special user group in your Magento store and you defined special prices or discounts to its members. From now on, X-Payments will “know” it from the associated session and show the correct total.

X-Payments now supports decimal product quantity. This feature will be useful if you sell products that are measured in pounds / feet / square feet (or kilograms / meters / square meters, accordingly – if you use the metric system).

This way, you can sell, say, 1½ lbs of melted gold or 5.7 linear meters of finest intricate nun-made lace for a wedding dress. :)

We’ve also implemented a lot of improvements code-wise but that’s mainly for us, developers, too.

==Bug fixes==

===Admin backend===

The table of payment cards used to work weird whenever a card was deleted. It now behaves itself.

If X-Payments is not configured, it should not be possible to add new cards. Of course, X-Payments did not allow that but the error message did not look good. It now does.

Your smart Magento store automatically captures/voids payments when an order is changed. For example, if an order gets canceled, it’s normal to void the payment.

There were occasional issues with secondary actions, and we took good care of them.

Whenever an order is edited, the system used to cancel the order, create a new one and consequently, void the payment. This is not necessary in a lot of cases, so now you can manually void payments if need be.

===Frontend===

We corrected error handling for the situations when a customer returns from the payment page. The error (if there was one, of course) is handled properly and logged for easier troubleshooting.

In some cases, the Payment Cards link did not show up and the admin could not view an existing card. We corrected that issue.

===Internal and Processing===

We have fixed a possible issue with rounding. It could have caused critical issues with tax calculation, you wouldn’t want that.

The auto-capture feature could fail in some cases, we will not let that happen again. The issue’s fixed.

We have corrected the processing of the "sumbitPaymentForm" event from X-Payments, it used to fail sometimes.

There was an issue with subscription prices not calculating properly – we corrected it.

==To sum up==

There have been a lot of minor improvements and a few major ones. Regardless of the importance, they will improve your overall X-Payments experience, and we hope you’re already enjoying them.

==Changelog 1.8.4==

Now for the promised changelog.

'''Admin Backend:'''
* Removed "Developer mode", only HTTPS protocol is now allowed
* Removed "IP addresses for X-Payments callbacks" option and the IP address check
* Improved page listing customers' saved payment cards. Implemented separate page to list saved cards from all customers
* Corrected card delete action
* Corrected add new card page if X-Payments is not configured
* Delete associated saved cards when a customer is deleted
* Reorganized appearance of the "X-Payments Order State" tab on the order details page. Added information about anti-fraud check
* Added protection from double form submits at the "X-Payments Order State" tab. Removed secondary actions. Improved saved cards form
* Added some corrections for the core payment secondary actions on order changes
* Do not void payment after edit order
* Corrected "Manual review required" text for the errors in internal validation
* Ability to set status for new orders
* Corrected saved cards form validation at order creation
* Corrected credit card logos
* Added maintenance mode
* "Update payment status" feature, which allows updating payment status according to the info from X-Payments
* Support of the Multi-store configuration

'''Frontend:'''
* Support of multi-address checkout and multi-currencies
* Improved error handling when a customer returns from the payment page
* Added ability to force tokenization
* Added tokenization-only feature when order is placed
* Changed default payment method name to "Credit or Debit Card"
* Corrected appearance of the AJAX loader at checkout
* Corrected appearance of the Payment Cards link and pages

'''Internal and Processing:'''
* Corrected occasional mis-reference with quotes and orders
* Corrected possible rounding issue
* Start customer's session for callback request for correct cart calculation
* Payment token TTL is now 900 seconds
* Corrected auto-capture feature
* Corrected processing of the "sumbitPaymentForm" event from XP
* Corrected subscription prices
* Decimal product quantity support
* Code-style improvements
* Removed unused PHP docs. Corrected comments

X-Payments:V3.1.5 Released

2019-04-08T12:23:51Z

Nastya: Created page with "X-Payments 3.1.5 comes with a bunch of improvements to the payment gateway integrations and overall security strengthening. Let us start with the payment gateway integrations..."

X-Payments 3.1.5 comes with a bunch of improvements to the payment gateway integrations and overall security strengthening. Let us start with the payment gateway integrations and then move on to the other fixes and improvements.

==Payment Gateways Updates==

In general, our updates for the payment gateways integrations reflect the changes in their own workflow but we also see into the future a bit and create new integrations as well.

===Intuit Quickbooks===

We developed a new integration for Intuit Quickbooks that uses Quickbooks Payment API. It’s available along with the existing QBMS API and their functionalities are quite similar as of now. However, although the integration using the legacy QBMS API is fully functional now, you might need the new one some time in the future – in case Quickbooks stop supporting QBMS API. Moreover, Intuit Quickbooks integration through the Quickbooks Payment API will allow us to implement new features (like Apple Pay support, for example) in the next X-Payments versions.

While we’re on the subject of Intuit QBMS. There used to be an issue with some billing addresses – the system wouldn’t accept an order if the submitted billing address exceeded 30 characters. Let’s just say it’s no longer an issue.

===Realex/Global Iris/Elavon===

We renamed Realex Payments to Global Payments in accordance with the change of the main company back in 2015.

We also fixed a couple of issues with 3-D secure not working correctly in some cases.

First of all, all Mastercard payments got declined because the ECI codes that 3-D Secure system sent did not match those configured in X-Payments (MasterCard uses a different set of codes). We have updated our code and now both MasterCard and Visa, American Express, and JCB values are valid and accepted by the system.

The other issue also involved 3-D Secure verification. The payment module allows a merchant to choose if they want to accept or decline orders if 3-D Secure is not supported by the buyer’s bank. In some cases, if ECI was configured to decline such orders, the module still sent information over to the gateway while the order showed up as declined in X-Payments admin area as well as in the store’s backend. This issue was also corrected.

===NMI===

Tokenization is now available for this payment gateway as well as support of AUD and EUR currencies.

===Braintree===

Country code was not sent to the payment gateway. Now the issue is fixed.

===PsiGate===

It now allows to capture, void, or refund a payment.

===Paya (SageUS)===

Tokenization used to work only if a buyer chooses to save their card for future use. We have now fixed the issue.

===Authorize.Net===

X-Payments usually sends the buyer’s IP address to the payment gateway for payment verification. As long as Authorize.Net only support IPv4 format, an issue might have occurred if a buyer had an IPv6 address. And although we have not registered such issues yet, we nevertheless updated the code to avoid them in the future. From now on, only IPv4 addresses will be sent over to Authorize.Net.

We have also worked on strengthening antifraud check for your eCommerce site.

Kount now saves more details (GEOX, LANGUAGE, and VELO) about its transaction check. You will have more information available to check such orders and manually process them if you find them trustworthy.

We also thought you might want to see ECI value in the admin panel – to have more information on the orders. So this info is now available, too.

We also detected an issue with the antifraud functionality. It was not possible to configure antifraud check if more than 1 payment configuration was available. We fixed it, of course.

==Bugs and improvements==

* '''Security updates''' implemented to avoid possible issues in the future.
* '''Search by price''' did not work correctly in the list of payments, we fixed it.
* '''3-D Secure feature''' wasn't working in some cases even supported by payment module. Fixed.
* Added support for '''HTTP/2 responses''', which helps avoid possible issues with HTTP/1.x-HTTP/2 compatibility. If you consider upgrading your server or making the switch to HTTP/2, you may do so and be sure X-Payments won’t be affected.
* We have also worked on improving '''database operations speed and performance'''.
* One of the '''text labels in the payment form''' would not be translated to another language along with the rest of the form because it exceeded maximum length. We have updated the code and the popup will be translated from now on.
* This X-Payments release comes with a few '''minor changes in the interface''' but they do not affect the regular workflow much.

'''X-Payments Hosted''' users – your instances have already been upgraded to the new version, so just enjoy the new features. With any questions or concerns, please feel free to [https://www.x-payments.com/contact-us.html contact us].

If you use '''X-Payments Enterprise''', you may find the necessary files in the File Area section in HelpDesk and the [[X-Payments:Upgrading|instructions right here]]. Do let us know if we can be of any assistance with the upgrade, we love helping out.

X-Payments:X-Payments Connector for Zoey v1.8.12 Released

2019-04-04T10:29:05Z

Nastya: Created page with "=X-Payments connector v1.8.12 for Zoey= We’re glad to announce the release of the renewed X-Payments connector for your Zoey-based eCommerce store. This one we prepared wit..."

=X-Payments connector v1.8.12 for Zoey=

We’re glad to announce the release of the renewed X-Payments connector for your Zoey-based eCommerce store. This one we prepared with special attention as there are quite a lot of new features now available.

==Multi-currency improvements==

First and foremost, we concentrated our attention on stable support for various currencies and languages. You can’t truly go global unless you can accept your international customers’ currency or otherwise localizing your store so that they feel at home buying from you.

If you are planning to expand worldwide or have already done so, we’ve got good news for you.

We optimized X-Payments so now you can configure your checkout page(s) so that your Canadian customers will get to choose from those payment methods that are available in Canada, and your European ones – those available in EU.

In the previous versions of X-Payments both of them saw the full list of payment methods, which might have caused confusion and affected your conversion rates.

==Multi-address checkout==

Next, we added support for multi-address checkout. That means your buyers can submit several shipping addresses at checkout.

That’s not a very obvious feature but it’s convenient nevertheless.

Imagine you would like to order Leo Tolstoy’s “War and Peace” as Christmas gifts for all your family members living abroad (a book is an excellent gift, after all).

You can make several orders submitting different shipping addresses each time but it takes time and – honestly – nerve. Or you can fill in all the necessary information at checkout just once and list all the addresses you would like the book to be shipped to. The choice is somewhat obvious, isn’t it?

Your clients will be happy if you give them such an opportunity, trust me (I did not just imagine the situation above, you know).

==Other improvements==

The rest of the changes are less impressive but useful nonetheless.

For instance, in a situation if a client went to checkout and did not complete it for some reason, a “Payment session expired” message used to show up. Which is good, this is the standard behavior if you do care about your clients’ data security.

However, in previous versions, this message showed up even if a client closed the website, went to Spain, came back and opened your site again. Which is misleading.

We corrected the behavior and the ‘session expired’ message only shows up in case it’s expired indeed.

We also added the ability to assign custom statuses to declined and new orders. Just in case you wanted to or if it’s necessary for integration with 3rd-party systems, e.g. accounting software.

There are also a few minor changes not worth mentioning here but making your checkout a tiny bit better for you and your customers.

==Changelog==

So to sum up, here’s the list of all changes for X-Payments connector for Zoey v1.8.12.

* Show different payment methods depending on the client’s currency.
* Support for multi-address checkout (i.e. shipping to multiple addresses).
* Correct behavior for the expired payment tokens at checkout. "Payment session expired" alert is not shown for the returning customers.
* Ability to specify status for declined and new orders.
* Minor changes.

X-Payments:V3.1.4 Released

2018-10-09T08:19:03Z

Nastya: /* Other important changes: */

Just a couple of months ago we released X-Payments version 3.1.3 and today the freshly-baked v3.1.4 is out! That’s been a lot of work and we are truly proud of the result.

So, enough talk, let’s see what’s new there.

First of all, there are some changes that require action from your side if you’re using Kount antifraud service.

Kount certificates have been deprecated for a while now and in the new library (RIS API 6.9.5) they have been removed and will no longer be supported. Instead, you should use API key and “Configuration key”. You will need to request the configuration key from Kount because it is now mandatory to make inquiries. These measures are intended for extra security and should not be neglected. 

==Other important changes: ==

<ul><li>We added new payment gateway integrations: BillriantPay and Netevia gateway. </li>
<li>Updated Bambora (Beanstream) library. 
In certain situations when Bambora required additional verification and 3-d secure was disabled in X-Payments, transactions failed with an unknown error. We handled the situation and now in such cases a warning shows up.</li>
<li>eWay Rapid: fixed issues with one-digit expiration month value. 
In some cases, a customer entered only one digit in the month field (e.g. 6 for June) whereas eWay Rapid payment gateway required a two-digit code. In this situation the transaction used to fail. Now, we’ve corrected this behavior and a zero is automatically added in front of the single digit. </li>
<li>Customer login is passed to Paypal Pro (Payflow API) as CUSTOM field. 
In some cases, a store administrator needs shopping cart customer login and for such situations, we added the ability to send this information in the CUSTOM field. </li>
<li>We have added “Philippine peso” currency support to PayPal Pro (PayPal API). </li>
<li>Issue with long billing addresses in Intuit Quickbooks was fixed. 
In a situation when a billing address was longer than 30 digits, transaction used to fail. We corrected the issue and now the address is cut to 30 digits. </li>
<li>Changed session cookie name and path. 
For self-hosted X-Payments installations, this name used to be similar to X-Cart’s cookie and it caused conflict. To avoid issues with X-Cart located on a higher level domain, we decided to use a completely different cookie name. </li>
<li>Changed “credit” to “credit or debit” label on payment form (shown only when iframe is disabled) and made it translatable. </li>
<li>We also made some minor changes in the interface and behavior to ensure smooth work and security, just as always. </li>
</ul>

For those our clients who use X-Payments Hosted, we will be performing the upgrade as usual, within two weeks from now. No action from your side is required, the upgrade will not disrupt your store’s work. You will be notified additionally after the upgrade is complete. With any questions or concerns, please [https://www.x-payments.com/contact-us.html contact us], we are always here to help.

If you use X-Payments Enterprise, you may find the necessary upgrade files and the [https://www.x-payments.com/help/X-Payments:Upgrading Upgrade Instructions] in the File Area section in your [https://secure.x-cart.com/ HelpDesk] account. Please do let us know if you need any help with the upgrade.

X-Payments:V3.1.4 Released

2018-10-03T07:59:28Z

Nastya:

Just a couple of months ago we released X-Payments version 3.1.3 and today the freshly-baked v3.1.4 is out! That’s been a lot of work and we are truly proud of the result.

So, enough talk, let’s see what’s new there.

First of all, there are some changes that require action from your side if you’re using Kount antifraud service.

Kount certificates have been deprecated for a while now and in the new library (RIS API 6.9.5) they have been removed and will no longer be supported. Instead, you should use API key and “Configuration key”. You will need to request the configuration key from Kount because it is now mandatory to make inquiries. These measures are intended for extra security and should not be neglected. 

==Other important changes: ==

<ul><li>We added new payment gateway integrations: BillriantPay and Netevia gateway. </li>
<li>Updated Bambora (Beanstream) library. 
In certain situations when Bambora required additional verification and 3-d secure was disabled in X-Payments, transactions failed with an unknown error. We handled the situation and now in such cases a warning shows up.</li>
<li>eWay Rapid: fixed issues with one-digit expiration month value. 
In some cases, a customer entered only one digit in the month field (e.g. 6 for June) whereas eWay Rapid payment gateway required a two-digit code. In this situation the transaction used to fail. Now, we’ve corrected this behavior and a zero is automatically added in front of the single digit. </li>
<li>Customer login is passed to Paypal Pro (Payflow API) as CUSTOM field. 
In some cases, a store administrator needs shopping cart customer login and for such situations, we added the ability to send this information in the CUSTOM field. </li>
<li>We have added “Philippine peso” currency support to PayPal Pro (PayPal API). </li>
<li>Issue with long billing addressed in Intuit Quickbooks was fixed. 
In a situation when a billing address was longer than 30 digits, transaction used to fail. We corrected the issue and now the address is cut to 30 digits. </li>
<li>Changed session cookie name and path. 
For self-hosted X-Payments installations, this name used to be similar to X-Cart’s cookie and it caused conflict. To avoid issues with X-Cart located on a higher level domain, we decided to use a completely different cookie name. </li>
<li>Changed “credit” to “credit or debit” label on payment form (shown only when iframe is disabled) and made it translatable. </li>
<li>We also made some minor changes in the interface and behavior to ensure smooth work and security, just as always. </li>
</ul>

For those our clients who use X-Payments Hosted, we will be performing the upgrade as usual, within two weeks from now. No action from your side is required, the upgrade will not disrupt your store’s work. You will be notified additionally after the upgrade is complete. With any questions or concerns, please [https://www.x-payments.com/contact-us.html contact us], we are always here to help.

If you use X-Payments Enterprise, you may find the necessary upgrade files and the [https://www.x-payments.com/help/X-Payments:Upgrading Upgrade Instructions] in the File Area section in your [https://secure.x-cart.com/ HelpDesk] account. Please do let us know if you need any help with the upgrade.

X-Payments:V3.1.4 Released

2018-10-03T07:58:43Z

Nastya: Nastya moved page X-Payments:V. 3.1.4 Released to X-Payments:V3.1.4 Released

Just a couple of months ago we released X-Payments version 3.1.3 and today the freshly-baked v3.1.4 is out! That’s been a lot of work and we are truly proud of the result.

So, enough talk, let’s see what’s new there.

First of all, there are some changes that require action from your side if you’re using Kount antifraud service.

Kount certificates have been deprecated for a while now and in the new library (RIS API 6.9.5) they have been removed and will no longer be supported. Instead, you should use API key and “Configuration key”. You will need to request the configuration key from Kount because it is now mandatory to make inquiries. These measures are intended for extra security and should not be neglected. 

==Other important changes: ==

<ul><li>We added new payment gateway integrations: BillriantPay and Netevia gateway. </li>
<li>Updated Bambora (Beanstream) library. 
In certain situations when Bambora required additional verification and 3-d secure was disabled in X-Payments, transactions failed with an unknown error. We handled the situation and now in such cases a warning shows up.</li>
<li>eWay Rapid: fixed issues with one-digit expiration month value. 
In some cases, a customer entered only one digit in the month field (e.g. 6 for June) whereas eWay Rapid payment gateway required a two-digit code. In this situation the transaction used to fail. Now, we’ve corrected this behavior and a zero is automatically added in front of the single digit. </li>
<li>Customer login is passed to Paypal Pro (Payflow API) as CUSTOM field. 
In some cases, a store administrator needs shopping cart customer login and for such situations, we added the ability to send this information in the CUSTOM field. </li>
<li>We have added “Philippine peso” currency support to PayPal Pro (PayPal API). </li>
<li>Issue with long billing addressed in Intuit Quickbooks was fixed. 
In a situation when a billing address was longer than 30 digits, transaction used to fail. We corrected the issue and now the address is cut to 30 digits. </li>
<li>Changed session cookie name and path. 
For self-hosted X-Payments installations, this name used to be similar to X-Cart’s cookie and it caused conflict. To avoid issues with X-Cart located on a higher level domain, we decided to use a completely different cookie name. </li>
<li>Changed “credit” to “credit or debit” label on payment form (shown only when iframe is disabled) and made it translatable. </li>
<li>We also made some minor changes in the interface and behavior to ensure smooth work and security, just as always. </li>
</ul>

For those our clients who use X-Payments Hosted, we will be performing the upgrade as usual, within two weeks from now. No action from your side is required, the upgrade will not disrupt your store’s work. You will be notified additionally after the upgrade is complete. With any questions or concerns, please [https://www.x-payments.com/contact-us.html contact us], we are always here to help.

If you use X-Payments Enterprise, you may find the necessary upgrade files and the [https://www.x-payments.com/help/X-Payments:Upgrading Upgrade Instructions] in the File Area section in your [https://secure.x-cart.com/ HelpDesk] account. Please do let us know if you need any help with the upgrade.

X-Payments:V. 3.1.4 Released

2018-10-03T07:58:43Z

Nastya: Nastya moved page X-Payments:V. 3.1.4 Released to X-Payments:V3.1.4 Released

#REDIRECT [[X-Payments:V3.1.4 Released]]

X-Payments:V3.1.4 Released

2018-10-03T07:57:57Z

Nastya: Created page with "Just a couple of months ago we released X-Payments version 3.1.3 and today the freshly-baked v3.1.4 is out! That’s been a lot of work and we are truly proud of the result...."

Just a couple of months ago we released X-Payments version 3.1.3 and today the freshly-baked v3.1.4 is out! That’s been a lot of work and we are truly proud of the result.

So, enough talk, let’s see what’s new there.

First of all, there are some changes that require action from your side if you’re using Kount antifraud service.

Kount certificates have been deprecated for a while now and in the new library (RIS API 6.9.5) they have been removed and will no longer be supported. Instead, you should use API key and “Configuration key”. You will need to request the configuration key from Kount because it is now mandatory to make inquiries. These measures are intended for extra security and should not be neglected. 

==Other important changes: ==

<ul><li>We added new payment gateway integrations: BillriantPay and Netevia gateway. </li>
<li>Updated Bambora (Beanstream) library. 
In certain situations when Bambora required additional verification and 3-d secure was disabled in X-Payments, transactions failed with an unknown error. We handled the situation and now in such cases a warning shows up.</li>
<li>eWay Rapid: fixed issues with one-digit expiration month value. 
In some cases, a customer entered only one digit in the month field (e.g. 6 for June) whereas eWay Rapid payment gateway required a two-digit code. In this situation the transaction used to fail. Now, we’ve corrected this behavior and a zero is automatically added in front of the single digit. </li>
<li>Customer login is passed to Paypal Pro (Payflow API) as CUSTOM field. 
In some cases, a store administrator needs shopping cart customer login and for such situations, we added the ability to send this information in the CUSTOM field. </li>
<li>We have added “Philippine peso” currency support to PayPal Pro (PayPal API). </li>
<li>Issue with long billing addressed in Intuit Quickbooks was fixed. 
In a situation when a billing address was longer than 30 digits, transaction used to fail. We corrected the issue and now the address is cut to 30 digits. </li>
<li>Changed session cookie name and path. 
For self-hosted X-Payments installations, this name used to be similar to X-Cart’s cookie and it caused conflict. To avoid issues with X-Cart located on a higher level domain, we decided to use a completely different cookie name. </li>
<li>Changed “credit” to “credit or debit” label on payment form (shown only when iframe is disabled) and made it translatable. </li>
<li>We also made some minor changes in the interface and behavior to ensure smooth work and security, just as always. </li>
</ul>

For those our clients who use X-Payments Hosted, we will be performing the upgrade as usual, within two weeks from now. No action from your side is required, the upgrade will not disrupt your store’s work. You will be notified additionally after the upgrade is complete. With any questions or concerns, please [https://www.x-payments.com/contact-us.html contact us], we are always here to help.

If you use X-Payments Enterprise, you may find the necessary upgrade files and the [https://www.x-payments.com/help/X-Payments:Upgrading Upgrade Instructions] in the File Area section in your [https://secure.x-cart.com/ HelpDesk] account. Please do let us know if you need any help with the upgrade.

X-Payments:Magento Connector v1.8.3

2018-08-30T12:06:41Z

Nastya: Nastya moved page X-Payments:Magento1-Connector-1.8.3 to X-Payments:Magento Connector v1.8.3

We have released an updated Magento 1 connector. We have improved both admin and customer experience to make payment processing even smoother.
=Improvements=
==Admin experience==
<ul>
<li>Admin backend reorganised. </li>
<li>Developer mode removed. 
Some sources say the developer mode does not fully comply with the PCI standards because such an account used to use HTTP instead of HTTPS. However, if you need an X-Payments instance on a separate HTTP server, for testing or development needs, you may create [https://letsencrypt.org/ a free SSL certificate] for testing purposes. </li>
<li>Improved welcome page. 
It became even more welcoming and better-looking than before. :) </li>
<li>Specific status added for declined pages. 
In the cases when a payment gateway declines a payment, the X-Payments admin can set up a specific status for such a payment. </li>
</ul>

==Customer experience==
<ul>
<li>Security and performance optimizations at checkout. 
We did some magic to improve the checkout page security (as though it needed improvement) and as a side effect, we made the checkout process faster. </li>
</ul>

=Bug Fixes=

==Admin area==
<ul>
<li>Appearance of the warning buttons on the order page corrected. 
After an internal X-Payments check or a payment gateway check, or any other external service check (Kount, No-Fraud, or Signifyd), in some cases, a manual check is necessary. In this case, the admin should either accept the payment or decline it, depending on the situation. For this purposes, there are two buttons: Accept and Decline. They used to work incorrectly in some cases or cause errors. The issue is now fixed and their appearance improved. </li>
</ul>

==Customer interface==
<ul>
<li>Bug fixes at checkout. </li>
<li>Appearance of the “My Payment Cards” link. 
The link used to show up incorrectly or not show up where it should have been. We fixed this bug in the new version. </li>
<li>Behavior issues when the payment session expires at checkout. 
The expired payment session used to show up for several days which caused inconvenience. We corrected that behavior. </li>
<li>Cart/quote state for the declined payment. 
In some cases, if a payment was declined by the payment gateway or an error occurred, the order used to be placed. This order was assigned a wrong status and the cart was automatically emptied. We have fixed this issue and now in case a payment does not go through, your client stays at checkout and can try to pay once more. In case of a failed payment an order is still created in the admin backend but now you can set up which status it should get. – canceled, declined, failed, or any custom status. </li>
<li>Shipping address processing (affected Signifyd anti-fraud service). 
In some cases, shipping address used to be sent forward to Signifyd wrongly. It caused issues with correct risk-assessment. We fixed the issue. </li>
</ul>

=Technical details=
==Internal==
<ul>
<li>API 1.9 support. 
X-Payments can now send more info on a payment, that means you can get more details in the admin area of your online store, without having to log into your X-Payments backend. Also, we updated data exchange mechanism, which improved the speed of X-Payments interaction with your store.</li>
<li>Order placement and payment processing procedures optimised. </li>
<li>Caching of the communication between X-Payments and your online store implemented. </li>
<li>Improved logging. </li>
<li>Correct cc_trans_id for successful payment which follows a failed one. </li>
<li>Fixed responding for callback requests. </li>
</ul>

==External==
<ul>
<li>Updated integration with StoneEdge. </li>
<li>Updated integration with the Vendor theme by Eternal. </li>
</ul>

X-Payments:Magento1-Connector-1.8.3

2018-08-30T12:06:41Z

Nastya: Nastya moved page X-Payments:Magento1-Connector-1.8.3 to X-Payments:Magento Connector v1.8.3

#REDIRECT [[X-Payments:Magento Connector v1.8.3]]

X-Payments:Magento Connector v1.8.3

2018-08-30T12:06:17Z

Nastya:

X-Payments:V. 3.1.3 Released

2018-07-16T09:35:05Z

Nastya: Nastya moved page User:Nastya to X-Payments:X-Payments 3.1.3 Released: Important Bug Fixing Update Available

User:Nastya

2018-07-16T09:35:05Z

Nastya: Nastya moved page User:Nastya to X-Payments:X-Payments 3.1.3 Released: Important Bug Fixing Update Available

#REDIRECT [[X-Payments:X-Payments 3.1.3 Released: Important Bug Fixing Update Available]]

X-Payments:V. 3.1.3 Released

2018-07-16T09:32:11Z

Nastya: Created page with "We have released a fresh X-Payments v. 3.1.3. We’ve addressed a few annoying bugs, so update is strongly recommended. These are the issues that have been fixed: <ul><li>..."