Hey there,
With a little bit of customization to this code, you can configure Authorize.net to use the correct post URL (either https://test.authorize.net/gateway/transact.dll for testing, or https://secure.authorize.net/gateway/transact.dll for production).
/*
Use the NETbilling host with the Authorize.net gateway class.
*/
function my_pmpro_authorizenet_post_url($post_url, $gateway_environment)
{
//could check gateway_environment == “live” here if we had test/live urls
return “https://secure.netbilling.com/gw/native/interactive2.2?x_Login”;
}
If you need further help using this, please consider becoming a member at http://www.paidmembershipspro.com/pricing/
Hope that helps!
Thanks,
Jess
I am having the same issue with invalid merchant configuration, despite putting in all of the correct gateway information and setting everything up on paypal. I know nothing about the authorize.net or how to use it. At this point it would be nice to have the paid membership but until I can get this site going I can not afford to purchase. I have spent more than 20 hours trying to configure and have tried accessing all support possible but get one error after another. Can you please help me. theyellowstonedaily.com
Which PayPal gateway are you using? You might want to take a look at this blog post on some things to look out for when using PayPal.
I am also trying to get Paid Membership Pro to work with Authorize.net. I have double and triple checked my Login name and transaction key (both work fine on eventbrite)
I keep getting a big red error box on membership credit card processing, “Could not connect to Authorize.net” but in my Authorize.net transaction log I am seeing voided transactions. My SSL is working fine and authorize.net transactions work outside this plugin.
I looked in the code at the my_pmpro_authorizenet_post_url function all appears correct.
Any suggestions,
Tim
Also the plugin is sending the purchaser and email as though the transaction was successful.
Hmmm.. are you using the latest version of PMPro (1.7.11 right now)?
That error should only be displayed when there is no response when CURLing Authorize.net. You can see that here, but it sounds like it’s going through just fine. It’s possible there may be a case where the response is formatted differently than what PMPro is looking for and that could cause the error.
Since you mentioned you had other plugins using the Authorize.net, it’s also possible there may be a conflict there as well. Have you tried deactiving and reactivating your plugins one by one to see if you can isolate the problem?
If that doesn’t work, let me know and I’ll forward this to Jason, our lead developer, for further investigation.
Thanks,
Jess
