Page MenuHomePhabricator

DLocal Audit - Test with new integration
Closed, ResolvedPublic4 Estimated Story Points

Description

Files shouldn't have changed:

  • test that new style donations get into the file
  • test that new style donations are imported into civi properly

If we have to make a new one there is a task breakdown of how we set it up for braintree here T303442: break down Download and parse Braintree audit files task

Event Timeline

It looks like the audit files will be the same, but we will have to distinguish between payments from the new and the old integration: T324292

Cstone renamed this task from DLocal Audit - Will anything change? to DLocal Audit - Test with new integration.Dec 19 2022, 9:37 PM
Cstone updated the task description. (Show Details)
Dwisehaupt set the point value for this task to 4.Dec 19 2022, 9:37 PM

Sebastian said today that he will try to get an audit file for us from the transactions on the test account.

The test audit file is in the /var/spool/audit/astropay/incoming folder with the name wikimedia_staging_report_2023-04-04.csv

So from the files we have so far, the new staging report has old style IDs (which I don't even know what they are they don't show up in either console like that on dlocal's end)

There was a new style id in the 2023-04-05 old report from them testing. If this is configurable on dlocal's end we can ask if they can add a new column for the new style id (the ones like R-[long string] )

So it looks like dlocal is still sending their id (Reference in the audit) as an old style/or just different id, for example:

3835162751

Which then when searching in their console is tied to:

R-648-c61c4b89-3f3f-482c-8a48-6d246e4b1c60

Shoot, are we creating duplicate donations then, if we're searching by gateway + gateway_txn_id, and the audit gives us a different gateway_txn_id?

@Ejegg I don't think any of the ones from yesterday were duplicated, at least the couple I checked. I am emailing dlocal to see what that id even is and if they can send over the longer one too in the report

I hope this is an appropriate place to note this, the dLocal console seems to be case sensitive when using the long transaction ID.

From Civi the letters are CAPS: T-648-20C6DACE-03E1-4E52-BC8B-B0A010F799DE

From the dLocal console lower case: T-648-20c6dace-03e1-4e52-bc8b-b0a010f799de

The console search will find the ID with the lower case, but not the caps. I will add this to the next checkin with dLocal to see if they can make their search not case sensitive for ID #s, and hopefully that will enable this search, but in case not thought I'd flag it here in case there's anything we can adjust.

Change 914035 had a related patch set uploaded (by Cstone; author: Cstone):

[wikimedia/fundraising/crm@master] Change the log directory for the astropay audit to dlocal

https://gerrit.wikimedia.org/r/914035

Change 914035 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Change the log directory for the astropay audit to dlocal

https://gerrit.wikimedia.org/r/914035

Ran the audit successfully with the dlocal log file folder, refunds went into civi properly. I'm turning it back on but will watch it for the next few days.

Change 917422 had a related patch set uploaded (by Cstone; author: Cstone):

[wikimedia/fundraising/crm@master] Add fix for stopping ty emails for duplicated audit donations.

https://gerrit.wikimedia.org/r/917422

Change 917422 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Add fix for stopping ty emails for duplicated audit donations.

https://gerrit.wikimedia.org/r/917422

Update on status:
Refunds and chargebacks still have the old style ID in the csv, next week should have the new style IDs.
Chargebacks coming in with an old style ID from before the switch can be requeued as astropay in the damaged UI and get into civi successfully.

Confirmed chargeback has the new style ID, waiting for a refund

Confirmed refund has new style ID

XenoRyet set Final Story Points to 8.