topic Is Message-Level Encryption (MLE) required for Unified Checkout webhooks to be triggered? in cybersource APIs

Is Message-Level Encryption (MLE) required for Unified Checkout webhooks to be triggered?

herath — Thu, 25 Jun 2026 09:42:31 GMT

I have successfully completed the Unified Checkout integration, and transactions are processing correctly. However, I am not receiving webhook notifications at my endpoint.

Can anyone confirm whether enabling MLE is mandatory for webhook delivery, or should webhooks work independently of the MLE configuration?

Re: Is Message-Level Encryption (MLE) required for Unified Checkout webhooks to be triggered?

jacobmattison6 — Tue, 30 Jun 2026 16:47:01 GMT

I'm not getting webhook notifications either. I think I have set up MLE, but it's a little unclear whether I did all of the necessary steps.

Re: Is Message-Level Encryption (MLE) required for Unified Checkout webhooks to be triggered?

Sunilkumar901 — Thu, 09 Jul 2026 13:01:18 GMT

From what I've seen, Message-Level Encryption (MLE) and webhook delivery are generally separate features. MLE is mainly used to encrypt sensitive payload data, while webhook notifications should still be triggered as long as the webhook endpoint is configured correctly and the required event subscriptions are enabled.

If the endpoint isn't receiving any requests, it may be worth checking a few things:

Verify that the webhook URL is publicly accessible and returns an HTTP 2xx response.
Confirm that the correct event types are subscribed in the CyberSource portal.
Check whether the webhook configuration is enabled for the environment you're testing (sandbox vs. production).
Review any delivery logs or retry history available in the portal to see whether the requests are failing or not being sent.

I'm also interested in the official clarification regarding whether MLE has any impact on webhook delivery, so hopefully someone from the CyberSource team can confirm.

Re: Is Message-Level Encryption (MLE) required for Unified Checkout webhooks to be triggered?

gennybell — Mon, 20 Jul 2026 08:06:48 GMT

Every refund request returns a "Not Authorized" error. I’ve verified my API keys and credentials multiple times, and they are configured correctly. Since payments are working without any issues, I’m unsure what could be causing the authorization failure specifically for refunds.