Seeing this also on a new Civi 5.18.4 + Stripe 6.2.2.
Matt - any summary of why this doesn't work? I'm going to guess that you don't want email receipts for every contribution (usually, only the first one), and that the StripeIPN code doesn't have enough information to distinguish the two cases?
The stripe extension uses the ContributionRecur.create API to update a recurring contribution that was created by the contribution page. So you'd need email receipts to be enabled on the contribution page. The parameter will not be modified or updated by the stripe extension. What is the default on is_email_receipt in civicrm_contribution_recur?
As we use the standard Contribution.repeattransaction API for the IPN callback that should respect whatever the recurring contribution has set for is_email_receipt.
@AlanDixon It would be nice to have something like what you have in IATs more generally available (ie the No, Only first, Always).
Confirmed, yes - it's the civi receipt that's not going out, and it's not going out for the initial contribution of a new recurring sequence (I don't yet know whether it's going out for subsequent ones).
The page that's used to create the recurring contributions is the same one that's used for one-time, and the one-time receipts are going out, so it's a problem specific to recurring contributions.
I'd also note that the is_email_receipt = 1 in the civicrm_contribution_recur table, so it would appear that the issue isn't in the ContributionRecur.create API.
The extension doesn't have a lot of input into the behaviour of the system for the initial contribution, but my expectation is that it's somewhere in the IPN callback. Perhaps there's some new code that helps implement the iATS-type functionality and recurring contributions need special handling?
Update: recurring contributions started before we upgraded to 6.2 are sending receipts for each payment as usual. New recurring contributions since 6.2 are failing to send receipts. Running 5.18 and Drupal 7.
@KMRD re: New recurring contributions since 6.2 - I assume you mean that they don't send a receipt for the initial contribution. Have you discovered if they also don't send receipts for the later/recurring contributions? Not obvious, but those are very different code pathways.
Previously a receipt was also sent to all the email addresses that are added to CC or BCC field during the contribution page setup, for initial contribution and subsequent ones. Now those people are not receiving receipt also, just wanted to add.
Edit:
For the donation receipt that was not sent for initial and subsequent subscription payment, I just found out, the contact profile has only one email (billing &primary). Not sure if that could be an issue.
@mattwire Is it possible to include a metadata manually on stripe dashboard of a contact for those receipts weren’t sent? So next time the subscription payment get processed, a receipt would be triggered from stripe to civicrm to be sent to user? Thanks
Hmm, I think I see the case when it could be replicated.
Civicrm recur contribution through stripe triggers 2 events on webhook - charge.succeeded and invoice.payment_succeeded. The order of this event decides if the email is sent or not. If the charge event is called before invoice, the receipt is not sent. In case of invoice called first - the receipt is sent correctly.
I've raised a PR !99 (merged) to fix this behavior. Can anyone pls apply the patch on their setup and confirm if you still see this issue? @tapash
@jitendra Thanks. After using your patch the receipt flow seems to be working as expected, at least receipt for first signup of a subscription was sent.
@jitendra PR !99 fixes the problem of initial & subscription receipt sending. Many Thanks!!
However, any donation created prior to applying this patch, in the "activities" I can see a donation receipt for subsequent payment is sent. In contribution pages, I have BCCed some people, but they are not receiving the copy of email. So, not really sure if that receipt is really sent or not! Is there a quick fix for that?
This is now merged and will be in 6.4 (not yet released). If you wish to use it on 6.3.2 there should be no issues with applying the patch manually.
@tapash for the bcc issue, I checked that today and it seemed to be ok for me. Can I suggest you download https://lab.civicrm.org/extensions/msgtplblocker and enable the option to create an activity for each email sent. Then you can see if the BCC is being set by looking at the activity. I don't think the BCC could be a problem with the stripe extension.
We are seeing this same behavior now under extension version 6.6.2:
As in OP: When a customer creates a sunscription via a contribution page, although payment was successful, no receipt was sent.
As clarified in comment by @KMRD: CiviCRM is sending receipts for later/recurring contributions. Initial receipt for recurring contributions is not sent.
I'm unsure of the behavior on previous extension versions (<= 6.6.1).
Can anyone else confirm whether that's happening for you under 6.6.2 or any version later than 6.4 (in which this appears to have been fixed)?