Run test transactions. Run stuff through the production gateway. Try to test the realtime listener and audit processor.
Which of their products are we using now? They've pitched a few for us to investigate, but let's focus on the shortest path to success:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Fix name of staged variable risk_score | mediawiki/extensions/DonationInterface | master | +6 -4 |
Change 248382 had a related patch set uploaded (by Ejegg):
Fix name of staged variable risk_score
We're currently using hosted payment pages, in an iframe. It's still enabled on production, and almost working - the error I'm getting now is that our fraud score offset isn't an integer, which is a really easy fix.
As a bit of context here: These forms worked with a few % lower success rate than our current forms. The way its integrated the 3rd party cookies were affecting many donors who ended up not being able to donate. So if we end up considering the same integration for Adyen, we need to be aware that the success rate/conversion rate will be lower than usual.
As a backup processor for this December, I think we should plan on the
shortest path to success an revisit a re-integration later.
Now loading their CC form in iframe, but getting 'Invalid Merchant Account' when submitting payment. Trying to get account status and see if we can reactivate it.
Going to deploy test credentials to production and put a payment through the whole pipeline, then mark it refunded.
Test donation made it all the way through to Civi: https://civicrm.wikimedia.org/civicrm/contact/view/contribution?reset=1&id=13257328&cid=12024420&action=view&context=contribution&selectedChild=contribute
Going to leave the listener and job runner on overnight to check the audit file processing.
@Ejegg - seems like this is a bit of a wandering/tracking task - should we close this and just keep the others open?