DESC:The following specification particularly describes and ascertains the nature of this invention and the manner in which it is to be performed:-

FIELD OF INVENTION
[0001] The present disclosure relates to electronic devices, and more particularly to method and electronic device for displaying transactions received from multiple point of sale (POS) devices corresponding to plurality of modes of payment available at the multiple POS devices. The present application is based on, and claims priority from an Indian Application Number 201921049230 filed on 29.11.2019 the disclosure of 5 which is hereby incorporated by reference herein.
BACKGROUND
[0002] In general, merchant outlets may lag in adopting technological advancements due to various factors such as affordability of technology, complexity of technology, time required for adaption of the technology, low engagement with customer base, etc. With advancement in technology various new modes of payment have emerged which makes adaption of digital payments a cumbersome task for the merchant outlets. In an example, if a merchant outlet comprises 3 branches then the merchant outlet will have to deal with multiple payment modes, multiple reports of transactions, various payment applications, etc which make acceptance of the digital payment a cumbersome task. For example, in case a merchant wants to access transactions performed at the 3 branches of the merchant outlet based on a first mode of payment then the merchant will have to separately access the transactions performed using the first mode of the payment at a first branch of the merchant outlet, then access the transactions performed using the first mode of the payment at a second branch of the merchant outlet, and so on. When there are a large number of branches for the merchant outlet, the repetitive process to access the transactions performed using the multiple modes of payment at each of the branches becomes very cumbersome and time consuming. Also, there is no means by which a comprehensive view of the transaction performed at the 3 branches of the merchant outlet may be provided based on the multiple modes of payment at the merchant outlet. As a result, the merchant may not use the transactions related data based on the modes of payment for providing customer benefits, for marketing, etc.
[0003] Further, in case the merchant outlet want to run a loyalty program or provide offers/rewards to customers based on the modes of payment accepted at the merchant outlet then the small merchant outlets will have to individually sort data related to modes of payment associated with each branch of the merchant outlet. This makes the task cumbersome which in turn impacts the small merchant outlet’s sales and leads to loosing loyal customer base. Further, some existing systems provide standalone features for deferring a transaction to a later point of time but requires the merchant outlets to install applications on point of sale (POS) terminals and are not necessarily linked to the modes of payments. Existing technological advancements necessitate replacement of existing POS terminals with more expensive variants and/ or incur significant change to infrastructure of the merchant outlets.
[0004] Thus, it is desired to address the above mentioned disadvantages or other shortcomings or at least provide a useful alternative.
OBJECT OF INVENTION
[0005] The principal object of the embodiments herein is to provide a method and electronic device for displaying transactions corresponding to plurality of modes of payment. The method can be used to receive transaction data from multiple POS devices, extract transaction data associated with each mode of payment and create multiple clusters using the extracted transaction data associated with each mode of payment. The method can then be used to generate multiple interactive user interface (UI) elements for each of the multiple clusters and display the multiple interactive UI elements on the electronic device. A user can select an interactive UI element associated with the transaction data associated with a mode of payment to access the transaction data associated with that mode of payment. Therefore, the proposed method provides comprehensive overview of the transactions performed at the multiple POS devices based on the modes of payment on the electronic device. Thereby, enhancing user experience and ease of access of the transaction data associated with the plurality of modes of payment.
SUMMARY
[0006] Accordingly the embodiments herein disclose a method for displaying transactions corresponding to a plurality of modes of payment by an electronic device. The method includes receiving a first data from a first POS device and a second data from a second POS device. Further, the method includes extracting transactions from the first data and the second data based on a first mode of payment and adding into a first cluster associated with the first mode of payment, followed by generating a first interactive UI element for the first cluster. Similarly the above steps are repeated to generate a second interactive UI element for a second cluster which represents the extracted transactions corresponding to the second mode of payment. Finally, the method includes displaying a common graphical layout comprising the first interactive UI element and the second interactive UI element on a screen of the electronic device.
[0007] In an embodiment, the method further includes detecting, by the electronic device, an input performed on the first interactive UI element and displaying, by the electronic device, the extracted transactions corresponding to the first mode of payment done at the first POS device and the extracted transactions corresponding to the first mode of payment done at the second POS device in response to the input on the at least one first interactive UI element.
[0008] In an embodiment, the method further includes detecting, by the electronic device, an input performed on the at least one second interactive UI element and displaying, by the electronic device, the extracted transactions corresponding to the second mode of payment done at the first POS device and the extracted transactions corresponding to the second mode of payment done at the second POS device in response to the input on the at least one second interactive UI element.
[0009] In an embodiment, the method further includes receiving, by the electronic device, a user identification (ID) which includes but not limited to a biometric of a user, a mobile number of the user and determining, by the electronic device, whether the user ID is associated with a user profile (s). The user profile includes user transaction information, number of user transactions performed through the plurality of modes of payment, offers, promotion and loyalty points for the user profile, feedback score provided through the user profile. Further, the method also includes performing, by the electronic device, automatically registering the user ID and creating a new user profile for the user ID, in response to determining that the user ID is not associated with the user profile (s), and retrieving the user profile and displaying the user profile on the screen of the electronic device, in response to determining that the user ID is associated with the user profile (s).
[0010] In an embodiment, the method further includes determining, by the electronic device, an eligibility of the user profile to process an ongoing transaction at a later period and displaying, by the electronic device, a message indicating that the user profile is eligible to process the ongoing transaction at the later period. Further, the method includes detecting, by the electronic device, an input to process the ongoing transaction at the later period and storing, by the electronic device, the ongoing transaction in the corresponding user profile to process at the later period.
[0011] In an embodiment, the method further includes determining, by the electronic device, the ongoing transaction stored in the user profile to be processed at the later period and determining, by the electronic device, at least one mode of communication for the user profile for sending a message to a user device to process the ongoing transaction stored in the user profile to be processed at the later period. Further, the method includes sending, by the electronic device (100), the message to the user device to complete the ongoing transaction stored in the user profile to be processed at the later period through the at least one determined mode of communication.
[0012] In an embodiment, the method further includes initiating, by the electronic device, a transaction through the user profile and automatically applying, by the electronic device, the offer, the promotion, the loyalty points based on the user profile to the initiated transaction. Further, the method includes generating, by the electronic device, a digital payment receipt for the transaction and displaying, by the electronic device, the digital payment receipt for the user profile on the screen of the first electronic device. The method also includes processing, by the electronic device, the digital payment receipt to complete the transaction and receiving, by the electronic device, the user feedback score on the feedback interactive UI element of the digital payment receipt; and automatically updating, by the electronic device, the digital payment receipt to the corresponding user profile.
[0013] In an embodiment, the method further includes determining, by the electronic device, a product based on the user profile and a learning of transactions associated with the user profile (s) and automatically displaying, by the electronic device, a recommendation of the product to the user.
[0014] In an embodiment, the method further includes determining, by the electronic device, a predefined event at a predefined period and filtering, by the electronic device, the user profiles based on qualification criteria such as a location of the user, a user transaction pattern, a user preference. Further, the method includes determining, by the electronic device, the mode of communication for each of the filtered user profiles and generating, by the electronic device, an alert for each of the filtered user profiles for the at least one predefined event; and automatically sending, by the electronic device, the alert for the predefined event through the determined mode of communication for each of the filtered user profiles.
[0015] Accordingly the embodiments herein disclose an electronic device for displaying transactions corresponding to a plurality of modes of payment. The electronic device includes a memory, a processor, a transaction management controller and a display. The transaction management controller is configured to receive a first data from a first POS device and receive a second data from a second POS device. Further, the transaction management controller is configured to extract transactions from the first data received from the first POS device and transactions from the second data received from the second POS device based on a first mode of payment. The transaction management controller is then configured to add the extracted transactions corresponding to the first mode of payment from the first data and the extracted transactions corresponding to the first mode of payment from the second data into a first cluster associated with the first mode of payment. Similarly, the transaction management controller is configured to extract transactions from the first data received from the first POS device and transactions from the second data received from the second POS device based on a second mode of payment. Then the transaction management controller is configured to add the extracted transactions corresponding to the second mode of payment from the first data and the extracted transactions corresponding to the second mode of payment from the second data into a second cluster associated with the second mode of payment. Further, the transaction management controller is configured to generate a first interactive UI element based on the first cluster and the first mode of payment; and a second interactive UI element based on the second cluster and the second mode of payment. The display is then configured to display a common graphical layout comprising the first interactive UI element and the second interactive UI element on the screen of the electronic device.
[0016] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the invention thereof, and the embodiments herein include all such modifications.
BRIEF DESCRIPTION OF FIGURES
[0017] This invention is illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
[0018] FIG. 1 is a block diagram of an electronic device for displaying transactions corresponding to a plurality of modes of payment, according to the embodiments as disclosed herein;
[0019] FIG. 2 is a flow chart illustrating a method for displaying transactions corresponding to the plurality of modes of payment by the electronic device, according to the embodiments as disclosed herein;
[0020] FIG. 3 illustrates an environmental setup for providing collated payment related information on the electronic device for a business owner, according to the embodiments as disclosed herein;
[0021] FIG. 4 illustrates various steps for displaying the collated payment related information on the electronic device within a store, according to the embodiments as disclosed herein;
[0022] FIGS. 5A -5C are examples illustrating common graphical layout comprising multiple interactive UI elements providing the collated payment related information on a screen of the electronic device, according to the embodiments as disclosed herein;
[0023] FIG. 5D is an example illustrating a transaction statement generated by the electronic device with a summary of transactions provided based on modes of payment, according to the embodiments as disclosed herein;
[0024] FIG. 6 is a flow chart illustrating an option to allow a customer to complete a transaction at a later instant of time, according to the embodiments as disclosed herein;
[0025] FIG. 7 is a flow chart illustrating implementation of loyalty functionality integrated with payment transaction by the electronic device, according to the embodiments as disclosed herein;
[0026] FIGS. 8A-8B illustrate an UI of the electronic device for providing customer transaction related information at the store based on user profiles, according to the embodiments as disclosed herein;
[0027] FIG. 9 illustrates an UI of the electronic device for receiving user feedback and ratings while processing payment by the electronic device, according to the embodiments as disclosed herein;
[0028] FIG. 10A is a flow chart illustrating a method for creating and executing a marketing campaign by the merchant based on multiple user profiles by the electronic device, according to the embodiments as disclosed herein;
[0029] FIG. 10B illustrates an UI of the electronic device for creating and executing marketing campaigns by the merchant using the electronic device, according to the embodiments as disclosed herein;
[0030] FIG. 11A is a flow chart illustrating a method for creating and executing a program by the merchant based on the multiple user profiles by the electronic device, according to the embodiments as disclosed herein;
[0031] FIG. 11B illustrates UI of the electronic device for creating and executing the programs/offers by the merchant using the electronic device, according to the embodiments as disclosed herein;
[0032] FIG. 12 illustrates UI of the electronic device for merchant communications and the campaigns using the electronic device, according to the embodiments as disclosed herein;
[0033] FIG. 13A is a flow chart illustrating the method by which banks can cross-sell financial products to the merchants through the electronic device, according to the embodiments as disclosed herein;
[0034] FIG. 13B illustrates an example scenario of proposed method which allows the banks to cross-sell financial products to the merchants through the electronic device, according to the embodiments as disclosed herein; and
[0035] FIG. 13C is a flow chart illustrating the method by which pre-approved products are provided to the owners through the electronic device, according to the embodiments as disclosed herein.

DETAILED DESCRIPTION OF INVENTION
[0037] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0038] As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as units or modules or the like, are physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.
[0039] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.
[0040] Accordingly the embodiments herein disclose a method for displaying transactions corresponding to a plurality of modes of payment by an electronic device. The method includes receiving a first data from a first POS device and a second data from a second POS device. Further, the method includes extracting transactions from the first data and the second data based on a first mode of payment and adding into a first cluster associated with the first mode of payment, followed by generating a first interactive UI element for the first cluster. Similarly the above steps are repeated to generate a second interactive UI element for a second cluster which represents the extracted transactions corresponding to the second mode of payment. Finally, the method includes displaying a common graphical layout comprising the first interactive UI element and the second interactive UI element on a screen of the electronic device.
[0041] In the conventional methods and systems, if a merchant wants to access transactions related data based on the modes of payment then the merchant will have to separately access the transactions performed using the first mode of the payment, then access the transactions performed using payment the second mode of the payment, etc. The repetitive process to access the transactions performed using the modes of payment makes the procedure cumbersome and time consuming. As a result, the merchant may not use the transactions related data based on the modes of payment for providing customer benefits, marketing, etc. Unlike to the conventional methods and systems, the proposed method is used to extract the transactions based on the modes of payment and segregate the transactions into clusters determined based on the modes of payment. Further, the proposed method is also used to generate and display multiple interactive UI elements for the clusters determined based on the modes of payment. Therefore, the merchant can access the transactions based on the modes of payment comprehensively on a single screen of the electronic device. This result in enhancing user experience and ease of access to the transactions related data based on the modes of payment. Further, the clustered transaction related data can be used to determine benefits to the customers based on the modes of the payment, marketing, etc.
[0042] Referring now to the drawings and more particularly to FIGS. 1 through 13C, where similar reference characters denote corresponding features consistently throughout the figure, these are shown preferred embodiments.
[0043] FIG. 1 is a block diagram of an electronic device (100) for displaying transactions corresponding to a plurality of modes of payment, according to the embodiments as disclosed herein.
[0044] Referring to the FIG. 1, the electronic device (100) may be but not limited to a laptop, a palmtop, a desktop, a mobile phone, a smart phone, Personal Digital Assistant (PDA), a tablet, a foldable device, a flexible device, an immersive system, and a point of sale (POS) device.
[0045] In an embodiment, the electronic device (100) includes a processor (120), a transaction management controller (140), a memory (160) and a display (180).
[0046] The processor (120) may include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU). The processor (120) may include multiple cores and is configured to execute the instructions stored in the memory (160).
[0047] The transaction management controller (140) includes a transaction extraction controller (142), a cluster controller (144), a display controller (146), a user profile controller (148), a transaction completion controller (150) and an endorsement controller (152). The transaction extraction controller (142) is configured to receive a first data from a first point of sale (POS) device (s) (300a). In an example, the first data is received in real-time from the first POS device (s) (300a). In another example, the first data is received at a pre-determined time from the first POS device (s) (300a). In yet another example, the first data is received from the first POS device (s) (300a) based on a user input. The first POS device (s) (300a) may be connected to the electronic device (100) through a mode of communication such as Wireless Fidelity (Wi-Fi), Bluetooth, ZigBee, working internet connectivity, connected through a common cloud server, etc. In an example, the electronic device (100) and the first POS device (s) may be a same device. The first data includes transactions performed at the first POS device (s) (300a) using multiple modes of payment supported by the first POS device (s) (300a) by multiple users. The multiple modes of payment is done through cash, credit/debit card, mobile wallet, Quick Response (QR) code, Unified Payments Interface (UPI), etc. For example, consider the first POS device (300a) supports transaction through credit/debit cards, cash and mobile wallets. Then the first data includes total amount and number of transactions performed at the first POS (300a) by using the credit/debit cards, credit/debit cards details associated with each of the transaction performed using the credit/debit cards, the total amount and the number of transactions performed at the first POS (300a) by cash, the total amount and the number of transactions performed at the first POS (300a) by using mobile wallets and the mobile wallets details associated with each of the transaction performed using the mobile wallets, etc. The transactions performed by a user (s) are recorded in a respective user profile associated with the user which is then stored in transaction database (164). The user profile includes details of user identity such as user mobile number, user address, user transaction history at the merchant outlet, promotion and loyalty points for the user profile, rewards, outstanding transactions saved to be processed at a later instant of time, number of user transactions performed through the plurality of modes of payment, user feedback score provided through the user profile, etc. The first POS device (s) (300a), the second POS device (s) (300b), the third POS device (s) (300c), etc. can be located in a same location or in multiple locations.
[0048] Similarly, the transaction extraction controller (142) is configured to receive a second data from second POS device (s) (300b), third data from third POS device (s) (300c), etc. The second data includes transactions performed at the second POS device (s) (300b) using multiple modes of payment supported by the second POS device (s) (300b), third data includes transactions performed at the third POS device (s) (300c) using multiple modes of payment supported by the third POS device (s) (300c), and the like.
[0049] The transaction extraction controller (142) is configured to extract transactions performed using a first mode of payment from the first data received from the first POS device (s) (300a), the second data received from the second POS device (s) (300b), the third data received from the third POS device (s) (300c), etc. For example, the transaction extraction controller (142) extracts the transactions performed using credit cards from the first data received from the first POS device (s) (300a), the second data received from the second POS device (s) (300b), the third data received from the third POS device (s) (300c), etc. The transaction extraction controller (142) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.
[0050] The cluster controller (144) is configured to add the extracted transactions corresponding to the first mode of payment from the first data, the second data, the third data, etc. into a first cluster associated with the first mode of payment. For example, the cluster controller (144) adds the extracted transactions performed using credit cards from the first data, the second data, the third data, etc. into the first cluster which is associated with the credit cards.
[0051] Similarly, the cluster controller (144) extracts transactions performed using the debit cards, the mobile wallets, the QR codes, the UPI, the cash, etc., from the first, the second data, the third data etc. and adds the extracts transactions into the clusters associated with the debit cards, the mobile wallets, the QR codes, the UPI, the cash, etc. respectively. The cluster controller (144) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.
[0052] Further, the display controller (146) is configured to generate a first interactive UI element based on the first cluster and the first mode of payment, a second interactive UI element based on the second cluster and the second mode of payment, etc. The first interactive UI element represents the extracted transactions corresponding to the first mode of payment done at the first POS device (s) (300a), the second POS device (s) (300b), the third POS device (s) (300c), etc. Similarly, the second interactive UI element represents the extracted transactions corresponding to the second mode of payment done at the first POS device (s) (300a), the second POS device (s) (300b), the third POS device (s) (300c), etc. For example, the first interactive UI element represents the extracted transactions corresponding to the credit cards done at the first POS device (s) (300a), the second POS device (s) (300b), the third POS device (s) (300c), etc. Similarly, the second interactive UI element represents the extracted transactions corresponding to the mobile wallets done at the first POS device (s) (300a), the second POS device (s) (300b), the third POS device (s) (300c), etc. Further, the display controller (146) is configured to generate a common graphical layout including the first interactive UI element, the second interactive UI element, the third interactive UI element, etc., and display the common graphical layout (500) on the display (180) of the electronic device (100).
[0053] The display controller (146) is configured to detect an input performed on the first interactive UI element and display the extracted transactions corresponding to the first mode of payment on the display (180) of the electronic device (100). Similarly, in case the display controller (146) detects an input performed on the second interactive UI element and displays the extracted transactions corresponding to the second mode of payment on the display (180) of the electronic device (100). The display controller (146) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.
[0054] The user profile controller (148) is configured to determine whether user identification (ID) received on the display (180) of the electronic device (100) is associated with any user profile stored in a user profile database (162). The user ID includes but not limited to a biometric of the user, a mobile number of the user, a user tag, etc. The user profile includes the transactions performed by the user.
[0055] Further, the user profile controller (148) automatically registers the user ID and creates a new user profile for the user ID on determining that the user ID is not associated with any user profile stored in the user profile database (162). The user profile controller (148) retrieves the user profile stored in the user profile database (162) and displays the user profile on the display (180) of the electronic device (100) on determining that the at least one user ID is associated with any user profile stored in the user profile database (162).
[0056] The user profile controller (148) is configured to determine an eligibility of the user profile (s) to process an ongoing transaction at a later period and display a message indicating that the user profile (s) is eligible to process the ongoing transaction (s) at the later period on the display (180) of the electronic device (100). The ongoing transaction can be for example, the user having made a purchase at the merchant outlet and a bill for the purchase is generated at the merchant outlet. The bill for the purchase is stored in the user profile based on the eligibility of the user profile to process the ongoing transaction at the later period. The processing of the ongoing transaction at the later period includes completing payment of an amount in the bill. The eligibility of the user profile (s) to process the ongoing transaction at the later period is determined based on a user transaction pattern, a current transaction amount, etc. Further, the user profile controller (148) on detecting an input from the user (s) / merchant indicating an intention to process the ongoing transaction at the later period saves the ongoing transaction in the user profile (s) and updates the user profile (s) stored in the user profile database (162). The user profile controller (148) is also configured to receive a user feedback score on a feedback interactive UI element of a digital payment receipt and automatically updates the digital payment receipt to the corresponding user profile. The feedback interactive UI element is a weblink or a Hypertext Transfer Protocol (HTTP) link using which the user feedback score is recorded. The user profile controller (148) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.
[0057] The transaction completion controller (150) automatically and periodically determines the ongoing transaction (s) to be processed at the later period saved in the user profile (s) stored in the user profile database (162) and automatically determines a mode of communication mentioned in the user profile (s) for sending the message to a user device (1000) to process the ongoing transaction saved in the user profile (s) to be processed at the later period. The mode of communication includes but not limited to short messaging service (SMS), on-call, social media account, electronic mail (e-mail), etc. Further, the transaction completion controller (150) sends the message to the user device to complete the ongoing transaction saved in the user profile to be processed at the later period through the determined mode of communication. The message to the user device to complete the ongoing transaction can include a link which the user can click to complete the ongoing transaction saved in the user profile.
[0058] The transaction completion controller (150) is also configured to automatically apply the offer, the promotion, and the loyalty points based on the fetched user profile to the transaction which is initiated at the electronic device (100) and generate a digital payment receipt for the transaction. The digital payment receipt includes transaction details and an feedback interactive UI element to receive the user feedback score. The transaction completion controller (150) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.
[0059] The endorsement controller (152) is configured to determine a product based on the user profile and a learning of transactions associated with multiple user profiles based on the modes of payment. Further, the endorsement controller (152) automatically displays a recommendation of the product to the user on the display (180) of the electronic device (100). In an example, the product is a financial product sold at the merchant outlet in collaboration with a partner bank. For example, consider that the transactions associated with the user profile are performed using the debit card and crosses a predefined threshold amount every month. Therefore, based on the user profile the endorsement controller (152) in collaboration with the partner bank (based on integration of partner bank’s Application Programming Interface (API) on the electronic device (100) and sharing of the user profile with the partner bank) can recommend a credit card with credit limits customized to the user at the merchant outlet.
[0060] Further, the endorsement controller (152) is configured to determine a predefined event at a predefined period and filter the user profiles based on qualification criteria. The predefined event at the predefined period includes for example a festival, a yearly event, birthday of the user (s), a specific offer defined by the merchant, a marketing campaign by the merchant, etc. The predefined period includes a duration for which the predefined event is valid. The qualification criteria include but not limited to a location of the user, a user transaction pattern, a user preference, etc. Further, the endorsement controller (152) determines the mode of communication for each of the filtered user profiles and automatically sends the alert for the predefined event through the determined mode of communication for each of the filtered user profiles. The endorsement controller (152) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.
[0061] The memory (160) includes a user profile database (162) and a transaction database (164). The user profile database (162) is configured to store the multiple user profiles registered at the merchant outlet using the user ID. The transaction database (164) is configured to store each transaction performed using multiple modes of payment at the electronic device (100). Also, the transaction database (164) stores the first data, the second data, the third data, etc. The transaction database (164) also stores the first cluster associated with the first mode of payment, the second cluster associated with the second mode of payment, the third cluster associated with the third mode of payment, etc. The memory (160) stores instructions to be executed by the processor (120). The memory (160) can include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (160) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (160) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache) such as for example the transaction corresponding to the user profiles.
[0062] In an embodiment, the display (180) is configured to display the common graphical layout which includes the first interactive UI element, the second interactive UI element, the third interactive UI element, etc. The display (180) is also configured to receive the input on the first interactive UI element and display the extracted transactions corresponding to the first mode of payment. Similarly, the display (180) is also configured to receive the input on the second interactive UI element and display the extracted transactions corresponding to the second mode of payment. The display (180) is also configured to receive the user ID and display the digital payment receipt for the user profile. The display (180) is implemented using touch sensitive technology and comprises one of liquid crystal display (LCD), light emitting diode (LED), etc.
[0063] Although the FIG. 1 shows the hardware elements of the electronic device (100) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the electronic device (100) may include less or more number of elements. Further, the labels or names of the elements are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function.
[0064] FIG. 2 is a flow chart illustrating a method for displaying transactions corresponding to the plurality of modes of payment by the electronic device (100), according to the embodiments as disclosed herein. The transaction management controller (140) in the electronic device (100) is configured to perform the steps 202 to 218. Referring to the FIG. 2, at step 202, the electronic device (100) receives the first data from first POS device (300a).
[0065] At step 204, the electronic device (100) receives the second data from the second POS device (300b).
[0066] At step 206, the electronic device (100) extracts the transactions from the first data received from the first POS devices and the transactions from the second data received from the multiple second POS device (300b) based on the first mode of payment.
[0067] At step 208, the electronic device (100) adds the extracted transactions corresponding to the first mode of payment from the first data and the extracted transactions corresponding to the first mode of payment from the second data into the first cluster associated with the first mode of payment.
[0068] At step 210, the electronic device (100) extracts the transactions from the first data received from the first POS device (300a) and the transactions from the second data received from the second POS device (300b) based on the second mode of payment.
[0069] At step 212, the electronic device (100) adds the extracted transactions corresponding to the second mode of payment from the first data and the extracted transactions corresponding to the second mode of payment from the second data into the second cluster associated with the second mode of payment.
[0070] At step 214, the electronic device (100) generates the first interactive UI element based on the first cluster and the first mode of payment.
[0071] At step 216, the electronic device (100) generates the second interactive UI element based on the second cluster and the second mode of payment.
[0072] At step 218, the electronic device (100) displays the common graphical layout comprising the first interactive UI element and the second interactive UI element on the display (180) of the electronic device (100).
[0073] The various actions, acts, blocks, steps, or the like in the method may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.
[0074] FIG. 3 illustrates an environmental setup for providing the collated payment related information on the electronic device (100) for a business owner, according to the embodiments as disclosed herein.
[0075] Referring to the FIG. 3, the environmental setup for providing the collated payment related information on the electronic device (100) for the business owner comprises multiple levels of payment related data.
[0076] At level 1, consider multiple POS devices which are located in a store 1. The store 1 can have the electronic device (100) which will collate the payment related information associated with all the POS devices in the store 1. The multiple POS devices may support various modes of payment such as the UPI, QR code based payment, card payment, cash, etc, In an example, the electronic device (100) can be one of the POS devices located in the store 1.
[0077] Further at level 2, the business owner may have multiple stores i.e., store 1, store 2, store 3, store 4, etc. At level 3, the payment related information associated with the multiple stores may be collated together and stored in the central server. Similarly, the payment related information from the multiple stores associated with a specific brand (as shown in level 3) may be collated together and stored. Further, at level 4, the payment related information associated with the multiple brands owned by the business owner can also be collated and stored in the central server. At each level, while storing the collated payment related information in the central server, the owner may specify the users (based on hierarchy) who can access the collated payment related information related to the specific level stored in the central server. Such as for example, the collated payment related information associated with the store 1 may be accessed by the store manager of store 1. Similarly, the collated payment related information associated with the store 2 may be accessed by the store manager of store 2. However, a brand manager may have access to the collated payment related information associated with all the stores which sell the specific brand.
[0078] Therefore, the business owner will be able to access the collated payment related information associated with all the outlets and brands on a single screen of the electronic device (100). The collated payment related information will comprise the total transaction performed, the total pending payments, the total payments made under a specific mode of payment, feedback scores provided by the users, UI to make offer/sale announcements, etc. Unlike to the conventional methods and system where the business owner will have to specifically check the payment related information related to specific outlet separately, the proposed method provides the collated information related to the entire business setup on one screen.
[0079] FIG. 4 illustrates various steps for displaying the collated payment related information on the electronic device (100) within the store, according to the embodiments as disclosed herein.
[0080] Referring to the FIG. 4, consider a store which allows the customers to make payment in several modes of payment such as for example by using the credit/ debit card, UPI based payment, QR code based payment, and cash payment.
[0081] At step 402a, consider that a first set of users make the payment using the credit/ debit card through the POS devices connected to the electronic device (100) at the store. It may be noted that the electronic device (100) may be a separate device or one of the POS devices at the store. At step 404a, the electronic device (100) processes the payment by sending the payment card related details to an acquirer switch of the sponsoring bank for example bank 1. At step 406a, the acquirer switch forwards the payment card related details to the network which may be an owned by a financial services company such as for example Visa ®. At step 408a, the network forwards the payment card related details to the issuer switch which is owned by a bank 2 (i.e., the bank which has issued the credit/ debit card to the individual user). At step 410a, the issuer bank verifies the payment card related details and authenticates the respective users after which the payment is accepted through the credit/ debit card. The payment success message is displayed on the screen of the electronic device (100) and the payment successful receipt is generated for each of the first set of users.
[0082] At step 402b, consider a second set of users make the payment through cash through the POS devices connected to the electronic device (100). The electronic device (100) processes the payment and generates the payment successful receipt for each of the second set of users.
[0083] Similarly, at step 402c, consider a third set of user make the payment using the QR code mode through their user device and the POS devices connected to the electronic device (100). A Dynamic QR is generated as per EMV Co Unified QR specs. Also, the electronic device (100) supports Static QR, compliant with EMV standards, which can be displayed at multiple points in the store. The user scans the QR code using the UPI/QR enabled app on their user device. At step 404c, the payment is processed by the issuer switch through the issuer bank. Further, the payment success message is displayed on the screen of the electronic device (100) and the payment success or decline is received as a callback API and the refreshed status is displayed on the electronic device (100) with the receipt generated for each of the third set of users. In an example, consider a UPI based payment then a UPI ID entered on the electronic device (100) is checked for validity based on the UPI API. Collect request is generated and submitted via the acquiring bank API. Transaction is routed through the NPCI network to the issuing bank. The issuing Bank/ Issuer PSP notifies the user to complete the transaction. The status of transaction as approved / declined is sent to the electronic device (100) based on the Callback API. In another example, consider the SMS based payment mode. An API is integrated with Payment Gateway (PG) service provider. The electronic device (100) generates a payment link and sends to user mobile number. The user clicks on the payment link, which is unique to the transaction. The user completes the transaction using one of the credit/debit/ prepaid card or by any of the payment modes supported by the PG provider. The status of transaction as approved / declined is sent to the electronic device (100) based on the Callback API. If customer takes no action, the transaction status is expired.
[0084] Further, at step 414, each of the payment details is stored in the memory (160) of the electronic device (100) in the user profiles of the respective users. In another example, the payment details saved into the user profiles of the respective users may be stored in the central server or a cloud server with access to a hierarchy of store employees.
[0085] At step 416, consider that the owner of the store wants to have a comprehensive view of the payment related information for the current day with the details of the modes of payment by which the users have made the payment at the store. In the conventional methods and systems the owner had to separately check the details associated with each of the mode of payment along with the amount received under each mode of payment which makes the process cumbersome. Unlike to conventional methods and systems, in the proposed method the electronic device (100) integrates the respective APIs for each payment mode and hence the owner will be able to view the comprehensive payment related information with details of each of the mode of payment used by the users for making the payment along with the amount received under each mode of payment on the screen of the electronic device (100) (as shown in FIG. 5A-5C).
[0086] Further, the proposed method offers engagement tools with banks including access to financial products of the Banks, made available in a pre-approved manner. The solution is integrated with respective Banks/ Partners offering these products thereby ensuring immediate fulfillment of opted in financial products without any friction. Furthermore, collection of loans extended to the merchants can be adjusted against settlements corresponding to the payments volume thereby reducing financial burden on the merchant and reducing risk of delinquencies for the lending Bank.
[0087] At step 418, the collection of loans extended to the merchant by the banks can be adjusted against settlements corresponding to the payments volume. Once the merchant/owner accesses the comprehensive view of the payment related information for the current day, and then the merchant may decide to settle an installment or a portion of the installment of the loans based on the total transactions of the day. In another example, the merchant may predefine a specific amount of the loan/ installment to be settled on a daily basis automatically by the electronic device (100). To settle the installment of the loans based on the total transactions of the day, the electronic device (100) interacts with a settlement server of a corresponding financial institution. Further, the settlement history is updated and the payment related information for the current day is displayed again for the merchant after the settlement of the installments.
[0088] Therefore, the proposed method also allows the merchants to automatically settle a portion of the installment/ loan based on the transactions of the day thereby reducing financial burden on the merchant and reducing risk of delinquencies for the lending bank.
[0089] FIGS. 5A -5C are examples illustrating the common graphical layout comprising multiple interactive UI elements providing the collated payment related information on the screen of the electronic device (100), according to the embodiments as disclosed herein.
[0090] Referring to the FIG. 5A, in conjunction with the FIG. 4 step 416, the owner can access the comprehensive payment related information associated with the multiple POS devices connected to the electronic device (100) by selecting the multiple interactive UI elements provided on the screen of the electronic device (100). At 502, the interactive UI element provides comprehensive sales related information such as the total transaction, transaction over a period of time, performance statistics, sales value, etc.
[0091] At 504, the interactive UI element provides comprehensive payment related information related to the various modes of payment available at the multiple POS devices of the store (s). The owner may select the interactive UI element for each mode of payment for which the owner wants to see the payment related information from the multiple POS devices of the store (s). The owner may also select the interactive UI element which provides the complete payment related information for all the modes of payment. Further, the multiple interactive UI elements may provide details in table. 1:
Interactive UI element Remarks
Sales Counter Real-time information for an aggregate of all successful transaction. Amount and transaction count
Top 3 Transactions Status of the latest three transactions done on the terminal
Payment Modes Doughnut Chart with split by payment mode for the transaction count
PayLater Summary Total Amount Due from Number of Customers
Summary View Successful transactions – Count and Amount by each payment mode; Failed Transactions – Count & Amount, Transactions in-progress Count & Amount; Transactions Voided – Count & Amount
Date Selection Summary view based on date selected
Transaction Details Each Payment Mode summary expands into a list of transactions. Each transaction further expands into transaction details
Table. 1
[0092] The FIG. 5B, which is in conjunction with the step 502 of the FIG. 5A, the UI of the electronic device (100) when the owner selects the interactive UI element which provides the comprehensive sales/ payment related information is provided. At step 502a, the total sales/payment related information over a period of 3 days (i.e., 11-13th April) is displayed in form of a bar graph along with the exact amount of sales/payment. Further at step 502b, the performance is provided in the form of a curve graph which is displaying the sales performance over a period of time. The owner can select any position on the curve graph to know the exact value of sales for a specific day.
[0093] The FIG. 5C, which is in conjunction with the step 504 of the FIG. 5A, the UI of the electronic device (100) when the owner selects the interactive UI element which provides the complete payment related information for all the modes of payment is provided. At step 504a, the owner selects a specific day for example 15th April for which the collated and comprehensive payment related information is displayed. This includes the modes of payment and the respective number of transactions in each of the modes of payments along with the amount of payment in each of those transactions. It also provides the total amount of transactions along with the total number of transactions. At step 504b, the graphical display of the payment with respect to each mode of payment is provided.
[0094] FIG. 5D is an example illustrating a transaction statement generated by the electronic device (100) with the summary of transactions provided based on the modes of payment, according to the embodiments as disclosed herein.
[0095] Referring to the FIG. 5D, in conjunction with the FIGS. 5A- 5C, the electronic device (100) further can generate the transaction summary based on the multiple modes of payment supported at the electronic device (100). In the transaction summary generated by the electronic device (100) comprises in addition to the regular transaction details, the summary of the transaction made using each of the modes of payment supported by the electronic device (100) along with associated charges. Therefore, in the proposed method the merchant can generate the transaction summary with the transaction made using each of the modes of payment supported by the electronic device (100). Further, the proposed method includes receiving the customer feedback which helps the merchant to learn about the customer experience and change approach accordingly through the customer feedback collection system. Without customer feedback, merchants likely receive only ad hoc information regarding the customers experience, the products and stores or are only aware of negative perceptions when they lose the customer. Capturing feedback allows merchants to course correct (stock products customers like the most, fix inefficiencies, etc.) and retain the customers. The customers can provide an assessment of the store experience independently without the assistance of the staff member. The rating tool allows the customers to share the rating and any qualitative feedback. The feedback link is triggered as part of the digital receipt for the payment when the mobile number is entered. The feedback related information is provided in the table. 2 and the table 3.
Information Remarks
Trigger Successful transaction completion
Receipt Delivery SMS with link. Click on the link opens up the digital receipt with all the transaction details.
Feedback Link Feedback APIs integrated with Digital Receipt. SMS carries a link for customer to rate the Merchant and leave qualitative feedback
Feedback Information Link integration captures TID and MID
Table. 2
Attribute Details
Smart Score ? Today: Shows consolidated rating across outlets in real-time
? Week: Displays Week-to-Date rating
? Month: Displays Month-to-Date rating
? Consolidated: Default view is configured for consolidated rating across locations
? Location-wise: Rating for each location displayed on selection from drop-down
Multiple Location View ? Summary of score across multiple location
? Reflects data for the time selection of Day, Week, Month
? Movement of score across time-series
Feedback ? Location-wise feedback comments
? Top 3 best and worst scores along with comments
Alerts & Triggers ? Alerts and triggers, enabling merchant based on predetermined and customized triggers
? Feedback data linked to the CRM to monitor and manage the experience of top customers
? Prompt to alert merchant when top customers provide significantly low scores on key metrics
Table. 3
[0096] FIG. 6A is a flow chart illustrating the option to allow the customer to complete the transaction at a later instant of time, according to the embodiments as disclosed herein.
[0097] Referring to the FIG. 6A, at step 602, the merchant initiates the transaction on the electronic device (100) by entering the unique ID of the customer such as the customer’s mobile number. At step 604, the electronic device (100) displays the user profile of the customer where the merchant will be able to see the purchase/transaction history of the customer. Further, at step 606, the merchant decides to extend the paylater option to the customer and at step 608, the merchant enters the customer details on the electronic device (100) if the user profile associated with the customer or the customer history is not found in the memory (160) or the central server of the store. If the user profile associated with the customer is available, then the same is auto-populated on the electronic device (100).
[0098] At step 610, the electronic device (100) receives the copy of invoice and is tagged to the paylater transaction by the merchant. At step 612, the electronic device (100) stores the paylater transaction in the transaction database (164) of memory (160). Further, at step 614, the electronic device (100) displays the paylater summary with ageing on the display (180) of the electronic device (100). At step 616, the merchant then sends the collection request to the customers along with the transaction invoice copy through the electronic device (100). At step 618, the customer receives the payment link and at step 620, the customer makes the partial or the full payment for the transaction. Further, at step 622, the electronic device (100) automatically updates the paylater outstanding balance in the user profile of the respective customer and at step 624, the electronic device (100) displays the updated details for the customer.
[0099] The proposed paylater option is designed with APIs for each functionality. The objective is to digitize the informal credit system offered by several merchants, as a traditional practice. Traditionally, the merchant opens a tab and records every transaction in a physical notebook and squares off the accounts at regular intervals or as per the customer requests. The proposed paylater option not only digitizes the process, but also integrates the payment capability to square off the accounts. Table. 4 provides the summarized details of the paylater option:
Information Remarks
PayLater Payment Mode Merchant enters customers mobile no for the first time on the electronic device (100). The electronic device (100) fetches the user profile associated with the customer. Merchant can take an informed decision on extending credit to the customer. In case, merchant intends extending credit, the merchant proceeds with capture of name, address and amount. The first paylater transaction records customer details and the transaction details. Every subsequent paylater transaction automatically brings up the customer details, merchant enters amount and records the transaction.
PayLater Summary Summary of paylater customers and sum of the transaction amount and number of customers with dues. The summary opens into bands of days outstanding 40+ Days, 30-40 Days, 20-30 Days, <20 Days. Each band has total dues and number of customers due from
PayLater Transaction Details Paylater summary can be extended to paylater transaction list. The list shows mobile number, customer name, amount due and days due
sort functionality on all these attributes. Filter on these attributes the merchant can search on mobile no/ name and identify the total outstanding of the customer and the ledger showing payments done and payment due.
PayLater Settlement of Dues Customer has the option of making part payment or total payment to settle the dues. Merchants select the amount to be settled and the payment mode. All the details are sent as the payload to the payment mode selected. Successful transaction completion results in dues being reduced
Bill Services Merchant has the option to tag and store transaction bill and SKU details along with the paylater transaction details. These bills can then be provided to the customers at request for confirmation and payments by the customer
Reminder Services Merchant can sort and filter the dues outstanding list. Swipe right to initiate a call to the customer. Swipe left to send a WhatsApp ® with Dues Summary and Payment Link
Table. 4
[00100] FIG. 6B illustrates UI of the electronic device (100) with the option to allow the customer to complete the transaction at the later instant of time, according to the embodiments as disclosed herein.
[00101] Referring to the FIG. 6B, consider a company XXX at step 630, the electronic device (100) displays a total value of the transactions which are saved to be completed at the later point of time at the company XXX. Further, the UI also provides a split of the total value into sub-amounts and the number of user profiles associated with each of the sub-amounts.
[00102] Consider the company XXX has 2 branches located in Janakpuri and Rohila. At step 632, the electronic device (100) displays the total value of the transactions which are saved to be completed at the later point of time at each of the branches along with the number of user profiles.
[00103] Further, the merchant can select the branch as janakpuri in case the merchant wants the transactions which are saved to be completed at the later point of time at the Janakpuri branch (as shown in step 634). The electronic device (100) will display the list of individual customers. Further, the merchant can select the individual customer in the list displayed at step 634 and at step 636 generates an alert to the individual customer to complete the transaction.
[00104] FIG. 7 is a flow chart illustrating the implementation of loyalty functionality integrated with the payment transaction by the electronic device (100), according to the embodiments as disclosed herein.
[00105] Referring to the FIG. 7, at step 702 the merchant initiates the transaction on the electronic device (100) by entering the customer mobile number. At step 704, the electronic device (100) automatically fetches the user profile associated with the customer and determines whether the customer is eligible for loyalty benefits at the store. In case the customer is determines to be eligible for the loyalty benefits at the store then at step 706 the electronic device (100) determines whether there are any transaction points to be redeemed based on a previous transaction performed by the user. Further, at step 708, the electronic device (100) automatically applies the points available for redemption, on determining that there are transaction points to be redeemed based on the previous transaction performed by the user. At step 710, the electronic device (100) automatically adjusts the invoice amount based on the redeemed points and at step 712, the electronic device (100) updates the user profile associated with the customer with the invoice and the deduction in the redemption points. At step 714, the customer makes payment using one of the modes of payment available at the electronic device (100)/POS device.
[00106] At step 704, if the electronic device (100) determines that the customer is not eligible for the loyalty benefits at the store, then at step 716 the electronic device (100) determines whether the current transaction performed by the customer qualifies for the loyalty benefits. If the electronic device (100) determines that the current transaction performed by the customer does not qualify for the loyalty benefits, then the electronic device (100) loops to step 706. If the electronic device (100) determines that the current transaction performed by the customer qualifies for the loyalty benefits, then the electronic device (100) calculates and credits the loyalty reward points and then loops to step 706. Also, the same data will be updated in the user profile for future reference.
[00107] In an example, the loyalty plan may be defined by the merchant as in table. 5.
Loyalty Plan Definition
Eligible Customers Loyal
Loyal Customer Definition More than 3 visits in last 3 months
Eligible Payment Transaction All
Qualifying Transaction Minimum INR 500
Reward points per INR 100 2
Validity 3 months
Redemption Threshold Minimum Balance 500 Points
Single Transaction Maximum 200 Points
Table. 5
[00108] The proposed method empowers the merchants to motivate the customers to return and spend more, through a CRM system that enables merchants to drive tailored customer interaction notifications based on predetermined and customized triggers as given in table. 6, table. 7 and table. 8.
Identifier for Customer : Mobile Number
Customer registration No registration process required
Name No name to be captured at the front-end because it will slow down the billing/ checkout process
Other demographics Progressive build-up of user profile associated with the customer based on multiple interactions of the customer with the merchant and data shared by the customer
New customer A customer who has shown up at the store level for the first time.
For example, if a merchant is looking at the dashboard in Month = May-20 and the customer’s First Shop Date (FSD) at the store is May-20, the customer is New.
Repeat Customer A customer who has shopped at the store before and has shopped again in the current month. The customer FSD at the store would be prior to the current month
Frequent customer Subset of ‘Repeat’ customer and configurable by the Business Owner, typically based on period or amount of transaction in a defined time period.
Real-time Customer Recognition As soon as the merchant enters the mobile number, categorization of customer (New/ Repeat/ Frequent) with number of visits displayed
Table. 6
Customizable Definition for Loyal Customer and Loyalty Plan
Loyalty Parameters Customizable by the Business Owner, typically based on frequency of visits, recency of visits, aggregated spend, # of products purchased, type of payment, in a specific time period
SKU level (or SKU group) loyalty definition possible in case of integrated implementation with Billing POS system
Loyalty Definition A customer can be loyal to a store or loyal to a brand of the chain of stores. Information will be available at a corporate level for the owner to see who are loyal to the Group of brands, individual brand or individual store.
Business Owner can configure the parameter: store, brand or corporate group to which loyalty should extend
Qualifying Transactions Rewards can be configured to require a minimum ticket size. Only transactions that meet the ticket size threshold will be considered as qualifying transactions
Loyalty Currency Reward (point) management system with configurable reward ratio, validity and expiry management, redemption thresholds, earn and burn management, integrated with liability management process
Redemption Process Transaction Platform prompts possibility of redeeming reward points on the dashboard and reward point redemption basis customer consent
Table. 7
Loyalty Management Dashboard on the electronic device (100) provides details such as:
Loyalty Dashboard • New vs. Repeat customers
• Avg ticket size of new vs repeat customers
• SPAC (Spend/ Active Customer) pre-post program
• TPAC (Transactions/ Active Customer) pre-post
• Reward earn-burn position
Accounting Provide full visibility on liability including opening balance of collectible points, points issued, redeemed and expired during the period, qualifying customers and amount in the month, number of Customers redeeming and Amount redeemed and the closing points and associated liability at the end of the period
Table. 8
[00109] FIGS. 8A-8B illustrates UI of the electronic device (100) for providing customer transaction related information at the store based on user profiles, according to the embodiments as disclosed herein.
[00110] The electronic device (100) enables the merchant to see daily, weekly, monthly or quarterly figures on Sales growth figure for last month compared to the month before and/or to the same month last year. Further, the electronic device (100) provides the merchants with complete view of the business and transactions where the merchant can select to view the business at an overall level, at a location level for all terminals. The electronic device (100) will contain multiple attributes that the merchant would like to see at any given point in time. The same view can be seen at a store level.
[00111] Referring to the FIG. 8A, consider a user say User A visits the store of company XXX. At the time of making the payment at the billing counter the owner/ store keeper enters the user ID such as the mobile number of the user on the electronic device (100). The electronic device (100) fetches the user profile associated with the user ID and provides details such as the number of visits to the store of the company XXX by the user A, the spend indicator of the user A, etc based on the customer specific intelligence. Further, the owner can know the transaction pattern of the user A by selecting the specific period such as in step 802 for a period of 30 days and in step 804 the owner determines the transaction pattern of the user A for 90 days. Further, at step 806, the owner can view the customer related information as well on the electronic device (100) such as the number of new customers and the number of repeat customers who have visited the store of the company XXX between a specific period of time (such as 1-15th April a sin the example).
[00112] The owner of the store can also view real-time information of the transactions during the day which are populated only from AUTHORIZATION transactions (based on employee hierarchy).
[00113] In a consolidated view reports are generated for SETTLED transactions only for the transaction date. The merchant customization of attributes to be chosen for the electronic device (100) is allowed based on the merchant’s digital quotient and a partner bank’s monetization considerations as provided in table. 9.
Attribute Details
Smart Counter 1. Today: Shows the Total amount of transactions and total number of transactions as of last minute.
2. Week: Displays Week-to-Date information for amount and transaction. Week start is default configured for Monday however, can be configured by the Merchant
3. Month: Displays Month-to-Date information for amount and transaction.
4. Consolidated: Default view is configured for consolidated status across location.
5. Location-wise: Information view for each location will be displayed on selection from drop-down
Last 3 Transactions 1. View of Last 3 transactions
2. Tap on transaction to view transaction history and transaction details
Multiple Location View 1. Integration chart with location name and transaction amount for the multiple stores located at different locations
2. Reflects data for the time selection of Day, Week, Month

Business Performance 1. Time series view with a 6-month view of business
2. Toggles between Transaction and Amount
3. Displays actual transaction/ amount when tapped on the data point
4. Display Actual # of Transactions and Actual Amount
5. Default time line is Month-to-date for the current month.
6. Hourly graph for Day selection, daily performance for Week selection, 6-month view for Month selection supported on web version of the Platform
Table. 9
[00114] In a transaction summary tab, the details and status of various transactions undertaken at the merchant location are displayed by the electronic device (100). The transaction summary tab also allows the merchant the option to access or download reports for predefined or customized date ranges as shown in step 808 and step 810 of the FIG. 8B. The details of the transaction summary tab are given in table. 10.
Attribute Details
Summary of Transactions 1. Summary of successful transactions by count and amount
2. Summary for each payment mode, in case multiple payment modes are supported by the bank
3. Void, Failed transactions by count and amount
4. Data for the day shown based on real-time authorization transactions
Transaction Details 1. Tap on specific payment mode to get a list of transactions
2. List of successful, void, failed transaction
3. Tap on specific transaction to get transaction details
4. Details: Transaction ID, Masked Card No, Payment network, Amount, Transaction status, Masked Mobile No (if captured)
Data Selection 1. Date scroll for single day selection
2. Date range with calendar selection
Location Selection 3. Default view shows consolidated across location
4. Location dropdown for selection of data at a specific location
Table. 10
[00115] Further, the credit to bank report provides reconciled statements together with details of transaction values, charges levied by the acquirer bank and net amount credited to the bank account of the merchant, as shown in the step 812 of the FIG. 8B. Details of the credit to bank report are given in table. 11.
Attribute Details
Credits to Bank Total Credited to Bank
Location Details Consolidated view
Location selection
TID level view
Data Selection 1. Date scroll for single day selection
2. Date range with calendar selection
Total Recon View of total recon: Gross Amount, Fee Deductions and Net Credit to allow easy reconciliation. View can be enabled subject to all data being available as part of recon
Table. 11
[00116] FIG. 9 illustrates UI of the electronic device (100) for receiving the user feedback and ratings while processing the payment by the electronic device (100), according to the embodiments as disclosed herein.
[00117] Referring to the FIG. 9, the proposed method allows the merchant to receive feedback and ratings from the customer and also project the overall feedback and ratings received from multiple users on the electronic device (100). At step 902, when the customer completes the transaction at the electronic device (100) the payment receipt generated comprises a link to receive the feedback and ratings from the customer.
[00118] At step 904, when the customer clicks on the link in the payment receipt, the UI for providing the feedback and ratings opens as shown. The customer can select the ratings and type the feedback, if any. Further, at step 906, the electronic device (100) allows the merchant to see the total ratings received from multiple customers along with the dates associated with the feedback statistics.
[00119] Further, the summary of the various attributes associated with the feedback and ratings systems are described in the table. 12.
Attribute Details
Features ? Enables small merchants to design and execute their campaigns
? Marketing channels: SMS, email, Facebook, Instagram, Whatsapp
? Merchant opts in for Marketing Service, selects channel, chooses template or types message, creates Sender ID/ uses default SenderID
? Take picture, add message and post to social media enabled
Data Sets ? Merchant has access to customer set whose mobile numbers were captured at transaction
? Merchant’s customer data set in the bank’s database allows intelligent filtering criteria
? Option also to upload external data from stored location or Google drive.
Integration ? Integration with SMS and Email gateways
? Integration with PG for collecting SMS Fees
Cost Estimate Data set selected, length of message contribute to SMS cost. Estimate provided prior to message broadcast scheduling
Reports Merchant gets to see SMS dashboard – delivered, DND, undelivered, amount deducted
All campaigns done so far
Analytics of incremental sales, if required
Alerts and Triggers ? Alerts and triggers, enabling merchant and customer notifications based on predetermined and customized triggers e.g.,
a. If the flagged (top 20%) customer hasn’t come by for one month, enable a one click message with a greeting or discount offer
b. If any customer has come by the store 5 or more times in a month, enable a one click thank you message
c. On national or religious holiday, enable a one click holiday greeting to all flagged (top 20%) customers
d. Prompt on how much revenue is being missed out on due to specific regular customers not coming by for a long time and provide simple marketing solution,
Table. 12
[00120] FIG. 10A is a flow chart illustrating a method for creating and executing a marketing campaign by the merchant based on the multiple user profiles by the electronic device (100), according to the embodiments as disclosed herein. The transaction management controller (140) in the electronic device (100) is configured to perform the steps 1002 to 1014. An example for a marketing campaign may be marketing products with specific discounts for a specific event such as a festival, end of season (EOS) sale, launch of a new collection/ brand of products, etc. Referring to the FIG. 10A, at step 1002, the electronic device (100) allows the merchant to create a new campaign for marketing their products/brand or the store. At step 1004, the electronic device (100) allows the merchant to select the title for the campaign and at step 1006 the electronic device (100) allows the merchant to select the mode of communication to send the campaign message to the multiple users and also to create a message by using text, images, videos, etc. Further, at step 1008, the electronic device (100) filters the registered user profiles based on qualification criteria such as location of the customers; number of transactions, total spends, etc. However, in case the merchant does not select any qualification criteria then the electronic device (100) selects all the user profiles to send the campaign messages.
[00121] At step 1010 the electronic device (100) allows the merchant to set a date/ time to send out the campaign messages to the filtered user profiles. Further, at step 1012, the electronic device (100) sends the campaign messages to the filtered user profiles at the set date/time and at step 1014 displays the status of the campaign messages on the screen.
[00122] FIG. 10B illustrates UI of the electronic device (100) for creating and executing marketing campaigns by the merchant using the electronic device (100), according to the embodiments as disclosed herein.
[00123] Referring to the FIG. 10B, in conjunction with the FIG. 10A, at step 1020, the UI of the electronic device (100) is provided where the merchant can create the new campaign by selecting the mode of communication for the campaign. The mode of communication can be SMS, e-mail, social networking sites (SNS), call, etc.
[00124] At step 1022, the UI of the electronic device (100) is provided where the merchant enters the title for the campaign, content to be sent as part of the message for the campaign to the user profiles selected by the electronic device (100). Further, at step 1024, the UI of the electronic device (100) is provided where the merchant can preview the message to be sent before sending out the message for the campaign. Therefore, the merchant can edit the message, add images, videos, etc to the message.
[00125] The proposed method provides rewards in the form of for example, cashback or a free merchandize based on number of visits (daily use product based outlets), total spend in a defined period (e.g., salons, beauty parlors) or a combination of both. Merchants need simple but effective tools to manage and build customer relationships not just the top 20 users they can remember, but also the next 50 - 100 users. They need tools that work across multiple storefronts and irrespective of who happens to be manning the till, enabling a more complete picture of the business. The proposed method allows the merchant to set rules that are conducive for any kind of outlet. The details are provided in table. 13.
Attribute Details
Features ? Enables small merchants to design and execute their reward programs
? SMS, email, Facebook, Instagram, Whatsapp
? Apply reward automatically at the front-end if the customer qualifies
Data Sets ? Merchant’s customer data set in the bank’s database allows intelligent filtering and qualification criteria
Rule Engine ? Reward type: % Off or Cash Discount
? Qualifying transactions, No of transactions, Amount
? Other attributes like payment mode, location etc.,
Cost Estimate Basis the target segment selection criteria and the rule set, merchant is shown an estimate of the program cost
Reports ? Returning customer, qualifying customers, Reward accrued and assigned, reward redeemed
? All campaigns done so far
? Analytics of incremental sales, if required
Alerts & Triggers ? Alerts and triggers, enabling merchant and customer notifications based on predetermined and customized triggers
? Pre-set programs e.g., festive, retention driver, frequency builder
Table. 13
[00126] FIG. 11A is a flow chart illustrating a method for creating and executing a program by the merchant based on the multiple user profiles by the electronic device (100), according to the embodiments as disclosed herein. The transaction management controller (140) in the electronic device (100) is configured to perform the steps 1102 to 1014. An example for a program may not be associated with a specific event and may be provided by the merchant based on the sales, profits, etc. Referring to the FIG. 11A, at step 1102, the electronic device (100) allows the merchant to create the new program. Further, at step 1104, the electronic device (100) allows the merchant to select a title for the program and at step 1106, to select the period for the program. Further, at step 1108, the electronic device (100) allows the merchant to set a reward type such as percentage of discount on purchase of specific amount, etc and at step 1110 the electronic device (100) filters the user profiles based on the qualification criteria such as location of the customers, payment mode, ticket size, etc. Furthermore, at step 1112, the electronic device (100) allows the merchant to select the reward calculation period for the program and the conditions for the reward. At step 1114 the electronic device (100) automatically calculates and displays the estimate program cost and allows the merchant to alter the program conditions. Further, at step 1116, the electronic device (100) sets the tracker to track the program throughout the period of the program.
[00127] The proposed method provides a communication channel with direct, ongoing interactions with merchant which helps the bank deliver offerings in the context of the usage and further boost Merchant engagement through Gamification. The bank can implement campaigns with gamification techniques for the entire trial-adoption-retention journey, product cross-sell, increase frequency and sales volume, drive breadth of usage across payment modes, reward revenue enhancing behavior. The proposed method provides rule based gamified interface, notification and communication to drive digital transactions. The gamification rules to track daily digital transactions, frequency, consistency, etc. The proposed method provides badges for each challenge level achieved with interface with social networking sites for posting status. The reward interface includes display points, cashback, vouchers as required by the bank. The program is configurable based on data captured by or, made available to the electronic device (100). Further, examples of the programs that the bank can set up are provided in table. 14 and table. 15.
Special Edition Badges
Rewards Category Description Badge
World Environment Day Go Green! Go Digital! Earn this badge by doing 20+ Digital transactions today Designed for the event
National Day Promote Digital Kuwait. Promote progress. Earn this badge by doing 10+ Digital transactions today Designed for the event
New Year’s Day Start the New Year with a digital pledge. Earn this badge by doing 10+ Digital transactions today Designed for the event
Weekly Digital Challenge
Rewards Category Description Badge
Perfect Week – Digital Transactions
(show as a past event) Earned 5 times by Sansa’s Salon!
Doing more than 5 Digital transactions every day of the week
Weekly Perfection Badge
Perfect Week – Digital Amount
(show as a past event) Earned 3 times by Sansa’s Salon!
Doing more than ? 2,000 Digital payments every day of the week
Weekly Perfection Badge
Daily Digital Challenge
Rewards Category Description Badge
Daily Target for Volume Customize store level target Animated notification and alert
Daily Target for Transactions Customize store level target Animated notification and alert
Table. 14
Campaign Design and Set-up
Attribute Details
Program Design Identify programs
Define program objective
Define offer eligibility
Define qualifying conditions
Terms & Conditions link
Link to videos (optional)
Incentive Define incentive type – Cashback, Voucher, Points
Badge Define badge category
Program UI Design Program Card and Animation
Design Program badge
Display progress bar
Display win
APIs Define data sources and UI supported
Develop and test APIs
Award File Award file conditions and generation
Profile update Update badge and reward status
Table. 15
[00128] FIG. 11B illustrates UI of the electronic device (100) for creating and executing the programs/offers by the merchant using the electronic device (100), according to the embodiments as disclosed herein.
[00129] Referring to the FIG. 11B, in conjunction with the FIG. 11A, at step 1120, the UI of the electronic device (100) is provided where the merchant can create the new programs/offers by adding the title, offer details, etc.
[00130] At step 1122, the UI of the electronic device (100) is provided where the merchant is allowed to determine the qualification criteria for filtering the user profiles which will be eligible for the program. The merchant can select multiple criteria, guided selection and recommendation of the user profiles.
[00131] At step 1124, the UI of the electronic device (100) is provided where the multiple offers which are provided by the merchant as part of the program are displayed. The offers are defined by the merchant based on various conditions such as mode of payment and the merchant can customize the program such as the the reward type, the program duration, etc. Further, when the filtered user profile make any transaction at the store, the electronic device (100) applies the reward in real-time without any merchant intervention.
[00132] FIG. 12 illustrates UI of the electronic device (100) for gamified merchant communications and campaigns using the electronic device (100), according to the embodiments as disclosed herein.
[00133] Referring to the FIG. 12, the proposed method provides API based Integration kit with independent business solutions including Merchant Billing POS. With increasing complexity and scale, businesses need to provide customers with faster and better experience at checkout and analyze business indicators in a holistic manner across payments, financial and other operational parameters. For example, integrating retail billing solutions (Retail POS) with payments is key to delivering a great checkout experience for the customer. Efficiency pay back for the employees and the business are huge. Billing / SKU information is captured on the billing POS. When integrated with a digital payment solution the entire data capture and data flow make the experience and the analytics richer. The benefits of the integrated API based solution are given in table. 16.
Delivers Superior Customer Experience
(as shown in step 1202) • SME gets a seamless one-click checkout experience
• Speeds up the checkout process - Less wait time for the SME’s customer
• Total flexibility – accept all payments methods seamlessly
Drives Operational Efficiency
(as shown in step 1204) • Eliminates need for multiple data entry and hence human error
• More robust and holistic MIS & Dashboards
• Ease of reconciliation and back office management
• Process day-close faster
Facilitates Richer Insights
(as shown in step 1206) • Combined offering enhances the proposition for respective partners
• Richer data points mean an opportunity for the merchant to drive more intelligent and customized marketing communication
• Option to further customize Loyalty
Table. 16
[00134] FIG. 13A is a flow chart illustrating the method by which the banks can cross-sell financial products to the merchants through the electronic device (100), according to the embodiments as disclosed herein.
[00135] Referring to the FIG. 13A, at step 1302, the electronic device (100) allows the merchant to initiate the transaction by entering the mobile number of the customer. Further, the electronic device (100) fetches the user profile based on the mobile number of the customer and checks for pre-approved offers, if any and fetches additional products/ offers based on customer demographics/ user profile.
[00136] At step 1304, the electronic device (100) displays the eligible offers and products for the customer from the corresponding partner banks. At step 1306, the merchant solicits customer interest and at step 1308, the electronic device (100) generates the lead. Further, at step 1310, the electronic device (100) receives any additional details required from the customer and at step 1313, the electronic device (100) receives the customer confirmation on the terms and conditions, records consent. At step 1316, the electronic device (100) product approved by the Bank (based on API integration) is sold/added to customer transaction. The proposed method at step 1318 allows the electronic device (100) to display the merchant incentive on screen of electronic device (100).
[00137] FIG. 13B illustrates an example scenario of the proposed method which allows the banks to cross-sell financial products to the merchants through the electronic device (100), according to the embodiments as disclosed herein.
[00138] Referring to the FIG. 13B, the proposed method facilitates the sharing of the user profile details with the corresponding user bank as shown in step 1 which allows the banks to cross-sell financial products to the merchant’s customers based on the user profiles through the electronic device (100), as shown in step 2. The banks can recommend/distribute the financial products by leveraging the merchant-customer relationship and at the same time offer the product to customers in a seamless manner and congruent to the customer need based on the type of merchant and nature of transaction (e.g., insurance policy at pharmacies, consumer durable loans for large ticket purchases, etc.). Under the proposed method, the bank will be able to identify the set of merchants who could act as distributor-partner and also identify the set of products that they could cross-sell at individual store level for better targeting based on the user profiles at the merchant outlets. Furthermore, the bank can also leverage the proposed graphical layout to gamify and incentivize the merchant to become active advocate of bank product to the customers. The summary is provided in table. 17.
Cross-Sell Product Set-up
Attribute Details
Qualifying Stores Merchant Business Category
Merchant Identifier
Available Product Product Set-up on the Platform
Selection of Products available for cross-sell at qualified stores
Qualifying Customers Eligible Mobile Numbers
Eligible Customer Profile based on transaction profile (number or amount in a period, etc)
Eligible transaction based on transaction amount
Incentive Define incentive for Merchants
Badge Define badge category
Incentive File Incentive file conditions and generation
Profile update Update badge and incentive status
Table. 17
[00139] FIG. 13C is a flow chart illustrating the method by which pre-approved products are provided to the owners through the electronic device (100), according to the embodiments as disclosed herein.
[00140] Referring to the FIG. 13C, consider in the back-end of the electronic device (100) at step 1350, the transaction database (164) includes offer rules engine which comprises rules that are used to identify pre-approved offers for owners and also to create pre-approved offers for owners based on performance of their establishments.
[00141] In the front end at, on the screen of the electronic device (100) at step 1352 the owner logs-in to the electronic device (100) and at step 1354 the pre-approved offers are displayed on the electronic device (100). At step 1356, the owner selects offers/ products which they want to use on the electronic device (100) and at step 1358, the electronic device (100) share an OTP for validation and allows the owner to accept terms and conditions. Once the owner accepts the same, at step 1360, the product is issued by the bank based on the bank API integration in real-time. Further, at step 1362, the electronic device (100) provides the product in real-time to the owner and is ready-for-use.
[00142] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

,CLAIMS:CLAIMS
We claim:
1. A method for displaying transactions corresponding to a plurality of modes of payment by an electronic device (100), the method comprising:
receiving, by the electronic device (100), a first data from at least one first point of sale (POS) device (300a), wherein the first data comprises a plurality of transactions done using the plurality of modes of payment available at the at least one first POS device (300a) through a plurality of user profiles;
receiving, by the electronic device (100), a second data from at least one second POS device (300b), wherein the second data comprises a plurality of transactions done using the plurality of modes of payment available at the at least one second POS device (300b) through the plurality of user profiles;
extracting, by the electronic device (100), transactions of the plurality of transactions from the first data received from the at least one first POS device (300a) and transactions of the plurality of transactions from the second data received from the at least one second POS device (300b) based on a first mode of payment of the plurality of modes of payments;
adding, by the electronic device (100), the extracted transactions corresponding to the first mode of payment from the first data and the extracted transactions corresponding to the first mode of payment from the second data into a first cluster associated with the first mode of payment;
extracting, by the electronic device (100), transactions of the plurality of transactions from the first data received from the at least one first POS device (300a) and transactions of the plurality of transactions from the second data received from the at least one second POS device (300b) based on a second mode of payment of the plurality of modes of payments;
adding, by the electronic device (100), the extracted transactions corresponding to the second mode of payment from the first data and the extracted transactions corresponding to the second mode of payment from the second data into a second cluster associated with the second mode of payment;
generating, by the electronic device (100), at least one first interactive user interface (UI) element based on the first cluster and the first mode of payment, wherein the first interactive UI element represents the extracted transactions corresponding to the first mode of payment done at the at least one first POS device (300a) and the extracted transactions corresponding to the first mode of payment done at the at least one second POS device (300b);
generating, by the electronic device (100), at least one second interactive UI element based on the second cluster and the second mode of payment, wherein the second interactive UI element represents the extracted transactions corresponding to the second mode of payment done at the at least one first POS device (300a) and the extracted transactions corresponding to the second mode of payment done at the at least one second POS device (300b);
displaying, by the electronic device (100), a common graphical layout (500) comprising the at least one first interactive UI element and the at least one second interactive UI element on a display (180) of the electronic device (100).
2. The method as claimed in claim 1, further comprising:
detecting, by the electronic device (100), an input performed on the at least one first interactive UI element; and
displaying, by the electronic device (100), the extracted transactions corresponding to the first mode of payment done at the first POS device (300a) and the extracted transactions corresponding to the first mode of payment done at the second POS device (300b) in response to the input on the at least one first interactive UI element.
3. The method as claimed in claim 1, further comprising:
detecting, by the electronic device (100), an input performed on the at least one second interactive UI element; and
displaying, by the electronic device (100), the extracted transactions corresponding to the second mode of payment done at the first POS device (300a) and the extracted transactions corresponding to the second mode of payment done at the second POS device (300b) in response to the input on the at least one second interactive UI element.
4. The method as claimed in claim 1, further comprising:
receiving, by the electronic device (100), at least one user identification (ID) comprising at least one of a biometric of a user, and a mobile number of the user;
determining, by the electronic device (100), whether the at least one user ID is associated with at least one user profile of the plurality of user profiles, wherein the at least one user profile comprises user transaction information, number of user transactions performed through the plurality of modes of payment, one of: offers, promotion and loyalty points for the user profile, user feedback score provided through the user profile;
performing, by the electronic device (100), one of:
automatically registering the at least one user ID and creating a new user profile for the at least one user ID, in response to determining that the at least one user ID is not associated with the at least one user profile of the plurality of user profiles, and
retrieving the user profile of the plurality of user profiles and displaying the user profile on the screen of the electronic device (100), in response to determining that the at least one user ID is associated with the user profile of the plurality of user profiles.
5. The method as claimed in claim 4, further comprising:
determining, by the electronic device (100), an eligibility of the user profile to process an ongoing transaction at a later period;
displaying, by the electronic device (100), a message indicating that the user profile is eligible to process the ongoing transaction at the later period;
detecting, by the electronic device (100), an input to process the ongoing transaction at the later period;
storing, by the electronic device (100), the ongoing transaction in the corresponding user profile and process the ongoing transaction at the later period.
6. The method as claimed in claim 5, further comprising:
determining, by the electronic device (100), the at least one ongoing transaction stored in the user profile to be processed at the later period;
determining, by the electronic device (100), at least one mode of communication for the user profile for sending a message to a user device to process the ongoing transaction stored in the user profile to be processed at the later period; and
sending, by the electronic device (100), the message to the user device to complete the ongoing transaction stored in the user profile to be processed at the later period through the at least one determined mode of communication.
7. The method as claimed in claim 4, further comprising:
initiating, by the electronic device (100), a transaction through the user profile;
automatically applying, by the electronic device (100), at least one of the offer, the promotion, and the loyalty points based on the user profile to the initiated transaction;
generating, by the electronic device (100), a digital payment receipt for the transaction, wherein the digital payment receipt comprises transaction details and a feedback interactive UI element to receive the user feedback score;
displaying, by the electronic device (100), the digital payment receipt for the user profile on the screen of the first electronic device (100);
processing, by the electronic device (100), the digital payment receipt to complete the transaction;
receiving, by the electronic device (100), the user feedback score on the feedback interactive UI element of the digital payment receipt; and
automatically updating, by the electronic device (100), the digital payment receipt to the corresponding user profile.
8. The method as claimed in claim 4, further comprising:
determining, by the electronic device (100), at least one product based on the user profile and a learning of transactions associated with the user profile; and
automatically displaying, by the electronic device (100), a recommendation of the at least one product to the user.
9. The method as claimed in claim 1, further comprising:
determining, by the electronic device (100), at least one predefined event at a predefined period;
filtering, by the electronic device (100), the plurality of user profiles based on a qualification criteria, wherein the qualification criteria is one of a location of the user, a user transaction pattern, and a user preference;
determining, by the electronic device (100), at least one mode of communication for each of the filtered user profiles of the plurality of user profiles;
generating, by the electronic device (100), an alert for each of the filtered user profiles for the at least one predefined event; and
automatically sending, by the electronic device (100), the alert for the at least one predefined event through the at least one determined mode of communication for each of the filtered user profiles.
10. A electronic device (100) for displaying transactions corresponding to a plurality of modes of payment, the electronic device (100) comprising:
a memory (160);
a processor (120) coupled to the memory (160); and
a transaction management controller (140), coupled to the memory (160) and the processor (120), and configured to:
receive a first data from at least one first point of sale (POS) device (300a), wherein the first data comprises a plurality of transactions done using the plurality of modes of payment available at the at least one first POS device (300a) through a plurality of user profiles;
receive a second data from at least one second POS device (300b), wherein the second data comprises a plurality of transactions done using the plurality of modes of payment available at the at least one second POS device (300b) through the plurality of user profiles;
extract transactions of the plurality of transactions from the first data received from the at least one first POS device (300a) and transactions of the plurality of transactions from the second data received from the at least one second POS device (300b) based on a first mode of payment of the plurality of modes of payments;
add the extracted transactions corresponding to the first mode of payment from the first data and the extracted transactions corresponding to the first mode of payment from the second data into a first cluster associated with the first mode of payment;
extract transactions of the plurality of transactions from the first data received from the at least one first POS device (300a) and transactions of the plurality of transactions from the second data received from the at least one second POS device (300b) based on a second mode of payment of the plurality of modes of payments;
add the extracted transactions corresponding to the second mode of payment from the first data and the extracted transactions corresponding to the second mode of payment from the second data into a second cluster associated with the second mode of payment;
generate at least one first interactive UI element based on the first cluster and the first mode of payment, wherein the first interactive UI element represents the extracted transactions corresponding to the first mode of payment done at the at least one first POS device (300a) and the extracted transactions corresponding to the first mode of payment done at the at least one second POS device (300b);
generate at least one second interactive UI element based on the second cluster and the second mode of payment, wherein the second interactive UI element represents the extracted transactions corresponding to the second mode of payment done at the at least one first POS device (300a) and the extracted transactions corresponding to the second mode of payment done at the at least one second POS device (300b);
a display (180) coupled to the memory (160), the processor (120) and the transaction management controller (140), and configured to:
display a common graphical layout (500) comprising the at least one first interactive UI element and the at least one second interactive UI element on the display (180) of the electronic device (100).
11. The electronic device (100) as claimed in claim 10, wherein the transaction management controller (140) is further configured to:
detect an input performed on the at least one first interactive UI element; and
display the extracted transactions corresponding to the first mode of payment done at the first POS device (300a) and the extracted transactions corresponding to the first mode of payment done at the second POS device (300b) in response to the input on the at least one first interactive UI element.
12. The electronic device (100) as claimed in claim 10, wherein the transaction management controller (140) is further configured to:
detect an input performed on the at least one second interactive UI element; and
display the extracted transactions corresponding to the second mode of payment done at the first POS device (300a) and the extracted transactions corresponding to the second mode of payment done at the second POS device (300b) in response to the input on the at least one second interactive UI element.
13. The electronic device (100) as claimed in claim 10, wherein the transaction management controller (140) is further configured to:
receive at least one user identification (ID) comprising at least one of a biometric of a user, and a mobile number of the user;
determine whether the at least one user ID is associated with at least one user profile of the plurality of user profiles, wherein the at least one user profile comprises user transaction information, number of user transactions performed through the plurality of modes of payment, one of: offers, promotion and loyalty points for the user profile, user feedback score provided through the user profile;
perform one of:
automatically register the at least one user ID and creating a new user profile for the at least one user ID, in response to determining that the at least one user ID is not associated with the at least one user profile of the plurality of user profiles, and
retrieve the user profile of the plurality of user profiles and displaying the user profile on the screen of the electronic device (100), in response to determining that the at least one user ID is associated with the user profile of the plurality of user profiles.
14. The electronic device (100) as claimed in claim 13, wherein the transaction management controller (140) is further configured to:
determine an eligibility of the user profile to process an ongoing transaction at a later period;
display a message indicating that the user profile is eligible to process the ongoing transaction at the later period;
detect an input to process the ongoing transaction at the later period;
store the ongoing transaction in the corresponding user profile and process the ongoing transaction at the later period.
15. The electronic device (100) as claimed in claim 14, wherein the transaction management controller (140) is further configured to:
determine the at least one ongoing transaction stored in the user profile to be processed at the later period;
determine at least one mode of communication for the user profile for sending a message to a user device to process the ongoing transaction stored in the user profile to be processed at the later period; and
send the message to the user device to complete the ongoing transaction stored in the user profile to be processed at the later period through the at least one determined mode of communication.
16. The electronic device (100) as claimed in claim 13, wherein the transaction management controller (140) is further configured to:
initiate a transaction through the user profile;
automatically apply at least one of the offer, the promotion, and the loyalty points based on the user profile to the initiated transaction;
generate a digital payment receipt for the transaction, wherein the digital payment receipt comprises transaction details and a feedback interactive UI element to receive the user feedback score;
display the digital payment receipt for the user profile on the screen of the first electronic device (100);
process the digital payment receipt to complete the transaction;
receive the user feedback score on the feedback interactive UI element of the digital payment receipt; and
automatically update the digital payment receipt to the corresponding user profile.
17. The electronic device (100) as claimed in claim 13, wherein the transaction management controller (140) is further configured to:
determine at least one product based on the user profile and a learning of transactions associated with the user profiles based on the plurality of modes of payment; and
automatically display a recommendation of the at least one product to the user.
18. The electronic device (100) as claimed in claim 10, wherein the transaction management controller (140) is further configured to:
determine at least one predefined event at a predefined period;
filter the plurality of user profiles based on a qualification criteria, wherein the qualification criteria is one of a location of the user, a user transaction pattern, and a user preference;
determine at least one mode of communication for each of the filtered user profiles of the plurality of user profiles;
generate an alert for each of the filtered user profiles for the at least one predefined event; and

automatically send the alert for the at least one predefined event through the at least one determined mode of communication for each of the filtered user profiles.

Dated this 26th November 2020

Signature
Arun Kishore Narasani
IN/PA 1049