X-Payments v1.0.6 released
 

Hi Everyone,

Detailed post about this release is available at
http://www.x-cart.com/blog/x-cart-455-and-xpayments-106-released.html

I want to thank Carpeperdiem for his valuable input that helped us to improve X-Payments with this release.

Major X-Payments improvements this time are:
1) improved iFrame integration algorithm and design changes - duplicate and not-finished orders should cease almost completely.
2) 4 last digits are displayed in X-Cart admin back-end if an order has been processed via X-Payments.
3) credit card type is selected automatically basing credit card # entered - this helps to reduce payment attempts by customers who forget to specify their card type at checkout.
4) X-Payments iFrame integration works with X-Cart Fast Lane Checkout now, too.

And some bug-fixes.

Re: X-Payments v1.0.6 released
 

LOL!

That is great news. I am looking forward to not sleeping this week. Thanks Alex and x-p team! :-)

Re: X-Payments v1.0.6 released
 

Yes, you need to upgrade X-Payments to v1.0.6 if you want to use X-Cart v4.5.5.
We will do automatic upgrade for all users of X-Payments Hosted service.

Re: X-Payments v1.0.6 released
 

Alex,

Having never done an X-Payments "upgrade" - is there any benefit from just starting over and doing a brand new install in a new parallel directory? For example, if xp 1.0.5 is currently in xpayments-server/secure/ the 1.0.6 install would be in xpayments-server/secure2/ ???

Is there a licensing issue that will prevent me from doing this?

I understand that I will lose all history and logs - but I want this install to be virgin.

Does this make sense?

Alternatively, do you bundle an upgrade script that doesn't abort if one file is different? The X-Cart version updater is intelligent in this way -- but we learned the X-Cart "module" upgrader is not as friendly or intuitive (that's the nice way to describe it).

I will follow your guidance. Thanks!

J

Re: X-Payments v1.0.6 released
 

And will the last-4 be available to invoice templates as a $variable ? I hope so. Makes for happy customers.

Re: X-Payments v1.0.6 released
 

:oops: We didn't implement this, but since data is passed to X-Cart you can just customize your email template at X-Cart side to include the 4 digits into order notifications.

Re: X-Payments v1.0.6 released
 

> Having never done an X-Payments "upgrade" - is there any benefit from just
> starting over and doing a brand new install in a new parallel directory? For
> example, if xp 1.0.5 is currently in xpayments-server/secure/ the 1.0.6 install
> would be in xpayments-server/secure2/ ???
>
> Is there a licensing issue that will prevent me from doing this?

There won't be any licensing issue if you are not using a test copy for real production and more than 30 days.

X-Payments upgrade is much easier than X-Cart's one. See http://help.x-cart.com/index.php?title=X-Payments:Upgrading
It is re-writing of files mostly + a couple of small changes.
You should be able to upgrade X-Payments yourself, but if you want to use a new clean install - why not. Just remove the redundant copy when you are done.


> Alternatively, do you bundle an upgrade script that doesn't abort if one file is
> different? The X-Cart version updater is intelligent in this way -- but we learned
> the X-Cart "module" upgrader is not as friendly or intuitive (that's the nice way
> to describe it).

As I said above X-Payments upgrade differs a lot from X-Cart one. Mostly due to the fact that X-Payments is not a customizable software due to PA-DSS certified status.

Re: X-Payments v1.0.6 released
 

Alex, confused by your answer.
In XP 1.0.5 and xcart 4.5.4, it does send the 4-digits back to the admin, but in an encrypted string that is only visible in the payment gateway log. like this:

==============================
+ Payment gateway log

--- Advanced info ---

Message:APPROVAL
txn_id: XXX
AVS:Address (Street) and 5 digit ZIP match
CVV:CVV2 Match
--- Advanced info ---
Reason: Approved: Payment is charged
(last 4 card numbers: 1234);
(card type: VISA);
==============================

What I was hoping for is that the contents of the last-4 card number and card type were returned to xpc/xcart as unencrypted strings (variables) that a template can then use --
we could then place this in the customer invoice, etc...

Payment method: VISA 1234

Are we talking about the same thing here? I hope so.

Re: X-Payments v1.0.6 released
 

Jeremy,

> In XP 1.0.5 and xcart 4.5.4, it does send the 4-digits back to the admin, but in
> an encrypted string that is only visible in the payment gateway log. like this:

We researched this issue and I fear a small customization is needed to have the last 4 digits displayed in an email template. This fell out of my sight for some reason otherwise I would have it implemented in our latest release.

Developers suggest using something like this in your email template:

Re: X-Payments v1.0.6 released
 

it should be "preg_match"

Re: X-Payments v1.0.6 released
 

Upgraded successfully to 1.0.6, it's working fine with my live site running 4.4.5. However, I'm working on a new version of the site which I just upgraded to 4.5.5.

The hangup I'm having is this - I'm trying to add X-Payments as a payment method now - when in the X-Payments Connector, I click on "Import payment methods". It says it is successful, but nothing shows up under the payment methods screen. Ideas?

Re: X-Payments v1.0.6 released
 

The set of this one is a lot nicer.... This should make customers happy

Re: X-Payments v1.0.6 released
 

I have xcart 4.5.2, will xpayments 1.0.6 work well with it?

Re: X-Payments v1.0.6 released
 

It will work fine with any X-Cart version that has X-Payments connector installed or built-in, but if you want the iFrame integration - it works with 4.5.5+ versions.

Re: X-Payments v1.0.6 released
 

Carpeperdiem, when I upgraded from X-Payments 1.04 to 1.05, I did what you are considering. I have 5 stores that use X-Payments. I consider it risky to commit to widespread use of a new version of ANY software before sampling the new version for a while, so I temporarily had both versions running (same site, different directories) while I made sure that 1.05 was ok. I waited maybe a week before moving all stores over to 1.05.

I plan to do the same this week when I make the move to 1.06. I'm looking forward to fewer dupe orders and not finished orders. I also plan to try the 4.5.5 iframe on one site, and if all goes well like you I'll be spending time (months?) upgrading all 5 modified, templated stores to 4.5.5. I hope they stay there a while.

Our business was down this past holiday season. I don't like anything that spooks a customer during checkout.

X-Payments 1.0.6 on 4.5.3 not so good so far
 

I set up a 4.5.5 store as planned using my 'mobile' license, but have had trouble in moving the license under the 'My Licenses' tab at the Help Desk. I wrote for help on that.

Meanwhile, I still wanted to try 1.0.6, so instead tried to get it running on a live 4.5.3 store currently using 1.0.5.

Initially there was in "Internal Error" message that came up and the credit card form never appeared. The error log said to go into X-Payments and approve a template file change, which I did and the error went away. I don't recall this happening when I went from 1.0.4 to 1.0.5. I personally changed no files.

After that 1.0.6 would show the card form and the cards would be charged, but would not return the customer to the site. The screen would be all white except in the upper left corner it says "Please wait while processing the payment details ...".

If an order is canceled while on the payment page, the customer sees a totally white page.

Behavior is the same on Chrome and FF. Trying it with the store both off and on made no difference.

Checking the forum for similar experiences, what I saw did not seem to match my case. So I decided to put 1.05 back into service.

Initially it behaved the same, so I did a round of payment method deletion, cache clearing, etc and 1.0.5 eventually returned to behave as it did before.

I see nothing in the error logs to suggest why X-Payments 1.0.6 would not take me back to the site in any case. When (if?) my 4.5.5 test site license gets moved I'll have more time to check it out because it won't be a real site and I don't have to worry about loss of sales. I may also clone the 4.5.3 onto the test site and try it that way.

Any suggestions?

EDIT: Successful transaction info reported back to X-Cart did NOT includes a transaction ID. Is this another example of not reporting back?
EDIT2: Oops. I just realized that I changed X-Payments versions and the 1.0.6 is unable to report back now.

Re: X-Payments v1.0.6 released
 

I had this problem too, what I ended up doing was going to the "payment gateway" tab, selecting all countries, then looked for my payment method and importing it from there.

Re: X-Payments v1.0.6 released
 

This worked for me to get credit card payments in - not sure how the heck to get it to import if you process more than one payment method using XPayments (i.e. you use Authorize.net through XPayments for credit cards but also want to use the iframe lite interface through xPayments to run PayPal as well...)

Re: X-Payments v1.0.6 released
 

Yeah, I forgot to mention in my initial post this:

* X-Payments iFrame integration works with X-Cart Fast Lane Checkout now, too.

Re: X-Payments v1.0.6 released
 

Alex,

Unfortunately, X-Cart management decided to make an absolute mess of an upgrade cycle -- and the benefits of X-Payment 1.0.6 will be lost on stores that are required to upgrade to 4.5.5

As you will read in my posts on this -- I am furious that X-Cart decided to bundle major, significant so-called "security" improvements into the 4.5.5 release.

What could have been some bug fixes and fixing some issues with the October release, instead added layers of complexity and introduced brand new features, that frankly are not needed and do not belong in a dot release.

I'm a very experienced xcart owner. I have done many, many , many upgrades. This one takes the cake for the most complexity - and total lack of testing before rollout.

I am suggesting that you recall it and try again, without the security "enhancements" which do not belong.

This upgrade was not ready for production.

PS -- Installing XP 1.0.6 was effortless. But I can't test it without 4.5.5 if I want the iFrame and FLC features (which is the reason for the bug fixes in the first place!)

Re: X-Payments v1.0.6 released
 

Does anyone else has this problem with x-payment? I'm running XC v4.5.5 and XP v1.0.6 using iframe to accept payments. So here is the issue.... everytime I add a product and go to checkout page (tried OPC and FLC) enter my personal details and then go back to home page or product page I'm getting "X-Payment Started" status in orders page.

Can someone help or direct me to right direction to solve this?

Re: X-Payments v1.0.6 released
 

Alex,

This does not work. It appends /"} -- no numbers. Tried this with XP 1.0.5 and 1.0.6
Also corrected the code: text_decrypt|preg_macth - to text_decrypt|preg_match

Not having the last-4 digits on the invoice is not doing our customers any favors. There is obviously no security risk and no PCI compliance issues with the last-4 and card type.

ALso in 4.5.4 - $order.details is empty on order_invoice.tpl and /order.php?orderid=xxxxxx

Is there another way to get this encrypted data from XP?

Try again, please?
Thanks,
J

Re: X-Payments v1.0.6 released
 

Sorry, Jeremy. I am not the best person to advise on coding :oops:

I hope someone else will suggest the solution.

Re: X-Payments v1.0.6 released
 

The solution is for X-Payments to not obfuscate or encrypt the credit card type and last 4 digits, and pass these variables back to XPC, right? :-)

It is agreed that this data does not break PCI compliance, so there is no reason it shouldn't be shared from XP, right? I hope this is on your list of things to fix?

Thx
J