- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Error connecting to AuthorizeNet
I am using Caldera Forms in WordPress with the Authorize.net Addon in Sandbox mode. Everything seems set, but I keep getting "Error connecting to AuthorizeNet" when trying to use the form. I've read other discussions on this forum with the same topic, but none of the responses seem to apply. I don't see any other error information.
โ09-28-2017 05:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @POLdave17,
Are you using Sandbox credentials when attempting to connect?
Certified Authorize.net developers

โ09-28-2017 06:25 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, I am using Sandbox credentials.
โ09-28-2017 06:51 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Then, are you sure your server is making a TLS1.2 connection?
Certified Authorize.net developers

โ09-28-2017 06:55 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am still not sure what the error was with the Sandbox version, but once I went live, it worked. Thanks.
โ10-06-2017 03:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's good, not only because you are able to use your application now, but because it makes for strong indicator that your issue was related to the requirement of a TLS 1.2 connection on the Sandbox.
You shoud resolve this issue before February 28, 2018, when TLS 1.2 will be required on the production API endpoint as well.
Certified Authorize.net developers

โ10-06-2017 10:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Im using TLS 1.2
Still gives me the same error
Please help
โ03-27-2018 01:44 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Check to make sure the certifacate (cert.pem) that you are using with your API is current or new. We were getting the same error with TLS 1.2 and resolved the issue by updating our test certificate. Hope ths helps.
โ04-12-2018 06:50 AM

