this has been long enough and we haven't seen any for a while, we can make a new ticket if they come back

The info being collected from the form also will create duplicate contacts for historical paypal donors. I was spot checking the test from last week and I saw some where the donor had typed in a different name in the form than is on their paypal account, so even though the email address was the same there are now two contacts as the names were different.

Spot checking them I've found a couple so far that were indeed duplicates but we only have the paypal one in civi:
221301618.1

Do you mean we only have the Gravy one in CiviCRM? I see the Gravy donation here, but no PayPal, which makes me wonder why the Audit didn't pull this one in too. Another bug maybe?

Searchkit here also with 2470: https://civicrm.wikimedia.org/civicrm/admin/search#/edit/3619

If we can get this query into a searchkit, you can delete them easily from the UI and it will get all the different pieces

We did fix this one

Another find, closing as it was for Ingenico

Found this searching for something else, going to close as it had to do with Ingenico

Ah yeah I think this is one of the descriptors:
Wikimedia Foundation - monthly gift

let's talk about this in a tech talk

Ah is what you are talking about in onAlterPaymentFormData? I saw it looking for something else so hadn't gone through the whole path

@KHancock99 ran into two declines with her mastercard https://wikimedia.gr4vy.app/merchants/default/transactions/622e712f-9192-42de-af3e-262f9b3fbaca/overview

@jgleeson I checked the config you set up with the spreadsheet that all looks good

@AKanji-WMF that's what this ticket is about, the translations of the preference center itself T376514: Figure out how translations of the email preference center will work

Looking at another cid mentioned cid=63232551 their donor record was created on 2024-02-06 with the mailing tied to sp73698998. Looks like they used two different email addresses. This record did not get the email, there is another cid=54631430 that did get the email. And then donated from the link two months later and used a different email address

This is interesting, something is happening that's causing a null response and then we lose the final status. Locally stepping through on a null response it's being caught and getting a final status of failed

@krobinson I think we would want to keep the flow the same where they see the TY page, get the email and the donation goes into civi it would be how that donation looks in civi

Dlocal asked for examples, sent some over and waiting for response

New proxies work, reports are appearing in the /incoming folder

We deployed a test patch with the config mentioned now getting:
Could not download report due to cURL error Received HTTP code 400 from proxy after CONNECT

Looks like this has been fixed in the meantime, refunds now keep their backend processor