Issue number/start date - different method?

[Richardpixel]

At the very least a simple warning box when selecting non compliant options should warn the user with a link to further information.

I second that!

[TraceyG]

And the answer is?

Sorry guys, this hasn't been forgotten, but at the moment Chris Barling is on holiday and development are stretched with holidays, 9.0.3 and support issues. I have chased them again and will see if I can get a response soon.

[leehack]

Ring him on the batphone Tracey. Go on, i dare you .

[Benjamin Dyer]

Good Afternoon Everyone,

Its important to note PCI-DSS compliance is the responsibility of the merchant.

Actinic offers the capability to integrate and use a wide range of PSPs and we can not be responsible for any 3rd party offerings. For PayPal pro questions I suggest you contact PayPal directly.

We recommend Actinic Payments as an easy solution for compliance.

Hope that clears it up.

Ben, Actinic

[Darren B]

* Puts on tin hat and hides in corner

[leehack]

It may be a good idea to have a word with your newsletter creators as i'm sure you would not want to be seen heavily promoting a service (like you have for the past 12 months) when you don't even know if it complies? I'm pretty sure we've had an email newsletter in the past month promoting it.

* Puts on tin hat and hides in corner

Indeed, can't believe i just read that.

[TraceyHand]

I'm hiding behind Darren...he's bigger than me!

[Mike Hughes]

Good Afternoon Everyone,

Its important to note PCI-DSS compliance is the responsibility of the merchant.

Actinic offers the capability to integrate and use a wide range of PSPs and we can not be responsible for any 3rd party offerings. For PayPal pro questions I suggest you contact PayPal directly.

We recommend Actinic Payments as an easy solution for compliance.

Hope that clears it up.

Ben, Actinic

Ben, That answer isn't even half hearted. It's a waste of space.

The issue with paypal pro is that the Actinic integration requires the card details to be captured on the merchants website using the actinic form. It's this capturing of the data that defeats PCi-DSS compliance, not paypal itself.

Secondly, you cannot ethically promote non-compliant CC processing and then claim "it's nothing to do with us". Complete tosh.

Mike

[TraceyG]

I've just taken a look on Paypals site and found:

'If you’re using Website Payments Pro or Virtual Terminal or your method of integration means you store card data, you are therefore responsible for your own PCI DSS compliance. To help you learn about security, privacy and disclosure PayPal has published a free guide that explains the security threats to your business and how you can comply with PCI DSS. '

However, the link to the free guide doesn't seem to work. I've emailed them about that and to find out why the Website Payments Pro is not PCI-DSS compliant. Maybe I can put a kb article together about this when I get the answers.

[jont]

Indeed, can't believe i just read that.

Did Ben used to be an MP? Where's Jeremy Paxman when you need him?

[Benjamin Dyer]

lol, I like that, I did once bump into JP, pussycat in real life.

[TraceyG]

I've emailed them about that and to find out why the Website Payments Pro is not PCI-DSS compliant.

I'm not having much luck finding this info out so far . Trying a different route, hopefully, I'll have an answer soon.

[TraceyG]

http://community.actinic.com/showthread.php?t=45030
Also see the pci-dss page on our website.