CiviCRM Community Forums (archive)

I am trying to estimate the level of effort needed to update/convert the existing Drupal module payment processor for Vanco to be a CiviCRM extension that can work with version 4.2 or better.

(The existing Vanco module is at: http://lamp1.axiaconnect.com/~filesbac/vanco/vanco.directpayment.processor_Civi4.1.x_D6.zip   thanks to BackOffice Thinking. It is also described at: http://civicrm.org/blogs/pkeogan/vanco-payment-processor-civicrm-33-34-and-41 )

After digging into the code, I noticed that the module overrides a number of tpl files because the core tpl files only allow for credit card payments, while the module allows someone to pay either by credit card or ACH.  Could the changes to the tpl files be incorporated in the core tpl files? I was thinking there would need to be some kind of flag for each payment processor to indicate if it allows ACH or Credit Cards or both.  Then there is the situation where the payment processor in general allows both, but the organization using CiviCRM is only set up for ACH or Credit Cards with that processor. (eg they use Vanco for ACH only, and use Authorize.net for credit cards)

While ACH (and therefore Vanco) is a U.S. specific system (described at: http://en.wikipedia.org/wiki/Automated_Clearing_House)   I am hopeful that the form fields that are needed in the .tpl files are very similar or the same as what is needed by payment processors for other countries.

Any thoughts on what changes would be needed to allow CiviCRM core to handle payment processors that offer ACH/eCheck/EFT/DirectDebit ?

We looked at Vanco too, but didn't want to have to support the module as this was for a low volume org.  To state the obvious, for a higher volume org ($3M -$5M+ in credit cards charges /yr) using ACH/ETF  can save over  $50K per year.  Nice payback to support this kind of effort

The Vanco extension we wrote for 3.4/4.1  is ready about to be released for 4.2x -- we've had about 4 organizations test it.  Vanco is really looking to make a push with CiviCRM and was very helpful in fixing all of the issues we diffident with the earlier versions.

If anyone wants a beta version please contact me.  Hopefully it will be in the extensions by May

Yes it does, what areas are you concerned about?

Thanks sonicthoughs.  We have plenty of business cases.   Please be aware that the Vanco release is for 4.2X not 4.3; It will take some additional work (maybe a make it happen project) to move it to 4.3.  You are right, the main reason why organizations want ACH to reduce costs especially for large transactions.

I suspect that the financial changes in 4.3 will effect it.  I am not positive though.

We are converting from a legacy online donation system to CiviCRM and need to have EFT / ACH functionality.   Is the Vanco extension fully functional or still in beta?  Do you need more testers?  Please contact me to see how we could work together on this.  Thanks! -  Dave

I'm very interested in using this in 4.4. Did anybody make further progress on this? I'd really like to support recurring contributions by both CC and bank account.

Fen, does Paypal Express allow recurring contributions? I can't for the life of me figure it out.

Thanks,
-Joseph