Page MenuHomePhabricator

Auth at Adyen, Capturing at Gravy, settled in Civi straggler
Open, LowPublic

Description

This fraudulent transaction from Civi is at Capturing status at Gravy, yet seems to have stopped at Auth status at Adyen.

The final webhook event log at Gravy Feb 8, 2026 says Capture. Poliane is unable to refund this at Gravy.

This Tasks is just a request to see if we can determine what caused this. Maybe it is a one-off of some sort.

From the fraud angle, it probably makes sense to cancel at Adyen, but I added this to the Transaction Log in the Gravy Tracker as the status is divergent at different places.

Event Timeline

Two more recent frauds that we're unable to refund at Gravy, this time from dLocal. The statuses seem to agree between them, but Gravy yields an 'unable to refund' message' and no option to void them.

Gravy transactionstatusdatedLocal transactionstatus
9daaa511-eb05-4c20-acd0-d5f1c6839852captured2/12/26T-648-x1korjlv-aoeempp0sl0s15-vr5029ulfb1oPaid
0f6c0819-542b-4dfd-a322-bc3e9546d37ccaptured2/12/26T-648-x1korjln-bsi13e61il2nrc-kgskt6kq4ju4Paid

I'll add these to the Transactions Tab in the Tracker.

I have escalated the unrefundable dLocal's from the Feb 12 comment to the Gravy tracker.

I have also flagged there CID 70056260. At Adyen the donor has two chargebacks from January 29th, for $104.00 and $5,200.00. Both show as Settled at Gravy, and only the smaller of the two reached Civi as a chargeback, the other still says Completed.

I am concerned that the transaction statuses are diverging between Gravy, Adyen and Civi as frequently as they are. This is affecting DR and MG teams, so I'd suggest bumping this Task to medium priority.

re: the two unrefundable dLocal's at Gravy, Love replied that "The refund was rejected because the account is closed." I've asked them if they can improve their process and update the statuses of these transactions.