@Eileenmcnaughton excited much!

I think we can close this as it became a back-and-forth conversation instead of a piece of work. We produced an experimented patch related to this for the gravy integration here T364506: Gravy backend createPayment and https://gerrit.wikimedia.org/r/c/wikimedia/fundraising/SmashPig/+/1029267

Installing on Mac is now pretty fast after we added a bunch of Mac optimisations in the new build scripts, e.g. It takes 5 minutes to install CiviCRM vs the old 2 hours.

We did this with fundraising-dev v2.

We now have ./setup.sh urls which kidna does the same thing so I think we're good here.

This is done! We had version 1.0.0 https://gerrit.wikimedia.org/r/admin/repos/wikimedia/fundraising/dev,tags

We can rebuild much quicker now so this isn't as much of a problem.

@Eileenmcnaughton I feel like we figured this one out with a cli command?

The dLocal sandbox is using IP allowlist access. I think we need to get the Gr4vy platform IP. I tried adding the dLocal connection today, but Gr4vy is requesting a "Merchant name" as part of the credentials. I can't see it referred to in the dlocal docs or the API credentials we use, so I tried our account name, but that didn't work.

It looks like we're going to need to request individual sandbox accounts here as the sign-up requires a phone number.

This looks potentially useful https://github.com/gr4vy/gr4vy-php

I guess we need to rename this from upgrading to migrating based on @Cstone's work on T358624 and create some tasks for migrating it to Adyen. I switched off the Amazon audit job today, as it's just adding to the unresolvable failmail pile.

I'm not sure of the best way to implement this. Did you have any thoughts when writing the ticket?

Our timeout is already 60 seconds for Adyen, and this will be retired 3 times. I'm now curious whether that means the donor will have to sit there for 3 minutes and how our PHP execution timeout behaves under those circumstances.