cancel
Showing results for 
Search instead for 
Did you mean: 

wehook setting failed

I am completely blocked while trying to set up a Webhook notification in my Sandbox account and would appreciate any insight from the community.

 

The Problem:

Whenever I attempt to save a new Webhook configuration, I immediately get this generic error:

 

“Sorry, we're unable to process your request at this time due to an issue with the information provided. Please check your data and try a new version.”

This happens with any HTTPS endpoint I provide, including:

 

Public testing services like https://webhook.site/... and https://httpbin.org/post

My own live server endpoint (which is publicly accessible)

Critical Context (What Does Work):

 

Payment API is fully functional. I have successfully processed test transactions using the same Sandbox account's API credentials and receive settlement emails. This confirms my API Login ID and Transaction Key are valid and the core gateway is working.

I am performing this in the Sandbox environment (sandbox.authorize.net).

Troubleshooting I've Already Done:

 

Verified the endpoint URLs are correct, publicly accessible, and return HTTP 200 to HEAD/GET requests.

Ensured all required fields are filled (Name, URL, Status=Active).

Tried different browsers (Chrome, Firefox) in incognito/private mode.

Used the simplest possible test URL (https://httpbin.org/post).

Looked for but could not find a separate “Security Settings” or “Webhook” toggle in my account menu (newer interface?).

My Question:

Has anyone encountered this specific “try a new version” error when creating a Sandbox Webhook? Is there a known:

 

Account permission that needs to be explicitly enabled?

Interface bug or workaround?

Step I might have missed?

The inability to test asynchronous notifications is a major blocker. Any guidance would be greatly appreciated!

 

Environment:

 

Interface: Sandbox Merchant Interface

API Use: Direct API integration (no SDK)

Language: PHP / iOS

Thank you.

quackadefresh
New Member
1 REPLY 1

I faced a similar issue in the sandbox. In my case, it was caused by missing permissions on the sandbox account. After enabling webhook and notification access in the account settings, the error stopped. Also, double-check that the endpoint is reachable and returns a 200 response. Restarting the setup after saving changes helped as well.

carolineharper
New Member