I own a license of GF, but not the Developer level. Bluepay's documentation mentions an Authorize.net AIM compatibility mode (https://secure.assurebuy.com/BluePay/BluePay_a.net/BluePay_Authorize.net_Emulator.txt) and I'd like to know if the Authorize.net Add-On could support this type of change, so that we could use Bluepay as processing backend.
PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.
Authorize.net add-on using Bluepay's compatibility mode
-
Posted 10 years ago on Thursday June 6, 2013 | Permalink
-
You would have to take our Authorize.net add-on and change it and create your own add-on for Bluepay. We don't have any hooks that would make this "easy" and if you changed our Authorize.net add-on, it would get overwritten in updates.
Posted 10 years ago on Friday June 7, 2013 | Permalink -
Ok, I'm knowledgeable enough to modify core files from your plugin and disabling its updates, although it goes against every "best practices" :(
But will I find the fields mentioned in the Bluepay documentation to change their URL target?
Posted 10 years ago on Friday June 7, 2013 | Permalink -
You will find the API url in the add-on to be able to change and update as needed.
Posted 10 years ago on Friday June 7, 2013 | Permalink
