topic Wrong Event Type in Webhook Ping Payload in Integration and Testing

Wrong Event Type in Webhook Ping Payload

1grukltd — Thu, 29 Jun 2017 10:55:29 GMT

Hi,

I have registered a webhook in my sandbox account and selected just a single event:

net.authorize.payment.capture.created

But when I ping it the payload is as follows:

{"notificationId":"f2d977df-1eba-4b81-8ec3-074f35d18a89","eventType":"net.authorize.payment.authcapture.created","eventDate":"2017-06-29T10:48:59.3649911Z","webhookId":"e4b78407-9d6c-4c4e-ba5e-5198daa98565","payload":{"responseCode":21,"authCode":"572","avsResponse":"M","authAmount":12.5,"entityName":"transaction","id":"245"}}

On 100% of my tests the event type in the payload is always:

net.authorize.payment.authcapture.created

and not

net.authorize.payment.capture.created

Is this just an anomlay of sandbox or ping requests? Or do I need to handle this somehow?

Many thanks

Graham

Re: Wrong Event Type in Webhook Ping Payload

Aaron — Fri, 30 Jun 2017 21:55:53 GMT

Hi @1grukltd,

The eventType and the payload are the same for all test notifications, regardless of what the Webhook is registered for. The 'pings' command is designed more for testing that your system can actually receive a notification, not for testing that it's processing every part of the notification correctly.

There are a few ways that we could enhance that in the future, possibly by allowing you to send a request to test that Webhook for a specific eventType, or by allowing you to send a specific payload to be passed on in the test notification. If that's something you'd like to see, I'd encourage you to post this onto our Ideas Forum where others can take a look, contribute feedback, and vote for new features.