Gotcha. Thank you for looking into it, @Ejegg!

Awesome. Thank you, @Ejegg! We'll shout if we see any confusion or other reports about it.

Thank you for confirming that 7 day timeframe for the 2nd failure email deployment, @MSuijkerbuijk_WMF!

To confirm, it sounds like there is nothing we can do to improve this on our end? If so I'll let the team know. :0)

A few thoughts/suggestions from me:

1. If possible could we move cancel up to be the first item in the dropdown please? I don't see DR sending these failure emails out manually very often, but we use cancel hundreds of times a day.

2. I sent the 1st and 2nd failure emails to myself (my CID is 68209875). However, both are labeled as "First failure email" in Activities.

3. I could have sworn I saw a specific time when I first previewed the template for the 2nd failure email it said the date and specific time, but now it's not there? I thought it said something like the date and then 9:01 pm and was going to suggest we don't put a specific time. May have just imagined not sure lol.
4. Related I can see on the second failure email we are including a date. It looks like we don't include this on the first failure email. I wonder if the inclusion of a date has the possibility to cause donor confusion. I think (correct me if wrong 😉) the dates in Civi are specific to Civi and it's timezone which I believe is Hawaii time. If the date that will be generated operates as other things we normally see in Civi I think the date the donor sees on this email may be different than the date they typically see their monthly billing attempt on their end and may not be the same date as what Civi says it is and thus have the possibility to create confusion?

5. This one could just be me but the framing of "last payment" in the 2nd failure email stood out to me. It kind of made me think it's the final payment of a monthly donation. If this stands out to anyone else maybe we could consider something like "the most recent processing attempt" or the "most recent billing attempt".

6. In our standard fundraising emails in the footer the part that says "Please let us know it" has a mailto link to donate@ as shown in the screenshot below. Currently on both failure emails it also says the "Please let us know it" but there is no link provided.

Interesting thanks @Ejegg! Luckily we have a workaround for now. If we notice we can just use our standard decline messaging.

Awesome, thank you for the quick fix @Ejegg! :)

Have another one that I think may be the same issue. Donor in Zendesk #1829484/CID 47129803 attempted to donate a total of 3 times on 01/20 and 01/21. All three attempts are declined with the response "expired card". However, the expiration date provided for each of the transactions is a future date.

Thanks all! I see ^ we did updates in English. Assuming we may be planning to make similar changes in other languages? A French donor in ticket #1819462 / cid 60259866 received a failure email today for their monthly donation and I noticed it's signed Denise Andrews, etc. I feel the signee is less of a priority in changing in all the respective languages quickly as long as if they were an annual donor the copy refers to them as such and links them to the annual form. :)

Thanks so much for the info, @Damilare! I'll update our documentation.

Thanks @Cstone and sorry for the delayed reply!

Thanks for looking into it @AnnWF!

Thanks @jgleeson! I've let the donors know. :)

A signature of "Wikimedia Foundation Fundraising Team" works for me. I can see that's what we're using for a different auto-email.

Regarding your note above "if you have DR documentation about not changing paypal_ec recurring donations, you might want to update it as it is no longer possible to change paypal_ec recurring donations from the CiviCRM UI."

Hello! Just flagging that we've heard from a donor today who encountered this error. Donor in Zendesk ticket #1803291/cid 2063093 provided the screenshot below and reported "Hello, I received this error when I tried to donate in the iOS application. My credit card was charged, so I assume that it worked, just that the confirmation did not appear. I hope you got it!"

Just noting that we continue to hear from donors who are encountering this issue. Zendesk #1791904 / CID 29491420 shared the screenshot below on 12/08.

Hey team! Just flagging a new one that's come in. Ticket #1799595 / CID 10492758 came in an hour ago and donor reports not seeing the Venmo button on Safari. Here is what the donor shared:

Hey @jgleeson! Having trouble getting that file I previously attached to be visible. Trying again here.

^ Thanks all! Definitely seems to be low volume which is good. 🙂 Did want to just note that we've come across another example this week. Donor in #1784930 noted "Hope all is well. I'm reaching out because I wanted to get my donation matched by my employer. But when I clicked the Paypal button, the option for checking matches skipped and I wasn't able to complete it. How can I get this fixed?"

Hiya! We've had what appears to be our first donor report of this issue that just came in last night.

If it's helpful to note on Wednesday I cleared my cookies/data in Google Chrome (my primary browser) and have been unable to recreate this again.

Just an update here. It's still broken for me on Google Chrome. I was curious to retry all the browsers. Firefox still worked fine for me today at least the few times I tried.

This is the first comment like this I've seen regarding the employer matching field using the PP flow and then the other donor I mentioned who also recently had the concern about being unable to see the privacy blurb when going through the PayPal flow. However, since it takes you to PayPal so fast I'm not sure if possibly we also don't see more comments on it as donors may just not notice.

As requested by @Cstone here's that screenshot. :)

Interesting to note that the button does appear on Google Chrome if you use the back button.

Two more from today:

Interesting! Yeah I also can no longer recreate it @Ejegg which is not a bad thing lol. I just tried on my mac on both Chrome and Safari, iPad, and iPhone and can no longer recreate this issue so maybe it resolved itself? 😅

Hey y'all!

Just flagging a fresh example. Donor in #1768332 / CID 38486846 donated twice via Google Pay in the app by mistake. Donor notes "I have looked at my bank account and noticed that 2 payments for £15 have gone out. I only chose the 1 payment of £15. There was an issue with the page that was hanging/pending when I submitted it. I re-entered the amount which did the same thing again."

Just flagging one additional manually settled donation at Gr4vy yesterday not in Civi:

Two more manually settled donations that were settled at Gr4vy yesterday have not made it to Civi:

Adding one additional example that came in yesterday. Donor in 1758179 / CID 68824702 donated 3 times by mistake via Google Pay from the WP app. Donor notes "I didn't mean to make three different $5.35 donations on 10/19/2025. I only meant to make one. Please cancel and refund two of those donations ($10.70 total)."

Awesome, thank you @Cstone! All looks great and every 1 month/year works perfectly. Thank you! :0)

We continue to see these. Unfortunately as the browser information is not always provide we're unsure, but are curious if it also could be affecting other browsers outside of Firefox. A few more examples I came across today:

Hey @Cstone and all! @MBeat33 shared that some more work had been done on the WIP:Recurring Contributions and to add any feedback we may have on the updates here. :)

Two more donations that I manually settled on Wednesday, 10/01, didn't make it to Civi.

Thanks @MBeat33!

Donor in 1732154 (no CID) flagged that they aren't being billed for their recurring donation. Their donation see transaction d7d408f6-94e7-4f41-85d4-88c5a58556ab was manually settled back in May and never made it to Civi or billed after.

Hey fr-tech! :) Reviving this phab as we're seeing more of these again.

@DSeyfert_WMF was able to fix this for us. Thank you, Dustin! Going ahead and closing out this task. :)

1734026/CID 63667322 got back to us with their tech specs that I've added above though its the same info. that you already found @jgleeson. :)

Another one guessing it's probably the same thing @jgleeson. Donor in #1723321 I manually settled their transaction b7b12b49-dc84-4108-9c42-a701668b6a24 on 09/04 and it's not in Civi.