From a batch of 10 refunds on 3/31, two yielded Server Error messages and then moved to status canceled, but the reversals are not in Civi:

1. cid=67499342 reference T-648-45b112ad-e05e-4e28-b7b8-7ba16534cbfc invoice 229591572.1
2. cid=67487553 reference T-648-422e39fb-bb6d-489d-ac30-b5bc61fbc94d invoice 229546648.1

I'll monitor next week to see if the weekly audit catches them.

The canceled transactions from the prior comment are not in Civi as of today.

@MBeat33 Following up on an old task here, checking the two transactions mentioned we never got updated statuses in the audit so they are still not refunded in civi.

Looking at civi I see not that many refunds from dlocal, and most related to fraud.

Is this low amount normal or is there still an issue with dlocal refunds getting into civi?

I do see 2 recent ones from gravy.

Thanks, @Cstone we haven't done a dLocal refund at dLocal since 8/5/2025. The refunds done at dLocal before then have reached Civi.

From Gravy, the two fraud refunds from September 9th 235466165.2 and 235466059.2 have reached Civi.

It doesn't look like there's still an issue - should I just manually update the status of two from the initial description in Civi?

@MBeat33 catching back up on this, yeah if we have fully moved off of them since August, manually marking them would be the easiest