Page MenuHomePhabricator

Handle Gravy Paypal Chargebacks and Refunds from the resolution center
Closed, ResolvedPublic8 Estimated Story Points

Description

These come from ipns and the audit files

Event Timeline

Cstone updated the task description. (Show Details)
Cstone renamed this task from Handle Gravy Paypal Chargebacks to Handle Gravy Paypal Chargebacks and Refunds from the resolution center.Oct 1 2025, 5:07 PM

@LWadleigh noticed from Zendesk a PayPal donation that is unrefundable at Gravy, 2e5429ee-0630-4bba-8fa9-ff19aab64517. The refund does not show in Civi, but at the PayPal console 1U047267MX847735A looks like it was resolved from the Dispute Resolution Center. We'd like to nudge this Task upward in priority as it's complicating responding to donors.

Question about how this Task may be solved, will it enable visibility of these reversals in Civi only, or at Gravy as well?

I ran through the Paypal Audit just now & got this output - which means it resovled 15 but failed to resolve 5 ... digging

Number missing from database: 20
Missing transactions found in logs: 15
Missing transactions not found in logs: 5

Missing transaction summary:
Regular donations: 4
20260115: 2
20260114: 2
Refunds and chargebacks: 1
20260115: 1
Recurring donations: 0
Missing Transaction IDs:

https://developer.paypal.com/docs/reports/reference/tcodes/

Trxn IDNotesTcodes
GRAVY 8f7ba3dd-79b1-4338-9494-4a52bf565d73 ( 4MkPCMTzDVhZEtJhRAIp2x )possibly they cancelled our authorization to bill their recurring payment? - but why is it 'S' (settled?) check not in the stl fileT9900/ T1302 -
GRAVY 88601879-3f14-4ce2-b95d-f0fcdcacebe5 ( 49Ks53GK4oCAW0mkSJ0e8b )same as abovesame, also found a T1300 (authorize)
PAYPAL 55141732EP456154Wfee on chargeback - handling addedT0106
PAYPAL 3DR37509X73713725fee on chargeback - handling addedT0106
RFD CHARGEBACK PAYPAL_EC 9RM01435G2755603Tchargeback + feeT1201,T0106

Just noting that at least 1 of the above is actually a fee that needs to be attached to a chargeback rather than a 'real transaction' (a fix for this is going out)

The last one is the one to focus on because it has not been reversed https://civicrm.wikimedia.org/civicrm/contact/view?reset=1&cid=8930782

I will try running again once new patches are out

@MBeat33 our parsing of the paypal reconciliation/audit files seems to be sorting these out now - since I'm using the paypal reconciliation files we have them back to 2014 & I can run the reconciliation script as far back as we need. I was planning to run from at least mid-December forwards but let me know if you want me to go back further

Many thanks, @Eileenmcnaughton Maybe going back to June 1 2025 might be good to establish clean numbers for the fiscal year? I'm not sure of the $ amount involved, or the tech load to do so. @EMartin do you think it would matter for reconciliation purposes to go back farther?

As a follow up question, would we expect Gravy to pick up the newly updated statuses of these PayPal reversed transactions? I have a recent transaction that is refunded at PayPal and in Civi, but not at Gravy:

https://civicrm.wikimedia.org/civicrm/contact/view?reset=1&cid=70050688
https://wikimedia.gr4vy.app/merchants/default/transactions/6aa1113b-02c6-415c-ad93-ec34be8d26a4/overview

If we can document how we expect these to appear at Gravy that would help the DR team know what to look for.

@MBeat33 Ok - I'll parse them back further - but I don't think this work I've done will affect Gravy console - the work from our side is done - ie Gravy has the same information that we have about those transactions - but it's on them to use it. We will get Civi data accurate though

Damilare set the point value for this task to 8.Feb 4 2026, 5:30 PM
AKanji-WMF moved this task from Sprint +1 to Current Sprint on the Fundraising-Backlog board.
AKanji-WMF subscribed.

Closing based on discussion with @Eileenmcnaughton in sprint planning; @MBeat33 has a related question as to how to get Gravy to share these in Gravy console to be progressed with them.