{"title":"Updating orders","category":"default","creationDate":1778252958,"content":"<h2 id=\"notifications\">Webhooks<\/h2>\n<p>To keep you updated on the status of a payment, we send you webhooks.\u00a0The Adyen payments add-on for SAP Commerce (Hybris) accepts webhooks sent from Adyen using the controller under\u00a0<strong>URL \/adyen\/v6\/notification\/json<\/strong>.<\/p>\n<p>To receive webhooks, you first need to set up a standard JSON webhook in the Adyen Customer Area. Refer to <a href=\"\/plugins\/hybris\/set-up-the-add-on#server-notification-settings\">Server webhook settings<\/a>.<\/p>\n<h2 id=\"http-basic-authentication\">HTTP basic authentication<\/h2>\n<p>The webhooks are secured via HTTP basic authentication. You need to configure your username and password for basic authentication in the Adyen Customer Area when you set up webhooks, and also in your SAP back office.\u00a0<\/p>\n<p>As an extra layer of security you can allowlist Adyen IP ranges so that the controller under <strong>\/adyen\/v6\/notification\/json<\/strong> is only available from the Adyen address space.\u00a0<\/p>\n<h2 id=\"cron-job\">Cron job<\/h2>\n<p>Adyen may send webhooks in batches, and their processing can be a resource-intensive procedure. The add-on provides the cron job\u00a0<code>AdyenProcessNotificationCronJob<\/code>\u00a0that processes webhooks regularly.<\/p>\n<h2 id=\"event-handling\">Event handling<\/h2>\n<p>The add-on handles webhooks by their <code>eventCode<\/code>:\u00a0<\/p>\n<ul>\n<li><strong>Authorization<\/strong>:\u00a0Events are handled by registering the appropriate AUTHORIZATION transaction entry and emitting the <code>AdyenPaymentResult<\/code> event (or the <code>AdyenAuthorized<\/code> event for plugin versions below 7.0.0) to the corresponding order processes.<\/li>\n<li><strong>Capture<\/strong>:\u00a0Events are handled by registering the appropriate CAPTURE transaction entry and emitting the <code>AdyenCaptured<\/code> event to the corresponding order processes.<\/li>\n<li><strong>Refund<\/strong>:\u00a0Events are handled by registering the appropriate REFUND_FOLLOW_ON transaction entry and emitting the <code>AdyenRefunded<\/code> event to the corresponding return processes.<\/li>\n<li><strong>Cancellation<\/strong>:\u00a0Events are handled by registering the appropriate CANCEL transaction entry.<\/li>\n<\/ul>","url":"https:\/\/docs.adyen.com\/plugins\/hybris\/updating-orders","articleFields":{"id":"25152315","type":"page","description":"Learn about the webhooks that we send to inform you of the payment status.","_expandable":{"operations":""},"status":"current"},"algolia":{"url":"https:\/\/docs.adyen.com\/plugins\/hybris\/updating-orders","title":"Updating orders","content":"Webhooks\nTo keep you updated on the status of a payment, we send you webhooks.\u00a0The Adyen payments add-on for SAP Commerce (Hybris) accepts webhooks sent from Adyen using the controller under\u00a0URL \/adyen\/v6\/notification\/json.\nTo receive webhooks, you first need to set up a standard JSON webhook in the Adyen Customer Area. Refer to Server webhook settings.\nHTTP basic authentication\nThe webhooks are secured via HTTP basic authentication. You need to configure your username and password for basic authentication in the Adyen Customer Area when you set up webhooks, and also in your SAP back office.\u00a0\nAs an extra layer of security you can allowlist Adyen IP ranges so that the controller under \/adyen\/v6\/notification\/json is only available from the Adyen address space.\u00a0\nCron job\nAdyen may send webhooks in batches, and their processing can be a resource-intensive procedure. The add-on provides the cron job\u00a0AdyenProcessNotificationCronJob\u00a0that processes webhooks regularly.\nEvent handling\nThe add-on handles webhooks by their eventCode:\u00a0\n\nAuthorization:\u00a0Events are handled by registering the appropriate AUTHORIZATION transaction entry and emitting the AdyenPaymentResult event (or the AdyenAuthorized event for plugin versions below 7.0.0) to the corresponding order processes.\nCapture:\u00a0Events are handled by registering the appropriate CAPTURE transaction entry and emitting the AdyenCaptured event to the corresponding order processes.\nRefund:\u00a0Events are handled by registering the appropriate REFUND_FOLLOW_ON transaction entry and emitting the AdyenRefunded event to the corresponding return processes.\nCancellation:\u00a0Events are handled by registering the appropriate CANCEL transaction entry.\n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Plugins","lvl2":"SAP Commerce (Hybris)","lvl3":"Updating orders"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/plugins","lvl2":"https:\/\/docs.adyen.com\/plugins\/hybris","lvl3":"\/plugins\/hybris\/updating-orders"},"levels":4,"category":"Plugins","category_color":"green","tags":["Updating","orders"]}}