Page MenuHomePhabricator

Adyen: have audit file pick up manually settled donations
Closed, ResolvedPublic


The donor in ZD 825786 let us know they got an error when creating a recurring Adyen donation. Seilo saw that their attempt was at Auth status and manually settled it ("sent capture") on October 8th. It is still not in Civi, so as we talked about in today's meeting if Civi could be made to pick these up from the audit file it would be great.

PSP referenceMerchant reference

Event Timeline

I will check for more cases of this next week, but this one settled in October is still not in Civi:
PSP reference Merchant reference
1536018863956193 92200232.3

81328909.1 is odd? It was settled manually by @EMartin on 2020-07-20, but
shows as Received in Civi on July 16th, 2020 3:18 PM TY sent, July 20th, 2020 11:23 PM

Change 679436 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] Add --file options to audit parser

Change 679436 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Add --file options to audit parser

OK, looks like the problem is not that the donation was manually settled, but that it was a recurring donation. The audit parser is still not smart enough to get those in to the database, but I have some ideas about how it could.

Tech notes: the audit parser searches for missing donations in the payments log files, but those aren't going to have anything for 2nd+ recurring installments. When the second part of the merchant reference is a number >1 we should search for previous installments (maybe before doing the log greps?) that have a contribution_recur_id and use the contact_id and contribution_recur_id from them if found.

For the work to make the audit parser support recurring donations, see T187505
Perhaps the IPN listener should have recorded this one, though?

for 81328909.1, the reason you see that received date is that we record the date of the initial authorization, regardless of when the record is written in Civi. This gives us more accurate data for e.g. CSV imports that might pull in a whole past month of data with individual dates in each row, but when the auth and the capture are so far apart we maybe should use the capture date.

Hi team, I'm adding a few recent transactions below, as we’re still seeing this as an issue for one-time donations:

Adyen transaction# 118461246.1 - CID 50723974 --> settled at Adyen on the 7th. The donor is upset and still waiting for a receipt but the donation has not reached Civi.

Adyen transaction# 118432361.1 - CID 25860179 --> settled at Adyen on March 30th. The donor is upset and still waiting for a receipt but the donation has not reached Civi.

Ps- Since this is about one-time donors, pls let me know if a new Task would be better. Thanks in advance!

@SHust to your question - it is probably better to close this & create a new phab if still an issue

@Eileenmcnaughton, Michael spot-checked some recent manual settles and they seem to reach Civi the same day or the next so you certainly close this ticket. Thanks for checking!

Eileenmcnaughton claimed this task.

thanks @SHust - I had a fun moment reading the old sprint names on this one