X-Cart forums

[balinor]

Dog and Acqua - here's the low down:

PA-DSS compliance means the cart you use has to meet a set of standards, this is different from the basic PCI compliance which deals with your server and how you handle CC info. So even if you don't store CC inf (and you should NEVER store CC info), and your scan comes back clean, you still need X-Payments if you want to process credit cards through a gateway on your site. X-Cart itself won't be compliant (until 4.4 or higher, who knows) but X-Payments will sort of bypass that requirement - all cc info will go through the X-Payments module. So yes, everyone who processes CC data through their web site (and not on a third party site like PayPal, Google Checkout, Authorize.net SIM, etc) will need this module.

Acquamarina, if a customer does not enter cc info on your site, you don't need to worry about it. This has nothing to do with the partial payment issue you linked, that is a completely different problem that won't be solved by X-Payments. That requires some customization to the Authorize.net payment module, which Qualiteam has yet to address, but you still have a year until that kicks in.

Hope that clears it up a little.

[Acquamarina]

Hi, Balinor,

That helped a lot, thank you so much. It looks like I will stay with PP and GoogleCheckout until this is sorted out.

Is this compliance also required if PayPal Pro is used? I would imagine it is...

Thanks again!

[DogByteMan]

And transmitting data directly over SSL to a gateway is less safe than this HOW?

[Acquamarina]

I guess for now all I can do is follow the thread. To me it looks as if there is no patch for 4.1.9 that would allow me to use the bridge module. I would have to upgrade the site to 4.2 or higher, than do it again later to a higher version for more features. Is that correct?

[DogByteMan]

Originally Posted by kevinrm

I've installed this (successfully),set this up with Authorize.net AIM, transaction keys, enabled everything, generated all keys, etc. If I try to check out, original checkout page still comes up. What are we supposed to see, something new right? At this stage I see nothing different...

(Late Note: I did not install X-Payments "Connector" so that may have something to do with it, will try it tomorrow. One tiny note at the very bottom of the X-Payments user guide is the only mention of this, I think that should be a bit more prominent, no?)

Since I have much work to do to get ready (Upgrade Shop for PHP 5.3.x and have the X-Payments altered for 4.1.12) I really would appreciate a description of how the interface works. Yes, I have completely read the manual. What I am wanting is a description of what happens from when the customer clicks checkout to order completion. Where are they entering their info, Checkout (I have One Page Checkout) or are they entering it within the X-Payments module. I can't install yet, but need to plan. A description would be nice, screen shot with it, even better.

[Duramax 6.6L]

Originally Posted by DogByteMan

Since I have much work to do to get ready (Upgrade Shop for PHP 5.3.x and have the X-Payments altered for 4.1.12) I really would appreciate a description of how the interface works. Yes, I have completely read the manual. What I am wanting is a description of what happens from when the customer clicks checkout to order completion. Where are they entering their info, Checkout (I have One Page Checkout) or are they entering it within the X-Payments module. I can't install yet, but need to plan. A description would be nice, screen shot with it, even better.

You will no longer have a one page checkout, customer enters all their info on one page, then goes to xpayments to enter credit card info, then sent back to the store with conformation. basically we are stuck with a three page checkout.

[DogByteMan]

I had sales-n-stats enterprise, which used a connector I assume is similar to what they are using here, I paid $400+, it didn't work so good. Does this connector seem to work better?

Does this not take away any advantage of having a direct gateway as opposed to PayPal or Google?

What are the requirements of PA DSS that our current checkouts do not meet?

[Duramax 6.6L]

As of July 1st, anyone processing credit cards online must use a certified shopping cart. Xcart will not be a certified shopping cart. Xpayments is Xcarts way of still being able to use your shopping cart, and using a certified credit card processing interface. Xpayments is certified to mc / visa specifications.

[DogByteMan]

So you are saying that you could not produce, for your own purposes a shopping site, including checkout mechanism of your own design and proprietary code. You have to use an approved source. Something basically sounds wrong about this whole mess. Where can one find, since I have never been contacted in any manner nor can I find any info at FirstData about all of this, the exact document for PA DSS and where is the site that deals with the code requirements to meet the standard.

[Duramax 6.6L]

Read this thread Has quite a few answers:
http://forum.x-cart.com/showthread.php?t=46073