Method And System For Wrong Recharge Reversal

Jio Platforms Limited
Awaiting Request for Examination App No 202321048583 Computer Science

Patent information

IP India · live record
Application number
202321048583
Filing date
19 July 2023
Status
Awaiting Request for Examination
Publication number
04/2025
Publication type
INA
Invention field
Computer Science

Abstract

The present disclosure relates to a method and a system for wrong recharge reversal. The method comprises; receiving, by a transceiver unit [102], a request related to a reversal of a wrong recharge plan; determining, by an analysis unit [104], a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a first data structure type stage, and a second data structure type stage; performing, by a subscription manager [106], one of a first procedure and a second procedure; and sending, by the transceiver unit [102] to a vendor server [108], a notification related to a change in user subscription plan to complete the wrong recharge reversal process. [FIG. 1]

Applicants

1
India
Jio Platforms Limited Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

Inventors

8
India
Sandeep NarulaOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Aayush BhatnagarOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Alpesh SonarOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Nisha BhanushaliOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Chandan KumarOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Md Ghajnafar ShahidOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Shaileshkumar Gunvantray JhaOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Kedar AnavkarOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

Claims

17
1 A method for a wrong recharge reversal, the method comprising: - receiving, by a transceiver unit [102] at a subscription engine module [101], a request related to a reversal of a wrong recharge plan made by a user ; - determining, by an analysis unit [104] at the subscription engine module [101], a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a first data structure type stage, and a second data structure type stage; - performing, by a subscription manager [106] at the subscription engine module [101], one of a first procedure and a second procedure based on the determination, wherein the first procedure is performed in an event the stage of the wrong recharge plan is determined as the first data structure type stage, and the second procedure is performed in an event the stage of the wrong recharge plan is determined as the second data structure type stage; and - sending, by the transceiver unit [102] at the subscription engine module [101] to a vendor server [108], a notification related to a change in user subscription plan to complete the wrong recharge reversal process.
2 The method as claimed in claim 1, wherein the request related to a reversal of a wrong recharge plan is generated using a graphical user interface and communicated to the subscription engine module [101] using a communication means.
3 The method as claimed in claim 1, wherein the first data structure type stage indicates a stage wherein the wrong recharge plan is in waiting stage for activation and the second data structure type stage indicates a stage wherein the wrong recharge plan is one of an active plan and a current plan.
4 The method as claimed in claim 1, wherein the first procedure relates to a queue system, and the first procedure comprises: - removing, by the subscription manager [106] at the subscription engine module [101], the wrong recharge plan from a queue for effecting the change in the user subscription plan; - generating, by the subscription manager [106] at the subscription engine module [101], a payment details record (PDR); and - processing, by the subscription manager [106] at the subscription engine module [101], a payment for the user based on the PDR.
5 The method as claimed in claim 1, wherein the second procedure relates to a stack system, and the second procedure comprises: - terminating, by the subscription manager [106] at the subscription engine module [101], a current user subscribed plan, based on one or more older recharge order details; - activating, by the subscription manager [106] at the subscription engine module [101], a new plan based on a history table; - generating, by the subscription manager [106] at the subscription engine module [101], a payment details record (PDR) and a subscription details record (SDR); and - processing, by the subscription manager [106] at the subscription engine module [101], a payment for the user based on the PDR.
6 The method as claimed in claim 5, wherein the method further comprises: - maintaining, by the subscription manager [106] at the subscription engine module [101] in a storage unit [110], the history table comprising a set of flags related to one or more user subscription plans.
7 The method as claimed in claim 5, wherein the new plan is a previous plan extracted from the history table.
8 The method as claimed in claim 1, wherein the determining, by the analysis unit [104] at the subscription engine module [101], the stage of the wrong recharge plan, is based on a recharge identity extracted from the request related to the reversal of the wrong recharge plan made by the user.
9 A system for a wrong recharge reversal, the system comprising a subscription engine module [101], the subscription engine module [101] further comprising: - a transceiver unit [102] configured to receive a request related to a reversal of a wrong recharge plan made by a user; - an analysis unit [104] connected at least to the transceiver unit [102], the analysis unit [104] configured to determine a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a first data structure type stage, and a second data structure type stage; and - a subscription manager [106] connected at least to the analysis unit [104], the subscription manager [106] configured to perform one of a first procedure and a second procedure based on the determination, wherein the first procedure is performed in an event the stage of the wrong recharge plan is determined as the first data structure type stage, and the second procedure is performed in an event the stage of the wrong recharge plan is determined as the second data structure type stage, wherein the transceiver unit [102] is further configured to send, to a vendor server [108], a notification related to a change in user subscription plan to complete the wrong recharge reversal process.
10 The system as claimed in claim 9, wherein the request related to a reversal of a wrong recharge plan is generated using a graphical user interface and communicated to the subscription engine module [101] using a communication means.
11 The system as claimed in claim 9, the first data structure type stage indicates a stage wherein the wrong recharge plan is in waiting stage for activation and the second data structure type stage indicates a stage wherein the wrong recharge plan is one of an active plan and a current plan.
12 The system as claimed in claim 9, wherein the first procedure relates to a queue system and the subscription manager [106], for performing the first procedure is configured to: - remove the wrong recharge plan from a queue for effecting the change in the user subscription plan; - generate a payment details record (PDR); and - process a payment for the user based on the PDR.
13 The system as claimed in claim 9, wherein the second procedure relates to a stack system and the subscription manager [106], for performing the second procedure is configured to: - terminate a current user subscribed plan, based on one or more older recharge order details; - activate a new plan based on a history table; - generate a payment details record (PDR) and a subscription details record (SDR); and - process a payment for the user based on the PDR.
14 The system as claimed in claim 13, wherein the subscription manager [106] is further configured to: - maintain, in a storage unit [110], the history table comprising a set of flags related to one or more user subscription plans.
15 The system as claimed in claim 13, wherein the new plan is a previous plan extracted from the history table.
16 The system as claimed in claim 9, wherein the analysis unit [104] is configured to determine the stage of the wrong recharge plan, based on a recharge identity extracted from the request related to the reversal of the wrong recharge plan made by the user.
17 A user device for a wrong recharge reversal, the user device comprising a subscription engine module [101], the subscription engine module [101] further comprising: - a transceiver unit [102] configured to receive a request related to a reversal of a wrong recharge plan made by a user; - an analysis unit [104] connected at least to the transceiver unit [102], the analysis unit [104] configured to determine a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a queue system stage, or a stack system stage; and - a subscription manager [106] connected at least to the analysis unit [104], the subscription manager [106] configured to perform one of a queue procedure and a stack procedure based on the determination, wherein the queue procedure is performed in an event the stage of the wrong recharge plan is determined as the queue system stage, and the stack procedure is performed in an event the stage of the wrong recharge plan is determined as the stack system stage, wherein the transceiver unit [102] is further configured to send, to a vendor server [108], a notification related to a change in user subscription plan to complete the wrong recharge reversal process.

Specification

Show full textCollapse

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 WRONG RECHARGE REVERSAL” 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 WRONG RECHARGE REVERSAL FIELD OF THE DISCLOSURE

[0001] The present disclosure relates generally to payment management systems. More particularly, the present disclosure relates to methods and system for wrong recharge reversal. 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] In the field of telecommunications industry, customer satisfaction is important for sustainable growth and success. One of the crucial aspects that influence the customer satisfaction is a process of recharging accounts to access one or more network services. However, despite the convenience and ubiquity of recharge options, instances of erroneous recharges pose significant challenges for both customers and network operators.

[0004] The instance of wrong recharges arises from a plurality of factors ranging from simple human errors to technical glitches in one or more transaction processing systems. For instance, the customer may inadvertently enter an incorrect mobile number, or select one or more inappropriate recharge plans, or may encounter system malfunctions during the recharge process. Such occurrences may lead to customers receiving benefits or monetary amounts they did not intend to purchase or, in worst-case scenarios, receiving no benefits at all despite completing the transaction.

[0005] Conventionally, the network operators have been ill-equipped to address wrong recharge scenarios effectively. Conventional implementations lack mechanisms for rectifying or reversing erroneous transactions. As a result, customers may experience dissatisfaction, and financial losses, tarnishing their perception of the network operator.

[0006] Thus, there exists an imperative need in the art for a method and a system for wrong recharge reversal, which the present disclosure aims to address. OBJECTS OF THE INVENTION

[0007] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0008] It is an object of the present disclosure to provide a system and a method for a wrong recharge reversal.

[0009] It is another object of the present disclosure to provide a solution that enables rectification and reversal of incorrect one or more recharge transactions.

[0010] It is yet another object of the present disclosure to provide a solution that enables efficient rectification and reversal of incorrect one or more recharge transactions.

[0011] It is yet another object of the present disclosure to provide a solution that enables simpler disposal of customer grievances.

[0012] It is yet another object of the present disclosure to provide a solution that ensures that customers are not unfairly charged or receive undesired recharge benefits. SUMMARY

[0013] This section is provided to introduce certain objects and aspects of the present invention 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.

[0014] An aspect of the present disclosure relates to a method for a wrong recharge reversal. The method comprising receiving, by a transceiver unit at a subscription engine module, a request related to a reversal of a wrong recharge plan made by a user. The method

further comprising determining, by an analysis unit at the subscription engine module, a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a first data structure type stage, and a second data structure type stage. The method thereafter comprising performing, by a subscription manager at the subscription engine module, one of a first procedure and a second procedure based on the determination, wherein the first procedure is performed in an event the stage of the wrong recharge plan is determined as the first data structure type stage, and the second procedure is performed in an event the stage of the wrong recharge plan is determined as the second data structure type stage. The method further comprising sending, by the transceiver unit at the subscription engine module to a vendor server, a notification related to a change in user subscription plan to complete the wrong recharge reversal process.

[0015] In an exemplary aspect of the present disclosure, the wrong recharge request is generated using a graphical user interface and communicated to the subscription engine module using a communication means.

[0016] In an exemplary aspect of the present disclosure, the first data structure type stage indicates a stage wherein the wrong recharge plan is in waiting stage for activation and the second data structure type stage indicates a stage wherein the wrong recharge plan is one of an active plan and a current plan.

[0017] In an exemplary aspect of the present disclosure, the first procedure relates to a queue system, and the first procedure comprises: removing, by the subscription manager at the subscription engine module, the wrong recharge plan from a queue for effecting the change in user subscription plan; generating, by the subscription manager at the subscription engine module, a payment details record (PDR); and processing, by the subscription manager at the subscription engine module, a payment for the user based on the PDR.

[0018] In an exemplary aspect of the present disclosure, second procedure relates to a stack system, and the second procedure comprises: terminating, by the subscription manager at the subscription engine module, a current user subscribed plan, based on one or more older recharge order details. The second procedure further comprising activating, by the subscription manager at the subscription engine module, a new plan based on a history

table. The second procedure further comprising generating, by the subscription manager at the subscription engine module, a payment details record (PDR) and a subscription details record (SDR). The second procedure further comprising processing, by the subscription manager at the subscription engine module, a payment for the user based on the PDR. 5

[0019] In an exemplary aspect of the present disclosure, the method further comprises maintaining, by the subscription manager at the subscription engine module in a storage unit, the history table comprising a set of flags related to one or more user subscription plans. 10

[0020] In an exemplary aspect of the present disclosure, the new plan is a previous plan extracted from the history table.

[0021] In an exemplary aspect of the present disclosure, the determining, by the 15 analysis unit at the subscription engine module, the stage of the wrong recharge plan, is based on a recharge identity extracted from the request related to the reversal of the wrong recharge plan made by the user.

[0022] Another aspect of the present invention relates to a system for a wrong recharge 20 reversal. The system comprises a subscription engine module. The subscription engine module further comprising a transceiver unit configured to receive a request related to a reversal of a wrong recharge plan made by a user. The subscription engine module further comprising an analysis unit connected at least to the transceiver unit, the analysis unit configured to determine a stage of the wrong recharge plan, wherein the stage of the wrong 25 recharge plan is one of a first data structure type stage, and a second data structure type stage. The subscription engine module further comprising a subscription manager connected at least to the analysis unit, the subscription manager configured to perform one of a first procedure and a second procedure based on the determination, wherein the first procedure is performed in an event the stage of the wrong recharge plan is determined as 30 the first data structure type stage, and the second procedure is performed in an event the stage of the wrong recharge plan is determined as the second data structure type stage, wherein the transceiver unit is further configured to send, to a vendor server, a notification related to a change in user subscription plan to complete the wrong recharge reversal process. 5

[0023] Another aspect of the present invention relates to a user device for a wrong recharge reversal, the user device comprising a subscription engine module. The subscription engine module further comprising a transceiver unit configured to receive a 5 request related to a reversal of a wrong recharge plan made by a user. The subscription engine module further comprising an analysis unit connected at least to the transceiver unit, the analysis unit configured to determine a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a queue system stage, or a stack system stage. The subscription engine module further comprising a subscription manager connected at 10 least to the analysis unit, the subscription manager configured to perform one of a queue procedure and a stack procedure based on the determination, wherein the queue procedure is performed in an event the stage of the wrong recharge plan is determined as the queue system stage, and the stack procedure is performed in an event the stage of the wrong recharge plan is determined as the stack system stage. The transceiver unit is further 15 configured to send, to a vendor server, a notification related to a change in user subscription plan to complete the wrong recharge reversal process.

[0024] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instruction for providing for a wrong recharge 20 reversal. The instructions include an executable code which, when executed by one or more units of the system, causes a transceiver unit of the system to receive a request related to a reversal of a wrong recharge plan made by a user. Further, the executable code when executed causes an analysis unit of the system to determine a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a first data structure type stage, 25 and a second data structure type stage. Further, the executable code when executed causes a subscription manager of the system to perform one of a first procedure and a second procedure based on the determination, wherein the first procedure is performed in an event the stage of the wrong recharge plan is determined as the first data structure type stage, and the second procedure is performed in an event the stage of the wrong recharge plan is 30 determined as the second data structure type stage. Further, the executable code when executed causes the transceiver unit [102] to send, to a vendor server a notification related to a change in user subscription plan to complete the wrong recharge reversal process. DESCRIPTION OF THE DRAWINGS 6

[0025] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different 5 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 according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled 10 in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0026] FIG.1 illustrates an exemplary block diagram of a system [100] for wrong recharge reversal, in accordance with exemplary embodiments of the present disclosure. 15

[0027] FIG.2 illustrates an exemplary method flow diagram [200] indicating the process for wrong recharge reversal when wrong recharge plan is in queue system, in accordance with exemplary embodiments of the present disclosure. 20 [0028] FIG. 3 illustrates an exemplary flow diagram for wrong recharge reversal, in accordance with exemplary embodiments of the present disclosure.

[0029] FIG. 4 illustrates another exemplary flow diagram [400] for wrong recharge reversal, in accordance with exemplary embodiments of the present disclosure. 25

[0030] Fig. 5 illustrates an exemplary representation of an exemplary queue associated with a queue system, in accordance with exemplary embodiments of the present disclosure.

[0031] Fig. 6 illustrates an exemplary representation of an exemplary stack associated 30 with a stack system, in accordance with exemplary embodiments of the present disclosure.

[0032] FIG. 7 illustrates an exemplary block diagram of a computing device [700] upon which an embodiment of the present disclosure may be implemented. 7

[0033] The foregoing shall be more apparent from the following more detailed description of the disclosure. DETAILED DESCRIPTION 5

[0034] In the following description, for the purposes of explanation, various 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 10 each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0035] The ensuing description provides exemplary embodiments only, and is not 15 intended to limit the scope, applicability, or configuration of the disclosure. Rather, 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. 20

[0036] 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 may be shown as components 25 in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0037] 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 diagram, or a block diagram. Although a flowchart may describe the operations as a sequential 30 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. 8

[0038] 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 necessarily to be construed as 5 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 similar to the term “comprising” as an open transition word— 10 without precluding any additional or other elements.

[0039] One or more modules, units, components (including but not limited to analysis unit and subscription manager) used herein may be software modules configured via hardware modules/processor, or hardware processors, the processors being a general- 15 purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. 20 [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. 25 [0041] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, 30 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, 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. 9

[0042] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” 5 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 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. 10 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 such unit(s) which are required to implement the features of the present disclosure. 15 [0043] 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 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- 20 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.

[0044] As discussed in the background section, that there are instances of erroneous recharges which usually arises from a plurality of factors ranging from simple human errors 25 to technical glitches in one or more transaction processing systems. For instance, the customers may input incorrect mobile numbers or select inappropriate recharge plans, while system glitches during the recharge process can further exacerbate these issues. Consequently, customers may inadvertently receive undesired benefits or face a complete lack of benefits despite completing the transaction. Conventionally, the network operators 30 fail to address wrong recharge scenarios effectively and conventional implementations lack mechanisms for rectifying or reversing erroneous transactions. As a result, customers may experience dissatisfaction, and financial losses, tarnishing their perception of the network operator. 10

[0045] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a solution for a wrong recharge reversal. The solution involves receiving of a request which is related to a reversal of a wrong recharge plan made by a user. Thereafter, a stage of the wrong recharge plan is 5 determined. Also, the stage of the wrong recharge plan is one of a first data structure type stage, and a second data structure type stage. Further, one of first procedure and a second procedure is performed based on the determination of stage. Also, the first procedure is performed in an event the stage of the wrong recharge plan is determined as the first data structure type stage, and the second procedure is performed in an event the stage of the 10 wrong recharge plan is determined as the second data structure type stage. Furthermore, a notification is transmitted related to the change in user subscription plan to complete the wrong recharge reversal process.

[0046] Referring to FIG. 1, an exemplary block diagram of a system [100] for wrong 15 recharge reversal is shown, in accordance with the exemplary embodiments of the present invention. The system [100] comprises at least a subscription engine module [101] and the subscription engine module [101] further comprises at least one transceiver unit [102], at least one analysis unit [104], at least one subscription manager [106] and at least one storage unit [110]. Also, all of the components/ units of the system [100] are assumed to be 20 connected to each other unless otherwise indicated below. Also, in FIG. 1 only a few units are shown, however, the system [100] may comprise multiple such units or the system

[100] may comprise any such numbers of said units, as required to implement the features of the present disclosure. For ease of reference, FIG. 1 depicts units/components of the system [100] by way of representation of blocks and FIG. 1 do not represent the internal 25 circuitry or connections of each component/unit of the system [100]. It will be appreciated by those skilled in the art that disclosure of such drawings/block diagrams includes disclosure of electrical components and connections between said electronic components, and electronic components or circuitry commonly used to implement such components. 30 [0047] The system [100] is configured for wrong recharge reversal, with the help of the interconnection between the components/units of the system [100].

[0048] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented 11

interchangeably. While specific embodiments may disclose a 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. 5 Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

[0049] In order to reverse wrong recharge, the transceiver unit [102] configured to 10 receive a request related to a reversal of a wrong recharge plan made by a user. The user may be a customer, an authorized retailer [404].

[0050] The present disclosure encompasses that the wrong recharge request may be a request generated using a graphical user interface of a user equipment such as a Point of 15 Sale (POS) device and communicated to the subscription engine module [101] using a communication means. The user may a retailer accessing said user equipment for generating the request.

[0051] As used herein, the “subscription engine module [101]” may refer to a server 20 that manages the entire lifecycle of subscriptions for the one or more customers. Further, the subscription engine module [101] may communicate with one or more content platforms to provision and enable consumption of content and enables the one or more customers to set up recurring events and manage their subscriptions. The subscription engine module [101] may serve as a central hub for subscription management, 25 communicating with the one or more customers through various communication channels such as web applications, mobile applications, integration Application Programming Interfaces (APIs), a webhooks. Furthermore, the subscription engine module [101] may utilise one or more protocols for communication as a Hypertext Transfer Protocol (HTTP), a web services (WS), a Representational State of Resource (REST), Events protocol over 30 TCP (Transmission Control Protocol) connector.

[0052] For instance, a user erroneously recharges the subscription with a wrong data plan and instead of purchasing a 5GB data plan, the user by mistake selects a 1GB plan while using a mobile operator recharge application on a mobile phone. Upon realizing the 12

error, the user navigates to the mobile operator recharge application and submits a wrong recharge reversal request. The same request is communicated to the subscription engine module [101] and further transmitted to the transceiver unit [102]. The request (i.e., wrong recharge reversal request) may include but not limited to a complaint data that is provided 5 by the user, a time stamp data related to the wrong recharge, a data about the wrong recharge such as a detail of a desired plan, a detail of the received wrong rechange, and alike.

[0053] Thereafter, the analysis unit [104] which connected at least to the transceiver 10 unit [102], is configured to determine a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a first data structure type stage, and a second data structure type stage.

[0054] The present disclosure encompasses that the first data structure type stage refers 15 to a stage where the recharge plan is in waiting stage for activation and the second data structure type stage refers to a stage where the recharge plan is an active plan or a current plan.

[0055] The present disclosure encompasses that the analysis unit [104] is configured to 20 determine the stage of the wrong recharge plan, based on a recharge identity extracted from the request related to the reversal of the wrong recharge plan made by the user.

[0056] The present disclosure encompasses that the recharge identity may refer to a data which describes a recharge of a subscription such as talk time recharge done by the 25 user. The recharge identity may include but is not limited to an identification number, a recharge name, a recharge value, a recharge time period, a recharge time stamp.

[0057] Further the subscription manager [106] which is connected at least to the analysis unit [104] is configured to perform one of a first procedure and a second procedure 30 based on the determination. The first procedure is performed in an event the stage of the wrong recharge plan is determined as the first data structure type stage. The second procedure is performed in an event the stage of the wrong recharge plan is determined as the second data structure type stage. 13

[0058] The present disclosure encompasses that the first procedure relates to a queue system. Also, the subscription manager [106], for performing the first procedure, relating to the queue system, is configured to remove the wrong recharge plan from a queue for effecting a change in user subscription plan. The subscription manager [106] is further 5 configured to generate a payment details record (PDR). The subscription manager [106] is further configured to process a payment for the user based on the PDR. The subscription manager [106] may be a processor which is configured to manage plurality of subscriptions associated with a plurality of users. Furthermore, the subscription manager [106] may be refer to a server configured to manage the entire subscription lifecycle of the subscriptions 10 associated with the plurality of users and may store and manages subscription data, including user profiles, recharge plans, and payment methods, processes recharge requests and activates/deactivates subscriptions accordingly, handles billing and payment processing, including invoicing, payment gateway integration, and revenue recognition, sends notifications and alerts to users regarding their subscription status, recharge 15 reminders, and low balance alerts and perform any such like function that may be appreciated by a person killed in the art as necessary to implement the present disclosure.

[0059] The queue system refers to a system that involves organization of a plurality of steps that are carried out may be in a first-in-first out (FIFO) manner, wherein the request 20 related to a reversal of a wrong recharge plan are processed in an order they are received. Further, the queue system may operate in any other such like manner that may be appreciated by a person skilled in the art to implement the solution of the present disclosure.

[0060] For instance, in case, the analysis unit [104] determines that the wrong recharge 25 plan is in the first data structure type stage that indicates a stage wherein the wrong recharge plan is in waiting stage for activation, then the subscription manager [106] removes the wrong recharge plan from a queue for effecting a change in user subscription plan and generates a PDR to process a payment for the user. The queue herein refers to a data structure that is utilized for managing and organizing a list of rechange plans or subscription 30 plans in a sequential manner. For example, as depicted in FIG. 5, in an exemplary queue associated with the queue system there may a plurality of plans such R1, R2, R3, R4, wherein a new plan R5 may be added after R4 and the plan R1 is processed first, as the queue is operated in the first-in-first out (FIFO) manner. 14

[0061] The Payment Details Record (PDR) is a digital document or record that contains information about a payment transaction. The PDR includes one or more details such as the amount paid, the date and time of the transaction, the payment method used (e.g., credit card, bank transfer), and any other relevant payment-related information. Further, in 5 accordance with present disclosure, the PDR may be utilized for a refund of an amount associated with the wrong recharge plan.

[0062] The present disclosure encompasses that the second procedure relates to a stack system. Also, the subscription manager [106], for performing the second procedure relating 10 to the stack system, is configured to terminate a current user subscribed plan, based on one or more older recharge order details. The one or more older recharger order details may refer to one or more historic recharge order details. The one or more historic recharge order details may include but not limited to a past recharge plan name (such as A1, B2, C4), a past recharge plan value (50 Rupees, 150 Rupees, 250 Rupees), a past recharge plan 15 timestamp (31 March, 01:12 P.M.). The subscription manager [106] is further configured to activate a new plan the based on a history table. The new plan is a previous plan extracted from the history table. The subscription manager [106] is further configured to generate a payment details record (PDR) and a subscription details record (SDR). The subscription manager [106] is further configured to process a payment for the user based on the PDR. 20

[0063] The stack system refers to a system for managing the one or more requests related to a reversal of a wrong recharge plan may be in a last-in-first-out (LIFO) manner, wherein the requests may be processed in last-in-first-out (LIFO) manner. For example, as depicted in FIG. 6, an exemplary stack associated with the stack system may handle add a 25 new request L5 in a list of requests (L1, L2, L3, L4) after L4 and process the request L5, as the stack system works according to the LIFO manner. Further, the stack system may operate in any other manner which may be obvious to a person skilled in the art to implement the solution of the present disclosure. 30 [0064] For instance, in case, the analysis unit [104] determines that the wrong recharge plan is in the second data structure type stage that indicates a stage wherein the wrong recharge plan is an active plan or a current plan. The subscription manager [106] terminates the current recharge plan based on one or more older recharge order details. Further the subscription manager [106] activate a new recharge plan based on a history table which 15

include information about one or more available subscription plans and one or more past preferences of the user. Thereafter, the subscription manager [106] generates two records i.e., PDR and SDR. The PDR includes an information about the payment transaction associated with upgrading the plan, one or more details such as the amount paid for the 5 plan, the payment method used, and the transaction date and time. The SDR data include updated recharge plan details such as plan type, duration and other details. Upon generation of the records, the subscription manager [106] process the payment for the user based on the PDR. 10 [0065] The present disclosure encompasses that the subscription manager [106] is further configured to maintain, in the storage unit [110], the history table comprising a set of flags related to one or more user subscription plans. The set of flags refers to one or more indicators that are stored within the history table which is maintained by the subscription manager [106]. The set of flags represent one or more specific conditions or statuses related 15 to the recharge plans.

[0066] For example, a flag indicates whether a user has opted for auto-renewal of their subscription, whether a plan includes access to premium features, or whether a subscription is currently active or inactive. The subscription manager [106] efficiently tracks and 20 manage various aspects of user subscription plans by maintaining the set of flags within the history table. The history table may refer to a database which stores the set of flags related to one or more user subscription plans in an organized manner.

[0067] Further, the transceiver unit [102] is further configured to send to a vendor 25 server [108], a notification related to the change in user subscription plan to complete the wrong recharge reversal process.

[0068] The vendor server [108] refers to a server operated by a third-party vendor or service provider that is responsible for managing one or more aspects of the user 30 subscription plans (i.e., recharge plans) or handling one or more transactions related to the wrong recharge reversal process.

[0069] Referring to FIG. 2 an exemplary method flow diagram [200] of method for wrong recharge reversal, in accordance with exemplary embodiments of the present 16

invention is shown. In an implementation the method [200] is performed by the system [100]. As shown in FIG. 2, the method [200] starts at step [202].

[0070] At step [204], the method [200] as disclosed by the present disclosure comprises 5 receiving, by a transceiver unit [102] at a subscription engine module [101], a request related to a reversal of a wrong recharge plan made by a user.

[0071] The present disclosure encompasses that the wrong recharge request is generated using a graphical user interface and communicated to the subscription engine 10 module [101] using a communication means.

[0072] For instance, a user erroneously recharges the subscription with a wrong data plan and instead of purchasing a 5GB data plan, the user by mistake selects a 1GB plan while using a mobile operator recharge application on a mobile phone. Upon realizing the 15 error, the user navigates to the mobile operator recharge application and submits a wrong recharge reversal request. The same request is communicated to the subscription engine module [101] and further transmitted to the transceiver unit [102].

[0073] Next, at step [206], the method [200] as disclosed by the present disclosure 20 comprises determining, by an analysis unit [104] at the subscription engine module [101], a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a first data structure type stage, and a second data structure type stage.

[0074] The present disclosure encompasses that the first data structure type stage refers 25 to a stage where the recharge plan is in waiting stage for activation and the second data structure type stage refers to a stage where the recharge plan is an active plan or a current plan.

[0075] The present disclosure encompasses that the determining, by the analysis unit 30 [104] at the subscription engine module [101], the stage of the wrong recharge plan, is based on a recharge identity extracted from the request related to the reversal of the wrong recharge plan made by the user. 17

[0076] Next, at step [208], the method [200] as disclosed by the present disclosure comprises performing, by a subscription manager [106] at the subscription engine module

[101], one of a first procedure and a second procedure based on the determination. The first procedure is performed in an event the stage of the wrong recharge plan is determined as 5 the first data structure type stage, and the second procedure is performed in an event the stage of the wrong recharge plan is determined as the second data structure type stage.

[0077] The present disclosure encompasses that the first procedure relates to a queue system. Also, the first procedure, relating to the queue system, comprises removing, by the 10 subscription manager [106] at the subscription engine module [101], the wrong recharge plan from a queue for effecting a change in user subscription plan. The first procedure further comprises generating, by the subscription manager [106] at the subscription engine module [101], a payment details record (PDR). The first procedure further comprises processing, by the subscription manager [106] at the subscription engine module [101], a 15 payment for the user based on the PDR.

[0078] For instance, in case, the analysis unit [104] determines that the wrong recharge plan is in the first data structure type stage that indicates a stage wherein the wrong recharge plan is in waiting stage for activation, then the subscription manager [106] removes the 20 wrong recharge plan from a queue for effecting a change in user subscription plan and generates a PDR to process a payment for the user. The Payment Details Record (PDR) is a digital document or record that contains information about a payment transaction. The PDR includes one or more details such as the amount paid, the date and time of the transaction, the payment method used (e.g., credit card, bank transfer), and any other 25 relevant payment-related information.

[0079] The present disclosure encompasses that the second procedure relates to a stack system. Also, the second procedure, relating to the stack system, comprises terminating, by the subscription manager [106] at the subscription engine module [101], a current user 30 subscribed plan, based on one or more older recharge order details. The second procedure further comprises activating, by the subscription manager [106] at the subscription engine module [101], a new plan based on a history table. The new plan is a previous plan extracted from the history table. The second procedure further comprises generating, by the subscription manager [106] at the subscription engine module [101], a payment details 18

record (PDR) and a subscription details record (SDR). The second procedure further comprises processing, by the subscription manager [106] at the subscription engine module [101], a payment for the user based on the PDR. 5 [0080] For instance, in case, the analysis unit [104] determines that the wrong recharge plan is in the second data structure type stage that indicates a stage wherein the wrong recharge plan is an active plan or a current plan. The subscription manager [106] terminates the current recharge plan based on one or more older recharge order details. Further the subscription manager [106] activate a new recharge plan based on a history table which 10 include information about one or more available subscription plans and one or more past preferences of the user. Thereafter, the subscription manager [106] generates two records i.e., PDR and SDR. The PDR includes an information about the payment transaction associated with upgrading the plan, one or more details such as the amount paid for the plan, the payment method used, and the transaction date and time. The SDR data include 15 updated recharge plan details such as plan type, duration and other details. Upon generation of the records, the subscription manager [106] process the payment for the user based on the PDR.

[0081] The present disclosure encompasses that the method further comprises 20 maintaining, by the subscription manager [106] at the subscription engine module [101] in a storage unit [110], the history table comprising a set of flags related to one or more user subscription plans.

[0082] The set of flags refers to one or more indicators that are stored within the history 25 table which is maintained by the subscription manager [106]. The set of flags represent one or more specific conditions or statuses related to the recharge plans.

[0083] For example, a flag indicates whether a user has opted for auto-renewal of their subscription, whether a plan includes access to premium features, or whether a subscription 30 is currently active or inactive. The subscription manager [106] efficiently tracks and manage various aspects of user subscription plans by maintaining the set of flags within the history table. 19

[0084] Thereafter, at step [210], the method [200] as disclosed by the present disclosure comprises sending, by the transceiver unit [102] at the subscription engine module [101] to a vendor server [108], a notification related to the change in user subscription plan to complete the wrong recharge reversal process. 5

[0085] The vendor server [108] refers to a server operated by a third-party vendor or service provider that is responsible for managing one or more aspects of the user subscription plans (i.e., recharge plans) or handling one or more transactions related to the wrong recharge reversal process. 10

[0086] The notification refers to a message or signal transmitted from the transceiver unit [102] at the subscription engine module [101] to the vendor server [108] to inform about the change in the user's subscription plan (i.e., recharge plan). 15 [0087] Thereafter, the method [200] terminates at step [212].

[0088] FIG. 3 illustrates an exemplary flow diagram [300] for wrong recharge reversal, in accordance with exemplary embodiments of the present disclosure. In an implementation the method [300] is performed by the system [100]. As shown in FIG. 3, the method [300] 20 starts at step S1, when a user [302] identifies a wrong recharge made by the user [302], via a user equipment such as mobile phone, laptop, electronic tablet. The user [302] may be a customer or a retailer. In case the user is the customer, then the user informs about the wrong recharge to an authorized retailer [304]. Thereafter the authorized retailed initiates a wrong recharge reversal process, wherein a request for wrong recharge reversal is 25 generated on a user interface of a subscription engine module [101].

[0089] At step S2, the request is forwarded to a server (i.e., vendor server [108]) of a service provider and thereafter the request is processed by conducting a plurality of steps disclosed in the method [200]. For example, determination of a stage of the wrong recharge 30 plan, performing one of a first procedure and a second procedure based on the determination.

[0090] Thereafter, if the wrong recharge plan is reversed successfully, then at step S3, a notification to the user [302] or the authorized retailer [304] is provided or else in case of 20

failure of the reversal of wrong recharge plan, the user [302] or the authorized retailer [304] is notified about such as failure.

[0091] Thereafter, upon step S3, the method [300] terminates at step S4. 5

[0092] FIG. 4 illustrates another exemplary flow diagram [400] for wrong recharge reversal, in accordance with exemplary embodiments of the present disclosure. In an implementation the method [400] is performed by the system [100]. As shown in FIG. 4, the method [400] starts at step S1, a recharge is done by an authorized retailer [304] upon 10 an instruction received from a user [302]. Further, the user [302] may visit the authorized retailer [304] which may have a point of sale (POS) machine [406] for activating a new recharge plan such as recharge B and the user [302] have a current recharge plan for such as recharge A. 15 [0093] Thereafter, the user [302] identifies that a wrong recharge (recharge C) has been done by the authorized retailer [304] and the user [302] informs the authorized retailer [304] about the same (i.e., wrong recharge i.e., the rechange C). However, as per the instructions provided by the user [302], a desired recharge was rechange B rupees. Thereafter, at step S2, the authorized retailer [304] initiates a wrong recharge reversal 20 process via generating a request related to wrong recharge reversal on a user interface that is associated with a subscription engine module [101].

[0094] Thereafter, the request is forwarded to a server (i.e., vendor server [108]). The server operates via two systems i.e., a queue system and a stack system. Further, all 25 recharge plans at a waiting stage are stored and maintained in the queue system, whereas all recharge plans at an active stage are stored and maintained in the stack system.

[0095] The server operates a plurality of steps disclosed/described in method [200] For example, determination of a stage of the wrong recharge plan, performing one of a first 30 procedure and a second procedure based on the determination.

[0096] Thereafter, at stage S3, a response to the request is provided by the server. The response may be a successful wrong recharge reversal or an unsuccessful wrong recharge reversal. 21

[0097] Further, upon receiving the response from the server, at step S4, the authorized retailer [304] notifies the user [302] about the response received from the server. 5 [0098] Thereafter the method [400] terminates upon completion of step S4.

[0099] FIG. 7 illustrates an exemplary block diagram of a computing device [700] upon which an embodiment of the present disclosure may be implemented. In an implementation, the computing device [700] implements the method [200] for a wrong recharge reversal 10 using the system [100]. In another implementation, the computing device [700] itself implements the method [200] for the wrong recharge reversal using one or more units configured within the computing device [700], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure. 15 [0100] The computing device [700] may include a bus [702] or other communication mechanism for communicating information, and a hardware processor [704] coupled with bus [702] for processing information. The hardware processor [704] may be, for example, a general-purpose microprocessor. The computing device [700] may also include a main memory [706], such as a random-access memory (RAM), or other dynamic storage device, 20 coupled to the bus [702] for storing information and instructions to be executed by the processor [704]. The main memory [706] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [704]. Such instructions, when stored in non-transitory storage media accessible to the processor [704], render the computing device [700] into a special-purpose machine 25 that is customized to perform the operations specified in the instructions. The computing device [700] further includes a read only memory (ROM) [708] or other static storage device coupled to the bus [702] for storing static information and instructions for the processor [704]. 30 [0101] A storage device [710], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [702] for storing information and instructions. The computing device [700] may be coupled via the bus [702] to a display [712], such as a cathode ray tube (CRT), for displaying information to a computer user. An input device [714], including alphanumeric and other keys, may be coupled to the bus [702] for 22

communicating information and command selections to the processor [704]. Another type of user input device may be a cursor controller [716], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [704], and for controlling cursor movement on the display [712]. This input 5 device [714] 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.

[0102] The computing device [700] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or 10 program logic which in combination with the computing device [700] causes or programs the computing device [700] to be a special-purpose machine. According to one embodiment, the techniques herein are performed by the computing device [700] in response to the processor [704] executing one or more sequences of one or more instructions contained in the main memory [706]. Such instructions may be read into the 15 main memory [706] from another storage medium, such as the storage device [710]. Execution of the sequences of instructions contained in the main memory [706] causes the processor [704] to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions. 20 [0103] The computing device [700] also may include a communication interface [718] coupled to the bus [702]. The communication interface [718] provides a two-way data communication coupling to a network link [720] that is connected to a local network [722]. Further, the local network [722] is connected with a host [724]. For example, the communication interface [718] may be an integrated services digital network (ISDN) card, 25 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 [718] may be a 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 [718] sends and receives electrical, 30 electromagnetic or optical signals that carry digital data streams representing various types of information.

[0104] The computing device [700] can send messages and receive data, including program code, through the network(s), the network link [720] and the communication 23

interface 1018. In the Internet example, a server [1030] might transmit a requested code for an application program through the Internet [728], the ISP [726], the local network [722] and the communication interface [1018]. The received code may be executed by the processor [704] as it is received, and/or stored in the storage device [710], or other non- 5 volatile storage for later execution.

[0105] Furthermore, the method and system for wrong recharge reversal may be implemented in different sectors such as the telecommunication sector. For instance, the user is using an application for a streaming service and accidentally subscribe to a wrong 10 recharge plan, so with the help of the method and system disclosed in the present disclosure, the user is able to reverse the wrong recharge plan. This is achieved by submitting a request through an interface of the application to reverse the wrong recharge plan. Thereafter, the recharge identity is extracted from the request related to the reversal of the wrong recharge plan made by the user to determine the stage of the wrong recharge plan. The stage includes 15 the first data structure type stage (such as plan is still pending activation) and the second data structure type stage (such as plan is currently active). Thereafter, based on the stage, the first procedure or the second procedure is followed to reverse the wrong recharge and once the reversal is completed, the notification to the vendor server [108] is transmitted to inform it about the change in the plan. 20

[0106] The present disclosure also relates to a user device for a wrong recharge reversal, the user device comprising a subscription engine module [101]. The subscription engine module [101] further comprising a transceiver unit [102] configured to receive a request related to a reversal of a wrong recharge plan made by a user. The subscription 25 engine module [101] further comprising an analysis unit [104] connected at least to the transceiver unit [102], the analysis unit [104] configured to determine a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a queue system stage, or a stack system stage. The subscription engine module [101] further comprising a subscription manager [106] connected at least to the analysis unit [104], the subscription 30 manager [106] configured to perform one of a queue procedure and a stack procedure based on the determination, wherein the queue procedure is performed in an event the stage of the wrong recharge plan is determined as the queue system stage, and the stack procedure is performed in an event the stage of the wrong recharge plan is determined as the stack system stage. The transceiver unit [102] is further configured to send to a vendor server 24

[108], a notification related to a change in user subscription plan to complete the wrong recharge reversal process.

[0107] Also, the present disclosure may relate to a non-transitory computer readable 5 storage medium storing instruction for providing for a wrong recharge reversal. The instructions include an executable code which, when executed by one or more units of the system, causes a transceiver unit [102] of the system [100] to receive a request related to a reversal of a wrong recharge plan made by a user. Further, the executable code when executed causes an analysis unit [104] of the system [100] to determine a stage of the wrong 10 recharge plan, wherein the stage of the wrong recharge plan is one of a first data structure type stage, and a second data structure type stage. Further, the executable code when executed causes a subscription manager [106] of the system [100] to perform one of a first procedure and a second procedure based on the determination, wherein the first procedure is performed in an event the stage of the wrong recharge plan is determined as the first data 15 structure type stage, and the second procedure is performed in an event the stage of the wrong recharge plan is determined as the second data structure type stage. Further, the executable code when executed causes the transceiver unit [102] to send, to a vendor server [108] a notification related to a change in user subscription plan to complete the wrong recharge reversal process. 20

[0108] As is evident from the above, the present disclosure provides a technically advanced solution for wrong recharge reversal. The system and method as disclosed by the present disclosure offers several advantages for both customers and telecom companies. Some of the advantages include error correction, customer satisfaction, brand reputation, 25 process efficiency, financial accuracy, simpler grievance handling, enhanced customer communication and fair billing.

[0109] Moreover, the primary advantage is the ability to rectify and reverse incorrect recharge transactions. Customers may report and get a resolution for wrongly recharged 30 amounts or benefits, ensuring accurate billing and preventing financial losses. Further, wrong recharge reversal demonstrates the telecom company's commitment to customer service and satisfaction. Resolving customer complaints promptly and effectively helps build trust and loyalty, enhancing the overall customer experience. Implementing a reliable wrong recharge reversal mechanism enhances the brand reputation of telecom companies. 25

It showcases their commitment to resolving customer issues and maintaining fairness in transactions, which can lead to positive word-of-mouth and a good industry image. The solution of a standardized wrong recharge reversal process streamlines the resolution procedure. It provides clear guidelines and workflow for customer support representatives 5 and other departments involved, reducing confusion and improving efficiency. By reversing wrong recharges, telecom companies maintain accurate financial records. This ensures that customers are billed correctly and prevents revenue leakage caused by erroneous recharge transactions. In many jurisdictions, telecom companies are required to have processes in place for handling customer complaints and resolving billing 10 discrepancies. The solution of wrong recharge reversal helps telecom companies avoid potential legal issues. During the wrong recharge reversal process, telecom companies have the opportunity to communicate with customers, address their concerns, and provide updates on the status of the reversal. This improves communication channels and fosters transparency between the company and its customers. The solution also ensures that 15 customers are not unfairly charged or receive undesired recharge benefits.

[0110] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the 20 present disclosure. These and other changes in the embodiments 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. 26

We Claim: 1. A method for a wrong recharge reversal, the method comprising: - receiving, by a transceiver unit [102] at a subscription engine module [101], a request related to a reversal of a wrong recharge plan made by a user ; - determining, by an analysis unit [104] at the subscription engine module [101], a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a first data structure type stage, and a second data structure type stage; - performing, by a subscription manager [106] at the subscription engine module [101], one of a first procedure and a second procedure based on the determination, wherein the first procedure is performed in an event the stage of the wrong recharge plan is determined as the first data structure type stage, and the second procedure is performed in an event the stage of the wrong recharge plan is determined as the second data structure type stage; and - sending, by the transceiver unit [102] at the subscription engine module [101] to a vendor server [108], a notification related to a change in user subscription plan to complete the wrong recharge reversal process.

2. The method as claimed in claim 1, wherein the request related to a reversal of a wrong recharge plan is generated using a graphical user interface and communicated to the subscription engine module [101] using a communication means. 3. The method as claimed in claim 1, wherein the first data structure type stage indicates a stage wherein the wrong recharge plan is in waiting stage for activation and the second data structure type stage indicates a stage wherein the wrong recharge plan is one of an active plan and a current plan. 4. The method as claimed in claim 1, wherein the first procedure relates to a queue system, and the first procedure comprises:

- removing, by the subscription manager [106] at the subscription engine module [101], the wrong recharge plan from a queue for effecting the change in the user subscription plan; - generating, by the subscription manager [106] at the subscription engine module [101], a payment details record (PDR); and

- processing, by the subscription manager [106] at the subscription engine module [101], a payment for the user based on the PDR. 5. The method as claimed in claim 1, wherein the second procedure relates to a stack system, and the second procedure comprises: - terminating, by the subscription manager [106] at the subscription engine module [101], a current user subscribed plan, based on one or more older recharge order details; - activating, by the subscription manager [106] at the subscription engine module [101], a new plan based on a history table; - generating, by the subscription manager [106] at the subscription engine module [101], a payment details record (PDR) and a subscription details record (SDR); and - processing, by the subscription manager [106] at the subscription engine module [101], a payment for the user based on the PDR. 6. The method as claimed in claim 5, wherein the method further comprises: - maintaining, by the subscription manager [106] at the subscription engine module [101] in a storage unit [110], the history table comprising a set of flags related to one or more user subscription plans. 7. The method as claimed in claim 5, wherein the new plan is a previous plan extracted from the history table. 8. The method as claimed in claim 1, wherein the determining, by the analysis unit [104] at the subscription engine module [101], the stage of the wrong recharge plan, is based on a recharge identity extracted from the request related to the reversal of the wrong recharge plan made by the user. 9. A system for a wrong recharge reversal, the system comprising a subscription engine module [101], the subscription engine module [101] further comprising: - a transceiver unit [102] configured to receive a request related to a reversal of a wrong recharge plan made by a user;

- an analysis unit [104] connected at least to the transceiver unit [102], the analysis unit [104] configured to determine a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a first data structure type stage, and a second data structure type stage; and - a subscription manager [106] connected at least to the analysis unit [104], the subscription manager [106] configured to perform one of a first procedure and a second procedure based on the determination, wherein the first procedure is performed in an event the stage of the wrong recharge plan is determined as the first data structure type stage, and the second procedure is performed in an event the stage of the wrong recharge plan is determined as the second data structure type stage, wherein the transceiver unit [102] is further configured to send, to a vendor server [108], a notification related to a change in user subscription plan to complete the wrong recharge reversal process. 10. The system as claimed in claim 9, wherein the request related to a reversal of a wrong recharge plan is generated using a graphical user interface and communicated to the subscription engine module [101] using a communication means. 11. The system as claimed in claim 9, the first data structure type stage indicates a stage wherein the wrong recharge plan is in waiting stage for activation and the second data structure type stage indicates a stage wherein the wrong recharge plan is one of an active plan and a current plan. 12. The system as claimed in claim 9, wherein the first procedure relates to a queue system and the subscription manager [106], for performing the first procedure is configured to:

- remove the wrong recharge plan from a queue for effecting the change in the user subscription plan; - generate a payment details record (PDR); and - process a payment for the user based on the PDR.

13. The system as claimed in claim 9, wherein the second procedure relates to a stack system and the subscription manager [106], for performing the second procedure is configured to: - terminate a current user subscribed plan, based on one or more older recharge order details; - activate a new plan based on a history table; - generate a payment details record (PDR) and a subscription details record (SDR); and - process a payment for the user based on the PDR. 14. The system as claimed in claim 13, wherein the subscription manager [106] is further configured to: - maintain, in a storage unit [110], the history table comprising a set of flags related to one or more user subscription plans. 15. The system as claimed in claim 13, wherein the new plan is a previous plan extracted from the history table. 16. The system as claimed in claim 9, wherein the analysis unit [104] is configured to determine the stage of the wrong recharge plan, based on a recharge identity extracted from the request related to the reversal of the wrong recharge plan made by the user. 17. A user device for a wrong recharge reversal, the user device comprising a subscription engine module [101], the subscription engine module [101] further comprising:

- a transceiver unit [102] configured to receive a request related to a reversal of a wrong recharge plan made by a user; - an analysis unit [104] connected at least to the transceiver unit [102], the analysis unit [104] configured to determine a stage of the wrong recharge plan, wherein the stage of the wrong recharge plan is one of a queue system stage, or a stack system stage; and - a subscription manager [106] connected at least to the analysis unit [104], the subscription manager [106] configured to perform one of a queue procedure

and a stack procedure based on the determination, wherein the queue procedure is performed in an event the stage of the wrong recharge plan is determined as the queue system stage, and the stack procedure is performed in an event the stage of the wrong recharge plan is determined as the stack system stage, wherein the transceiver unit [102] is further configured to send, to a vendor server [108], a notification related to a change in user subscription plan to complete the wrong recharge reversal process.

Documents

Sign in to open
Application documents
1 202321048583-STATEMENT OF UNDERTAKING (FORM 3) [19-07-2023(online)].pdf 19 Jul 2023
2 202321048583-PROVISIONAL SPECIFICATION [19-07-2023(online)].pdf 19 Jul 2023
3 202321048583-FORM 1 [19-07-2023(online)].pdf 19 Jul 2023
4 202321048583-FIGURE OF ABSTRACT [19-07-2023(online)].pdf 19 Jul 2023
5 202321048583-DRAWINGS [19-07-2023(online)].pdf 19 Jul 2023
6 202321048583-FORM-26 [20-09-2023(online)].pdf 20 Sep 2023
7 202321048583-Proof of Right [11-10-2023(online)].pdf 11 Oct 2023
8 202321048583-ORIGINAL UR 6(1A) FORM 1 & 26)-261023.pdf 04 Nov 2023
9 202321048583-FORM-5 [17-07-2024(online)].pdf 17 Jul 2024
10 202321048583-ENDORSEMENT BY INVENTORS [17-07-2024(online)].pdf 17 Jul 2024
11 202321048583-DRAWING [17-07-2024(online)].pdf 17 Jul 2024
12 202321048583-CORRESPONDENCE-OTHERS [17-07-2024(online)].pdf 17 Jul 2024
13 202321048583-COMPLETE SPECIFICATION [17-07-2024(online)].pdf 17 Jul 2024
14 Abstract-1.jpg 05 Sep 2024