| Eileenmcnaughton | |
| Jul 6 2026, 2:55 AM |
| F92014913: image.png | |
| Jul 6 2026, 2:55 AM |
e.g see
https://civicrm.wikimedia.org/civicrm/contact/view/contribution?reset=1&action=view&id=145702445
The correct backend processor ID is dHJhbnNhY3Rpb25fY2E5MXhyNnE - we will need to repair all the gravy / transactions that have come in to date. Not sure if we update our IPN handling or gravy is putting the wrong things in the wrong places
I accidentally fixed this one first. There are 249 transactions that came in from the IPN listener where these ids are the same and missing the venmo id
We seem to have another 128... eg https://civicrm.wikimedia.org/civicrm/contact/view/contribution?reset=1&action=view&id=145881677
@Laurabarluzzi and I hunted the source down today, gravy is sending back their recon id in the payment_service_transaction_id which has otherwise been a backend processor id.
I asked gravy if this is a bug or feature on their side,
Change #1309756 had a related patch set uploaded (by Cstone; author: Cstone):
[mediawiki/extensions/DonationInterface@master] Don't set backend_processor_id on the first venmo api call
Change #1309756 merged by jenkins-bot:
[mediawiki/extensions/DonationInterface@master] Don't set backend_processor_id on the first venmo api call
Deployed the change to not save the backend processor id on the redirect url api call
Change #1310694 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@master] Repair braintree with incorrect backend_gateway_txn_id
Confirmed that the bug has been fixed, just needs the backfill now that Eileen is working on
Change #1310694 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Repair braintree with incorrect backend_gateway_txn_id