We have Authorize.net and Stripe as payment processors. We'd like to have recurring memberships run on the 1st of the month. I see under contributions there looks to be the potential to set it but that isn't working. (Does Civi still support the ability to set a specific start date for recurring contributions?) There is no such setting for membership. enter image description here

How can we pass this data to e.g. Authorize.net? Is it technically possible to have custom code achieve this and has anyone done so?

2 Answers 2


Auto-recurring memberships are triggered by the corresponding recurring contribution, so what you need is:

  1. A payment processor that supports future dates for recurring contributions.
  2. 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: https://github.com/adixon/ca.civicrm.contributionrecur

I'm not sure if my implementation in that custom extension will work with Authorize and/or Stripe, but you could try it. Those processors might need a small patch for it to work.


This is available thru the Stripe integration as a new feature discussed in issue #199. For reference, it started with the 6.5 release.

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.