Patent Application
20180357629
This application claims priority to Singapore Application Serial No. 10201704799V, filed Jun. 12, 2017, which is incorporated herein by reference in its entirety.
The present disclosure generally relates to an electronic system and method for distributed payment of a transaction. More particularly, the present disclosure describes various embodiments of an electronic system and method for distributed payment of a transaction between a merchant and a group of customers.
When a group of people or customers visits or patronizes a merchant such as a restaurant, pub, bar, cinema, theme park, or entertainment venue, etc., the merchant provides them with a single consolidated bill of their expenses. Normally, one representative in the group of customers will offer to pay for the consolidated bill and the remaining customers will reimburse the representative with their respective portions of the bill. The remaining customers may pay back the representative in cash, online banking, or through a mobile payment application. The customers will need to calculate the amount of money to return to the representative based on the final amount in the bill and their respective portions. The calculation can be tedious if the respective portions are not identical, such as when the customers purchase different foods in a restaurant. This problem is also accentuated if there are additional taxes to be included, resulting in odd dollars and cents.
There is current no feasible method for everyone in the group of customers to pay the bill unless individual bills are generated, which would pose additional problems for the merchant. Therefore, in order to address or alleviate at least one of the aforementioned problems and/or disadvantages, there is a need to provide an electronic system and method for distributed payment of a transaction, in which there is at least one improved feature.
According to a first aspect of the present disclosure, there is an electronic system, a computerized method, and a non-transitory computer-readable storage medium for distributed payment of a transaction between a merchant and a group of customers. Each customer has an electronic device linked to a payment instrument of the customer, and the method is implemented on a first electronic device of a first customer in the group of customers. The method comprises steps of: receiving, from a server of the merchant, an electronic bill of the transaction, the electronic bill comprising details of a number of billable items; generating a first payment data token comprising details of the payment instrument of the first customer; broadcasting a communication signal for detecting other electronic devices of the group of customers proximate to the first electronic device; receiving, from the electronic devices of one or more other customers in the group of customers, other payment data tokens in response to detection of the electronic devices, the other payment data tokens comprising details of the payment instruments of the one or more other customers; distributing the billable items in the electronic bill among the first and other payment data tokens; generating a distributed electronic bill of the transaction comprising details of the payment instruments from the distributed payment data tokens and a cost payable by each payment instrument; and communicating the distributed electronic bill to the server for subsequent processing of payment from each payment instrument, such that the transaction is collectively payable by the payment instruments corresponding to the distributed payment data tokens.
According to a second aspect of the present disclosure, there is an electronic system, a computerized method, and a non-transitory computer-readable storage medium for distributed payment of a transaction between a merchant and a group of customers. Each customer has an electronic device linked to a payment instrument of the customer. The system comprises a server of the merchant and configured for performing steps of the method, comprising: communicating, to a first electronic device of a first customer in the group of customers, an electronic bill of the transaction, the electronic bill comprising details of a number of billable items; receiving, from the first electronic device, a distributed electronic bill of the transaction, wherein the billable items are distributed among one or more payment data tokens of the customers, each payment data token comprising details of a payment instrument of the customer; communicating, to a payment network, details of the payment instruments from the distributed payment data tokens and a cost payable by each payment instrument for subsequent processing of payment from each payment instrument, wherein the transaction is collectively payable by the payment instruments corresponding to the distributed payment data tokens.
An electronic system and method for distributed payment of a transaction according to the present disclosure is thus disclosed herein. Various features, aspects, and advantages of the present disclosure will become more apparent from the following detailed description of the embodiments of the present disclosure, by way of non-limiting examples only, along with the accompanying drawings.
In the present disclosure, depiction of a given element or consideration or use of a particular element number in a particular figure or a reference thereto in corresponding descriptive material can encompass the same, an equivalent, or an analogous element or element number identified in another figure or descriptive material associated therewith. The use of “I” in a figure or associated text is understood to mean “and/or” unless otherwise indicated. For purposes of brevity and clarity, descriptions of embodiments of the present disclosure are directed to an electronic system and method for distributed payment of a transaction, in accordance with the drawings. While aspects of the present disclosure will be described in conjunction with the embodiments provided herein, it will be understood that they are not intended to limit the present disclosure to these embodiments. On the contrary, the present disclosure is intended to cover alternatives, modifications and equivalents to the embodiments described herein, which are included within the scope of the present disclosure as defined by the appended claims. Furthermore, in the following detailed description, specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be recognized by an individual having ordinary skill in the art, i.e. a skilled person, that the present disclosure may be practiced without specific details, and/or with multiple details arising from combinations of aspects of particular embodiments. In a number of instances, known systems, methods, procedures, and components have not been described in detail so as to not unnecessarily obscure aspects of the embodiments of the present disclosure.
In representative or exemplary embodiments of the present disclosure, there is provided an electronic system 10 as illustrated in
Each customer in the group of customers holds an electronic device 200 that includes or is linked to a payment instrument 202. In a transaction between the merchant and the group of customers, such as paying for dinner at a restaurant or purchase of multiple movie tickets in a cinema, one of the electronic devices 200 (first electronic device 200a) receives an electronic bill of the transaction from the server 100. Communications between the server 100 and the electronic devices 200 occur between a data communication module 100a of the server and a data communication module/component 201a of each electronic device 200. The electronic bill, which is calculated and generated by a bill generation module/component 100b of the server 100, contains a list of the billable items, such as the food items in the dinner or a list of the purchased movie tickets. The electronic bill may be communicated from the server 100 to the first electronic device 200a by displaying a barcode, e.g. QR code, for the first electronic device 200a to read or scan.
Each electronic device 200 includes a tokenization module/component 201b for generating payment tokens that include details of payment instruments 202. After receiving the electronic bill, the first electronic device 200a then generates a first payment token that includes details of the payment instrument 202 of the customer holding the first electronic device 200a (first customer). After receiving the electronic bill, the first electronic device 200a broadcasts a communication signal for detecting other electronic devices 200. When another electronic device 200 is proximate to the first electronic device 200a, i.e. within the broadcast range of the communication signal, a payment token from the other electronic device 200 is communicated to the first electronic device 200a. The other payment tokens include details of the payment instruments 202 of the other customers in the group of customers.
The first customer then uses the first electronic device 200a to distribute the billable items in the electronic bill among the payment data tokens. Particularly, the billable items are allocated to the customers such that each customer is responsible to pay for their rightful portion of the electronic bill. A distributed electronic bill of the transaction is subsequently generated, specifically by a distributed bill generation module/component 201d. As any one of the electronic devices 200 is configurable as the first electronic device 200a, each electronic device 200 includes a token distribution module/component 201c for distributing the billable items in the electronic bill among the payment data tokens, as well as the distributed bill generation module 201d for calculating and generating the distributed electronic bill. The distributed electronic bill is collectively payable by the payment instruments 202 of the group of customers. The first electronic device 200a then communicates the distributed electronic bill, including details of the payment instruments 202 from the payment data tokens, to the server 100 for subsequent processing of payment from each payment instrument 202.
The system 10 includes a payment network 20 communicatively linked to the server 100. The server 100 communicates the details of each payment instrument 202 to the payment network 20 for processing of payment. Specifically, payment from each payment instrument 202 is processed independently such that there are multiple sub-transactions to pay for the electronic bill of this transaction. Each sub-transaction occurs between the merchant and one of the customers, such that all in the group of customers collectively pay for the transaction. Accordingly, payment of the transaction is distributed among the group of customers.
Thus, even though the merchant issues a single bill for the transaction, e.g. dinner or movie tickets, each customer can pay for their own portion of the bill. This obviates the need for one representative customer to pay on behalf of the rest and then having the rest paying back their portions to the representative customer.
As used herein, a “payment network 20” may be exemplarily described as a system network for settling financial transactions. The payment network 20 may be operated by an organization such as a payment card or credit card association, e.g. MasterCard® or Visa®. The payment network 20 connects or links together multiple financial institutions, particularly issuer banks and acquirer banks for processing payment of the transactions between merchants and customers.
As used herein, an “electronic device 200” may be exemplarily described as a mobile device such as a mobile phone, smartphone, personal digital assistant (PDA), tablets, laptop, or computer.
As used herein, an “electronic bill” may be exemplarily described as a statement of money owed to a merchant for products/goods/services supplied by the merchant, wherein the statement is presented in an electronic or digital format.
As used herein, a “payment instrument 202” may be exemplarily described as any suitable cashless payment mode or mechanism, such as payment cards. Payment cards may include credit cards, debit cards, prepaid cards, and/or charge cards which the customer uses to pay for transactions. In addition to payment cards, payment instruments may include, but are not limited to, membership cards, promotional cards, frequent flyer cards, identification cards, gift cards, and/or any other payment cards that may hold payment card information and which may be stored electronically.
As used herein, a “payment data token” may be exemplarily described as a non-sensitive data element that is generated by a tokenization process from a sensitive data element, such as payment instrument details. The “payment data token” functions as a reference or identifier that maps back to the sensitive data element (payment instrument details) through a tokenization system, as will be readily understood by the skilled person. Furthermore, various embodiments describe multiple electronic devices 200, each with its payment instrument 202 and payment data token. For clarity, the first electronic device 200a is associated with the first payment instrument 202a and the first payment data token, and so forth for the other ordinals.
In various embodiments further with reference to
Following on the previous examples, at the end of the dinner or after the ticket details have been finalized, in a step 302 of the method 300, the server 100 of the merchant generates, with the bill generation module 100b, an electronic bill of the transaction. The electronic bill includes details of a number of billable items of the transaction. In the dinner example, the billable items refer to the dishes (e.g. food/drinks/sides/desserts) ordered by the customers and the cost of each dish. In the ticket example, the billable items refer to the tickets purchased by the customers and the cost of each ticket. The electronic bill may further include service charges and/or taxes, e.g. value-added tax (VAT), on top of the total cost of the billable items. Examples of an electronic bill are shown in Tables 1A and 1 B below.
Each customer in the group of customers holds an electronic device 200. Each electronic device 200 includes or is linked to one or more payment instruments 202 of the respective customer, such that the electronic device 200 is configured and operative as a digital wallet and allows the customer to pay for transactions. The digital wallet may be operated on a software application executable on the electronic device 200. An example of a digital wallet is MasterPass® by MasterCard®. Details of the payment instruments 202 may be stored locally on the electronic device 200 or retrieved remotely with the electronic device 200.
With reference to
Although various embodiments are described for five customers with five electronic devices 200, it will be appreciated that there can be any number of customers, i.e. two or more, in the group of customers for distributed payment of a transaction between a merchant and the group of customers.
Referring to
After receiving the electronic bill, a summary of the billable items is displayed on the first electronic device 200a such that the first customer can subsequently distribute the billable items for collective payment by the group of customers. In a step 306, the first customer initiates a function on the first electronic device 200a to generate a payment data token with the tokenization module 201b. The function may be referred to as an “Authorized to Pay” function embedded in a software application or operating system of the first electronic device 200a. The payment data token includes details of the payment instrument of the first customer. For clarity, this payment data token of the first customer is referred to as the first payment data token and includes details of the first payment instrument 202a.
A payment data token may be referred to as a tokenized variant of the corresponding payment instrument 202. Sensitive data elements associated with details of the payment instrument 202 are substituted with a non-sensitive equivalent in the payment data token for secure communication in an encrypted form.
In a step 308, the first electronic device 200a broadcasts or transmits a communication signal with the data communication module 201a for detecting other electronic devices 200 proximate to the first electronic device 200a. The communication signal is continuously or continually broadcasted by the first electronic device 200a and has a limited broadcast range to detect nearby electronic devices 200. Particularly, the communication signal is an active communication signal that searches for other electronic devices 200b/c/d/e of the group of customers.
In a step 310, one of the other electronic devices 200b/c/d/e generates a payment data token with the respective tokenization module 201b, each payment data token including details of the corresponding payment instrument 202b/c/d/e. For example, the second customer initiates an “Authorized to Pay” function on the second electronic device 200b to generate a second payment data token that includes details of the second payment instrument 202b. Like the first payment data token, the second payment data token is a tokenized variant of the second payment instrument 202b for secure communication in an encrypted form.
In a step 312, the other electronic device 200b/c/d/e broadcasts a communication signal with the respective data communication module 201a for detecting electronic devices 200, specifically the first electronic device 200a. To avoid confusion, this communication signal broadcasted from the other electronic device 200b/c/d/e may be referred to as a passive communication signal. In the example of the second electronic device 200b, the second payment data token is carried in the form of a data packet by the passive communication signal broadcasted thereby. When the second customer places the second electronic device 200b close enough to the first electronic device 200a, the active communication signal and passive communication signal are within broadcast range of each other, enabling the first electronic device 200a to detect the second electronic device 200b.
Accordingly, the method 300 includes a step 314 of detecting one of the other electronic devices 200b/c/d/e by the first electronic device 200a, specifically with the data communication module 201a. The detection of the other electronic device 200b/c/d/e by the first electronic device 200a enables both devices to engage each other and become communicative with each other. In a step 316 and using the example of the second electronic device 200b, the second payment data token carried by the passive communication signal is communicated to and received by the data communication module 201a of the first electronic device 200a in response to detection of the second electronic device 200b. Communication between the first electronic device 200a and second electronic device 200b may occur via known contactless/wireless communication protocols, such as Wi-Fi, NFC, or Bluetooth.
The steps 310, 312, 314, and 316 are iterated for each of one or more of the other electronic devices 200b/c/d/e of the group of customers. A step 318 of the method 300 determines whether there is any remaining electronic device 200b/c/d/e that has not communicated the payment data token to the first electronic device 200a. In one embodiment, all five customers in the group of customers share the total cost of the electronic bill. The steps 310, 312, 314, and 316 would be repeated for the second electronic device 200b, third electronic device 200c, fourth electronic device 200d, and fifth electronic device 200e. In another embodiment, one customer, e.g. the fifth customer, in the group of customers is not required to pay, such as because the other customers are giving him/her a treat. The steps 310, 312, 314, and 316 would be repeated for the second electronic device 200b, third electronic device 200c, and fourth electronic device 200d.
Accordingly, if the step 318 determines that there is a remaining electronic device 200b/c/d/e that needs to but has not communicated the payment data token to the first electronic device 200a, the step 318 returns to the step 310 for this remaining electronic device 200b/c/d/e.
Conversely, if the step 318 determines that there is no remaining electronic device 200b/c/d/e, this means that the first electronic device 200a has received all the required other payment data tokens from the other electronic devices 200b/c/d/e and the step 318 proceeds to a step 320 described below. The first electronic device 200a stores a plurality of payment data tokens and each payment data token is associated with the respective payment instrument 202. Notably, the plurality of payment data tokens includes the other payment data tokens as well as the first payment data token generated in the step 306. Each of the other payment data tokens may be valid for a predefined duration as determined by the respective customer with the respective electronic device 200b/c/d/e. Allowing the other payment data tokens to be valid for the predefined duration, or in other words temporarily stored on the first electronic device 200a, prevents the first customer from using (or abusing) the other payment data tokens for other transactions. For example, after the predefined duration (e.g. 60 seconds) lapses, the other payment data tokens are automatically invalidated or erased from the first electronic device 200a.
In the step 320 of the method 300, the first customer uses the first electronic device 200a, specifically the token distribution module 201c, to distribute the billable items in the electronic bill among the plurality of payment data tokens. In one embodiment, each payment data token includes an identifier that is displayed on the first electronic device 200a together with the billable items. The identifier may include an alias of the respective customer that allows the first customer to uniquely identify the other customers and distribute the billable items accordingly.
In one embodiment of the step 320, distributing the billable items includes allocating or assigning each billable item to at least one identifier from the payment data tokens. Following on the dinner and ticket examples above, Tables 2A and 2B below show the allocation of the billable items to the identifiers.
It can be noted from Table 2A that each customer pays for their respective dish and the cost of the billable item “Beer tower” is shared among all five customers. Furthermore, the service charge and tax amounts are automatically calculated and equally shared among all five customers.
It can be noted from Table 2B that the cost of the billable item “Ticket 5” is shared among the first to fourth customers. In other words, the first to fourth customers are treating the fifth customers to the ticket. No billable item is allocated to the identifier of the fifth customer. Alternatively, the fifth electronic device 200e of the fifth customer does not communicate the fifth payment data token to the first electronic device 200a.
It will be appreciated that in another embodiment of the step 320, distributing the billable items includes allocating or assigning each identifier of the customer from the payment data tokens to at least one billable item. Tables 3A and 3B below show the allocation of the identifiers to the billable items.
After the step 320 of distributing the billable times among the plurality of payment data tokens, the first customer, in a step 322, initiates a function on the first electronic device 200a to finalize the distribution and generate a distributed electronic bill of the transaction with the distributed bill generation module 201d. This distributed electronic bill includes details of the payment instruments 202 corresponding to the distributed payment data tokens and the amount or cost payable by each payment instrument 202, such that the transaction is collectively payable by the payment instruments 202.
In a step 324, the first customer uses the first electronic device 200a to communicate the distributed electronic bill to the server 100. Particularly, first electronic device 200a communicates with the server 100 via a merchant terminal. For example, the first customer places the electronic device 200a near the merchant terminal for communicative engagement with the data communication module 201a and by known contactless/wireless communication protocols, such as NFC. The distributed electronic bill is communicated to the server 100 for subsequent processing of payment of the respective amount/cost from each payment instrument 202. Tables 4A and 4B below summarizes the amount payable by each customer with the respective payment instrument 202, including the relevant service charge and tax.
In a step 326, the server 100 communicates, to the payment network 20, details of the payment instruments 202 for subsequent processing of payment from each payment instrument 202. It will be appreciated that the processing of transactions in the payment network 20 is performed in a standard manner and will be readily understood by the skilled person.
The distributed electronic bill of the transaction provides the merchant with details of the payment instrument 202 and the amounts payable by each customer with the payment instruments 202. Payment from each payment instrument 202 is processed independently from one another such that there are multiple sub-transactions to pay for this transaction. In each sub-transaction, the server 100 generates sub-transaction data that includes details of the payment instrument 202a/b/c/d/e and the payable amount to the payment network 20. The server 100 communicates the sub-transaction data of the multiple sub-transactions to the payment network 20 which then processes each sub-transaction in a standard manner. In a step 328, transaction result codes for the sub-transactions are communicated from the payment network 20 to the server 100, which collectively indicate that the total cost of the transaction has been collectively paid by the payment instruments 202 and the transaction is successfully completed.
Therefore, in both the dinner and ticket examples, even though the merchant issues a single bill for the transaction, each customer can pay for their own portion of the bill. This obviates the need for one representative customer to pay on behalf of the rest and then having the rest paying back their portions to the representative customer. Any relevant service fee or tax is automatically calculated so that the customers do not need to manually calculate the exact amount to return to the representative customer. Moreover, each customer can use their own payment instrument, e.g. credit card, to pay for their portion of the bill with the merchant and earn credit card rebates at the same time. The merchant also has an advantage in that the merchant does not need to issue multiple bills for each customer; a single bill can be paid for by payments from the multiple sub-transactions.
The following is a description of the technical architecture of the server 100 with reference to
The technical architecture of the server 100 includes a processor 102 (also referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage 104 (such as disk drives or memory cards), read only memory (ROM) 106, and random access memory (RAM) 108. The processor 102 may be implemented as one or more CPU chips. Various modules or components for performing various operations or steps of the method 300 are configured as part of the processor 102 and such operations or steps are performed in response to non-transitory instructions operative or executed by the processor 102.
The technical architecture further includes input/output (I/O) devices 110, and network connectivity devices 112. The secondary storage 104 typically includes a memory card or other storage device and is used for non-volatile storage of data and as an over-flow data storage device if RAM 108 is not large enough to hold all working data. Secondary storage 104 may be used to store programs which are loaded into RAM 108 when such programs are selected for execution.
The secondary storage 104 has a processing component 114, including non-transitory instructions operative by the processor 102 to perform various operations or steps of the method 300 according to various embodiments of the present disclosure. The ROM 106 is used to store instructions and perhaps data which are read during program execution. The secondary storage 104, the ROM 106, and/or the RAM 108 may be referred to in some contexts as computer-readable storage media and/or non-transitory computer-readable media. Non-transitory computer-readable media include all computer-readable media, with the sole exception being a transitory propagating signal per se.
The I/O devices 110 may include printers, video monitors, liquid crystal displays (LCDs), plasma displays, touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, and/or other known input devices.
The network connectivity devices 112 may take the form of modems, modem banks, Ethernet cards, universal serial bus (USB) interface cards, serial interfaces, token ring cards, fibre distributed data interface (FDDI) cards, wireless local area network (WLAN) cards, radio transceiver cards that promote radio communications using protocols such as code division multiple access (CDMA), global system for mobile communications (GSM), long-term evolution (LTE), worldwide interoperability for microwave access (WiMAX), near field communication (NFC), radio frequency identity (RFID), and/or other air interface protocol radio transceiver cards, and other known network devices. These network connectivity devices 112 may enable the processor 102 to communicate with the Internet or one or more intranets. With such a network connection, it is contemplated that the processor 102 might receive information from the network, or might output information to the network in the course of performing the operations or steps of the method 300. Such information, which is often represented as a sequence of instructions to be executed using processor 102, may be received from and outputted to the network, for example, in the form of a computer data signal embodied in a carrier wave.
The processor 102 executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk based systems may all be considered secondary storage 104), flash drive, ROM 106, RAM 108, or the network connectivity devices 112. While only one processor 102 is shown, multiple processors may be present. Thus, while instructions may be discussed as executed by a processor, the instructions may be executed simultaneously, serially, or otherwise executed by one or multiple processors.
It will be appreciated that the technical architecture of the server 100 may be formed by one computer, or multiple computers in communication with each other that collaborate to perform a task. For example, but not by way of limitation, an application may be partitioned in such a way as to permit concurrent and/or parallel processing of the instructions of the application. Alternatively, the data processed by the application may be partitioned in such a way as to permit concurrent and/or parallel processing of different portions of a data set by the multiple computers. In an embodiment, virtualization software may be employed by the technical architecture to provide the functionality of a number of servers that is not directly bound to the number of computers in the technical architecture. In an embodiment, the functionality disclosed above may be provided by executing the application and/or applications in a cloud computing environment. Cloud computing may include providing computing services via a network connection using dynamically scalable computing resources. A cloud computing environment may be established by an enterprise and/or may be hired on an as-needed basis from a third party provider.
It is understood that by programming and/or loading executable instructions onto the technical architecture of the server 100, at least one of the CPU 102, the ROM 106, and the RAM 108 are changed, transforming the technical architecture in part into a specific purpose machine or apparatus having the functionality as taught by various embodiments of the present disclosure. It is fundamental to the electrical engineering and software engineering arts that functionality that can be implemented by loading executable software into a computer can be converted to a hardware implementation by known design rules.
In the foregoing detailed description, embodiments of the present disclosure in relation to an electronic system and method for distributed payment of a transaction are described with reference to the provided figures. The description of the various embodiments herein is not intended to call out or be limited only to specific or particular representations of the present disclosure, but merely to illustrate non-limiting examples of the present disclosure. The present disclosure serves to address at least one of the mentioned problems and issues associated with the prior art. Although only some embodiments of the present disclosure are disclosed herein, it will be apparent to a person having ordinary skill in the art in view of this disclosure that a variety of changes and/or modifications can be made to the disclosed embodiments without departing from the scope of the present disclosure. Therefore, the scope of the disclosure as well as the scope of the following claims is not limited to embodiments described herein.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10201704799V | Jun 2017 | SG | national |
