CiviContribute can be used to record and manage payments accepted through channels outside of CiviCRM, such as checks, money orders, cash, and PoS terminals. However, it is very convenient to allow users to make payments directly through CiviCRM pages for donations, memberships, and events. This requires the organization to get an account with payment processor, and to configure a CiviCRM payment processor plugin to connect with your account at the payment processor. Once setup, you likely will not need to change the configuration again.
Plugins are available to enable CiviCRM to process payments directly via several payment processors. Their features, the countries they are available in, their costs, their ease of use by your users, and whether you need a Merchant account a bank or an SSL certificate for you website vary by payment processor. This information is tabulated below for your reference.
Setup and Configuration
To setup a new payment processor, click on Administer > System Settings > Payment Processors, Add Payment Processor.
Select a Payment Processor Type that corresponds to the payment processor you have setup an account with after referring to the Processor Comparison Chart below. Provide a name for the payment processor that will be used to enable the payment processor on Contribution and Event Pages in your system. Select a Financial Account that your bookkeeping system uses to track monies in the payment processor account. Usually you will want to have a separate Financial Account for each payment processor.
Optionally provide a description for the payment processor, and indicate if the payment processor should be Enabled, which makes it available for use on Contribution and Event pages. For convenience in configuring those pages, you can indicate that one payment processor is the Default.
The remaining fields to be setup on this form vary by Payment Processor. Refer to the links in the individual Processor Configuration Guides below for setup instructions for your specific payment processor type.
Processor Comparison Chart
See http://book.civicrm.org/user/contributions/payment-processors for an overview of things to consider when selecting a processor.
*Note that 'triggered recurring' refers to where a processor retains the authorization on the credit card and will recharge it on request. This is not currently implemented in civiCRM.
Click on the appropriate link below for information on set-up for your processor of choice.
This page will be updated as support for additional processors becomes available. If you are interested in developing a plug-in for another processor - review this page. Then contact the CiviCRM development team at firstname.lastname@example.org if you need further guidance.
Processor Configuration Guides
Page: Authorize.net Configuration Page: Card Access Services CASConnect Configuration Page: First Data, Linkpoint, Global Gateway Page: Google Checkout Configuration Page: iATS Payments Configuration Page: Moneris Configuration Guide Page: PayFlow Link Page: PayJunction Configuration Page: PayPal Website Payments Pro and Express Configuration Page: PayPal Website Payments Standard and Recurring Contributions Page: Trouble shooting payment processor setup Page: Setting up Moneris Hosted Payment Processor for CiviCRM Page: Setting up Ogone Payment Processor for CiviCRM