Some refunds we performed in June for CID cid=26093476 also have not reached Civi:

Thank you @DStrine

Closing this as duplicate, thanks for flagging @CDenes_WMF

fwiw this sample form looks like option 1a, with the donor's first name in the salutation, and the full name below near the summary details

Personally I think the 0000s may be more intuitive than a single # (and #s in groups of 4 might look like numbers have been entered and hidden), so I'd say go with the 0000s. @Pcoombe @CDenes_WMF you were in the other task about this, so I thought I'd loop you in to socialize the decision: do 0000's work for you here?

Marking resolved as a duplicate of T254032: Removing asterisks in payment page card number field

Clearly what we need is an ABC test of **** versus 1234 versus 0000, with a pop up for AmEx users translated into all languages and - just kidding! 0000s sounds good to me, thanks for the suggestion and documentation @DStrine @mepps

@SHust says this use case is the main reason agents go back to the legacy interface, so if we could add this functionality, agents could work exclusively from Deduper.

Confirmed in call that for English this is switched on as of today - thank you!

"answer is 800k+"

US and NL will cover almost all of our tax receipt requests @DStrine Canada is a very small part of them.

Thank you!

Lisa Gruwell

12:29 PM (31 minutes ago)

to me
Approved!

Lisa Gruwell

12:29 PM (31 minutes ago)

to me
Approved!

Sure thing, @DStrine

Thank you @Eileen McNaughton <emcnaughton@wikimedia.org>

@Eileenmcnaughton I'm not sure if this is related to this task, but multiple agents are getting this error today when deduping:

Thank you @Eileenmcnaughton!

I've seen some websites use 1224 1234 1234 1234 in the card field, so that's one option.

donate@ is an address that is set up as a support address in Zendesk, so anything sent to it goes to the DS team

Hungarian is customary to use the surname in the salutation, I'm pretty sure.

Thank you @Dzahn for the substantial update. I really appreciate it and am learning this is a pretty layered question. I am meeting with Josephine tomorrow to see if we can push forward any of the steps to simplify these emails.

In meeting today, fr-tech checked logs and it's not clear yet what happened with this one. @Ejegg mentioned possibly running sql queries to find the # of 'not yet canceled's' versus 'next scheduled dates' to see how many like this there may be.

Some notes from the meeting today:

Thanks, @Pcoombe

Thank you for this task, @EMartin

Thank you @Dzahn and @JGulingan

will check with Rakhi to see if her permission has changed

I'm concerned that with scaling up transaction volume (if we go w/Adyen for EN6C cards for example) we might see an increase in donors asking if we received their successful donations. If we see that in Q2 I might ask to prioritize this task higher.

Many thanks, @Cstone

Who rocks? Sam and Moska rock. Thank you.

There are more refunds that never transmitted from Ingenico to Civi:

Thanks, @Cstone, and sorry for my mistake on the dates for those.

Thank you @Cstone Do you know if the two examples from the 29th should have been prevented by the fix from the 28th?

We are continuing to see bulk email complaints from donors whose recent contributions via iDEAL/Adyen have not reached Civi. Kris just processed about a dozen, of which these are a sample:

Kris H found another one. Trxn 80213557.1 was settled and captured at Adyen on 2020-04-25 13:36:34 PDT but is still not in Civi. cid=20454734 is the only donor record with that email address - can you remind me when the patch was applied? What's the date after which we wouldn't expect to see any more stragglers, @AndyRussG ?

After checking in with fr-tech just now, this looks not be an issue during tomorrow's send or going forward. The affected donors from before yesterday's patch will get their TY emails with the weekly audit, and we can follow up with them as needed. Thanks to all who helped resolve this one!

@AndyRussG thank you! Please do send me the list of the donors whose transactions have settled but who haven't received TYs, as some of them may have changed methods to donate and we can follow up with them generally.

Great, thank you.

Thanks, @Ejegg - do you know what the 'real' status of these donations is? Should we refund three of them if one will settle into Civi?

@EMartin we got another one just now, where a recurring PayPal is not processing, but the donor seems to have not received the usual email from Paypal:

After checking with @EMartin we'll wait to see if the donor comes back with anything interesting - this one case is probably not worth escalating to our PayPal rep yet.

Thanks, @Cstone I've updated Collab documentation with that information.

possibly older donations affected:

Thanks, @mepps! Is the comment in IRC that this change started on Mar 25 accurate? If so we can review all the manual cancels from then forward, and if the date is different please let me know.

Thanks all. Yes, @mepps I think until recently the complete ones were showing as black, not grey, and we were able to cancel them manually.

This donation now says Apr 18, 2020 is the next time PayPal will attempt to charge this. I have asked the donor to log in to their PayPal account to see if PayPal gives them any visibility into what's going on, but it sounds sort of unusual ("withdrawals followed by immediate refunds") and may not be the usual error caused by Paypal requiring donors to have a back up payment method.

Thank you for the info, @LeanneS

More about the use case: the donor in cid=31594834 reached out to us in Zendesk because the TY email they received for their recent check donation did not have the "no goods or services" text, so they were unable to use it as an official receipt. This generates more manual work for Donor Services, and seems like it shouldn't be too much work to automate?

To simplify one of the User Stories: "As a DS team member I need an option to send a single TY email or an annual summary in multiple locations in civi" - it's perfectly ok if there is just one location in Civi from which to manually send one time and annual summary TY emails.