After updating to WishList Member 3.33.0 or higher, you may see a “WishList Member Security Notice – Authorize.net” on your dashboard that reads: “Authorize.net webhooks cannot be securely verified until you add your Signature Key. WishList Member is accepting them without verification until you do.” This article explains why the notice appears and how to resolve it.
Why You're Seeing This Notice
Authorize.net sends webhooks to your site to report events such as cancellations, refunds, and voids. Authorize.net signs each webhook using your account's Signature Key, and WishList Member checks that signature to confirm the webhook genuinely came from Authorize.net.
If no Signature Key is saved in your Authorize.net settings, WishList Member cannot verify those webhooks, so it shows this notice.
What This Means for Your Payments
Your site keeps working in the meantime. Authorize.net events are still being processed, so your members' access continues to update.
The notice is about verification, not interruption. Until you add your Signature Key, WishList Member accepts Authorize.net webhooks without confirming each one came from Authorize.net. Adding the Signature Key restores that verification.
The notice stays in place until the Signature Key is saved and a verified webhook is received, and it cannot be dismissed. That is intentional: it is a reminder to complete a one-time setup step. Since this step affects how your payments are verified, we encourage you to take care of it soon.
How to Resolve It
- Log in to the Authorize.net Merchant Interface.
- Go to the Account > API Credentials & Keys section in Authorize.net. Your Signature Key is managed there. If you do not already have one, you can create a new Signature Key from this screen.
- Copy your Signature Key.
- In WishList Member, go to the Setup > Integrations > Payment Providers section and open the Authorize.net configuration. You can also click “Configure Authorize.net” in the notice.
- Paste your Signature Key into the Signature Key field and save your settings.
For WishList Member to receive these events, your Authorize.net account also needs a webhook pointing at your site (set in the Account > Settings > Webhooks section in the Authorize.net Merchant Interface). If you have been receiving cancellations and refunds correctly until now, this is already in place.
Once WishList Member receives and verifies a webhook using your Signature Key, the notice clears.
Still Seeing the Notice?
If the notice is still showing after you have added your Signature Key, please confirm the key was pasted in full with no extra spaces, and that your Authorize.net webhooks are active and pointed at your site. The notice clears on its own once WishList Member receives a webhook it can verify with the saved key.
Note: if you generate a new Signature Key in Authorize.net, the previous one stops working. Make sure the key saved in WishList Member is the one currently active in your Authorize.net account.
