Article ID: 128789, created on May 4, 2016, last review on Jun 27, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5


There is a message sent from Authorize.Net to one or several customers that says

Dear Authorize.Net Merchant:

During a system scan, we noticed that your website or payment solution is
using the HTTP GET method when submitting your transaction requests to

Because HTTP GET methods do not adhere to current TLS protection
requirements, Authorize.Net will not allow HTTP GET methods for transaction
requests as of June 30, 2016. We recommend that you immediately update your
code to use the HTTP POST method instead.

Any transaction request submitted using HTTP GET after June 30th will be

Please contact your Web developer or solution provider for assistance, or
check out our Certified Developer Directory at
to find a developer to help you.

If you have already made these changes, please disregard this message. If
you have any questions about this email, please contact Customer Support.

Thank you for your attention to this matter and for being an Authorize.Net


Should anything be done by an OBAS Provider to match the upcoming changes?

Cause switch from GET to POST requires certain changes in OBAS code that were implemented in OBAS 4.5.6 release. The software issue number is PBAS-30299.


To resolve the issue, please upgrade to 4.5.6 as described in How to upgrade OBAS system to the latest available version.

If upgrade is not an option for you, there is a hotfix for OBAS 4.5.5 release. Please download 64-bit hotfix or 32-bit hotfix depending on your OS and install it by running the commands below.

For 64-bit OS:

# rpm -Uvh hspc-plugin-pp-op-anet-4.5.5-59.swsoft.x86_64.rpm
# hspc-upgrade-manager --finish

For 32-bit OS:

# rpm -Uvh hspc-plugin-pp-op-anet-4.5.5-59.swsoft.i386.rpm
# hspc-upgrade-manager --finish

Warning: Running hspc-upgrade-manager --finish will cause OBAS downtime for several minutes.

Search Words

important notice from

June 30, 2016




624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF