adjust audit to catch Adyen script refunds?
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	MBeat33
	Apr 11 2023, 6:07 PM

Description

It looks like recent script-initiated refunds may not be reaching Civi?

merch ref	status: SentForRefund	status: Settled	status: Refunded	status: Refunded Bulk	in Civi 4/11?	CID
174933393.1	Apr 4	Apr 6	Apr 10	n/a	no	cid=59433462
174938411.1	Apr 4	Apr 6	Apr 10	n/a	no	cid=59434343
174933897.1	Apr 3	Apr 6	Apr 10	n/a	no	cid=59433543
174933395.1	Apr 4	Apr 6	Apr 10	n/a	no	cid=59433461
174935322.1	Apr 3	Apr 6	Apr 10	n/a	no	cid=59433797
174922548.1	n/a	n/a	n/a	Apr 6	yes	cid=59432466
174991892.1	n/a	n/a	n/a	Apr 6	yes	cid=59442254
174984711.1	n/a	n/a	n/a	Apr 6	yes	cid=59441553
174991892.1	n/a	n/a	n/a	Apr 6	yes	cid=59442254

Refunded Bulk transactions seem to be the ones manually refunded by DR team at the console. If the audit normally picks up the script refunds in like 10 days I will resolve this task and pipe down.

Related Objects

Mentioned In: T336439: Handle Adyen refund IPNs
Mentioned Here: T336439: Handle Adyen refund IPNs
T325415: Adyen Audit - manually settled transactions not being imported into civi with the nightly audit file

Event Timeline

MBeat33 created this task.Apr 11 2023, 6:07 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 11 2023, 6:07 PM

MBeat33 updated the task description. (Show Details)Apr 11 2023, 6:10 PM

This is possibly related to T325415: Adyen Audit - manually settled transactions not being imported into civi with the nightly audit file

Looking at this more these aren't related

XenoRyet moved this task from Triage to DRI Backlog on the Fundraising-Backlog board.Apr 11 2023, 8:02 PM

XenoRyet added a project: Fundraising Tech - Chaos Crew.

Cstone moved this task from Backlog to User Bug Backlog on the Fundraising Tech - Chaos Crew board.Apr 11 2023, 11:00 PM

@MBeat33 I don't know why but the script refunds didn't get to refunded status until 4/10 as you saw. They were in the 4/10 audit file which ran 3 hours ago and the ones listed that were missing in civi now are properly showing as refunded.

It would be good to ask Adyen why the refunds initiated from the API took so much longer to get to refunded status.

Thank you, @Cstone for the info. I will queue that question for next week's Adyen call.

I shared these transactions with Jake & he's looking into the gap in timing for refunds...

I sent these transactions to Adyen support, and they confirmed that similar notifications are being sent for the manual refunds + the API ones. Below are two notification logs they sent. This task is not a huge priority, so we can close it as below the threshold of need, unless it's a simple thing to change.

Notification Log #1

Timestamp: 2023-04-04T04:16:18.976Z

Endpoint: https://payments-listener.wikimedia.org/adyen

Request:

<?xml version="1.0" encoding="UTF-16"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
    <sendNotification xmlns="http://notification.services.adyen.com">
        <notification>
            <live>true</live>
            <notificationItems>
                <NotificationRequestItem>
                    <additionalData>
                        <entry>
                            <key xsi:type="xsd:string">bookingDate</key>
                            <value xsi:type="xsd:string">2023-04-04T06:16:09Z</value>
                        </entry>
                    </additionalData>
                    <amount>
                        <currency xmlns="http://common.services.adyen.com">USD</currency>
                        <value xmlns="http://common.services.adyen.com">200</value>
                    </amount>
                    <eventCode>REFUND</eventCode>
                    <eventDate>2023-04-04T06:15:24+02:00</eventDate>
                    <merchantAccountCode>WikimediaDonations</merchantAccountCode>
                    <merchantReference>174933395.1</merchantReference>
                    <originalReference>KFTDJK4FZQV4K472</originalReference>
                    <paymentMethod>discover</paymentMethod>
                    <pspReference>X8KVR5B5WF74MKG2</pspReference>
                    <reason/>
                    <success>true</success>
                </NotificationRequestItem>
            </notificationItems>
        </notification>
    </sendNotification>
</soap:Body>

</soap:Envelope>

Response:

<?xml version="1.0" encoding="UTF-16"?>
<SOAP-ENV:Envelope

xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://notification.services.adyen.com">
<SOAP-ENV:Body>
    <ns1:sendNotificationResponse>
        <ns1:notificationResponse>[accepted]</ns1:notificationResponse>
    </ns1:sendNotificationResponse>
</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Notification Log #2

Timestamp: 2023-04-06T17:10:49.038Z

URL: https://payments-listener.wikimedia.org/adyen

Request:

<?xml version="1.0" encoding="UTF-16"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
    <sendNotification xmlns="http://notification.services.adyen.com">
        <notification>
            <live>true</live>
            <notificationItems>
                <NotificationRequestItem>
                    <additionalData>
                        <entry>
                            <key xsi:type="xsd:string">bookingDate</key>
                            <value xsi:type="xsd:string">2023-04-06T19:10:20Z</value>
                        </entry>
                    </additionalData>
                    <amount>
                        <currency xmlns="http://common.services.adyen.com">USD</currency>
                        <value xmlns="http://common.services.adyen.com">300</value>
                    </amount>
                    <eventCode>REFUND</eventCode>
                    <eventDate>2023-04-06T19:09:30+02:00</eventDate>
                    <merchantAccountCode>WikimediaDonations</merchantAccountCode>
                    <merchantReference>174922548.1</merchantReference>
                    <originalReference>W4R4D9VQ7ZT3MKG2</originalReference>
                    <paymentMethod>visa</paymentMethod>
                    <pspReference>BMJWB6HQ8W329C32</pspReference>
                    <reason/>
                    <success>true</success>
                </NotificationRequestItem>
            </notificationItems>
        </notification>
    </sendNotification>
</soap:Body>

</soap:Envelope>

Response:

<?xml version="1.0" encoding="UTF-16"?>
<SOAP-ENV:Envelope

xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://notification.services.adyen.com">
<SOAP-ENV:Body>
    <ns1:sendNotificationResponse>
        <ns1:notificationResponse>[accepted]</ns1:notificationResponse>
    </ns1:sendNotificationResponse>
</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

^ with the info Adyen sent back I created this ticket to handle refund ipns T336439: Handle Adyen refund IPNs
This should hopefully get them into civi faster

Cstone moved this task from User Bug Backlog to Done on the Fundraising Tech - Chaos Crew board.May 10 2023, 8:53 PM

Thank you, @Cstone

Dwisehaupt moved this task from Done to Completed 20230426 - 20230522 on the Fundraising Tech - Chaos Crew board.May 22 2023, 7:38 PM

adjust audit to catch Adyen script refunds?Closed, ResolvedPublicActions

Description

Related Objects

Event Timeline

adjust audit to catch Adyen script refunds?
Closed, ResolvedPublic
Actions