| Eileenmcnaughton | |
| May 22 2026, 1:35 AM |
| F83305171: image.png | |
| May 22 2026, 1:35 AM |
Our repair expired again & we can see some still wrong - this time native adyen recur
has
capture_id WTBM24G85CRPKM69
auth_id = empty
gateway_txn_id = FR5GJH46XKBVQM35
backend_processor_txn_id = WTBM24G85CRPKM69
Change #1291058 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@master] Extend repair date
Change #1291058 merged by Ejegg:
[wikimedia/fundraising/crm@master] Extend repair date
Sadly we didn't record the raw API response in our job logs.
2026-05-13 00:27:44,213 Charging contribution_recur id: 2296429 with invoice_id: 231964006.12
2026-05-13 00:27:46,472 Payment successful - invoice_id: 231964006.12 with status: Completed and processor_id: FR5GJH46XKBVQM35
In the Adyen API logs, the capture response is shown as this:
{
"merchantAccount": "WikimediaDonations",
"paymentPspReference": "FR5GJH46XKBVQM35",
"pspReference": "WTBM24G85CRPKM69",
"status": "received",
"amount": {
"currency": "JPY",
"value": 300
}
}The ApprovePaymentResponseMapper in the SmashPig code should map the pspReference to captureID and the paymentPspReference to AuthID and BackendProcessorTransactionID. Next step is to re-examine the code in the Civi recurring processor.
Change #1292884 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@deployment] Extend repair date
Change #1292884 merged by jenkins-bot:
[wikimedia/fundraising/crm@deployment] Extend repair date
Change #1293741 had a related patch set uploaded (by Ejegg; author: Ejegg):
[wikimedia/fundraising/SmashPig@master] Fallback for missing paymentPspReference
Change #1293741 merged by jenkins-bot:
[wikimedia/fundraising/SmashPig@master] Fallback for missing paymentPspReference