21 results found

1. Please Fix "Bug" re recurrent payments ASAP

   Am using authorize.net and the main reason we joined Apricot was the functionality of setting up recurrent payments. Turns out it's true that you work with authorize.net and its true that you offer recurrent payments; however the software presently only allows the customer to setup recurrent payments from an e-mail and does NOT allow the administrator to do so on their behalf - this creates a need for a number of additional steps including sending the invoice by e-mail to the administrator, downloading the e-mail, and then creating the recurrent level and payments through the e-mailed invoice. Am told this is a known "bug" that should be fixed in the next release to be made available sometime in the next few months. If in fact there already is a solution for this at the software level could we please have it made available now as a "hot fix" in advance of waiting for the next full release. The present "bug" but is wasting a lot of time. THx and adds unnecessary confusion to the workflow process.

   Am using authorize.net and the main reason we joined Apricot was the functionality of setting up recurrent payments. Turns out it's true that you work with authorize.net and its true that you offer recurrent payments; however the software presently only allows the customer to setup recurrent payments from an e-mail and does NOT allow the administrator to do so on their behalf - this creates a need for a number of additional steps including sending the invoice by e-mail to the administrator, downloading the e-mail, and then creating the recurrent level and payments through the e-mailed invoice. Am told this… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Online payments  ·  Delete…  ·  Admin →
   Resolved  ·  AdminKatya Tyukina (Director of Product Management, Wild Apricot by Personify) responded

   Fixed in 5.2 release.