Re: X-Payments transfer to other server with upgraded store
 

I resolved it.
I had forgotten to add the specific user to the x-payments database.

Re: X-Payments transfer to other server with upgraded store
 

Now I am getting the following message in X-Payments Connector configuration page:


X-Cart store logs:

Nevertheless, the upgraded 4.6.4 x-cart store does communicate with the migrated x-payments to the new server, since payment methods from x-payments can be re-imported.
I have to say, the only place where x-payments server IP address is defined in x-cart store admin is in the "Connection settings" tab of the X-Payments Connector configuration page, in the "IP addresses for X-Payments callbacks (optional)" setting. I cannot reach the store connection settings page, where the "X-Payment URL" setting can be set, among others. (using the 1.0.4 x-payments)

Any tips on this?

Re: X-Payments transfer to other server with upgraded store
 

I have seen this recently. I believe it should clear up once you set the x-cart store to use HTTPS on checkout and payment pages and have an SSL Certificate installed.

Re: X-Payments transfer to other server with upgraded store
 

Yes, it seems it is an SSL-missing issue, I am also getting the following error message, in 'Security' page, under 'HTTPS options' section.

Actually, I have setup the upgraded store on the new server with an IP address, with a copy of x-payments in a separate hosting account, with it's own SSL, while the old-version current store runs live in the old server.

In order to check x-payments connectivity in the upgraded store, before closing the current live old-version store, an SSL must also exist in the upgraded store environment, but this SSL currently is used for the live site (the old version).

After the current domain points to the new server, the SSL also will be transferred to this server, so I guess, only then, I will be able to check x-payments in the upgraded store.

And before this, I will close the old store and run a final database synchronization in the new server (for any recently-inserted customers, orders, etc) and also move over the final x-payments database to the x-payments new hosting account and eventually point the domain to the new server, transferring also the SSL. So, while the old store is closed and before opening the upgraded store, only then, I can test x-payments.

Is there any alternative procedure so I can test x-payments before closing the old live store and without installing an additional SSL in the upgraded store environment?

Re: X-Payments transfer to other server with upgraded store
 

What I did eventually is to change the HTTPS protocol from libCurl to OpenSSL. Also I applied the patch for POODLE vulnerability in SSLv3 (see this thread) and both the HTTPS/SSL check warning and the
error message stopped appearing.
I presume that the X-Payments Connector works ok, although I haven't found any 'Test Module' button to run a connectivity test.

Re: X-Payments transfer to other server with upgraded store
 

> although I haven't found any 'Test Module' button to run a connectivity test.

It has been removed in 4.6.4 and new connection routine is now in place - see http://help.x-cart.com/index.php?title=X-Cart:X-Payments_Connector#X-Payments_2.1.x_and_new_X-Cart_connector_modules

Re: X-Payments transfer to other server with upgraded store
 

Alex, I have the old 1.0.4 X-Payments version (as stated in previous posts in this thread).

Re: X-Payments transfer to other server with upgraded store
 

You should to upgrade to at least 1.0.6 and the new connectors work with X-Payments 1.x, too.

Re: X-Payments transfer to other server with upgraded store
 

• Quote:

  You should to upgrade to at least 1.0.6 and the new connectors work with X-Payments 1.x, too.

  Is the upgrade to 1.0.6 required for correct functionality of the X-Payments Connector in the 4.6.4 upgraded store, or can it work with 1.0.4 version?

• Does this upgrade need a payed licence? I don't seem to find 1.0.6 version in my File Area.

• Some recent orders have a 'Failed' status, with the following logs:
  
  Payment gateway log: ("Order Details" page):
  Quote:

  --- Advanced info --- Reason: Internal error (Response is not valid.<br />Check logs.) CVV info: not set /

  
  X-Cart store log:
  Quote:

  [03-Nov-2014 13:28:57] (shop: 03-Nov-2014 14:28:57) PAYMENTS message: Payment processing failure. Login: username IP: 104.10.42.129 ---- Payment method: Credit Card (Pay on next page) (X-Payments: Authorize.Net AIM) bill_output = Array ( [cvvmes] => not set / [code] => 2 [billmes] => Internal error (Response is not valid.<br />Check logs.) ) original_bill_output = Array ( [cvvmes] => not set / [code] => 2 [billmes] => Internal error (Response is not valid.<br />Check logs.) ) Request URI: /shop/payment/payment_cc.php Backtrace: /home/domain/public_html/shop/payment/payment_ccmid.php:460 /home/domain/public_html/shop/payment/payment_ccend.php:48 /home/domain/public_html/shop/payment/payment_cc.php:359

• Do the above mean that a CVV code was not input by the customer during checkout, or is it an internal x-payments error which needs fix?

• in case it needs a fix, would the upgrade to 1.0.6 most probably fix it?

• Also, when I attempted to re-deploy the configuration bundle, I got a popup warning:

. The database has been transferred from the old server to the new server (as described in the previous posts), with the same online store details. The store domain is the same, just different server and store upgrade. Should I re-add the store to X-Payments?

Re: X-Payments transfer to other server with upgraded store
 

> Is the upgrade to 1.0.6 required for correct functionality of the X-Payments
> Connector in the 4.6.4 upgraded store, or can it work with 1.0.4 version?

It is recommended. We did not test the new connectors with X-Payments versions earlier than 1.0.6. Besides 1.0.6 has many bug-fixes vs 1.0.4


> Does this upgrade need a payed licence?

Every owner of X-Payments 1.x downloadable license has free access to all versions within 1.x branch. 1.0.6 is the last version we developed in 1.x branch.


> I don't seem to find 1.0.6 version in my File Area.

I advise you to contact our CR reps via your HelpDesk account regarding this.