DESC:TECHNICAL FIELD

The present disclosure relates to the field of payment processing system and communication systems, and more specifically to a method and payment terminal for improving data communication reliability during transaction processing.

BACKGROUND

Payment systems have undergone evolution in recent years. With development of Information Technology (IT) and electronic era, electronic card transactions have become one of the most versatile payment methods for exchange of goods and services. Currently, there are very common and preferred means of payment by consumers leading to significant increase in their use ever since the method of electronic payment was invented. An increase in demand of e-payment enabling systems to have increased the variety of such products.
Current technologies within payment domain attempts to communicate using dedicated, pre-defined connections between a transacting terminal and a payment gateway server. During a transaction processing, issues of unreliability in network is prevalent across the payment processing domain. In existing systems, entire communication between the terminal and the payment gateway server is dependent on a strength and quality of a signal on which the terminal is communicating. Often the strength of a carrier signal varies from one area to another causing a noticeable unreliability in the communication resulting in transaction failures, problems such as, double debits, connection failures, and finally suboptimal customer experience causing loss.
The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

SUMMARY

Disclosed herein is a computer implemented method for improving data communication reliability in a network during transaction processing. The method includes identifying a plurality of user devices in proximity to the payment terminal and configuring a Peer-to-Peer (P2P) network using the plurality of user devices in response to receiving an acknowledgment from each of the plurality of user devices for a connection request. The method includes initiating a transaction by sending a plurality of transaction requests to a payment server. Each of the plurality of transaction request is transmitted via a direct connection between the payment terminal and the payment server, and via at least two user devices amongst the plurality of user devices using the P2P network. Thereafter, the method includes receiving a response for each of the plurality of transaction request from the payment server.
In another embodiment, the present disclosure discloses a method for improving data communication reliability in a network during transaction processing. The method includes receiving a plurality of transaction requests from a payment terminal. Each of the plurality of transaction request is received via a direct connection between the payment terminal and the payment server, and via a P2P network formed using at least two user devices amongst a plurality of devices. In response to the plurality of transaction requests, the method includes merging the plurality of transaction requests as a single transaction request. Thereafter, the method includes providing an acknowledgment to the payment terminal for each of the plurality of transaction requests separately.
Further, the present disclosure includes a payment terminal for improving data communication reliability in a network during transaction processing. The payment terminal includes a processor and a memory communicatively coupled to the processor. The memory stores processor instructions, which, on execution, causes the processor to identify a plurality of user devices in proximity to the payment terminal and configure a Peer-to-Peer (P2P) network using the plurality of user devices in response to receiving an acknowledgment from each of the plurality of user devices for a connection request. Further, the payment terminal initiates a transaction by sending a plurality of transaction requests to a payment server. Each of the plurality of transaction request is transmitted via a direct connection between the payment terminal and the payment server, and via at least two user devices amongst the plurality of devices using the P2P network. Thereafter, the payment terminal receives a response for each of the plurality of transaction requests from the payment server.

Furthermore, the present disclosure includes a payment server for improving data communication reliability in a network during transaction processing. The payment server includes a processor and a memory communicatively coupled to the processor. The memory stores processor instructions, which, on execution, causes the processor to receive a plurality of transaction requests from a payment terminal. Each of the plurality of transaction request is received via a direct connection between the payment terminal and the payment server, and via a P2P network formed using at least two user devices amongst a plurality of devices. In response to the plurality of transaction requests, the payment server merges the plurality of transaction requests as a single transaction request. Thereafter, the payment server provides an acknowledgment to the payment terminal for each of the plurality of transaction request separately.
The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features may become apparent by reference to the drawings and the following detailed description.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

The example embodiment(s) of the present invention are illustrated by way of example, and not in way by limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:

FIGURE 1 show an exemplary environment for improving data communication reliability in a network during transaction processing, in accordance with an embodiment of the present disclosure;

FIGURE 2 shows an exemplary detailed block diagram of a payment terminal, in accordance with embodiments of the present disclosure;

FIGURE 3 shows an exemplary detailed block diagram of a payment server, in accordance with embodiments of the present disclosure;

FIGURE 4 shows a flow chart illustrating method steps for improving data communication reliability in a network during transaction processing at payment terminal, in accordance with an embodiment of the present disclosure;

FIGURE 5 shows a flow chart illustrating method steps for improving data communication reliability in a network during transaction processing at payment server, in accordance with an embodiment of the present disclosure; and

FIGURE 6 shows an exemplary embodiment improving data communication reliability in a network during transaction processing, in accordance with an embodiment of the present disclosure.

It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it may be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown. While each of the figures illustrates a particular embodiment for purposes of illustrating a clear example, other embodiments may omit, add to, reorder, and/or modify any of the elements shown in the figures.

DETAILED DESCRIPTION

In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and may be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the scope of the disclosure.

The terms “comprises”, “includes” “comprising”, “including” or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “comprises… a” or “includes…a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or apparatus.

Embodiments of the present disclosure are directed to a method and a payment terminal for improving data communication reliability in a network during transaction processing. With advancement in internet technology, e-commerce, online transaction/remote transaction has become a common mode of payment transaction for users. Current technologies within payment domain attempts to communicate using dedicated and pre-defined connections between a transacting terminal and a payment server. However, during the transaction processing, issue of unreliability in the network is quite prevalent across payment processing systems. This leads to poor network reliability which results in several issues such as, double debit, connection failures, and finally suboptimal customer experience causing loss.

The present disclosure discloses the payment terminal for improving data communication reliability in a network during transaction processing. The payment terminal may be a dedicated Point of Sale (POS) device associated with users/merchant for performing a payment transaction. While performing a transaction, the payment terminal identifies a plurality of user devices in proximity to the payment terminal and initiates a connection request to each of the plurality of user devices. In response to receiving an acknowledgment from each of the plurality of user device for the connection request, a Peer-to-Peer (P2P) network is configured using the plurality of user devices. Thus, the payment terminal initiates a transaction by sending a plurality of transaction requests to a payment server. Each of the plurality of transaction request is transmitted via a direct connection between the payment terminal and the payment server, and via at least two user devices amongst the plurality of user devices using the P2P network. Thereafter, a response for each of the plurality of transaction request is received from the payment server. The payment server provides an acknowledgment to the payment terminal for each of the plurality of transaction requests by merging the plurality of transaction requests as a single transaction request.

Embodiments of the present disclosure have several advantages. For example, embodiments allow neighboring user devices to connect with a payment terminal and create a peer-to-peer network. This helps to enhance the reliability in communication between the payment terminal and a payment server. Previously, transactions were dependent on direct connection between the payment terminal and the payment server. Embodiments of the present disclosure ensures that there are no dropouts during a transaction. In order to reduce the dropouts, the present disclosure adds redundancy in the payment terminal, wherein the payment terminal directly sends the transaction requests using the direct mode to the payment server and via least two neighboring user devices until an acknowledgement from the payment server is received asynchronously. Accordingly, embodiments provide a more reliable and convenient method for users for payment transactions.

In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.

FIGURE 1 show an exemplary environment for improving data communication reliability in a network during transaction processing, in accordance with an embodiment of the present disclosure.

As shown in FIGURE 1, environment 100 includes a payment terminal 101 connected through a Peer to Peer (P2P) network 103 and a direct mode of communication network 109 to a payment server 107. In an embodiment, the payment terminal 101 may be a Point of Sale (POS) device associated with a merchant. The P2P network 103 includes a user device 1051………..and a user device 105N (collectively referred as plurality of user devices 105). In an embodiment, the communication network 109 may include, for example, e-commerce network, wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, Wi-Fi, cellular network, etc. In an embodiment, the payment server 107 may facilitate transaction processing for e-businesses, online retailers and the like. Typically, the payment server 107 may facilitate a payment transaction by a transfer of information between the payment terminal 101 and an acquiring bank. For conducting a reliable transaction, the payment terminal 101 may detects current network conditions of the direct mode. In an embodiment, the current network conditions may be detected using any known existing techniques and methods.

Consider, based on the detection, the payment terminal 101 predicts one or more network issues in the direct connection mode of communication network 109. For example, the one or more network issues may be network link down, connection errors and the like. In such case, the payment terminal 101 may initialize scanning proximity area for identifying a plurality of user devices 105 in proximity to the payment terminal 101. The scanning may be performed using predefined techniques such as, Near Field Communication (NFC), Bluetooth, Internet Control Message Protocol (ICMP) or any other pre-existing scanning techniques. In an embodiment, the plurality of user devices 105 may be associated with the merchant or any customer at location of the merchant. In an embodiment, the plurality of user devices 105 may be any Wi-Fi enabled user devices present in proximity of the payment terminal 101. In an embodiment, the plurality of user devices 105 may include, but not limited to, a desktop computer, a Personal Digital Assistant (PDA), a notebook, a smartphone, a tablet, and any other computing devices. A person skilled in the art would understand that, any other computing device for communication with a display unit, not mentioned explicitly, may also be used in the present disclosure.

On discovering a plurality of devices upon scanning, the payment terminal 101 may send a connection request to each of the plurality of user devices 105. In an embodiment, the plurality of user devices 105 may include an application for responding to the connection request. In an embodiment, each of the plurality of user devices 105 may be registered with the payment terminal 101 for providing P2P services. The plurality of user devices 105 may either accept or reject the connection request from the payment terminal 101. In case of acceptance, the payment terminal 101 may receive an acknowledgment from each of the plurality of user devices 105. Upon receiving the acknowledgment, the payment terminal 101 may configure the Peer-to-Peer (P2P) network 103 using the plurality of user devices 105. In an embodiment, the payment terminal 101 may configure the P2P network 103 using a predefined model. In an embodiment, the P2P network 103 may be configured with a predefined time period of the transaction.

Thus, once the P2P network 103 is configured, the payment terminal 101 may initiate a transaction by sending a plurality of transaction requests to the payment server 107. The payment terminal 101 transmits the plurality of transaction request via the direct mode of communication network 109 to the payment server 107 and via at least two user devices amongst the plurality of user devices 105 using the P2P network 103. The payment terminal 101 may generate a transaction request to be transmitted via the P2P network 103 by including transaction details such as, transaction ID, payment details etc., associated with a transaction request transmitted using the direct connection between the payment terminal 101 and the payment server 107.
On receiving the plurality of transaction requests from the payment terminal 101, the payment server 107 may merge the plurality of transaction requests as a single transaction request. The payment server 107 merges the plurality of transaction requests based on the transaction details associated with each of the plurality of transaction requests. Thus, the payment server 107 may transmit an acknowledgment to the payment terminal 101 for each of the plurality of transaction requests separately. In an embodiment, the payment terminal 101 may not wait for each separate acknowledgment, in case of receiving the acknowledgment for the transaction request transmitted from the direct mode of communication network 109. In an embodiment, the payment terminal 101 may remove at least one user device of the plurality of user devices 105 from the P2P network 103 on receiving a request from the at least one user device during or post the transaction.

FIGURE 2 shows an exemplary detailed block diagram of a payment terminal, in accordance with embodiments of the present disclosure.

The payment terminal 101 may include at least one Central Processing Unit (“CPU” or “processor”) 201 and a memory 204 for storing instructions executable by the at least one processor 201. The processor 201 may comprise at least one data processor for executing program components for executing user or system-generated requests. The memory 204 is communicatively coupled to the processor 201. The payment terminal 101 further comprises an Input/ Output (I/O) interface 203. The I/O interface 203 is coupled with the processor 201 through which an input signal or/and an output signal is communicated.

In one embodiment, the payment terminal 101 may include, for example, a display unit 202, a scanning module 208, a network configuration module 209, a transaction initiating module 210, a card reader 211, a receipt printer 212, a communication unit 213 and a keypad 214. It will be appreciated that such aforementioned units may be represented as a single unit or a combination of different units.

The display unit 202 may be housed on the payment terminal 101 and communicatively coupled to the processor 201. The display unit 202 may be used to display various information like configuration details, payment amount of the ongoing transaction and result of the transaction from the payment server 107 for example success or failure.

In an embodiment, the scanning module 208 be configured to detect current network condition of the direct mode of communication network 109. In case of detecting one or more network issues in the direct connection, the scanning module 208 may perform scanning for the plurality of user devices 105 in proximity to the payment terminal 101 to identify the plurality of user devices 105. The scanning module 208 may scan using the predefined techniques such as, NFC, Bluetooth, Internet Control Message Protocol (ICMP) and the like.

The network configuration module 209 may configure the P2P network 203 using the plurality of user devices 105. In an embodiment, the network configuration module 209 may configure the P2P network 103 using the predefined model or any other existing mechanisms known to person skilled in the art.

The transaction initiating module 210 may initiate the transaction by sending the plurality of transaction requests to the payment server 107. The transaction initiating module 210 may first send the transaction request via the direct communication network 109 between the payment terminal 101 and the payment server 107. Further, the transaction initiating module 210 may generate the plurality of transaction request for sending via the at least two user devices amongst the plurality of user devices 105 using the P2P network 103. The transaction initiating module 210 may generate the plurality of transaction request by including the transaction details such as, transaction ID, amount etc., associated with the transaction request transmitted via the direct communication network 109.

The card reader 211 may be housed on the payment terminal 101 and communicatively coupled to the processor 201. The card reader 211 may be capable of extracting details of physical payment card used for making the payments. The details of the physical payment card may include primary account number and issuer identification number. The card reader 211 extracts the details of the physical payment card using information encoded in the magnetic stripe on the physical payment card or using information stored on integrated circuits. In another embodiment, card reader 211 may be capable of extracting the details of the physical payment card via a wireless communication between the physical payment card and the card reader 211, such as via Near-Field Communication (NFC), Bluetooth, or a similar wireless protocol.

The receipt printer 212 may be housed on the payment terminal 101 and communicatively coupled to the processor 201. The receipt printer 212 may be used to generate a hard copy (paper copy) of transaction details, details regarding the gateway, details of the physical payment card, payment amount of a transaction and/or the result of a transaction.

The communication unit 213 may be programmed or configured for sending and receiving information to and from the payment server 107 from the direct communication network 109 and the P2P network 103. For instance, the communication unit 213 may receive the response for each of the plurality of transaction request from the payment server 107.
The keypad 214 may be housed on the payment terminal 101 and communicatively coupled to the processor 201. The keypad 214 may be used to receive input from user. The input from the user may include, secure pin used for authorizing the transaction. In an embodiment, keypad 214 may be implemented as a digital or virtual keypad on display unit 202. For example, display unit 202 may include touch-sensitive inputs that detect user inputs.

In one embodiment, the data 200 stored in the memory 204 may include network data 205, transaction data 206 and other data 207. The network data 205 may include details regarding the plurality of user devices 105 in the P2P network 103.Further, the network data 205 may include configuration details for configuring the P2P network 103. The transaction data 206 may include any relevant information for performing the transaction. For example, the transaction data 206 may include any sensitive account information and/or personal information that may be used to identify and/or authenticate a user account. Further, the transaction data 206 may include information about the plurality of transaction requests associated with each transaction. Further, the information may include transaction details such as, transaction ID, amount and the like.

In an embodiment, other data 207 may include information necessary for encrypting and decrypting transaction related data and payment details.

FIGURE 3 shows an exemplary detailed block diagram of a payment server, in accordance with embodiments of the present disclosure.

The payment server 107 may include at least one Central Processing Unit (“CPU” or “processor”) 301 and a memory 304 storing instructions executable by the at least one processor 301. The processor 301 may comprise at least one data processor for executing program components for executing user or system-generated requests. The memory 304 is communicatively coupled to the processor 301. The payment server 107 further comprises an Input/ Output (I/O) interface 303. The I/O interface 303 is coupled with the processor 301 through which an input signal or/and an output signal is communicated.

The payment server 107 may include data 305 and one or more modules 308 which are described herein in detail. In an embodiment, data 305 may be stored within the memory 305. The data 305 may include, for example, transaction request data 306 and other data 307.

The transaction request data 306 may include the plurality of transaction requests received through the direct connection between the payment terminal 101 and the payment server 107, and via the P2P network 103. The plurality of transaction requests includes the transaction details associated with the transaction.
The other data 307 may store data, including temporary data and temporary files, generated by modules 308 for performing the various functions of the payment server 107.

In an embodiment, the data 305 in the memory 304 are processed by one or more modules 308 present within the memory 304 of the payment server 107. In an embodiment, the one or more modules 308 may be implemented as dedicated units. As used herein, the term module refers to an application specific integrated circuit (ASIC), an electronic circuit, a field-programmable gate arrays (FPGA), Programmable System-on-Chip (PSoC), a combinational logic circuit, and/or other suitable components that provide the described functionality. In some implementations, the one or more modules 308 may be communicatively coupled to the processor 301 for performing one or more functions of the payment server 107. The said modules 308 when configured with the functionality defined in the present disclosure will result in a novel hardware.

In one implementation, the one or more modules 308 may include, but are not limited to a communication module 309 and a transaction merging module 310. The one or more modules 308 may also include other modules 311 to perform various miscellaneous functionalities of the payment server 107. The other modules 311 may include processing module for processing the transactions requests.

The communication module 309 may be programmed or configured for sending and receiving information from the payment terminal 101. The communication module 309 may receive the plurality of transaction requests from the payment terminal 101. Further, the communication module 309 may provide the acknowledgment to the payment terminal 101 for each of the plurality of transaction requests separately.
The transaction merging module 310 may merge the plurality of transaction requests from the payment terminal 101 as the single transaction request. The transaction merging module 310 may receive the plurality of transaction requests and map the transaction details with each request. The transaction details such as, transaction ID, amount and the like. On identifying similar transaction details, the transaction merging module 310 may consider the mapped transaction requests as emerging for same transaction and merge the transaction requests as single transaction requests.

FIGURE 4 shows a flow chart illustrating method steps for improving data communication reliability in a network during transaction processing at payment terminal, in accordance with an embodiment of the present disclosure.

The order in which the method 400 is described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from scope of the subject matter described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof.

As illustrated in FIGURE 4, the method 400 may comprise one or more steps for improving data communication reliability in a network during transaction processing at payment terminal 101.

For conducting a reliable transaction, the payment terminal 101 may detect the current network conditions of the direct mode of communication network 109. Consider, based on the detection, the payment terminal 101 predicts the one or more network issues in the direct connection mode of communication network 109. For example, the one or more network issues may be network link down, connection errors and the like. In such case, the payment terminal 101 may initialize scanning proximity area.

At the step 401, the payment terminal 101 identifies the plurality of user devices 105 the in proximity to the payment terminal 101 by scanning the proximity area using the predefined scanning techniques such as, such as, Near Field Communication (NFC), Bluetooth, Internet Control Message Protocol (ICMP) or any other pre-existing scanning techniques. In an embodiment, on discovering the plurality of user devices 105, the payment terminal 101 may send the connection request to each plurality of user devices 105.
At block 403, in response to receiving the acknowledgment from each of the plurality of user devices 105 for the connection request, the payment terminal 101 may configure the Peer-to-Peer (P2P) network 103 using the plurality of user devices 105. In an embodiment, the P2P network 103 may be configured using the predefined model.
At block 405, the payment terminal 101 may initiate the transaction by sending the plurality of transaction requests to the payment server 107. The payment terminal 101 transmits each of the plurality of transaction request via the direct communication network 109 between the payment terminal 101 and the payment server 107, and via at least two user devices amongst the plurality of user devices 105 using the P2P network 103. In an embodiment, the plurality of transaction requests transmitted via at least two user devices comprises transaction details associated with the transaction request transmitted using the direct connection between the payment terminal 101 and the payment server 107.
At block 407 the payment terminal 101 may receive the response for each of the plurality of transaction request from the payment server 107. In an embodiment, during or post the transaction, if at least one user device of the plurality of user devices 105 wishes to leave the P2P network 103, the payment terminal 101 may remove the at least one user device from the P2P network 103.

FIGURE 5 shows a flow chart illustrating method steps for improving data communication reliability in a network during transaction processing at payment server, in accordance with an embodiment of the present disclosure.

The order in which the method 500 is described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the spirit and scope of the subject matter described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof.

At the step 501, the payment server 107 receives the plurality of transaction requests from the payment terminal 101. Each of the plurality of transaction request is received via the communication network 109 between the payment terminal 101 and the payment server 107, and via the P2P network 103.
At block 503, in response to the plurality of transaction requests, the payment server 107 merges the plurality of transaction requests as the single transaction request. The payment server 107 merges the plurality of transaction requests as the single transaction request based on the transaction details associated with each of the plurality of transaction requests.

At block 505, the payment server 107 provides the acknowledgment to the payment terminal 101 for each of the plurality of transaction requests separately.
FIGURE 6 shows an exemplary embodiment improving data communication reliability in a network during transaction processing, in accordance with an embodiment of the present disclosure.

FIGURE 6 illustrates a scenario of performing transaction at a shop. As shown, the shop includes the payment terminal 101 which is directly connected to the payment server 107. Consider, the payment terminal 101 is performing a transaction for a user 602. Before initiating the transaction, the payment terminal 101 detects the current network condition for the direct connection. Based on the detection, consider, the payment terminal 101 predicts network link slowdown. In such case, the payment terminal 101 may start scanning proximity area to identify user devices. Consider, the payment terminal 101 identifies three user devices, a mobile phone 601 associated with the user 602, a mobile phone 603 of merchant and a tablet 604 of the merchant. The payment terminal 101 sends a connection request to each of the three user devices. Consider, the payment terminal 101 receives an acknowledgment from the mobile phone 603 and the tablet 604. In such case, the payment terminal 101 may configure a P2P network 606 using the mobile phone 603 and the tablet 604. Thus, once the P2P network 606 is configured, the payment terminal 101 initiates the payment transaction for the user 602 by transmitting the plurality of transaction requests. In current scenario, the payment terminal 101 transmits three transaction requests, i.e. first transaction request using the direct connection between the payment terminal 101 and the payment server 107, a second and third transaction requests via the mobile phone 603 and the tablet 604 using the P2P network 606. While transmitting the second and the third transaction requests, the payment terminal 101 may include the transaction details associated with the first transaction request. Therefore, once the transaction is performed, the payment terminal 101 may receive the acknowledgment for each of the three transaction requests from the payment server 107. In an embodiment, the payment terminal 101 may receive the acknowledgment for only the second and third transaction requests.

The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise.

The terms "including", "comprising", “having” and variations thereof mean "including but not limited to", unless expressly specified otherwise.

The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms "a", "an" and "the" mean "one or more", unless expressly specified otherwise.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.

When a single device or article is described herein, it may be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it may be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the invention need not include the device itself.

The illustrated operations of FIGURE 4 and FIGURE 5 show certain events occurring in a certain order. In alternative embodiments, certain operations may be performed in a different order, modified or removed. Moreover, steps may be added to the above described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.

Thus, system and method for improving data communication reliability in a network during transaction processing allows neighboring user devices to connect with a payment terminal 101 and create a peer-to-peer network. This helps to enhance the reliability in communication between the payment terminal 101 and the payment server 107. Previously, transactions were dependent on direct connection between the payment terminal 101 and the payment server 107. Embodiments of the present disclosure ensures that there are no dropouts during a transaction. In order to reduce the dropouts, the present disclosure adds redundancy in the payment terminal 101, wherein the payment terminal 101 directly sends the transaction requests using the direct mode to the payment server 107 and via least two neighboring user devices until an acknowledgement from the payment server 107 is received asynchronously. Accordingly, the present disclosure provides a more reliable and convenient method for users for payment transactions

Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.

While various aspects and embodiments have been disclosed herein, other aspects and embodiments may be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Referral Numerals:
Reference Number Description
100 Environment
101 Payment terminal
103 P2P network
105 Plurality of user devices
107 Payment server
109 Communication network
200 Data
201 Processor
202 Display unit
203 I/O interface
204 Memory
205 Network data
206 Transaction data
207 Other data
208 Scanning module
209 Network configuration module
210 Transaction initiating module
211 Card reader
212 Receipt printer
213 Communication unit
214 Keypad
301 Processor
303 I/O interface
304 Memory
305 Data
306 Transaction request data
307 Other data
308 Modules
309 Communication module
310 Transaction merging module
311 Other modules
601, 603 Mobile phone
602 User/customer
604 Tablet
606 P2P network
,CLAIMS:We claim:
1. A method for improving data communication reliability in a network during transaction processing, the method comprising:
identifying, by a payment terminal, a plurality of user devices in proximity to the payment terminal;
configuring, by the payment terminal, a Peer-to-Peer (P2P) network using the plurality of user devices in response to receiving an acknowledgment from each of the plurality of user devices for a connection request initiated by the payment terminal;
initiating, by the payment terminal, a transaction by sending a plurality of transaction requests to a payment server, wherein each of the plurality of transaction request is transmitted via a direct connection between the payment terminal and the payment server, and via at least two user devices amongst the plurality of user devices using the P2P network; and
receiving, by the payment terminal, a response for each of the plurality of transaction request from the payment server.

2. The method as claimed in claim 1, wherein identifying the plurality of user devices comprises performing device scanning using predefined techniques.

3. The method as claimed in claim 1 further comprising removing at least one user device of the plurality of devices from the P2P network based on a request from the at least one user device during or post the transaction.

4. The method as claimed in claim 1, wherein the plurality of transaction request is transmitted via at least two user devices on detecting one or more network issues in the direct connection between the payment terminal and the payment server.

5. The method as claimed in claim 1, wherein the plurality of transaction requests transmitted via at least two user devices comprises transaction details associated with a transaction request transmitted using the direct connection between the payment terminal and the payment server.

6. A method for improving data communication reliability in a network during transaction processing, the method comprising:
receiving, by a payment server, a plurality of transaction requests from a payment terminal, wherein each of the plurality of transaction request is received via a direct connection between the payment terminal and the payment server, and via a P2P network formed using at least two user devices amongst a plurality of devices;
in response to the plurality of transaction requests, merging, by the payment server, the plurality of transaction requests as a single transaction request; and
providing, by the payment server, an acknowledgment to the payment terminal for each of the plurality of transaction requests separately.

7. The method as claimed in claim 6, wherein the plurality of transaction requests is merged as the single transaction request based on transaction details associated with each of the plurality of transaction requests.

8. A payment terminal for improving data communication reliability in a network during transaction processing, the payment terminal comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores the processor instructions, which, on execution, causes the processor to:
identify a plurality of user devices in proximity to the payment terminal;
configure a Peer-to-Peer (P2P) network using the plurality of user devices in response to receiving an acknowledgment from each of the plurality of user devices for a connection request initiated by the payment terminal;
initiate a transaction by sending a plurality of transaction requests to a payment server, wherein each of the plurality of transaction request is transmitted via a direct connection between the payment terminal and the payment server, and via at least two user devices amongst the plurality of devices using the P2P network; and
receive a response for each of the plurality of transaction requests from the payment server.

9. The payment terminal as claimed in claim 8, wherein the processor identifies the plurality of user devices by performing device scanning using predefined techniques.

10. The payment terminal as claimed in claim 8, wherein the processor removes at least one user device of the plurality of devices from the P2P network based on a request from the at least one user device during or post the transaction.

11. The payment terminal as claimed in claim 8, wherein the processor transmits the transaction request via at least two user devices on detecting one or more network issues in the direct connection between the payment terminal and the payment server.

12. The payment terminal as claimed in claim 8, wherein the plurality of transaction requests transmitted via at least two user devices comprises transaction details associated with a transaction request transmitted using the direct connection between the payment terminal and the payment server.

13. A payment server for improving data communication reliability in a network during transaction processing, the payment server comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores the processor instructions, which, on execution, causes the processor to:
receive a plurality of transaction requests from a payment terminal, wherein each of the plurality of transaction request is received via a direct connection between the payment terminal and the payment server, and via a P2P network formed using at least two user devices amongst a plurality of devices;
in response to the plurality of transaction requests, merge the plurality of transaction requests as a single transaction request; and
provide an acknowledgment to the payment terminal for each of the plurality of transaction request separately.

14. The payment server as claimed in claim 13, wherein the processor merges the plurality of transaction requests as the single transaction request based on transaction details associated with each of the plurality of transaction requests.