You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a webhook notification sent by Adyen cannot be authenticated due to incorrect Basic of HMAC authentication then the adyen/error.isml template is rendered (here), but since this response uses a successful HTTP status code Adyen will consider this notification as accepted.
Also if another issue occurs when string the webhook notification then the notifyError.isml template is rendered (here), but again with a successful HTTP status code so Adyen will also consider this notification as accepted.
Considering these notifications as accepted by Salesforce Commerce Cloud means that merchants will not be properly informed that notifications are in fact not configured correctly, and can lead to orders not being placed.
The text was updated successfully, but these errors were encountered:
If a webhook notification sent by Adyen cannot be authenticated due to incorrect Basic of HMAC authentication then the
adyen/error.isml
template is rendered (here), but since this response uses a successful HTTP status code Adyen will consider this notification as accepted.Also if another issue occurs when string the webhook notification then the notifyError.isml template is rendered (here), but again with a successful HTTP status code so Adyen will also consider this notification as accepted.
See also https://www.adyen.com/knowledge-hub/webhooks-accept-2xx
Considering these notifications as accepted by Salesforce Commerce Cloud means that merchants will not be properly informed that notifications are in fact not configured correctly, and can lead to orders not being placed.
The text was updated successfully, but these errors were encountered: