5

Since yesterday you can now do that if you're using Drupal! @jackrabbithanna (Mark) added some code to CiviCRM Entity Project, which now exposes civicrm_contribution_recur as an Entity in Drupal so that you can manipulate it in Drupal like any other Entity. Will post some steps/screenshots here: git clone https://github.com/jackrabbithanna/civicrm_entity....


5

Two bits are required for anonymous users to be able to access URLs like: /civicrm/contribute/updatebilling?reset=1&coid=4263&cs=b88004e51f6c99b0601aceab7e489315_1530392348_168 Permissions: make online Contributions Administer -> CiviContribute -> IATS Payments Settings Check the box: Enable self-service to recurring contribution Contact Billing ...


4

I almost have this polished, just one little piece that may be beyond what my pea brain can handle. The short of it is that from the affected contact you need to send an e-mail with tokens. (I've put this into a template.) In the body of the e-mail put a link similar to this: https://yoursite.com/civicrm/?page=CiviCRM&q=civicrm/contribute/updatebilling&...


4

Yes, thanks to generous contributions from the community, this feature has now been added. See this issue for details.


4

You're in the right place to see what's going on, but the wrong spot to do anything. The field will arrive in the template fully-rendered, within {$form.is_recur.html} or an equivalent Smarty variable. Editing the template won't help you there. The form PHP code would allow you to change it, but that's not the best way to go about this: doctoring core ...


4

You are correct - you can not Edit ACHEFT Card on File via the CiviCRM interface: (left: ACH/EFT; right is Credit Card): To Edit the Routing + Account Number associated with the ACHEFT recurring series go to iATSpayments.com -> Virtual Terminal -> Customer Database -> Find the record -> hit Edit -> and make Edits to the Payment Information section. This ...


4

Yes - absolutely - the recurring series only stops if its status is switch to: cancelled or the number of installments have been completed (both are native CiviCRM behaviour).


4

Black Fly Solutions has an extension called ca.civicrm.contribution_recur that enhances recurring contributions. One option it adds is to force recurring payments, which should meet your first need. The contribution widget only shows total contributions, not total of recurring contributions. To show that you'd need a bit of custom work.


3

The answer depends on your payment processor, but here's the general plan: Contact your payment processor and inform them that you want ARB (Automated Recurring Billing) added to your account. There's generally an additional monthly charge (around $10-20/month). Most payment processors (e.g. Authorize.Net, PayPal) will send a notification to a ...


3

I think you're asking a very UK-specific question about direct debit. UK has special rules for direct debit that CiviCRM doesn't know anything about. But the iATS Payments payment processor does support the required workflow and the civicrm extension for iATS Payments does have a dedicated payment processor for that purpose, so that might work for you. ...


3

To generate these required Sepa mandate reference codes I thought I could use the API SepaMandate with the create action. This API requires an entity table and id, which I do not have yet. There's currently two API calls for creating a SEPA mandate: SepaMandate.create and SepaMandate.createfull. The first one requires indeed a contribution/...


3

We do not use Stripe so this might not help. But this is how it works for iATS. Go to Administer > CiviContribute > iATS Payments Settings (the very bottom option) One of the check boxes is "Enable email receipting for each recurring contribution" If this is checked you will be sending a receipt with each donation.


3

A great question, and before last week I would have said, no, it's better to create separate contribution pages for one-time vs. recurring contributions. But then I saw how GiftTool does it (e.g. here: https://www.gifttool.com/donations/Donate?ID=1992&AID=1663) and realised you could do that in CiviCRM as well - it's just using a little javascript. In ...


3

Change the date for the next scheduled recurrence. Table civicrm_contribution_recur > Column next_sched_contribution_date Change it to today and run your cron job or change it to tomorrow and it should process them with tomorrows transactions.


3

Apparently Paypal charges extra for recurring functionality and you have not subscribed to the additional $30/mo DPRP service. DPRP is disabled. DPRP is disabled for this merchant. https://www.paypal-community.com/t5/About-Business-Archive/quot-DPRP-is-disabled-for-this-merchant-quot-plz-help/m-p/991717#M14689 In your bounty comment you state: I am ...


3

I had a similar issue, not sure if it's the same but I applied this patch to correct: https://github.com/drastik/com.drastikbydesign.stripe/pull/249/files


3

Your IPN path is configured in paypal - the best path to point it to is yoursite/civicrm/payment/ipn/x where x is the number of the processor. Once you have updated it in paypal it is possible to re-send missed ipns from the paypal console


3

There likely isn't one clear winner here. But authorize.net has been my go-to recently. That and PayPal Pro are built-in to Civi out of the box. The Stripe payment processor extension is operating on 855 installs. iATS Payments is on 602 installs. Here is a very helpful review from Gingko Street Labs which also addresses the 4 aforementioned processors: ...


3

The key to selecting a Payment Processor is the functionality you’re looking for. The iATS extension is probably the single-most sophisticated payment-processing integration (for US/CA) - especially re: recurring contribution functionality and the abilty to control/edit/update/schedule recurring contributions from the CiviCRM side. And finally please note ...


3

It might be possible to use Webform CiviCRM (https://www.drupal.org/project/webform_civicrm) to set up a page that forces recurring contributions. Conditionals can be set up to control terms, # of installments, and frequency of installments. I usually put those into a fieldset hidden from the end-user. If I recall correctly, it should be possible to set up ...


3

You would need to reach out to Paypal and Stripe directly to ask them about how to initiate the process of transferring your recurring giving. I would suggest inventorying your existing recurring records in Paypal first, to see how complex the data is; in a recent transition to Stripe, we encountered some challenges with constituents who had multiple ...


3

Having reviewed this I believe that your Paypal is possibly configured to point to an older version of the IPN path. You can change this yourself within your Paypal account, the docs I can see suggest: To configure Instant Payments Notification (IPN) for your PayPal account Click: Profile, under Selling preferences click "Instant Payment Notification ...


3

Alternatively you can use Civirules to send an automated email: https://docs.civicrm.org/civirules/en/latest/


2

This was a bug I introduced in an attempt to set is_recur to true, so the checkbox would be checked. Thank you for your help.


2

While it's still clear you've got a bug, I'm pretty sure your issue isn't that you have "1" but rather that the unit--week, month, year--is missing. The numeral is there in case you wanted to donate quarterly--it would say "3 month(s)". Again, not that this makes it any better. However, it might help you or whoever diagnose the bug. Hopefully it's as ...


2

This has been fixed now. If you get the latest version of the Stripe extension's code from Github, you will have email receipts for recurring contributions.


2

CRM-15629 produces similar symptoms with certain configurations of PayPal. Also, please update your question with a CiviCRM version?


2

There is a feature request for this. You can post if you (or anyone else) is interested in supporting. Ref: https://www.drupal.org/node/2557997


2

This is from a bug introduced in 4.6.x series, fixed in 4.6.9, as per https://issues.civicrm.org/jira/browse/CRM-17108 Solution: update CiviCRM to the most recent 4.6.x


2

I found the problem. The permissions were not set correctly for recurring contributions on authorizeIPN.php. So when the silent post was running it was getting a 404. I did not see this in the log. For others out there make sure authorizeIPN.php is retrievable.


Only top voted, non community-wiki answers of a minimum length are eligible