Skip to content

Conversation

@fulldecent
Copy link
Contributor

@fulldecent fulldecent commented Jul 12, 2017

Reference: https://www.authorize.net/content/dam/authorize/documents/AIM_guide.pdf version June 2016 page 39.

Fixes input sanitization issue #244.

@fulldecent
Copy link
Contributor Author

Bump. Issue is identified and fix is ready to deploy.

@fulldecent
Copy link
Contributor Author

Status of AIM API:

Supported but no longer updated

https://developer.authorize.net/api/upgrade_guide/

Authorize.Net’s legacy name-value-pair API is still supported, however it will not be
updated, except for critical security updates.

https://www.authorize.net/content/dam/authorize/documents/AIM_guide.pdf

Thank you for adding those notices.


That said, this PR is still valid for the input sanitization problem #244. You are welcome to merge. Or if bug fixes are no longer in scope for AIM then you are welcome to close.

Bumping now because documentation update is complete. And also, I'm trying to clean out my PR log :-)

@fulldecent
Copy link
Contributor Author

@adavidw ^^

@anuragg29 anuragg29 merged commit 46df374 into AuthorizeNet:master Jan 19, 2018
@fulldecent fulldecent deleted the patch-2 branch January 19, 2018 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants