Authorize.net webhooks
Last verified against Authorize.net's documentation on September 27, 2026.
Authorize.net sends webhooks when something happens to a transaction, a customer profile, or a subscription: a payment is captured, a refund settles, a recurring payment fails. Authorize.net signs each notification with HMAC-SHA512, retries a failed one up to 10 times over about eight days, and can mark an endpoint inactive if it keeps failing, which stops future notifications entirely. This page covers what Authorize.net sends, how it delivers, how to fix the common errors, and where HookDeploy fits.
What Authorize.net sends webhooks for
| Area | Example events | Typical use |
|---|---|---|
| Payments | net.authorize.payment.authcapture.created, net.authorize.payment.capture.created, net.authorize.payment.refund.created, net.authorize.payment.void.created | Fulfill orders and record refunds |
| Fraud | net.authorize.payment.fraud.held, net.authorize.payment.fraud.approved, net.authorize.payment.fraud.declined | Release or cancel held orders |
| Customers | net.authorize.customer.created, net.authorize.customer.paymentProfile.created | Sync stored payment profiles |
| Subscriptions | net.authorize.customer.subscription.created, net.authorize.customer.subscription.suspended, net.authorize.customer.subscription.terminated | Keep recurring billing in sync |
Each notification is a JSON POST with a notificationId, an eventType, an eventDate, a webhookId, and a small payload with the entity’s ID and key fields. For full transaction details, call the Transaction Details API with that ID.
How Authorize.net delivers webhooks
| Behavior | Detail |
|---|---|
| Method and format | POST with a JSON body |
| Signature header | X-ANET-Signature, formatted sha512=<hex> |
| Signing scheme | HMAC-SHA512 over the raw body, keyed with your account’s Signature Key |
| Success | 200 |
| Retries | Up to 10: three at 3-minute intervals, three at 8-hour intervals, then four at 48-hour intervals |
| After retries | The notification is marked Failed. The notification history API shows every attempt |
| Inactive endpoints | Endpoints that keep failing can be set inactive, and inactive endpoints receive no notifications |
| Deduplication | notificationId |
Common Authorize.net webhook errors and how to fix them
Signature doesn’t match
- Case. The hex digest in the header is uppercase. Compare case-insensitively, or uppercase your own digest.
- Prefix. Strip
sha512=before comparing. - Parsed body. Hash the raw bytes, not a re-serialized object.
- Wrong key. The key is your Signature Key, from Account, then Settings, then API Credentials and Keys. Generating a new Signature Key replaces the old one everywhere it’s used.
Endpoint went inactive
Authorize.net stops sending to endpoints that keep failing. Its own guidance is to respond with 200 as soon as the notification arrives and process it afterward, because a handler that fails midway doesn’t just lose that event, it can stop future ones. Reactivate the endpoint in Account, then Webhooks, once it’s fixed.
Payload is missing details
The payload carries only the entity ID and a few fields. Fetch the transaction or profile from the API before acting on it.
Duplicate notifications
Retries resend the same notification. Deduplicate on notificationId.
Why use HookDeploy with Authorize.net
Keep your endpoint active
HookDeploy captures every Authorize.net webhook at Cloudflare’s edge and responds right away, before forwarding it to your server. Authorize.net sees a 200 every time, so your endpoint stays active even while your own server is down, and nothing waits days in Authorize.net’s retry schedule.
- Destination retries. Starter retries 3 times (after 30 seconds, 5 minutes, and 30 minutes). Pro and Scale retry up to 5 times on a schedule you choose. Free doesn’t retry automatically.
- Incidents. Forward failures are grouped into incidents, and you can bulk-replay them once your server recovers.
- History. HookDeploy keeps captured webhooks for your plan’s retention period, from 7 days on Free to 365 days on Enterprise.
One webhook, many systems
Send each Authorize.net event to your app, your accounting or ERP system, and an alert channel in parallel. A failing destination doesn’t hold up the others. Free includes 1 destination per endpoint, Starter includes 5, and Pro and above are unlimited.
Deliver to systems Authorize.net can’t reach
The HookDeploy Agent connects outward from your network over mTLS and delivers events to a local port, so a billing or fulfillment service in a private network can receive Authorize.net events with no public endpoint.
Develop against real events
A tap sends a temporary copy of live Authorize.net events to 127.0.0.1 on your machine while production keeps receiving them.
Know the limits
- Signature headers. HookDeploy forwards
X-ANET-Signatureunchanged. Don’t use a transformation on a destination that verifies it, since that changes the body. - Plan limits. On Free, requests beyond the monthly allowance or the daily limit get a
429, which Authorize.net treats as a failed delivery. Paid plans keep accepting traffic past the included volume.
Retries, replays, and duplicates
Authorize.net’s signature covers only the body, with no timestamp, and HookDeploy forwards the body and X-ANET-Signature header unchanged, so retries and replays verify exactly like the original delivery. A privacy filter or body key sanitization rule changes the stored copy used for retries and replays, and then the signature won’t match.
Authorize.net’s retries, HookDeploy’s retries, and replays can all deliver the same notification. Deduplicate on notificationId.
Set up Authorize.net with HookDeploy
- In HookDeploy, create an endpoint (for example,
Authorize.net production) and copy its URL. - On the Forwarding tab, add a destination pointing to your handler, or to an agent for private delivery, and set its retries.
- In the Authorize.net Merchant Interface, go to Account, then Webhooks, and click Add Endpoint. Paste your HookDeploy URL, set it to active, and choose your events.
- Make sure your account has a Signature Key, from Account, then Settings, then API Credentials and Keys.
- Use Test Webhook on the endpoint, and confirm the notification appears in HookDeploy and reaches your handler.
Example handler (Node.js and Express)
import crypto from 'node:crypto';
import express from 'express';
const app = express();
// Raw body parser on this route, registered before any global JSON middleware.
app.post('/webhooks/authorize-net', express.raw({ type: 'application/json' }), async (req, res) => {
const received = (req.get('x-anet-signature') ?? '').replace(/^sha512=/i, '').toUpperCase();
const expected = crypto
.createHmac('sha512', process.env.ANET_SIGNATURE_KEY)
.update(req.body) // raw bytes
.digest('hex')
.toUpperCase();
const valid =
received.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(received), Buffer.from(expected));
if (!valid) return res.status(401).send('Invalid signature');
res.sendStatus(200); // respond first, so failures in processing can't deactivate the endpoint
const event = JSON.parse(req.body.toString('utf8'));
await enqueue({ notificationId: event.notificationId, type: event.eventType, entityId: event.payload?.id });
// Deduplicate on notificationId, then fetch full details from the API.
});
FAQ
How do I verify an Authorize.net webhook?
Compute an HMAC-SHA512 of the raw request body with your Signature Key, and compare it to the value in the X-ANET-Signature header after removing its sha512= prefix. The header uses uppercase hex, so compare case-insensitively.
How many times does Authorize.net retry a webhook?
Up to 10 times until it gets a 200: three times at 3-minute intervals, three more at 8-hour intervals, and four at 48-hour intervals. After that, the notification is marked Failed.
Why did Authorize.net stop sending webhooks?
Endpoints that keep failing can be marked inactive, and inactive endpoints get no notifications. Respond with 200 immediately and process afterward, then reactivate the endpoint in Account, then Webhooks.
Why is the Authorize.net payload so small?
Notifications carry the entity ID and a few key fields. Call the Transaction Details API, or the customer and subscription APIs, for the full record.
How do I deduplicate Authorize.net webhooks?
Use the notificationId, which stays the same across retries of the same notification.
Does HookDeploy break Authorize.net signature verification?
No. The signature covers only the body, and HookDeploy forwards the body and X-ANET-Signature header unchanged, so first deliveries, retries, and replays all verify. A transformation or privacy filter changes the body, and then the signature won't match at that destination.