Recurring payment notifications

[Eileen]

The authorize.net code seems to be set up to send receipts on the first & last recurring contribution - which is what our customers seem to want (regardless of the contribution page settings - or rather  - they should get first & last notifications if the contribution page is set to send notifications.)

However, the BaseIPN class sends out receipts for each contribution - which is not at all what they want - do other people hit this / have an opinion.

Among our customers the 'start & finish only' seems to be unanimous.

[ptpmark]

Just stopping by to vote yes on this comment and inquire if anyone has modified the code somewhere along the line. Some of our sites do NOT want CiviCRM to send intermediate email notifications  for recurring contributions that are being collected by authorize.net

[Eileen]

I feel like we 'fixed'  this by a combination of a post hook or similar & a patch to make core respect the actual setting

https://issues.civicrm.org/jira/browse/CRM-13273

(Not quite sure where the post hook code is - but it must be fairly straight forward)

[jamie]

I've been working on this issue  for a while and after doing some careful review, I think we can do this by running this SQL statement on a daily cron job (assuming nobody has a recurring contribution that goes more than once a day):

UPDATE civicrm_contribution_recur SET is_email_receipt = 0 WHERE is_email_receipt = 1 AND id IN (SELECT DISTINCT contribution_recur_id FROM civicrm_contribution WHERE contribution_status_id = 1);

The idea is to turn off receipts for any recurring contribution that has at least one contribution that is already made.