We had several clients where recurring payments in Authorize.net were not properly updating Wild Apricot payment database and one client where integration was failing altogether.
We have tracked this down to being due to certain settings in their Authorize.net accounts (Custom field separators for 'Direct Response').
-----
UPDATE:
Our update 4.3.1 on Dec 20th resolved this problem for direct (non-recurring payments) but some clients still experienced problems with recurring payments:
- members were being charged several times in a row
- renewal date in Wild Apricot was not updating after a successful charge
This was happening due to Wild Apricot system not being able to properly process Authorize.Net payment confirmation response because of those custom separator settings.
Again, this only affects those clients who use certain custom settings in Authorize.Net. Unfortunately we have no way to identify them from Wild Apricot side - so far we have two accounts who reported this to our tech support.
Since this is a pretty painful problem, we decided to suspend processing all Authorize.net recurring payments for all clients for a few days as a temporary measure until we publish a fix on Tue Dec 27th. The fix has been prepared so it is being tested now. Once we publish the update, system will automatically resume processing those recurring payments and 'catch up' all the payments that have should have been charged in the previous several days.
Thus, from Friday Dec 23 till Tue Dec 27 no recurring payments will be processed via Authorize.Net and member renewal dates might become overdue. Once the fix is published, everything should be reprocessed automatically and get back to normal.
We will also do manual checking of accounts known to be affected.
The biggest downside risk is if you have a very stringent renewal policy set up in renewal workflow, system might start sending emails and other renewal actions for members whose renewal payments are being missed because of this suspension.
If you have any renewal actions set to be triggered within less than 4 days after a failed renewal, please disable them for now.
Please contact support if you believe that your account might have been affected by this problem so that we can make sure to check it.
Our apologies for the inconvenience.
Final fix has been published on Dec 28th and all recurring payments resumed. We have identified 17 member records in total across 5 clients who might have been affected by this bug and will be contacting administrators of those 5 accounts individually.
Dmitry Buterin, Chief Apricot