1) Make sure the Silent post URL is properly configured in Authorize.net.
Example: https://YOURSITE.COM/civicrm/payment/ipn/2 (the 2 needs to be replaced with your CiviCRM Payment Processor ID#)
2) It is possible that recurring payments are not processed instantly. It could be that recurring payments are processed in the middle of the night for example and ...
Auto-recurring memberships are triggered by the corresponding recurring contribution, so what you need is:
A payment processor that supports future dates for recurring contributions.
A way to restrict which dates are allowable.
For 2., the functionality is built into the iATS Payments extension, and also in my extension here:
Thanks for looking into membership extras. Just a quick point that we are planning a release at the end of Jan which will fix a lot of bugs and issues so I would suggest to wait till that is released before using this fully.
Answers to questions below:
Does this plugin actually create a recurring contribution record the same way that online payments ...
I wonder if using this extension might work instead?
It provides a slightly more sophisticated off-line payment processor, as well as a job that will provide implicit membership renewals using the 'auto-membership' feature.
How contributions are created as part of a recurring series is not well-defined by CiviCRM core, it depends on the payment processor.
iATS Payments will create the new contribution in the recurring sequence based on a combination of:
1. the settings in the recurring record and
2. it's best guess of a previous contribution to use as a template (i.e. the ...