FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR IMPLEMENTING CONFIGURABLE WEBHOOKS”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR IMPLEMENTING CONFIGURABLE
WEBHOOKS
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to subscriptions management. More particularly, embodiments of the present disclosure relate to implementing configurable webhooks.
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Webhooks are user-defined HTTP (Hypertext transfer protocol) callbacks that are triggered on occurrence of an event. When the relevant event occurs, the source makes a request to the universal resource indicator (URI) configured for the webhook. Users can use them to cause events on one site to invoke behaviour on another. Subscription engines (SEs) allow any vendor/enterprise to sell their content on marketplace via admin portal plans. On behalf of them, subscription engines show plans in the marketplace and the customer can purchase them. The subscription engine (SE) only maintains subscriptions and payment related data, while provisioning/access is given by vendor. But vendor systems are all together a new environment, that is, the subscription engines may not be able to interact with vendor systems as the vendor systems exist in different environments. One of the mechanisms to make subscription engine and vendor systems interact is webhook which is known for sending data to a vendor.

[0004] In conventional implementation of webhooks, data related to a single plan could be sent to only a single webhook. Moreover, in conventional implementation of webhook, the system will try to send data to the webhook only once. There is no provision for re-sending the data to the webhook of the vendor. This may lead to data loss. In conventional implementation of webhook, it was not possible to configure the number of webhooks to which data of a single plan/service/offer can be sent to keep the subscription engine and vendor systems in sync. In conventional implementations, vendors were not enabled to create/configure their own endpoints where they require the plan data. Existing systems in the market for managing digital content subscriptions typically suffer from several shortcomings that limit their effectiveness and efficiency. Firstly, there is often a lack of seamless integration between the subscription management platforms and the vendors' systems. This results in a significant delay and complexity when synchronizing subscription changes such as new purchases, pauses, or terminations between the subscription service and the content providers. Vendors must usually rely on periodic updates or manual checks to refresh their user access rights, which can lead to customer dissatisfaction due to access issues or delays. Additionally, most existing solutions do not offer a sufficiently flexible notification system that can inform vendors immediately when a change occurs. This lack of real-time updates can impede the ability of content providers to provide timely services to their customers. For instance, when a customer purchases a new subscription, the vendor might not be aware of this transaction immediately, potentially causing a delay in the provisioning of the service. Furthermore, existing systems often do not provide a robust framework for handling errors and retries in the event of communication failures. This can lead to further delays and complications in ensuring that subscription data across systems is consistent and up-to-date. The absence of an effective error-handling mechanism can result in customers being unable to access services they have paid for, thereby affecting the user experience negatively.

[0005] Thus, there exists an imperative need in the art to provide a method and a system for implementing configurable webhooks.
SUMMARY
[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0007] An aspect of the present disclosure may relate to a method for implementing configurable webhooks. The method includes facilitating, by an authorization unit at a subscription engine, logging in of a user upon receiving a set of user details, wherein the set of user details are saved in a storage unit. The method further includes allowing, by a webhook configurator at the subscription engine, the creation of one or more webhooks by the user using a user interface. The method further includes triggering, by an event manager unit at the subscription engine, a target webhook upon occurrence of one or more events, wherein the target webhook is related to the one or more events. Thereafter, the method includes sending, by a transceiver unit at the subscription engine to a vendor device, a notification indicating the occurrence of the event based on the triggering of the target webhook.
[0008] In an exemplary aspect of the present disclosure, the method further comprising receiving, by the user via the user interface at the subscription engine, a user input for configuring the one or more webhooks, wherein the configuration comprises at least one of an endpoint address, an authorisation details, a retry number, a retry interval parameter, a pause capability parameter, a resume capability parameter, an edit capability parameter, and a delete capability parameter.

[0009] In an exemplary aspect of the present disclosure, the method further comprises storing, by the storage unit at the subscription engine, a detail of the configured one or more webhooks.
[0010] In an exemplary aspect of the present disclosure, the method further comprises, wherein the one or more events are configured by manual inputs of the user, via the user interface.
[0011] In an exemplary aspect of the present disclosure, the method further comprises, monitoring, by a monitoring unit at the subscription engine, the triggering of the target webhook upon the occurrence of the one or more events. The method further includes generating, by the monitoring unit at the subscription engine, one of a successful trigger result and an unsuccessful trigger result, wherein the successful trigger result is generated in an event the notification indicating the occurrence of the event based on the triggering of the target webhook is sent by the transceiver unit to the vendor device upon the occurrence of the event, and the unsuccessful trigger result is generated in an event the notification indicating the occurrence of the event based on the triggering of the target webhook is not sent by the transceiver unit to the vendor device upon the occurrence of the event.
[0012] In an exemplary aspect of the present disclosure, the method further comprises, receiving, by the event manager unit at the subscription engine, a manual user input for triggering the target webhook. Thereafter, the method includes triggering, by the event manager unit, the target webhook based on the manual user input.
[0013] In an exemplary aspect of the present disclosure, the method further comprises, displaying, by the user interface at the subscription engine, a set of details related to the one or more events, the set of details comprising one of the successful trigger results and the unsuccessful trigger result, and a metadata related to the one or more events.

[0014] Another aspect of the present disclosure may relate to a system for
implementing configurable webhooks, the system comprises a subscription engine.
The subscription engine further comprises an authorization unit configured to
5 facilitate logging in of a user upon receiving a set of user details, wherein the set of
user details are saved in a storage unit. The subscription engine further includes a webhook configurator connected at least to the authorization unit, the webhook configuration configured to allow a creation of one or more webhooks by the user using a user interface. The subscription engine further includes an event manager
10 unit connected at least to the webhook configurator, the event manager unit
configured to trigger a target webhook upon occurrence of one or more events, wherein the target webhook is related to the one or more events. The subscription engine further includes a transceiver unit connected at least to the event manager unit, the transceiver unit configured to send to a vendor device, a notification
15 indicating the occurrence of the event based on the triggering of the target webhook.
[0015] Another aspect of the present disclosure may relate to a user equipment for implementing configurable webhooks, the user device comprising a subscription engine, the subscription engine further comprising: an authorization unit configured
20 to facilitate logging in of a user upon receiving a set of user details, wherein the set
of user details are saved in a storage unit; a webhook configurator connected at least to the authorization unit, the webhook configurator configured to allow a creation of one or more webhooks by the user using a user interface; an event manager unit connected at least to the webhook configurator, the event manager unit configured
25 to trigger a target webhook upon occurrence of one or more events, wherein the
target webhook is related to the one or more events; and a transceiver unit connected at least to the event manager unit, the transceiver unit configured to send to a vendor device, a notification indicating the occurrence of the event based on the triggering of the target webhook.
30
6

[0016] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for implementing
configurable webhooks, the instructions include executable code which, when
executed by a one or more units of a system, causes: an authorization unit to
5 facilitate logging in of a user upon receiving a set of user details, wherein the set of
user details are saved in a storage unit, the webhook configuration to allow a
creation of one or more webhooks by the user using a user interface; the event
manager unit to trigger a target webhook upon occurrence of one or more events,
wherein the target webhook is related to the one or more events; and a transceiver
10 unit to send to a vendor device, a notification indicating the occurrence of the event
based on the triggering of the target webhook.
OBJECTS OF THE DISCLOSURE
15 [0017] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0018] It is an object of the present disclosure to provide a system and a method for implementing configurable webhooks. 20
DESCRIPTION OF THE DRAWINGS
[0019] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
25 and systems in which like reference numerals refer to the same parts throughout the
different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system
30 according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such
7

drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0020] FIG. 1 illustrates an exemplary block diagram of a computing device upon
5 which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure.
[0021] FIG. 2 illustrates an exemplary block diagram of a system for implementing
configurable webhooks in accordance with exemplary implementations of the
10 present disclosure.
[0022] FIG. 3 illustrates a method flow diagram for implementing configurable webhooks in accordance with exemplary implementations of the present disclosure.
15 [0023] FIG. 4 illustrates a flow diagram for implementing configurable webhooks
in accordance with exemplary implementations of the present disclosure.
[0024] FIG. 5 illustrates an exemplary block diagram of a user equipment for
implementing configurable webhooks in accordance with exemplary
20 implementations of the present disclosure.
[0025] FIG. 6 illustrates an exemplary interface of a platform for creating webhooks by vendors in accordance with exemplary implementations of the present disclosure. 25
[0026] FIG. 7 illustrates an exemplary interface of a platform for modifying configuration of webhooks in accordance with exemplary implementations of the present disclosure.
8

[0027] FIG. 8 illustrates an exemplary interface of a platform displaying notifications for configured webhooks in accordance with exemplary implementations of the present disclosure.
5 [0028] FIG. 9 illustrates an exemplary interface of a platform for retry and view
details in case of failure in accordance with exemplary implementations of the present disclosure.
[0029] The foregoing shall be more apparent from the following more detailed
10 description of the disclosure.
DETAILED DESCRIPTION
[0030] In the following description, for the purposes of explanation, various
15 specific details are set forth in order to provide a thorough understanding of
embodiments of the present disclosure. It will be apparent, however, that
embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one
another or with any combination of other features. An individual feature may not
20 address any of the problems discussed above or might address only some of the
problems discussed above.
[0031] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather,
25 the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
30
9

[0032] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these
specific details. For example, circuits, systems, processes, and other components
5 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0033] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
10 diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
15
[0034] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not
20 necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner
25 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0035] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
30 processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
10

of microprocessors, one or more microprocessors in association with a (Digital
Signal Processing) DSP core, a controller, a microcontroller, Application Specific
Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing,
5 input/output processing, and/or any other functionality that enables the working of
the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0036] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
10 “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
“a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The
user equipment/device may include, but is not limited to, a mobile phone, smart
15 phone, laptop, a general-purpose computer, desktop, personal digital assistant,
tablet computer, wearable device or any other computing device which is capable
of implementing the features of the present disclosure. Also, the user device may
contain at least one input means configured to receive an input from at least one of
a transceiver unit, a processing unit, a storage unit, a detection unit and any other
20 such unit(s) which are required to implement the features of the present disclosure.
[0037] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable
25 medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
30
11

[0038] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with
5 each other, which also includes the methods, functions, or procedures that may be
called.
[0039] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a
10 general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
15
[0040] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information, or a combination thereof between units/components within the system and/or connected with the system.
20
[0041] As discussed in the background section, in conventional implementation of webhooks, data related to a single plan could be sent to only a single webhook. Moreover, in conventional implementation of webhook, the system will try to send data to the webhook only once. There is no provision for re-sending the data to the
25 webhook of the vendor. This may lead to data loss. In conventional implementation
of webhook, it was not possible to configure the number of webhooks to which data of a single plan/service/offer can be sent to keep the subscription engine and vendor systems in sync. In conventional implementations, vendors were not enabled to create/configure their own endpoints where they require the plan data. Existing
30 systems in the market for managing digital content subscriptions typically suffer
from several shortcomings that limit their effectiveness and efficiency. Firstly, there
12

is often a lack of seamless integration between the subscription management
platforms and the vendors' systems. This results in a significant delay and
complexity when synchronizing subscription changes such as new purchases,
pauses, or terminations between the subscription service and the content providers.
5 Vendors must usually rely on periodic updates or manual checks to refresh their
user access rights, which can lead to customer dissatisfaction due to access issues or delays. Additionally, most existing solutions do not offer a sufficiently flexible notification system that can inform vendors immediately when a change occurs. This lack of real-time updates can impede the ability of content providers to provide
10 timely services to their customers. For instance, when a customer purchases a new
subscription, the vendor might not be aware of this transaction immediately, potentially causing a delay in the provisioning of the service. Furthermore, existing systems often do not provide a robust framework for handling errors and retries in the event of communication failures. This can lead to further delays and
15 complications in ensuring that subscription data across systems is consistent and
up-to-date. The absence of an effective error-handling mechanism can result in customers being unable to access services they have paid for, thereby affecting the user experience negatively.
20 [0042] To overcome these and other inherent problems in the art, the present
disclosure proposes a solution of implementing configurable webhooks within a
subscription engine to enhance synchronization and real-time updates between
content vendors and the subscription management system. The solution includes
facilitating the creation, configuration, and monitoring of webhooks through a user-
25 friendly interface, which allows content providers to receive immediate
notifications about customer actions such as purchases, pauses, or terminations of
subscriptions. By introducing a solution where webhooks can be configured to send
notifications to multiple endpoints, the invention effectively addresses the
limitation of conventional systems that could only send data to a single webhook.
30 The flexibility allows multiple vendors to be updated simultaneously, ensuring that
all relevant parties receive timely updates on subscription changes, which is crucial
13

for services requiring immediate access provisioning. Furthermore, the present
disclosure includes robust error handling mechanisms by introducing features such
as retry intervals and manual retry options for webhooks. This ensures that even in
cases of communication failures, attempts to send notifications can be retried,
5 reducing the risk of data loss, and ensuring that vendors always receive the
necessary data to manage access rights effectively. The solution also provides the
ability for users to manually input configurations and trigger events, enhancing the
control vendors have over the synchronization process. The level of control is
particularly beneficial in scenarios where real-time data syncing between the
10 subscription engine and vendor systems is critical for customer satisfaction and
operational efficiency.
[0043] It would be appreciated by the person skilled in the art that the present
disclosure provides a comprehensive and innovative approach to managing digital
15 content subscriptions by addressing the key shortcomings of existing systems,
thereby improving integration, real-time communication, and error handling in the context of subscription management.
[0044] FIG. 1 illustrates an exemplary block diagram of a computing device [100]
20 (also referred to herein as a computer system [100]) upon which the features of the
present disclosure may be implemented in accordance with exemplary
implementation of the present disclosure. In an implementation, the computing
device [100] may also implement a method for implementing configurable
webhooks utilising the system. In another implementation, the computing device
25 [100] itself implements the method for implementing configurable webhooks using
one or more units configured within the computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
30 [0045] The computing device [100] may include a bus [102] or other
communication mechanism for communicating information, and a processor [104]
14

coupled with bus [102] for processing information. The processor [104] may be, for
example, a general purpose microprocessor. The computing device [100] may also
include a main memory [106], such as a random access memory (RAM), or other
dynamic storage device, coupled to the bus [102] for storing information and
5 instructions to be executed by the processor [104]. The main memory [106] also
may be used for storing temporary variables or other intermediate information
during execution of the instructions to be executed by the processor [104]. Such
instructions, when stored in non-transitory storage media accessible to the processor
[104], render the computer device [100] into a special-purpose machine that is
10 customized to perform the operations specified in the instructions. The computing
device [100] further includes a read only memory (ROM) [108] or other static storage device coupled to the bus [102] for storing static information and instructions for the processor [104].
15 [0046] A storage device [110], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
20 displaying information to a computer user. An input device [114], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command selections to the processor [104]. Another type of user input device may be a cursor controller [116], such as a mouse, a trackball, or cursor direction keys, for communicating direction
25 information and command selections to the processor [104], and for controlling
cursor movement on the display [112]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
30 [0047] The computing device [100] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
15

and/or program logic which in combination with the computing device [100] causes
or programs the computing device [100] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the
computing device [100] in response to the processor [104] executing one or more
5 sequences of one or more instructions contained in the main memory [106]. Such
instructions may be read into the main memory [106] from another storage medium,
such as the storage device [110]. Execution of the sequences of instructions
contained in the main memory [106] causes the processor [104] to perform the
process steps described herein. In alternative implementations of the present
10 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0048] The computing device [100] also may include a communication interface
[118] coupled to the bus [102]. The communication interface [118] provides a two-
15 way data communication coupling to a network link [120] that is connected to a
local network [122]. For example, the communication interface [118] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [118] may be a
20 local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
implementation, the communication interface [118] sends and receives electrical,
electromagnetic, or optical signals that carry digital data streams representing
various types of information.
25
[0049] The computing device [100] can send messages and receive data, including
program code, through the network(s), the network link [120] and the
communication interface [118]. In the Internet example, a server [130] might
transmit a requested code for an application program through the Internet [128], the
30 ISP [126], the local network [122], host [124] and the communication interface
[118]. The received code may be executed by the processor [104] as it is received,
16

and/or stored in the storage device [110], or other non-volatile storage for later execution.
[0050] The computing device [100] encompasses a wide range of electronic
5 devices capable of processing data and performing computations. Examples of
computing device [100] include, but are not limited only to, personal computers,
laptops, tablets, smartphones, servers, and embedded systems. The devices may
operate independently or as part of a network and can perform a variety of tasks
such as data storage, retrieval, and analysis. Additionally, computing device [100]
10 may include peripheral devices, such as monitors, keyboards, and printers, as well
as integrated components within larger electronic systems, showcasing their versatility in various technological applications.
[0051] Referring to FIG. 2, an exemplary block diagram of a system [200] for
15 implementing configurable webhooks is shown, in accordance with the exemplary
implementations of the present disclosure. The system [200] comprises at least one authorization unit [202], at least one webhook configurator [204], at least one user interface [206], at least one event manager unit [208], at least one transceiver unit [210], at least one storage unit [212] and at least one monitoring unit [214]. Also,
20 all of the components/ units of the system [200] are assumed to be connected to
each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 2 only a few units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers
25 of said units, as required to implement the features of the present disclosure.
Further, in an implementation, the system [200] may be present in a user device to implement the features of the present disclosure. The system [200] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a user equipment (UE)). In another
30 implementation, the system [200] may reside in a server or a network entity. In yet
17

another implementation, the system [200] may reside partly in the server/ network entity and partly in the user device.
[0052] The system [200] is configured for implementing configurable webhooks
5 with the help of the interconnection between the components/units of the system
[200].
[0053] The system [200] for implementing configurable webhooks comprises a subscription engine [201]. The subscription engine [201] comprises the
10 authorization unit [202] configured to facilitate logging in of a user upon receiving
a set of user details, wherein the set of user details are saved in a storage unit [212]. The authorization unit [202] within the subscription engine is specifically designed to manage user access by facilitating the login process. When a user attempts to log into the system, the authorization unit [202] receives a set of user details. This
15 typically includes credentials such as a username and a password. The authorization
unit [202] then compares the credentials against the user details stored in the storage unit [212]. If the credentials provided by the user match the details in the storage unit, the authorization unit authenticates the user's identity. The authentication process ensures that only legitimate users can access the system. Upon successful
20 authentication, the authorization unit may also facilitate the creation of a session
for the user. This session allows the user to interact with the system without needing to re-authenticate for each action or request within a session duration. The storage unit [212] is further configured to store at the subscription engine [201], details of the configured one or more webhooks wherein the one or more events are
25 configured by manual inputs of the user, via the user interface [206]. The users
interact with the system through the user interface to define or specify the events that should trigger the webhooks. The manual inputs could include specifying event types, conditions, or criteria that will activate the corresponding webhooks.
30 [0054] The webhook configurator [204] of the system is connected at least to the
authorization unit [202], the webhook configurator [204] configured to allow a
18

creation of one or more webhooks by the user using a user interface [206]. The
webhook configurator [204] ensures that after the user successfully logs in,
verifying their identity and access rights via the authorization unit [202], they can
then proceed to define and set up webhooks according to their specific
5 requirements. The user interface [206] provides a visual and interactive platform
through which users can easily configure various aspects of the webhooks, such as setting the endpoint URLs, defining event triggers, and specifying other relevant parameters like retry intervals or security settings. The webhook configurator [204] allows users to manage how and when data should be communicated to external
10 systems or applications, facilitating real-time data exchange and operational
efficiency. The webhook configurator [204] enables dynamic and customizable integration between the subscription engine [201] and external vendor systems or other third-party services. The disclosure encompasses the webhook configurator [204] for enabling users to create and modify webhooks through a user interface.
15 While creating the webhooks, the user interface [206] is configured to receive at
the subscription engine [201], a user input for configuring the one or more webhooks, wherein the configuration comprises at least one of an endpoint address, an authorisation details, a re-try number, a retry interval parameter, a pause capability parameter, a resume capability parameter, an edit capability parameter,
20 and a delete capability parameter. Also, the user interface [206] is further
configured to display at the subscription engine [201], a set of details related to the one or more events, the set of details comprising one of the successful trigger result and the unsuccessful trigger result, and a metadata related to the one or more events. Users can input configurations for one or more webhooks through the user interface
25 [206], including details such as endpoint addresses, authorization credentials, retry
settings, pause, and resume capabilities, as well as edit and delete options. Additionally, the user interface [206] is equipped to display information from the subscription engine [201], including details related to events such as successful or unsuccessful trigger results, along with metadata pertaining to these events. The
30 metadata includes additional information or descriptors related to the events being
monitored and managed by the subscription engine [201] such as timestamps
19

indicating when events occurred, identifiers for the events, descriptions or categorizations of the events, JavaScript Object Notation (JSON) message, subscriber identifier and any other pertinent data that provides context or insights into the nature and characteristics of the events being tracked. 5
[0055] The event manager unit [208] of the system is connected at least to the webhook configurator [204], the event manager unit [208] configured to trigger a target webhook upon occurrence of one or more events, wherein the target webhook is related to the one or more events. When an event occurs that matches the criteria
10 set for the target webhook, the event manager unit [208] activates the target
webhook. The event manager unit [208] is further configured to receive, at the subscription engine [201], a manual user input for triggering the target webhook; and trigger the target webhook based on the manual user input. The manual user input provided directly by a user rather than automatically generated. The event
15 manager unit is designed to respond to the occurrence of one or more events. When
the events occur, the event manager unit [208] triggers the target webhook. The triggering action is initiated by the event manager unit [208] in response to the occurrence of the specified events.
20 [0056] The transceiver unit [210] is connected at least to the event manager unit
[208], the transceiver unit [210] configured to send to a vendor device, a notification indicating the occurrence of the event based on the triggering of the target webhook. The notifications are sent in the form of data interchange format such as but not limited to JSON. The notification includes event occurrence information such as,
25 but not limited to, subscriber identifier, webhook identifier, site identifier, plan
identifier, plan name, and plan code. The notifications are sent when a particular event occurs, which is triggered by the activation of a target webhook. Essentially, when the event manager unit [208] detects the triggering of the specified webhook, it signals the transceiver unit [210] to send a notification to the vendor device,
30 informing them of the event occurrence. This setup allows for timely
20

communication of important events within the system to the external vendor, ensuring effective coordination and response.
[0057] The subscription engine [201] further comprises a monitoring unit [214]
5 configured to monitor the triggering of the target webhook upon the occurrence of
the one or more events; and generate one of a successful trigger result and an unsuccessful trigger result, wherein the successful trigger result is generated in an event the notification indicating the occurrence of the event based on the triggering of the target webhook is sent by the transceiver unit [210] to the vendor device upon
10 the occurrence of the event, and the unsuccessful trigger result is generated in an
event the notification indicating the occurrence of the event based on the triggering of the target webhook is not sent by the transceiver unit [210] to the vendor device upon the occurrence of the event. When an event occurs, the monitoring unit [214] checks if the corresponding webhook has been triggered. If the webhook is
15 triggered, it indicates that the event has occurred as expected. In this case, the
monitoring unit [214] generates a "successful trigger result." This means that the notification, informing about the occurrence of the event, is successfully sent by the transceiver unit [210] to the vendor device. However, if the monitoring unit [214] does not detect the activation of the webhook when the event occurs, it signifies
20 that the event has not been properly recognized or processed. In this scenario, the
monitoring unit [214] generates an "unsuccessful trigger result." This indicates that the notification about the event has not been sent by the transceiver unit [210] to the vendor device as expected.
25 [0058] Referring to FIG. 3, an exemplary method flow diagram [300] for
implementing configurable webhooks, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the
30 present disclosure. Also, as shown in FIG. 3, the method [300] starts at step [302].
21

[0059] At step 304, the method comprises facilitating, by an authorization unit
[202] at a subscription engine [201], logging in of a user upon receiving a set of
user details, wherein the set of user details are saved in a storage unit [212]. The
authorization unit [202] within the subscription engine [201] is specifically
5 designed to manage user access by facilitating the login process. When a user
attempts to log into the system, the authorization unit [202] receives a set of user details. This typically includes credentials such as a username and a password. The authorization unit [202] then compares the credentials against the user details stored in the storage unit [212]. If the credentials provided by the user match the details in
10 the storage unit, the authorization unit authenticates the user's identity. The
authentication process ensures that only legitimate users can access the system. Upon successful authentication, the authorization unit may also facilitate the creation of a session for the user. This session allows the user to interact with the system without needing to re-authenticate for each action or request within a session
15 duration. Also, the method further comprises storing, by the storage unit [212] at
the subscription engine [201], a detail of the configured one or more webhooks. wherein the one or more events are configured by manual inputs of the user, via the user interface [206]. The users interact with the system through the user interface to define or specify the events that should trigger the webhooks. These manual
20 inputs could include specifying event types, conditions, or criteria that will activate
the corresponding webhooks.
[0060] At step 306, the method comprises allowing, by a webhook configurator [204] at the subscription engine [201], a creation of one or more webhooks by the
25 user using a user interface [206]. The webhook configurator [204] ensures that after
the user successfully logs in, verifying their identity and access rights via the authorization unit [202], they can then proceed to define and set up webhooks according to their specific requirements. The user interface [206] provides a visual and interactive platform through which users can easily configure various aspects
30 of the webhooks, such as setting the endpoint URLs, defining event triggers, and
specifying other relevant parameters like retry intervals or security settings. The
22

webhook configurator [204] allows users to manage how and when data should be
communicated to external systems or applications, facilitating real-time data
exchange and operational efficiency. The webhook configurator [204 enables
dynamic and customizable integration between the subscription engine [201] and
5 external vendor systems or other third-party services. The disclosure encompasses
the webhook configurator [204] for enabling users to create and modify webhooks through a user interface. While creating the webhooks, the method comprising receiving, by the user via the user interface [206] at the subscription engine [201], a user input for configuring the one or more webhooks, wherein the configuration
10 comprises at least one of an endpoint address, an authorisation details, a retry
number, a retry interval parameter, a pause capability parameter, a resume capability parameter, an edit capability parameter, and a delete capability parameter. Also, the method further comprising displaying, by the user interface [206] at the subscription engine [201], a set of details related to the one or more
15 events, the set of details comprising one of the successful trigger result and the
unsuccessful trigger result, and a metadata related to the one or more events. Users can input configurations for one or more webhooks through the user interface [206], including details such as endpoint addresses, authorization credentials, retry settings, pause, and resume capabilities, as well as edit and delete options.
20 Additionally, the user interface [206] is equipped to display information from the
subscription engine [201], including details related to events such as successful or unsuccessful trigger results, along with metadata pertaining to these events. The metadata includes additional information or descriptors related to the events being monitored and managed by the subscription engine [201] such as timestamps
25 indicating when events occurred, identifiers for the events, descriptions or
categorizations of the events, and any other pertinent data that provides context or insights into the nature and characteristics of the events being tracked.
[0061] At step 308, the method comprises triggering, by an event manager unit
30 [208] at the subscription engine [201], a target webhook upon occurrence of one or
more events, wherein the target webhook is related to the one or more events. When
23

an event occurs that matches the criteria set for the target webhook, the event
manager unit [208] activates the target webhook. The method further comprising
receiving, by the event manager unit [208] at the subscription engine [201], a
manual user input for triggering the target webhook; and triggering, by the event
5 manager unit [208], the target webhook based on the manual user input. The manual
user input provided directly by a user rather than automatically generated. The event
manager unit is designed to respond to the occurrence of one or more events. When
these events happen, the event manager unit [208] is programmed to trigger a
specific webhook, referred to as the target webhook. This triggering action is
10 initiated by the event manager unit in response to the occurrence of the specified
events.
[0062] At step 310, the method comprises sending, by a transceiver unit [210] at the subscription engine [201] to a vendor device, a notification indicating the
15 occurrence of the event based on the triggering of the target webhook. The
notifications are sent when a particular event occurs, which is triggered by the activation of a target webhook. Essentially, when the event manager unit [208] detects the triggering of the specified webhook, it signals the transceiver unit [210] to send a notification to the vendor device, informing them of the event occurrence.
20 This setup allows for timely communication of important events within the system
to the external vendor, ensuring effective coordination and response.
[0063] The method further comprising monitoring, by a monitoring unit [214] at the subscription engine [201], the triggering of the target webhook upon the
25 occurrence of the one or more events; and generating, by the monitoring unit [214]
at the subscription engine [201], one of a successful trigger result and an unsuccessful trigger result, wherein the successful trigger result is generated in an event the notification indicating the occurrence of the event based on the triggering of the target webhook is sent by the transceiver unit [210] to the vendor device upon
30 the occurrence of the event, and the unsuccessful trigger result is generated in an
event the notification indicating the occurrence of the event based on the triggering
24

of the target webhook is not sent by the transceiver unit [210] to the vendor device
upon the occurrence of the event. The subscription engine [201] includes a
monitoring unit [214] which is responsible for observing the activation of a specific
webhook when certain events occur. When an event occurs, the monitoring unit
5 [214] checks if the corresponding webhook has been triggered. If the webhook is
triggered, it indicates that the event has occurred as expected. In this case, the monitoring unit [214] generates a "successful trigger result." This means that the notification, informing about the occurrence of the event, is successfully sent by the transceiver unit [210] to the vendor device. However, if the monitoring unit [214]
10 does not detect the activation of the webhook when the event occurs, it signifies
that the event has not been properly recognized or processed. In this scenario, the monitoring unit [214] generates an "unsuccessful trigger result." This indicates that the notification about the event has not been sent by the transceiver unit [210] to the vendor device as expected.
15
[0064] Thereafter, the method terminates at step [412].
[0065] Referring to FIG. 4, illustrates a flow diagram [400] for implementing
configurable webhooks in accordance with exemplary implementations of the
20 present disclosure. As shown in FIG. 4.
[0066] Step 402 - Configure Webhooks Based on the Events Required: The initial
step involves the user, typically an administrator from the vendor's side, using the
subscription engine's [201] user interface to set up webhooks. The configuration
25 process includes defining which events will trigger the webhooks, such as new
subscriptions, subscription updates, pauses, or cancellations.
[0067] Step 404 - Notification Through Webhook API: Once the webhooks are
configured, the subscription engine [201] monitors for these specified events. Upon
30 the occurrence of one or more of these events, the system automatically triggers the
configured webhooks. The event manager unit then sends notifications to the
25

predetermined vendor endpoints through the webhook API, ensuring that vendors are promptly informed about the subscription activities related to their content.
[0068] Step 406 - Plan Name is Received by the Vendor: Following the notification
5 sent by the webhook API, the vendor system receives the plan name or identifier,
which could include details of the event that has occurred. This allows the vendor to process the incoming data appropriately and take necessary actions, such as updating access rights for a user based on the new subscription status.
10 [0069] Referring to FIG. 5, illustrates an exemplary block diagram [500] of a user
equipment [502] for implementing configurable webhooks in accordance with exemplary implementations of the present disclosure. The block diagram [500] comprises a user equipment [502], a network [504], and a server [506]. In an embodiment, the user equipment [502] comprises the subscription engine.
15
[0070] As disclosed, the user equipment [502] comprises a subscription engine [201] with vendor systems via webhooks. The process starts within the subscription engine [201], which houses the operational logic and data concerning subscriptions. When a relevant event occurs, such as a new subscription or a change in an existing
20 one, the subscription engine [201] initiates a webhook.
[0071] The user equipment [502] comprising the subscription engine [201], the subscription engine [201] further comprising: an authorization unit [202] configured to facilitate logging in of a user upon receiving a set of user details,
25 wherein the set of user details are saved in a storage unit [212]; a webhook
configurator [204] connected at least to the authorization unit [202], the webhook configurator [204] configured to allow a creation of one or more webhooks by the user using a user interface [206]; an event manager unit [208] connected at least to the webhook configurator [204], the event manager unit configured to trigger a
30 target webhook upon occurrence of one or more events, wherein the target webhook
is related to the one or more events; and a transceiver unit [210] connected at least
26

to the event manager unit [208], the transceiver unit [210] configured to send to a vendor device, a notification indicating the occurrence of the event based on the triggering of the target webhook.
5 [0072] FIG. 6 illustrates an exemplary interface [600] of a platform for creating
webhooks by vendors in accordance with exemplary implementations of the present disclosure. The interface [600] is part of the administrative portal designed for managing webhooks within the subscription engine system. It allows vendors to set up new webhook endpoints by providing essential details such as the endpoint
10 name, URL, HTTP authentication username, and password. The user-friendly
layout facilitates easy configuration and management of webhooks, ensuring that vendors can seamlessly receive notifications about various subscription-related events, such as purchases, pauses, and terminations. The interface [600] facilitates in bridging the gap between the subscription engine and the vendor systems,
15 enabling automated, real-time communication, and ensuring synchronized
operations across different platforms. The interface [600] also includes options to view, pause, resume, and delete existing webhook configurations, providing comprehensive control and flexibility for the vendors.
20 [0073] FIG. 7 illustrates an exemplary interface [700] of a platform for modifying
the configuration of webhooks in accordance with exemplary implementations of the present disclosure. The interface [700] is part of the administrative portal and is designed to provide an overview and management of existing webhook endpoints. It displays a list of configured webhooks, each with its status (e.g.,
25 Active) and associated endpoint URL. The interface [700] includes options to add
new endpoints and to pause all existing endpoints with a simple button click. Additionally, each webhook entry includes a contextual menu (accessible via the three-dot icon) that offers further actions such as editing, pausing, resuming, or deleting the webhook. This centralized management view allows administrators to
30 efficiently oversee and modify webhook configurations, ensuring that the
subscription engine remains in sync with vendor systems.
27

[0074] FIG. 8 illustrates an exemplary interface [800] of a platform displaying
notifications for configured webhooks in accordance with exemplary
implementations of the present disclosure. The interface [800] is part of the
5 administrative portal that provides a comprehensive view of webhook activities. It
lists notifications triggered by various webhook endpoints, detailing their status, type, and relevant timestamps. The display includes columns for the identifier, type of event (e.g., ‘account_created_sample’), creation date, and the next retry attempt if the initial notification failed. The interface [800] allows filtering of notifications
10 based on endpoints and delivery status, offering insights into both delivered and
failed notifications. The filtering capability, combined with the detailed logs of each webhook event, enables administrators to monitor the performance and reliability of webhook integrations, ensuring timely and accurate notifications to vendors about subscription-related events. Additionally, a "Configure" button enables the
15 ability to adjust webhook settings directly from the interface [800], enhancing the
administrative control over webhook configurations and their operational behaviours.
[0075] FIG. 9 illustrates an exemplary interface [900] of a platform for retrying and
20 viewing details in case of webhook notification failure in accordance with
exemplary implementations of the present disclosure. The interface [900], part of
the administrative portal, provides detailed information about a specific webhook
event. It includes essential details such as the webhook ID, state (e.g., Delivered),
endpoint name and URL, type of event (e.g., reactivate-subscription’), account
25 information, creation date, and timestamps of the last and next retry attempts.
Additionally, the interface displays the number of tries and includes a JSON
payload that was sent during the webhook event, offering a comprehensive view of
the data transmitted. In case of failure, the interface [900] provides a "Resend"
button, enabling administrators to manually trigger a retry of the webhook
30 notification.
28

[0076] Further another aspect of the present disclosure may relate to a non-
transitory computer readable storage medium storing instructions for implementing
configurable webhooks, the instructions include executable code which, when
executed by a one or more units of a system, causes: an authorization unit to
5 facilitate logging in of a user upon receiving a set of user details, wherein the set of
user details are saved in a storage unit, the webhook configuration to allow a
creation of one or more webhooks by the user using a user interface; the event
manager unit to trigger a target webhook upon occurrence of one or more events,
wherein the target webhook is related to the one or more events; and a transceiver
10 unit to send to a vendor device, a notification indicating the occurrence of the event
based on the triggering of the target webhook.
[0077] As is evident from the above, the present disclosure provides a technically advanced solution for implementing configurable webhooks. Implementing the
15 features of the present disclosure, one can sync both independent system
(subscription engine and vendor system) so that end customer will get smooth service experience. Further, implementing the present solution, it is possible to configure the number of webhooks to which data of a single plan/service/offer can be sent. Also, the present solution also enables vendors to create/configure their
20 own endpoints where they require the plan data.
[0078] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a
25 particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units, as disclosed in the disclosure, should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended
30 functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
29

[0079] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
that many changes can be made to the implementations without departing from the
5 principles of the present disclosure. These and other changes in the implementations
of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
30

We Claim:
1. A method for implementing configurable webhooks, the method
comprising:
- facilitating, by an authorization unit [202] at a subscription engine [201], logging in of a user upon receiving a set of user details, wherein the set of user details are saved in a storage unit [212];
- allowing, by a webhook configurator [204] at the subscription engine [201], a creation of one or more webhooks by the user using a user interface [206];
- triggering, by an event manager unit [208] at the subscription engine [201], a target webhook upon occurrence of one or more events, wherein the target webhook is related to the one or more events; and
- sending, by a transceiver unit [210] at the subscription engine [201] to a vendor device, a notification indicating the occurrence of the event based on the triggering of the target webhook.
2. The method as claimed in claim 1, the method comprising:
- receiving, by the user via the user interface [206] at the subscription
engine [201], a user input for configuring the one or more webhooks,
wherein the configuration comprises at least one of an endpoint address,
an authorisation details, a retry number, a retry interval parameter, a
pause capability parameter, a resume capability parameter, an edit
capability parameter, and a delete capability parameter.
3. The method as claimed in claim 2, wherein the method further comprises:
- storing, by the storage unit [212] at the subscription engine [201], a
detail of the configured one or more webhooks.
4. The method as claimed in claim 1, wherein the one or more events are
configured by manual inputs of the user, via the user interface [206].

5. The method as claimed in claim 1, the method further comprising:
- monitoring, by a monitoring unit [214] at the subscription engine [201], the triggering of the target webhook upon the occurrence of the one or more events; and
- generating, by the monitoring unit [214] at the subscription engine [201], one of a successful trigger result and an unsuccessful trigger result, wherein the successful trigger result is generated in an event the notification indicating the occurrence of the event based on the triggering of the target webhook is sent by the transceiver unit [210] to the vendor device upon the occurrence of the event, and the unsuccessful trigger result is generated in an event the notification indicating the occurrence of the event based on the triggering of the target webhook is not sent by the transceiver unit [210] to the vendor device upon the occurrence of the event.
6. The method as claimed in claim 5, the method further comprising:
- receiving, by the event manager unit [208] at the subscription engine [201], a manual user input for triggering the target webhook; and
- triggering, by the event manager unit [208], the target webhook based on the manual user input.
7. The method as claimed in claim 1 and 5, the method further comprising:
- displaying, by the user interface [206] at the subscription engine [201],
a set of details related to the one or more events, the set of details
comprising one of the successful trigger result and the unsuccessful
trigger result, and a metadata related to the one or more events.
8. A system for implementing configurable webhooks, the system comprising
a subscription engine [201], the subscription engine [201] further
comprising:

- an authorization unit [202] configured to facilitate logging in of a user upon receiving a set of user details, wherein the set of user details are saved in a storage unit [212];
- a webhook configurator [204] connected at least to the authorization unit [202], the webhook configurator [204] configured to allow a creation of one or more webhooks by the user using a user interface [206];
- an event manager unit [208] connected at least to the webhook configurator [204], the event manager unit [208] configured to trigger a target webhook upon occurrence of one or more events, wherein the target webhook is related to the one or more events; and
- a transceiver unit [210] connected at least to the event manager unit [208], the transceiver unit [210] configured to send to a vendor device, a notification indicating the occurrence of the event based on the triggering of the target webhook.
9. The system as claimed in claim 8, wherein the user interface [206] is
configured to:
- receive at the subscription engine [201], a user input for configuring the
one or more webhooks, wherein the configuration comprises at least one
of an endpoint address, an authorisation details, a re-try number, a retry
interval parameter, a pause capability parameter, a resume capability
parameter, an edit capability parameter, and a delete capability
parameter.
10. The system as claimed in claim 9, wherein the storage unit [212] is further
configured to:
- store at the subscription engine [201], details of the configured one or
more webhooks.
11. The system as claimed in claim 8, wherein the one or more events are
configured by manual inputs of the user, via the user interface [206].

12. The system as claimed in claim 8, wherein the subscription engine [201]
further comprises a monitoring unit [214] configured to:
- monitor the triggering of the target webhook upon the occurrence of the one or more events; and
- generate one of a successful trigger result and an unsuccessful trigger result, wherein the successful trigger result is generated in an event the notification indicating the occurrence of the event based on the triggering of the target webhook is sent by the transceiver unit [210] to the vendor device upon the occurrence of the event, and the unsuccessful trigger result is generated in an event the notification indicating the occurrence of the event based on the triggering of the target webhook is not sent by the transceiver unit [210] to the vendor device upon the occurrence of the event.
13. The system as claimed in claim 12, wherein the event manager unit [208] is
further configured to:
- receive, at the subscription engine [201], a manual user input for triggering the target webhook; and
- trigger the target webhook based on the manual user input.
14. The system as claimed in claim 8 and 12, wherein the user interface [206]
is further configured to:
- display at the subscription engine [201], a set of details related to the
one or more events, the set of details comprising one of the successful
trigger result and the unsuccessful trigger result, and a metadata related
to the one or more events.
15. A user equipment [502] for implementing configurable webhooks, the user
equipment [502]comprising a subscription engine [201], the subscription
engine [201] further comprising:

- an authorization unit [202] configured to facilitate logging in of a user upon receiving a set of user details, wherein the set of user details are saved in a storage unit [212];
- a webhook configurator [204] connected at least to the authorization unit [202], the webhook configurator [204] configured to allow a creation of one or more webhooks by the user using a user interface [206];
- an event manager unit [208] connected at least to the webhook configurator [204], the event manager unit [208] configured to trigger a target webhook upon occurrence of one or more events, wherein the target webhook is related to the one or more events; and
- a transceiver unit [210] connected at least to the event manager unit [208], the transceiver unit [210] configured to send to a vendor device, a notification indicating the occurrence of the event based on the triggering of the target webhook.