PCI DSS free Gateway Plugins

  • Posts: 55
  • Thank you received: 3
8 years 2 months ago #249763

-- Joomla version -- : n/a
-- PHP version -- : n/a
-- Browser(s) name and version -- : n/a
-- Error-message(debug-mod must be tuned on) -- : n/a

I am wondering if there is any discussion (couldn't find any), re the use of payment plugins that don't require PCI DSS compliance on the host server. I was just looking at the MIGS plugin, but there is no indication on the product page as to whether it may or may not be.

On researching the options, I think the simple way to avoid PCI DSS requirements (on your hosting environment) is to use Direct Post as the post method; so that even whilst a form for cc details may be generated on your own hosted site, the action of that form submits the details directly to the payment gateway concerned, with then a 'callback' from the gateway to your own site with a paid/notpaid result.

Most of the plugins I have looked at, do not do this, but instead post the form (including cc data) into the hikashop scripts (thus then requiring your hosting to meet PCI DSS compliance - ie very expensive hosting.)

As coding wise, it can be straightforward to use direct post, I am not sure why very few payment plugins use this action? I see that 'stripe' uses an iframe popup on one example i saw (in a wordpress shopping cart) - with the iframe being generated by the stripe site - so it may be that those guys have thought about how most shared hosting in the world does not meet PCI DSS security requirements.

I would ask the hikashop devs to consider a clear indication on each of the payment plugins to indicate whether the end user should insist on PCI DSS hosting to use the particular plugin or not (sorry if I have missed this, and it already exists)

Thanks
Ian

Please Log in or Create an account to join the conversation.

  • Posts: 82864
  • Thank you received: 13372
  • MODERATOR
8 years 2 months ago #249795

Hi,

Most payment plugins actually redirect the customer to the payment gateway for entering the credit card at the end of the checkout and thus don't require that.
Only a handful of them ask the credit card data during the checkout, like the MIGS plugin and indeed, in that case, PCI DSS is strongly advised on the hosting.
Having a credit card form sending the credit card data to the payment gateway in the middle of the checkout is tricky. The issue is that the checkout pages are a form already. And having a form in a form is not possible. That's why the iframe is a good compromise, but not all payment gateways offer that capability. Some also propose to have the credit card form at the end of the checkout, in which case there is no checkout form anymore.

Basically PCI DSS compliance should be asked for payment plugins where you enter the credit card data in the middle of the checkout: PayPal Pro, Authorize.net in AIM, MIGS, the "credit card" payment plugin, eSelect, iPayDNA, iveri, PayJunction, Payment Express in PxPost, VirtualMerchant, WestPac in API, WorldNetTPS.
As you can see, for 4 of them, there is an alternative solution with the same payment gateway (another API which doesn't collect the credit card during the checkout).

Please Log in or Create an account to join the conversation.

  • Posts: 55
  • Thank you received: 3
8 years 2 months ago #249866

nicolas wrote: Hi,

As you can see, for 4 of them, there is an alternative solution with the same payment gateway (another API which doesn't collect the credit card during the checkout).

Thanks Nicolas
Which four sorry?
ie not sure which one's you mean

Please Log in or Create an account to join the conversation.

  • Posts: 82864
  • Thank you received: 13372
  • MODERATOR
8 years 2 months ago #249868

PayPal, Authorize.net, Payment Express and WestPac.

Please Log in or Create an account to join the conversation.

Time to create page: 0.059 seconds
Powered by Kunena Forum