authnet merge requestshttps://lab.civicrm.org/extensions/authnet/-/merge_requests2022-08-11T15:08:07Zhttps://lab.civicrm.org/extensions/authnet/-/merge_requests/17implement Authnet.ipn API2022-08-11T15:08:07ZJonGoldimplement Authnet.ipn APIThis is a port of the Stripe.ipn API to Authnet.
This only supports passing a SystemLog ID and not the transaction ID - I made an attempt, and it seems possible, but not without refactoring `CRM_Core_Payment_AuthNetIPN::processWebhook()...This is a port of the Stripe.ipn API to Authnet.
This only supports passing a SystemLog ID and not the transaction ID - I made an attempt, and it seems possible, but not without refactoring `CRM_Core_Payment_AuthNetIPN::processWebhook()`, and this seemed more obviously safe.
If this is OK except for docs, let me know and I'll add docs.https://lab.civicrm.org/extensions/authnet/-/merge_requests/20throw exception on error2022-03-07T23:18:03ZJonGoldthrow exception on errorCompanion MR to https://lab.civicrm.org/extensions/mjwshared/-/merge_requests/29.Companion MR to https://lab.civicrm.org/extensions/mjwshared/-/merge_requests/29.https://lab.civicrm.org/extensions/authnet/-/merge_requests/16Draft: Initial support for AcceptJS2021-09-19T13:54:33Zmattwiremjw@mjwconsult.co.ukDraft: Initial support for AcceptJS![Accept.js demo](/uploads/d10a20d761af2e40087fcbff1224469a/Untitled.mp4)![Accept.js demo](/uploads/d10a20d761af2e40087fcbff1224469a/Untitled.mp4)https://lab.civicrm.org/extensions/authnet/-/merge_requests/6Do not check test processor webhook2021-03-19T19:44:02ZalicefruminDo not check test processor webhookWe configured a `Payment_AuthNetEcheck` processor using this extension.
We were getting an System Warning for the API KEY being "unauthorized" for the test processor and only the test processor (10). The live payment processor (9) was/i...We configured a `Payment_AuthNetEcheck` processor using this extension.
We were getting an System Warning for the API KEY being "unauthorized" for the test processor and only the test processor (10). The live payment processor (9) was/is working as expected and is not showing a system check.
The API Login ID, Transaction Key, Signature Key, Site URL and Recurring Payments URL settings are identical for paymentprocessor 9 and 10.
See Screenshot below:
![error](/uploads/52e585d484efe3cd4d181114ee5bb0fd/error.png)
The proposed solution is to not bother checking the test processor API KEY.https://lab.civicrm.org/extensions/authnet/-/merge_requests/2Update repo_url (needs the other MR merged too!)2020-04-30T12:05:22ZhomotechsualUpdate repo_url (needs the other MR merged too!)