8

As I'm sure you are learning, PCI compliance is a complicated business. The payment processor (I discuss eWay below) and your own operations play the biggest role in PCI compliance. Some of the issues on the organization's end are: your own server's security protocols (including, but not limited to, SSL) how the payment information is transferred to the ...


4

You shouldn't need a payment processor to do a self-signup. But also - you don't need to meet the standards for PCI compliance that you're suggesting if you choose an appropriate payment processor. Use either an "off-site" processor like PayPal Standard, or one that loads Javascript on your page to collect credit card info so that it never ...


3

I have had experience with AuthorizeNet and PCI compliance both with CiviCRM installs and other sites with custom configurations. the process is the same, generally the merchant account provider will require scans through a service provider. You will most likely need to make adjustments to server settings, primarily port/firewall adjustments. Depending on ...


3

A great explanation of PCI compliance and things an organization should consider relating to PCI compliance is available from this CiviCon Denver 2015 talk: CiviCon Denver Data Security and Payment. See my answer here for other relevant info: https://civicrm.stackexchange.com/a/10453/105 We also use Drupal 7 and Civi 4.6, but are hosted on MediaTemple and ...


2

CiviCRM 4.5.x branch has stopped receiving security updates a very long time ago. Best to upgrade to 4.6.x or 4.7.x as soon as possible! If you need help - find a partner near you in the partner listings: https://civicrm.org/partners-contributors


1

Depending on your CMS you might be able to do all of that without the need for CiviCRM. If you are worried about credit card information then CiviCRM has a number of payment processor options which mean you never see a credit card number, just the transaction ID of your payment processor of choice - check out https://civicrm.org/extensions/stripe-payment-...


1

So far there is some support for transparent redirect in the Omnipay extension but not in the core codebase, as it requires an extra form in the process. It's likely that at some point Omnipay will ship with core - so developing it in this context is fine. However, although there is an Omnipay library for Paypal its not currently in the extension


1

I have had to research this subject for my organisation so thought I'd add this answer with more eWAY-specific detail. The CiviCRM core eWAY payment processor and the two 'eWAY Recurring' extensions here and here all use eWAY's Legacy Direct XML API. The CiviCRM Omnipay extension only recently added support for eWAY. This extension is built on the Omnipay ...


Only top voted, non community-wiki answers of a minimum length are eligible