Removed deprecated module DirectPost from Authorize.net payment method #3972
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
Template : admin
empiricompany
approved these changes
May 6, 2024
Flyingmana
approved these changes
May 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR targets
nextDirectPost is an old submodule of the Authorize.net payment method that's been bundled in M1 since many many years.
DirectPost has beed deprecated years ago, not only in M1 but most of all by Authorize itself, in fact:
https://developer.authorize.net/api/upgrade_guide.html
Since a few years it's not even possible to create a new DirectPost account, in fact it needs this "Merchant MD5" configuration parameter:
But it's not possible to generate it anymore on the authorize.net website:
rendering the whole thing useless
This PR removed all traces of DirectPost which is not working anymore and has to go, while (I've tested both) the normal Authorize.net module is perfectly working.