Description:TECHNICAL FIELD
[0001] The present disclosure, in general, relates to approaches for purchasing one or more products, and in particular, relates to approaches for purchasing one or more products based on a transaction amount aggregated over a time period.

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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Various methodologies and ways may exist for a user who may want to purchase certain goods or assets. In cases where the user may be unable to pay the transactional amount in exchange of the goods to be purchased, various financial organizations and companies may provide the user with credit facility. Further, in certain cases, where the user may be unable to pay the entire transactional amount at one time, such financial organizations may also provide the user with the option to pay a periodic amount for a certain period of time.
[0004] However, all such facilities and options to provide the user with the option of credit may require the financial organizations to verify the user. The financial organizations, providing the credit to the user, may verify the user based on certain parameters before providing the credit. Such parameters may include, for example, a historical record of the transactional behaviour of the user.
[0005] Therefore, in cases where the user may not be verified, the user may fail to secure the credit facility from such financial organizations. As a result, the user may be unable to purchase the goods or assets which the user intended to purchase. Further, it may also be the case that the interest rate at which the credit may be provided to the user may be high. The user may not wish to avail the credit at such high rates of interest.
[0006] Therefore, there exists a need for approaches where a user may be able to purchase one or more products efficiently and conveniently.

SUMMARY
[0007] 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.
[0008] Aspects of the present disclosure relate to approaches for purchasing one or more products. In particular, the present disclosure provides approaches for purchasing one or more products based on a transaction amount aggregated over a time period.
[0009] An embodiment of the present disclosure pertains to a system for purchasing one or more products. The system may include one or more processors operatively coupled with a save now buy later (SNBL) server. The one or more processors may be coupled with a memory, and the memory may store instructions. The instructions when executed by the one or more processors may cause the system to receive information from a user associated with a computing device. The computing device may be operably coupled to the SNBL server via a network. The information may include at least a time period, an aggregated transaction amount to be paid in one or more transactions by the user over the time period, and one or more product categories. Further, the aggregated transaction amount may be directed towards a purchase of the one or more products from the one or more product categories. Thereafter, a transfer of the one or more transactions in each sub period of the time period may be enabled from a user transaction account to an SNBL account associated with the user. Upon completion of payment of the aggregated transaction amount by the user over the time period, a rebate amount may be generated over the aggregated transaction amount. Further, the purchase of the one or more products from the one or more product categories may be enabled using the aggregated transaction amount.
[0010] In one aspect, the one or more processors may be configured to enable the user to modify the information for the purchase of the one or more products from the one or more product categories.
[0011] In another aspect, the one or more processors may be configured to record the one or more transactions in said each sub period and estimate a balance amount to be paid in the remaining time period based on the aggregated transaction amount.
[0012] In yet another aspect, the one or more processors may be configured to estimate an end date associated with the purchase of the one or more products using the aggregated transaction amount.
[0013] In yet another aspect, the one or more processors may be configured to deactivate the transfer of the one or more transactions at a particular time instance in the time period and redirect a net amount of the one or more transactions from the SNBL account associated with the user towards the user transaction account.
[0014] In yet another aspect, the one or more processors may be configured to generate the net amount by deducting a fee amount from the one or more transactions transferred from the user transaction account to the SNBL account until the particular time instance.
[0015] In yet another aspect, the one or more processors may be configured to record at least one of a status and a user identification (ID) associated with the transfer of the one or more transactions in said each sub period.
[0016] In yet another aspect, the information received from the user may include at least details of the user transaction account. The user transaction account may be associated with at least one of a credit card, a debit card, or a unified payments interface (UPI).
[0017] Another embodiment of the present disclosure pertains to a method for purchasing one or more products. The method may include receiving, by one or more processors, information from a user associated with a computing device. The information may include at least a time period, an aggregated transaction amount to be paid in one or more transactions by the user over the time period, and one or more product categories. The aggregated transaction amount may be directed towards a purchase of the one or more products from the one or more product categories. The method may further include enabling, by the one or more processors, a transfer of the one or more transactions in each sub period of the time period from a user transaction account to an SNBL account associated with the user. Thereafter, the method may include, upon completion of payment of the aggregated transaction amount by the user over the time period, generating, by the one or more processors, a rebate amount over the aggregated transaction amount and enabling the purchase of the one or more products from the one or more product categories using the aggregated transaction amount.
[0018] In one aspect, the method may include enabling, by the one or more processors, the user to modify the information for the purchase of the one or more products.
[0019] In another aspect, the method may include recording, by the one or more processors, the one or more transactions in said each sub period and estimating, by the one or more processors, a balance amount to be paid in the remaining time period based on the aggregated transaction amount.
[0020] In yet another aspect, the method may include deactivating, by the one or more processors, the transfer of the one or more transactions at a particular time instance in the time period and redirecting, by the one or more processors, a net amount of the one or more transactions from the SNBL account associated with the user towards the user transaction account.
[0021] In yet another aspect, the method may include generating, by the one or more processors, the net amount by deducting a fee amount from the one or more transactions transferred from the user transaction account to the SNBL account until the particular time instance.
[0022] Yet another embodiment of the present disclosure pertains to a user equipment (UE) for purchasing one or more products. The UE may include one or more processors communicatively coupled to a system. The one or more processors may be coupled with a memory, and the memory may store instructions. The instructions when executed by the one or more processors may cause the UE to transmit information from a user associated with the UE to the system. The UE may be operably coupled to a save now buy later (SNBL) server via a network. The information may include at least a time period, an aggregated transaction amount to be paid in one or more transactions by the user over the time period, and one or more product categories. Further, the aggregated transaction amount may be directed towards a purchase of the one or more products from the one or more product categories. Thereafter, a transfer of the one or more transactions in each sub period of the time period may be enabled from a user transaction account to an SNBL account associated with the user. Upon completion of payment of the aggregated transaction amount by the user over the time period, a rebate amount may be generated over the aggregated transaction amount. Further, the purchase of the one or more products from the one or more product categories may be enabled using the aggregated transaction amount.
[0023] Various objects, features, aspects and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components.

BRIEF DESCRIPTION OF THE DRAWINGS
[0024] The accompanying drawings are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0025] FIG. 1 illustrates an exemplary network environment with a system for purchasing one or more products based on a transaction amount aggregated over a time period, in accordance with an embodiment of the present disclosure;
[0026] FIG. 2 illustrates an exemplary block diagram representing functional units of the system, in accordance with an embodiment of the present disclosure;
[0027] FIG. 3A depicts an exemplary screenshot of a user equipment (UE) showing the purchase of one or more products, as per an implementation of the present subject matter;
[0028] FIG. 3B depicts an exemplary screenshot of a UE showing transfer of one or more transaction amount, as per an implementation of the present subject matter;
[0029] FIG. 3C depicts an exemplary screenshot of a UE showing management of one or more transactions, as per an implementation of the present subject matter;
[0030] FIG. 3D depicts an exemplary screenshot of a UE illustrating completion of payment of an aggregated transaction amount, as per an implementation of the present subject matter;
[0031] FIG. 4 illustrates an exemplary flow diagram representing steps of a method for purchasing one or more products based on a transaction amount aggregated over a time period, in accordance with an embodiment of the present disclosure; and
[0032] FIG. 5 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be utilized, in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION
[0033] 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 can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
[0034] The ensuing description provides exemplary embodiments only, and is not 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 invention as set forth.
[0035] 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, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0036] 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 process, many of the operations can 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. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0037] 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 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—without precluding any additional or other elements.
[0038] As used herein, “'connect”, “configure”, “couple” and its cognate terms, such as “connects”, “connected”, “configured”, and “coupled” may include a physical connection (such as a wired/wireless connection), a logical connection (such as through logical gates of semiconducting device), other suitable connections, or a combination of such connections, as may be obvious to a skilled person.
[0039] As used herein, “send”, “transfer”, “transmit”, and their cognate terms like “sending”, “sent”, “transferring”, “transmitting”, “transferred”, “transmitted”, etc. include sending or transporting data or information from one unit or component to another unit or component, wherein the content may or may not be modified before or after sending, transferring, transmitting.
[0040] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0041] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
[0042] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such details as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosures as defined by the appended claims.
[0043] The approaches of the present subject matter provide an efficient, robust, and convenient way for purchasing one or more products based on a transaction amount aggregated over a time period. As would be appreciated, the user, over a customized period of time, may save portions of a transactional amount, thereby enabling the user to aggregate the amount and fulfil their requirements. The period over which the amount may be saved, may be selected by the user based on specific saving capabilities of the user. Further, the approaches of the present subject matter may also provide the user to save their money, thereby helping the user in availing financial freedom.
[0044] The manner in which the proposed system is used for purchasing one or more products based on a transaction amount aggregated over a time period is further explained in detail with respect to FIGs. 1-5. It is to be noted that drawings of the present subject matter shown here are for illustrative purposes only and are not to be construed as limiting the scope of the subject matter claimed. Further, FIGs. 1-3 have been explained together, and same reference numerals have been used to refer to identical components and entities.
[0045] FIG. 1 illustrates an exemplary network environment 100 including a system 102. The system 102 may be used for purchasing one or more products based on a transaction amount aggregated over a time period, in accordance with an embodiment of the present disclosure. In an embodiment, the system 102 may be implemented as any hardware-based, software-based, or network-based computing device known to a person skilled in the art. Such explanation has not been provided here for the sake of brevity. It may be further noted that the system 102 may be implemented as any system capable of receiving an input, processing it, and generating an output.
[0046] Continuing further, as depicted in FIG. 1, the network environment 100 may include a save now buy later (SNBL) server 104 in communication with the system 102 over a network 106. In an embodiment, the SNBL server 104 may be implemented using any or a combination of hardware-based, software-based, network-based computing device, or a cloud-based computing device.
[0047] In an embodiment, the network 106 may be a wireless network, a wired network or a combination thereof that can be implemented as one of the different types of networks, such as Intranet, Local Area Network (LAN), Wide Area Network (WAN), Internet, and the like. Further, the network 106 may either be a dedicated network or a shared network. The shared network may represent an association of different types of networks that can use variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like.
[0048] Referring to FIG. 1, the SNBL server 104 may include at least one of a plurality of processor(s) 108, referred to as processor 108. Although, as depicted in FIG. 1, the processor 108 may be present within the SNBL server 104 and may be in communication with the system 102 over the network 106. However, the same should not be construed to limit the scope of the present subject matter in any manner. The processor 108 may be present within the system 102 as well, as would be explained with reference to FIG. 2. Such an example would also lie within the scope of the present subject matter. The manner in which the processor 108 would be implemented, would be explained in further details in conjunction with FIG. 2.
[0049] As further depicted in FIG. 1, the system 102 may be in communication with a plurality of user equipment (UEs) (110-1, 110-2…110-N) (collectively referred to as the UE 110 and individually referred to as the UE 110). Such UE 110 may be implemented as any computing device, and may interchangeably be referred to as computing devices 110. Examples of such UE 110 may include, but are not limited to, a Personal Computer (PC), a portable PC, a mobile phone, a handheld computer, a laptop, a wearable device, or any other end-user computing device. Each UE 110 may be associated with, and operated by a respective user 112. It may be noted that aforementioned examples of the UE 110 are only illustrative, and should not be construed to limit the scope of the present subject matter in any manner. Any other type of end-user device used by the user 112 would also lie within the scope of the UE 110 and the present subject matter.
[0050] A person of ordinary skill in the art will appreciate that the network environment 100 may be modular and flexible to accommodate any kind of changes in the network environment 100.
[0051] The working of the system 102 is explained in conjunction with FIG. 2. FIG. 2 illustrates a block diagram representing functional units of the proposed system for purchasing one or more products based on a transaction amount aggregated over a time period, such as system 102.
[0052] As depicted in FIG. 2, the exemplary functional units of the system 102 may include one or more processor(s) 108. The one or more processor(s) 108 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that manipulate data based on operational instructions. Among other capabilities, the one or more processor(s) 108 may be configured to fetch and execute computer-readable instructions stored in a memory 202 of the system 102. The memory 202 may store one or more computer-readable instructions or routines, which may be fetched and executed to create or share the data units over a network service. The memory 202 may include any non-transitory storage device including, for example, volatile memory such as Random-access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-only Memory (EPROM), flash memory, and the like.
[0053] In an embodiment, the system 102 may also include an interface(s) 204. The interface(s) 204 may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. The interface(s) 204 may facilitate communication of the system 102 with various devices coupled to the system 102. The interface(s) 204 may also provide a communication pathway for one or more components of the system 102. Examples of such components include, but are not limited to, processing engine(s) 206 and database 208.
[0054] In an embodiment, the processing engine(s) 206 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the system 102. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) 206 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) 206 may include a processing resource (for example, one or more processors, such as processor 108), to execute such instructions.
[0055] In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) 206. In such examples, the system 102 may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 102 and the processing resource. In other examples, the processing engine(s) 206 may be implemented by electronic circuitry. In an embodiment, the database 208 may include data that is either stored or generated as a result of functionalities implemented by the processing engine(s) 206. In an embodiment, the processor 108 may be implemented within the processing engine(s) 206.
[0056] Continuing with the approaches of the working of the present subject matter, it may be noted that although the foregoing description would be explained with respect to a single UE 110 being operated by a single user 112, it may be noted that the same is done only for the sake of clarity. The proposed approach for purchasing one or more products based on a transaction amount aggregated over a time period may be implemented to any number of users 112 operating any number of UEs 110. All such examples would be covered within the scope of the present subject matter. Further, it may be the case that a single user 112 may be operating multiple accounts, where each account may be aggregating a transactional amount over different time periods. All such examples would lie within the scope of the present subject matter.
[0057] Continuing further, in one example, the user 112 may be operating a UE 110. The user 112 may initiate the proposed approach of the present subject matter. In one example, the UE 110 may include a display device (not shown in FIGs. 1-2) coupled to the UE 110. In another example, in the cases of the UE 110 being a portable computing device such as a portable computer and a mobile phone, the display device may be present within the UE 110 itself. However, it may be noted that all such examples are only illustrative.
[0058] In yet another example, the UE 110 may include a user interface for enabling the user 112 operating the UE 110 to initiate the program. In yet another example, the user 112 may have a set of credentials to login into the system 102. It may be again noted that all such examples are only illustrative, and the proposed subject matter may be implemented in any manner known to a person skilled in the art.
[0059] Continuing further, upon initialization, the UE 110 may transmit information from the user 112 associated with the UE 110 to the system 102. The one or more processors 108, herein referred as the processor 108, may receive the information from the user 112. The information may include, but not be limited to, a time period, an aggregated transaction amount to be paid in one or more transactions by the user 112 over the time period, and one or more product categories. Examples of time period may include, but are not limited to, 3 months, 6 months, and 1 year. However, it may be noted that such examples are only illustrative, and the information may include any other field as well, as entered by the user 112. All such examples would be covered within the scope of the present subject matter.
[0060] Continuing further, as would be understood and described previously, the aggregated transaction amount may be directed towards a purchase of the one or more products from the one or more product categories. One such example has been depicted in FIG. 3A. FIG. 3A depicts an exemplary screenshot of the UE 110 implementing the purchase of one or more products, as per an implementation of the present subject matter. As depicted in FIG. 3A, the user 112 may provide a ‘product name,’ ‘product category,’ ‘transaction amount,’ ‘time period,’ and ‘frequency.’ However, it may be again noted that all such fields are only exemplary, and other fields would also be covered within the scope of the present subject matter.
[0061] In one example, the user 112 may be provided with a set of pre-defined information fields. Such pre-defined information fields may be configured and provided by an administrator to the system 102. In another example, the processor 108 may be configured to enable the user 112 to modify the information for the purchase of the one or more products from the one or more product categories. The user 112 may modify the information based on their preferences and convenience. All such examples would be covered without deviating from the scope of the present subject matter.
[0062] Continuing further, thereafter, the processor 108 may enable a transfer of the one or more transactions in each sub period of the time period from a user transaction account to an SNBL account associated with the user 112. In one example, the processor 108 may be configured to record at least one of a status and a user identification (ID) associated with the transfer of the one or more transactions in said each sub period. As would be appreciated, such recording may enable the user 112 to track the transactions at a later point in time.
[0063] In another example, the user transaction account may be associated with at least one of a credit card, a debit card, or a unified payments interface (UPI). This has been depicted in FIG. 3B. FIG. 3B depicts an exemplary screenshot of the UE 110 depicting transfer of the one or more transaction amount, as per an implementation of the present subject matter. However, it may be again noted that all such examples are only illustrative, and the user transaction account may include any other examples as well without deviating from the scope of the present subject matter.
[0064] In an embodiment, the SNBL account may be implemented as an account at the system 102 or the SNBL server 104, in a manner known to a person skilled in the art. In another example, the SNBL account may be managed by a third party organization in association with the system 102. All such examples and other variations would be covered within the scope of the present subject matter.
[0065] Continuing further, while the user 112 is performing the transfer of the one or more transactions in each sub period of the time period, the processor 108 may manage the manner in which the transactions are being handled in multiple ways. For example, in one example, the processor 108 may be configured to record the one or more transactions in said each sub period and estimate a balance amount to be paid in the remaining time period based on the aggregated transaction amount. In another example, the processor 108 may be configured to estimate an end date associated with the purchase of the one or more products using the aggregated transaction amount. This has been depicted in FIG. 3C.
[0066] FIG. 3C depicts an exemplary screenshot of the UE 110 illustrating management of the one or more transactions, as per an implementation of the present subject matter.
[0067] In yet another example, as also depicted in FIG. 3C, it may be the case that the user 112 may wish to discontinue the transactions and may cancel the intent to buy the desired product. The user 112 may wish to get back the amount that the user 112 has deposited over the period of time. Therefore, in such cases, the processor 108 may be configured to deactivate the transfer of the one or more transactions at a particular time instance in the time period and redirect a net amount of the one or more transactions from the SNBL account associated with the user 112 towards the user transaction amount. The net amount, in another example, may be generated by deducting a fee amount from the one or more transactions transferred from the user transaction account to the SNBL account until the particular time instance.
[0068] Continuing further, upon completion of payment of the aggregated transaction amount by the user 112 over the time period, the processor 108 may be configured to generate a rebate amount over the aggregated transaction amount. Such aggregated transaction amount may then enable the purchase of the one or more products from the one or more product categories using the aggregated transaction amount. This has been depicted in FIG. 3D. FIG. 3D depicts an exemplary screenshot of a UE 110 illustrating completion of payment of the aggregated transaction amount, as per an implementation of the present subject matter.
[0069] In yet another example, the user 112, to buy the one or more products, may opt for a part payment in the form of the amount from the SNBL account. The remaining payment may be made by the user 112 at the time of purchasing the desired product.
[0070] FIG. 4 illustrates an exemplary flow diagram representing steps of a method 400 for purchasing one or more products based on a transaction amount aggregated over a time period, in accordance with an embodiment of the present disclosure. The method 400 may be implemented within the system 102, as described in conjunction with FIGs. 1-2.
[0071] At block 402, the method 400 may include receiving information from a user 112 associated with a computing device 110. The information may include at least a time period, an aggregated transaction amount to be paid in one or more transactions by the user over the time period, and one or more product categories. The aggregated transaction amount may be directed towards a purchase of the one or more products from the one or more product categories.
[0072] At block 404, the method 400 may include enabling a transfer of the one or more transactions in each sub period of the time period from a user transaction account to an SNBL account associated with the user 112.
[0073] At block 406, the method 400 may include, upon completion of payment of the aggregated transaction amount by the user 112 over the time period, generating a rebate amount over the aggregated transaction amount and enabling the purchase of the one or more products from the one or more product categories using the aggregated transaction amount.
[0074] It may be appreciated that the steps shown in FIG. 4 are merely illustrative. Other suitable steps may be used for the same, if desired. Moreover, the steps of the method 400 may be performed in any order and may include additional steps.
[0075] FIG. 5 illustrates an exemplary computer system 500 in which or with which embodiments of the present disclosure may be utilized. The computing system 500 may be implemented as or within the system 102 described in conjunction with FIGs. 1-2. As depicted in FIG. 5, the computer system 500 may include an external storage device 510, a bus 520, a main memory 530, a read-only memory 540, a mass storage device 550, communication port(s) 560, and a processor 570. A person skilled in the art will appreciate that the computer system 500 may include more than one processor 570 and communication ports 560. The processor 570 may include various modules associated with embodiments of the present disclosure. The communication port(s) 560 may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) 560 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 500 connects.
[0076] In an embodiment, the main memory 530 may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 540 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor 570. The mass storage device 550 may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces).
[0077] In an embodiment, the bus 520 communicatively couples the processor 570 with the other memory, storage, and communication blocks. The bus 520 may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 570 to the computer system 500.
[0078] In another embodiment, operator and administrative interfaces, e.g. a display, keyboard, and a cursor control device, may also be coupled to the bus 520 to support direct operator interaction with the computer system 500. Other operator and administrative interfaces may be provided through network connections connected through the communication port(s) 560. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 500 limit the scope of the present disclosure.
[0079] Thus, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating systems and methods embodying this invention. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Similarly, any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the entity implementing this invention. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named.
[0080] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.
, Claims:1. A system (102) for purchasing one or more products, the system (102) comprising:
one or more processors (108) operatively coupled with a save now buy later (SNBL) server (104), wherein the one or more processors (108) are coupled with a memory, and wherein said memory stores instructions which when executed by the one or more processors (108) causes the system (102) to:
receive information from a user (112) associated with a computing device (110), wherein the information comprises at least a time period, an aggregated transaction amount to be paid in one or more transactions by the user (112) over the time period, and one or more product categories, wherein the aggregated transaction amount is directed towards a purchase of the one or more products from the one or more product categories, and wherein the computing device (110) is operably coupled to the SNBL server (104) via a network (106);
enable a transfer of the one or more transactions in each sub period of the time period from a user transaction account to an SNBL account associated with the user (112);
upon completion of payment of the aggregated transaction amount by the user (112) over the time period, generate a rebate amount over the aggregated transaction amount and enable the purchase of the one or more products from the one or more product categories using the aggregated transaction amount.
2. The system (102) as claimed in claim 1, wherein the one or more processors (108) are configured to enable the user (112) to modify the information for the purchase of the one or more products from the one or more product categories.

3. The system (102) as claimed in claim 1, wherein the one or more processors (108) are configured to record the one or more transactions in said each sub period and estimate a balance amount to be paid in the remaining time period based on the aggregated transaction amount.
4. The system (102) as claimed in claim 1, wherein the one or more processors (108) are configured to estimate an end date associated with the purchase of the one or more products using the aggregated transaction amount.
5. The system (102) as claimed in claim 1, wherein the one or more processors (108) are configured to deactivate the transfer of the one or more transactions at a particular time instance in the time period and redirect a net amount of the one or more transactions from the SNBL account associated with the user (112) towards the user transaction account.
6. The system (102) as claimed in claim 5, wherein the one or more processors (108) are configured to generate the net amount by deducting a fee amount from the one or more transactions transferred from the user transaction account to the SNBL account until the particular time instance.
7. The system (102) as claimed in claim 1, wherein the one or more processors (108) are configured to record at least one of a status and a user identification (ID) associated with the transfer of the one or more transactions in said each sub period.
8. The system (102) as claimed in claim 1, wherein the information received from the user (112) comprises at least details of the user transaction account, and wherein the user transaction account is associated with at least one of a credit card, a debit card, or a unified payments interface (UPI).
9. A method (400) for purchasing one or more products, the method (400) comprising:
receiving (402), by one or more processors (108), information from a user (112) associated with a computing device (110), wherein the information comprises at least a time period, an aggregated transaction amount to be paid in one or more transactions by the user (112) over the time period, and one or more product categories, wherein the aggregated transaction amount is directed towards a purchase of the one or more products from the one or more product categories, and wherein the computing device (110) is operably coupled to a save now buy later (SNBL) server (104) via a network (106);
enabling (404), by the one or more processors (108), a transfer of the one or more transactions in each sub period of the time period from a user transaction account to an SNBL account associated with the user (112);
upon completion of payment of the aggregated transaction amount by the user (112) over the time period, generating (406), by the one or more processors (108), a rebate amount over the aggregated transaction amount and enabling the purchase of the one or more products from the one or more product categories using the aggregated transaction amount.
10. The method (400) as claimed in claim 9, comprising enabling, by the one or more processors (108), the user (112) to modify the information for the purchase of the one or more products.
11. The method (400) as claimed in claim 9, comprising recording, by the one or more processors (108), the one or more transactions in said each sub period and estimating, by the one or more processors (108), a balance amount to be paid in the remaining time period based on the aggregated transaction amount.
12. The method (400) as claimed in claim 9, comprising deactivating, by the one or more processors (108), the transfer of the one or more transactions at a particular time instance in the time period and redirecting, by the one or more processors (108), a net amount of the one or more transactions from the SNBL account associated with the user (112) towards the user transaction account.
13. The method (400) as claimed in claim 12, comprising generating, by the one or more processors (108), the net amount by deducting a fee amount from the one or more transactions transferred from the user transaction account to the SNBL account until the particular time instance.

14. A user equipment (UE) (110) for purchasing one or more products, the UE (110) comprising:
one or more processors communicatively coupled to a system (102), the one or more processors being coupled with a memory, wherein said memory stores instructions which when executed by the one or more processors causes the UE (110) to:
transmit information from a user (112) associated with the UE (110) to the system (102), wherein the information comprises at least a time period, an aggregated transaction amount to be paid in one or more transactions by the user (112) over the time period, and one or more product categories, wherein the aggregated transaction amount is directed towards a purchase of the one or more products from the one or more product categories, and wherein the UE (110) is operably coupled to a save now buy later (SNBL) server (104) via a network (106);
enable a transfer of the one or more transactions in each sub period of the time period from a user transaction account to an SNBL account associated with the user (112);
upon completion of payment of the aggregated transaction amount over the time period, enable the purchase of the one or more products from the one or more product categories using a rebate amount and the aggregated transaction amount, wherein the rebate amount is provided over the aggregated transaction amount upon the completion of the payment.