[font=Helvetica]CCB needs to finish their integration with Authorize.net which also allows recurring donations so churches would then have the option to choose whatever processor they want to use instead of being forced into using only the proprietary processors that CCB has a relationship with. The only ones that benefits from this arrangement is CCB & the proprietary processors, at the expense of churches. Churches are forced to pay higher processing rates which is money that could stay in Kingdom work. [/font]
[font=Helvetica]In checking with a developer, [font=Helvetica]there is no technical reason for this to be so complicated. The developer said, unless they are using absolutely horrible programmers who are unfamiliar with APIs (which is not the case as they have an API), this should be a straightforward process.[/font]
[font=Helvetica]For example, an entirely open source non-profit CRM, CiviCRM, offers integration with numerous payment providers: Authorize.net, PayPal, Moneris, PayJunction, iATS Payments, and so on: http://wiki.civicrm.org/confluence/disp ... Processors[/font][/font]
Is there an existing feature that you'd like to see enhanced or refined? Post about it here!
1 post • Page 1 of 1