CiviCRM Community Forums (archive)

Hi, I suppose this is more the start of  a wiki entry than anything else but it needs a bit more input / checking that it's correct. I have used the database table as the basis for info about payment types & recurring contributions but I'm not quite sure if it's correct on whether Authorize.net does recurring payments

Basically the questions you need to consider choosing a payment processor are:

 

1)                  Hosting - Do I want to host it myself. The advantage of hosting is that the transaction is more seamless to the end customer. The disadvantage is the cost & complexity of having your own ssl cert

2)                  Regional Availability – For many countries there aren’t payment processors written that support their currencies. Paypal is the most widely available option

3)                  Merchant account vs built in – Most organizations who accept credit card payments will have their own merchant account through a bank but these usually have monthly charges which may not suit smaller organizations. (they generally have lower percentage payments though.). You can expect to pay a fee for the merchant account and to the payment processor (although these may be bundled together). Some, like World Pay & Paypal do not require separate merchant accounts

4)                  COST Transaction processing & fixed charges vary and need to be investigated. I noticed on forum posts that it is recommended to get Authorize.net through a reseller than direct as it is cheaper that way.

 

name	billing_mode	is_recur	Comments	Regional availability	Merchant Account required
Dummy	1
PayPal_Standard	4	YES	Confusing for users who only want to pay by credit   cards. High abandon rate	Multi currency – supports just about   everywhere	No Note that there is a delay in withdrawing funds of   3-5 days and withdrawals need to be manually actioned
PayPal	3				?
PayPal_Express	3				?
Google_Checkout	4				?
Moneris	1	YES		canada/ US	?
AuthNet_AIM	1		Code appears to support recurring payments but   default DB option is not set to – what is status		Yes
PayJunction	1	YES
Payment_Express	4	No -  processor only does triggered recurring*		NZD + some other Asia /  Pacific	Yes
eWAY	1	No (but could be coded)		AUD
FirstData	1	No (but could be coded)	contact is Eileen - needs live testing	 
Elavon	1	No (but available from processor. Code not yet   written)	Core from 2.2 stable
WorldPay		 	Not available but there is code mostly complete; which could be followed up	Multicurrency	No

Billing modes

1 = Processed on site -  ssl cert required - (seemless to user) – ‘form mode’

3 = Uses ‘button’ provided by payment processor – ‘button mode’

4 = Payment page is hosted by payment processor. No SSL cert is required by website. Browser is redirected (notify mode)

 

Recurring

*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.

 

fixed - thanks

Hmm - we need a field in the forums to formalise (with an 's') that salutation....

The table layout here is misleading - it is authorize.net that my comments about recurring apply to.

Another item on my to-do list - move this info to the wiki....

You have such a way with words ...

OK - I have copied it across

http://wiki.civicrm.org/confluence/display/CRMDOC/CiviContribute+Payment+Processor+Configuration

Still lots of gaps but hopefully people will fill them in