When we started with WA almost a year ago, we made it clear that it was important to us to be able to process C/C transactions and that our payment processor was Elavon. We were told that Elavon support was expected to be included in your next release, and this was a major factor in our decision to adopt WA.
As we now know, your solution was based on the use of CRE Secure as an intermediary. Unfortunately, at our relatively low transaction volumes, this solution would nearly double our C/C processing costs, which is not feasible.
On the basis of what we thought was reliable information from you, we went ahead and adopted WA and are faced now with a commitment to provide online payments. It is our understanding that Elavon is the payment process of choice of a very large number of Canadian non-profits who must either be facing the same difficulty or have not adopted WA because of the lack of a practical interface to Elavon.
We urge you to provide, as soon as possible, either an appropriate technical solution, or a financial arrangement that makes practical the use of CRE Secure .
Adding a new gateway doesn’t align with our current focus for the product. Supporting each payment systems takes time and resources away from our development and support teams to provide the better, more reliable service.
We currently are using Elavon for our non-profit as well. We were/are planning to set up our database through Wild Apricot, but this may factor into our decision to not choose Wild Apricot as our database provider. Could you please look into possible compatibility, at an affordable rate, so that we can continue with our plan to have Wild Apricot provide service to our membership. Thank you.
Shane Callaghan commented
Another vote for Elavon
FWIW, we also would like to have elavon as an option.
Dmitry Buterin commented
Thanks for posting. I would appreciate hearing from other users who currently use or want to use Elavon.