It sounds like we're happy to consolidate all payments into a single report for now. I'll build in the work from this ticket to separate each payment by backend processor as a follow-up to T367788: Gravy Audit/Settlement Processing

We might need to broaden the scope of this ticket and block all IPNs that include the Gravy metadata.

I successfully tested with AU, NZ, CA, and IE, and I can see transactions in the Gravy and Adyen consoles.

After reading the Zendesk API docs, I couldn't see a way to combine properties to search against. Instead, in the patch on this ticket, I've swapped "submitter" for "requester" as it should cover both scenarios we need: when the donor emails in and when donor services create a ticket on behalf of a donor and set the donor as the requester.

Let's drop these right away instead of letting them get on the jobs-adyen queue and filter out that way.

Test links spreadsheet has been started here

The Adyen production configuration and the initial Gravy "flow" config have been added to the Gravy production console.

@EMartin @RKumar_WMF now have access to the gravy prod console

Adyen has enabled the new Gravy-compatible production account, so I'll add that to the new connection details with the API keys generated yesterday. Adyen requires you to save these locally, as after that, they are no longer accessible.

I sent over the PCI documents yesterday in that email requesting the API user account be upgraded. I cc'ed in fr-tech.

I'll finish off what I have here and push it up shortly

The associated gitlab commit is here.

Thanks again @Wfan for the additional feedback. I've updated the image to show the correct format for the Alt block and updated the title as requested. I agree that it makes sense to differentiate them, especially when we add new ones. Here's the latest: