Answers.Body: <p>This is available thru the <a href="https://docs.civicrm.org/stripe/en/latest/" rel="nofollow noreferrer">Stripe integration</a> as a new feature discussed in issue <a href="https://lab.civicrm.org/extensions/stripe/-/issues/199" rel="nofollow noreferrer">#199</a>. For reference, it started with the  <a href="https://docs.civicrm.org/stripe/en/latest/releasenotes/#release-65" rel="nofollow noreferrer">6.5 release</a>.</p>
  <p><a href="https://i.sstatic.net/7rhLW.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/7rhLW.png" alt="enter image description here" /></a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-07-21T21:01:43.160Z
Answers.LastActivityDate: 2023-07-21T21:01:43.160Z
Answers.UserDisplayName: Andy Burns
Answers.Body: <p>Auto-recurring memberships are triggered by the corresponding recurring contribution, so what you need is:</p>
  
  <ol>
  <li>A payment processor that supports future dates for recurring contributions.</li>
  <li>A way to restrict which dates are allowable.</li>
  </ol>
  
  <p>For 2., the functionality is built into the iATS Payments extension, and also in my extension here:
  <a href="https://github.com/adixon/ca.civicrm.contributionrecur" rel="nofollow noreferrer">https://github.com/adixon/ca.civicrm.contributionrecur</a></p>
  
  <p>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.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-14T18:14:18.750Z
Answers.LastActivityDate: 2020-01-14T18:14:18.750Z
Answers.UserDisplayName: Alan Dixon
Body: <p>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. (<a href="https://civicrm.stackexchange.com/questions/3328/does-civi-still-support-the-ability-to-set-a-specific-start-date-for-recurring-c">Does Civi still support the ability to set a specific start date for recurring contributions?</a>) There is no such setting for membership.
  <a href="https://i.sstatic.net/oqT6x.png" rel="noreferrer"><img src="https://i.sstatic.net/oqT6x.png" alt="enter image description here"></a></p>
  
  <p>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?</p>
  
Tags: <civimember><recurring-contributions>
Title: How to set a recurring membership start date to be 1st of the month
ThreadText: # How to set a recurring membership start date to be 1st of the month
  
  (Asked by: username_0 on 2020-01-08)
  
  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?](https://civicrm.stackexchange.com/questions/3328/does-civi-still-support-the-ability-to-set-a-specific-start-date-for-recurring-c)) There is no such setting for membership.
  [![enter image description here](https://i.sstatic.net/oqT6x.png)](https://i.sstatic.net/oqT6x.png)
  
  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?
  
  **Tags:** civimember, recurring-contributions
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2023-07-21. Score: 2 | Accepted answer
  
  This is available thru the [Stripe integration](https://docs.civicrm.org/stripe/en/latest/) as a new feature discussed in issue [#199](https://lab.civicrm.org/extensions/stripe/-/issues/199). For reference, it started with the [6.5 release](https://docs.civicrm.org/stripe/en/latest/releasenotes/#release-65).
  
  [![enter image description here](https://i.sstatic.net/7rhLW.png)](https://i.sstatic.net/7rhLW.png)
  
  
  ---
  
  ### Answer by username_1 on 2020-01-14. Score: 4
  
  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.
  
  
  ---
  
  