Webhook in OFSLL facilitates to send Event outcome data to external system. If the external system is OBRH which is the endpoint to receive and process Event data payload from OFSLL, ensure that the Authentication Mode in Webhook is configured to ORACLE BANKING ROUTING HUB. For more information, refer to Webhook Definition section.

Below is an illustration indicating the flow of data between OFSLL and OBRH.

Figure B-5 Webhook - OBRH Process

Description of "Figure B-5 Webhook - OBRH Process"

• OFSLL Webhook generates events which are configured for specific actions.
• From Webhook, the data is transferred in the form of Request using http protocol and is first authenticated in an Authenticate Server. On authentication, a response is received in Response Token Key.
• Post authentication, to connect OBRH, OFSLL further needs to send addition Authentication attributes and Request Header. The same can be defined in Attribute Value field of Webhook definition. For more information, refer to Authentication Attributes section.
  Below are some of the example of Attribute Values that can be defined for OBRH headers:

  Table B-3 OBRH Interfacing support

  Attribute Value	Example
  TOKEN REQUEST HEADER	appId
  REQUEST HEADER	entityId appId branchCode userId SERVICE-CONSUMER SERVICE-CONSUMER SERVICE

  Note:

  OBRH currently does not support return of customizing HTTP header [X-Hmac] because of which enable of Verified indicator using Test button cannot be done. Verification functionality should be done manually/via script and needs to be automated using OBRH once new feature of customizing HTTP header is enabled.