Answers.Body: <p>If you did manage to fool civicrm into thinking your second payment processor can accept recurring contributions, that sounds like a bad thing?</p>
  <p>Your method looks like it should work, but you might need some aggressive cache clearing (eg. by enabling/disabling some other extension).</p>
  <p>Handling mixes of processors with different capabilities is a tough issue.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-09-07T16:33:32.290Z
Answers.Text: simply editing the is_recur option does not seem to work, could you elaborate on what you mean by cache clearing?
Answers.UserDisplayName: waikaeth
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-09-09T15:02:16.827Z
Answers.Text: Chances are for most payment processors, the payment processor configuration is in a managed record, so you wouldn't be able to override it via the command line. By aggressive cache clearing, I mean that a lot of civicrm configuration gets stored in a cache, some of which may not get cleared unless you enable/disable an extension (any extension, but don't break your site!).
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-09T13:07:59.577Z
Answers.LastActivityDate: 2021-08-09T13:07:59.577Z
Answers.UserDisplayName: Alan Dixon
Body: <p>I am using WP Version 5.7.2 and CiviCRM V 5.37.0. The two payment processors are Stripe and BTCPay.</p>
  <p>Frustratingly, If you have two payment processors and one of them does not support recurring contributions the option will not be available on the entire contribution page. <a href="https://civicrm.stackexchange.com/questions/39680/how-do-i-enable-recuring-donations-when-i-have-two-payment-processors-enabled-o">How do I enable recuring donations when I have two payment processors enabled, one which supports recuring donations and one that does not?</a></p>
  <p>Is there a way to lie to civicrm to tell it that the second plugin accepts recurring contributions? I tried editing <code>is_recur</code> settings of this file to 1 but that did not work <a href="https://github.com/rukykf/btcpay/blob/master/btcpay.mgd.php" rel="nofollow noreferrer">https://github.com/rukykf/btcpay/blob/master/btcpay.mgd.php</a></p>
  <p>Having two payment pages is not a real option, promoting financial privacy is a big part of what we do, so I can't relegate crypto payments to a second class status requiring additional clickthroughs, and I don't want to have to manually update the donation widget either.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-09-03T15:40:07.890Z
Comments.Text: I would look at a 3rd party webform for your contribution page. I do not know what is available for WP. Drupal has Webform CiviCRM integration available. With this you could create a webform for your contribution page that has the Civi/payment processor(s) baked into it.
Comments.UserDisplayName: Iowa Boy
Tags: <wordpress><civicontribute><payment-processor><recurring-contributions>
Title: Fooling civicrm into thinking payment processor supports recurring donatoins
ThreadText: # Fooling civicrm into thinking payment processor supports recurring donatoins
  
  (Asked by: username_0 on 2021-07-27)
  
  I am using WP Version 5.7.2 and CiviCRM V 5.37.0. The two payment processors are Stripe and BTCPay.
  
  Frustratingly, If you have two payment processors and one of them does not support recurring contributions the option will not be available on the entire contribution page. [How do I enable recuring donations when I have two payment processors enabled, one which supports recuring donations and one that does not?](https://civicrm.stackexchange.com/questions/39680/how-do-i-enable-recuring-donations-when-i-have-two-payment-processors-enabled-o)
  
  Is there a way to lie to civicrm to tell it that the second plugin accepts recurring contributions? I tried editing `is_recur` settings of this file to 1 but that did not work <https://github.com/rukykf/btcpay/blob/master/btcpay.mgd.php>
  
  Having two payment pages is not a real option, promoting financial privacy is a big part of what we do, so I can't relegate crypto payments to a second class status requiring additional clickthroughs, and I don't want to have to manually update the donation widget either.
  
  **Tags:** wordpress, civicontribute, payment-processor, recurring-contributions
  
  > **Comments:**
  > **username_1**: I would look at a 3rd party webform for your contribution page. I do not know what is available for WP. Drupal has Webform CiviCRM integration available. With this you could create a webform for your contribution page that has the Civi/payment processor(s) baked into it.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2021-08-09. Score: 0
  
  If you did manage to fool civicrm into thinking your second payment processor can accept recurring contributions, that sounds like a bad thing?
  
  Your method looks like it should work, but you might need some aggressive cache clearing (eg. by enabling/disabling some other extension).
  
  Handling mixes of processors with different capabilities is a tough issue.
  
  > **Comments:**
  > **username_0**: simply editing the is_recur option does not seem to work, could you elaborate on what you mean by cache clearing?  
  > **username_2**: Chances are for most payment processors, the payment processor configuration is in a managed record, so you wouldn't be able to override it via the command line. By aggressive cache clearing, I mean that a lot of civicrm configuration gets stored in a cache, some of which may not get cleared unless you enable/disable an extension (any extension, but don't break your site!).  
  
  ---
  
  