BACKGROUND

[0001] In the United States millions of retail transactions occur every day. A user swipes his or her credit card at a point of sale (POS) device at the retailer to purchase an item or provides credit card information to a website for online orders. These types of transactions leave a footprint of the credit card information of the user for unscrupulous individuals to steal. This can lead to fraudulent transactions or identity theft.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] FIG. 1 is a block diagram of an example system of the present disclosure;

[0003] FIG. 2 is an example of an apparatus of the present disclosure;

[0004] FIG. 3 is another example of an apparatus of the present disclosure;

[0005] FIG. 4 is a flow diagram of an example method for matching transaction information for payment from a perspective of a consumer;

[0006] FIG. 5 is a flow diagram of an example method for matching transaction information for payment from a perspective of a retailer;

[0007] FIG. 6 is a flow diagram of an example method for matching transaction information for payment from a perspective of a third party financial service provider; and

[0008] FIG. 7 is a flow diagram of an example method for pre-paying a retailer for an item. DETAILED DESCRIPTION

[0009] The present disclosure discloses a system and method for performing a cash-less and card-less transaction between a consumer and a retailer. The system and method of the present disclosure perform the transaction without leaving any "footprints" of the transaction that can be stolen leading to fraudulent transactions or identity theft.

[0010] In addition, the systems and methods of the present disclosure can be deployed without additional hardware at the retailer. In other words, the retailer can use the existing hardware. The consumer may use his or her mobile endpoint device that has be modified with an application to execute the functions of the method described herein.

[0011] FIG. 1 illustrates an example system 100 of the present disclosure. The system 100 may include a third party financial service provider (TPFSP) 102, a retailer 108 and a consumer 1 16 with an endpoint device 1 14. In one example, the TPFSP 102 may include an application server (AS) 104 and a database (DB) 106. The TPFSP 102 may be a bank, a clearing house, a financial service branch of a retailer, a credit card company, and the like.

[0012] The AS 104 may include a processor and a non-transitory computer readable storage medium for storing instructions to be executed by the processor to perform the functions described herein. The DB 106 may store various information including consumers 1 16 who are customers of the TPFSP 102 and financial account information associated with each consumer 1 16.

[0013] In one example, the retailer 108 may be a brick and mortar retailer or an online retailer and may include a point of sale (POS) device 1 10. The POS device 1 10 may be a cash register/scanning system, a credit card terminal device, a server that hosts a webpage interface for online retailers, and the like. The POS device 1 10 may include a processor and a non-transitory computer readable storage medium for storing instructions to be executed by the processor to perform the functions described herein.

[0014] The POS 1 10 may be able to generate a machine readable code 1 12 that can be scanned by the mobile endpoint device 1 14. In one example, the machine readable code 1 12 may be a quick response (QR) code. The machine readable code 1 12 may contain transaction information associated with an item or service that is purchased by the consumer 1 16. The transaction information may include a store identification (e.g., a store name, a store number, and the like), a transaction identification (e.g., a unique numerical value associated with a particular transaction), an amount (e.g., a total amount of the transaction), and the like.

[0015] In some implementations, the machine readable code 1 12 may be generated on a printed receipt. In other implementations, the machine readable code 1 12 may be generated and displayed on a display of the POS device 1 10. In other examples, the machine readable code 1 12 may be displayed on a check out webpage of an online transaction.

[0016] In one example, the consumer 1 16 uses the endpoint device 1 14 to scan the machine readable code 1 12 to complete a transaction. The endpoint device 1 14 may be a mobile endpoint device, such as for example, a smart phone, a tablet computer, a lap top computer, and the like. In some

implementations where the endpoint device 1 14 is unable to scan the machine readable code 1 12, the machine readable code 1 12 may be verbally provided or manually input into the endpoint device 1 14. For example, the machine readable code 1 12 may include a numerical code or bar code that has a numerical value that can be read or typed into the endpoint device 1 14.

[0017] In one example, the endpoint device 1 14 may have a camera to capture the machine readable code 1 12 and a global positioning system (GPS) radio or receiver to track a location of the endpoint device 1 14. The endpoint device 1 14 may also be modified to execute an application issued by the TPFSP 102 to perform the cash-less/card-less transaction. The application may register the consumer 1 16 with a log in and password information that are stored in the DB 106 of the TPFSP 102.

[0018] In one implementation, the application on the endpoint device 1 14 may decipher the transaction information contained in the machine readable code 1 12. The application on the endpoint device 1 14 may then send the deciphered transaction information along with a GPS location of the endpoint device 1 14 and a user identification (e.g., obtained from the log in to the application) to the TPFSP 102. In one example, the application on the endpoint device 1 14 may encrypt the transmission. The transaction information may be transmitted via either a wired or wireless communication over the Internet 150.

[0019] In parallel, the retailer 108 may send transaction information to the TPFSP 102. For example, the consumer 1 16 may select an option for a cashless/card-less transaction on the POS device 1 10. The consumer 1 16 may provide a name of the TPFSP 102 and the POS device 1 10 may send a wired or wireless communication containing the transaction information to the TPFSP 102. In one example, the transaction information sent by the retailer 108 may include financial account information associated with the retailer 108 to receive funds or payment (e.g., an account number and a routing number for electronic payment), a store identification, a store location, a transaction identification and an amount.

[0020] In one implementation, if the transaction is an online purchase via a website, the store location information may be a virtual location. For example, the store location may be the location of the endpoint device 1 14 of the consumer 1 16. For example, the retailer 108 may know the location of the endpoint device 1 14 of the consumer 1 16 via an internet protocol (IP) address of the endpoint device 1 14. In another example, the store location may be a home address of the consumer 1 16 based upon log in information of the consumer 1 16 to an online webpage of the retailer 108. Otherwise, for a brick and mortar or physical retailer 108, the store location may be a GPS location of the retailer 108 or an address.

[0021] The TPFSP 102 may then compare the transaction information received from the endpoint device 1 14 and the retailer 108 to determine if the transaction information matches. For example, the TPFSP 102 may determine whether the GPS location of the endpoint device 1 14 and the store location information match within a threshold (e.g., within 100 feet of the estimated location of the endpoint device 1 14 and the store location address, within 10 degrees of the GPS coordinates of the endpoint device 1 14 and the store location, and the like). The TPFSP 102 may determine whether the transaction I D and the amount received from the endpoint device 1 14 and the retailer 108 match, and so forth.

[0022] If the transaction information from the endpoint device 1 14 and the transaction information from the retailer 108 match, then the TPFSP 102 may transfer funds from a financial account of the consumer 1 16 to a financial account of the retailer 108. The TPFSP 102 may then send a confirmation to the endpoint device 1 14 and the POS device 1 10 indicating that the transaction is completed. The consumer 1 16 may then take the items or receive the services from the retailer 108.

[0023] Notably, during the transaction described above, the consumer 1 16 does not provide information to the retailer 108. The retailer receives no personal or financial account information from the consumer 1 16 to complete the transaction. In addition, the transaction described can be implemented using existing hardware of the retailer 108.

[0024] Furthermore, the transaction described above provides no motivation for an unscrupulous user to try and steal or intercept the machine readable code 1 12. For example, if another user captured the machine readable code 1 12 via his or her device, the user would be log in to his or her own TPFSP 102 and pay for the items instead of the consumer 1 16.

[0025] In one illustrative scenario, a consumer 1 16 may be forced by a thief to scan the machine readable code 1 12 using the endpoint device 1 14 of the consumer. However, in one example a user defined distress signal may be transmitted that indicates the transaction information is being transmitted under distress. For example, the distress signal may be a pre-defined keystroke pattern or numerical code that is entered in the application. The distress signal would notify the TPFSP 102 to cancel the transaction and allow the TPFSP 102 to contact authorities (e.g., the police) to the location of the transaction (e.g., based on the store location information that was received in the transaction information or the GPS location of the endpoint device 1 14 that was received).

[0026] In some implementations, an amount threshold may be assigned to each fingerprint to prevent inadvertent transactions. For example, the endpoint device 1 14 may have a fingerprint sensor that can identify the fingerprint of different fingers of the consumer 1 16. A thumb may be assigned to a limit of $50, the index finger may be assigned a limit of $100, and so forth. The consumer 1 16 may transmit the transaction information to the TPFPS 102 with a confirmation of an index finger fingerprint scan on the endpoint device 1 14. The consumer 1 16 may have believed the total purchase was for $79. However, the total may have been for $790. The TPFSP 102 may deny the transaction since the consumer 1 16 authorized a transaction limit of $100.

[0027] In some implementations, the system 100 may also be used to prepay for items or services sold by the retailer 108. For example, the consumer 1 16 may send a request to the TPFPS 102 for pre-payment to the retailer 108 via the endpoint device 1 14. The request may include a name of the retailer 108, the location of the retailer 108, an amount, and the like.

[0028] The TPFPS 102 may transfer funds from the financial account of the consumer 1 16 to the financial account of the retailer 108 per the request. The TPFPS 102 may then generate and transmit a machine readable code (e.g., a QR code) to the endpoint device 1 14 that includes confirmation of the prepayment to the retailer 108.

[0029] The consumer 1 16 may then display the machine readable code to the retailer 108 so that the retailer 108 can scan and decipher the machine readable code (e.g., using a scanner that is part of the POS device 1 10).

Alternatively for an online transaction, the consumer 1 16 may electronically transmit the machine readable code to the retailer 108. The retailer 108 may read the confirmation in the machine readable code and provide the items or services to the consumer 1 16.

[0030] FIG. 2 illustrates an example of an apparatus 200. In one example, the apparatus may be the endpoint device 1 14. In one example, the apparatus 200 may include a processor 202 and a non-transitory computer readable storage medium 204. The non-transitory computer readable storage medium 204 may include instructions 206, 208, 210 and 212 that when executed by the processor 202, cause the processor 202 to perform various functions.

[0031] In one example, the instructions 206 may include instructions to receive a machine readable code generated by a party (e.g., a retailer) that includes transaction information. The instructions 208 may include instructions to decipher the transaction information from the machine readable code. The instructions 210 may include instructions to transmit the transaction information to a third party (e.g., a third party financial service provider). The instructions 212 may include instructions to receive a confirmation that payment has been made to the party for a transaction based upon a match of the transaction information to additional transaction information that was sent from the party to the third party.

[0032] FIG. 3 illustrates another example of an apparatus 300. In one example, the apparatus 300 may also be the endpoint device 1 14. In one example, the apparatus 300 may include a processor 302 and a non-transitory computer readable storage medium 304. The non-transitory computer readable storage medium 304 may include instructions 306, 308 and 310 that when executed by the processor 302, cause the processor 302 to perform various functions.

[0033] In one example, the instructions 306 may include instructions to send a request to a third party (e.g., a third party financial service provider) for prepayment to a party (e.g., a retailer). The instructions 308 may include instructions to receive a machine readable code containing confirmation of the pre-payment to the party. The instructions 310 may include instructions to display the machine readable code to be scanned by the party indicating that the pre-payment was sent to the party for at least one item for purchase.

[0034] FIG. 4 illustrates a flow diagram of an example method 400 for matching transaction information for payment from a perspective of a consumer. In one example, the blocks of the method 400 may be performed by the endpoint device 1 14 or the apparatus 200.

[0035] At block 402, the method 400 begins. At block 404, the method 400 receives a machine readable code generated by a party (e.g., a retailer) that includes transaction information. In one example, the machine readable code may be a QR code that is scanned by the endpoint device of the consumer from a receipt, a display of a POS device of the retailer, from a checkout webpage for an online transaction with the retailer, and the like. The transaction information may include a store identification (e.g., a store name, a store number, and the like), a transaction identification (e.g., a unique numerical value associated with a particular transaction), an amount (e.g., a total amount of the transaction), and the like.

[0036] At block 406, the method 400 deciphers the transaction information from the machine readable code. For example, an application on the endpoint device of the consumer may obtain the transaction information from the QR code that was scanned.

[0037] At block 408, the method 400 transmits the transaction information to a third party (e.g., a third party financial service provider). In one example, the transaction information transmitted by the endpoint device of the consumer may include the transaction information that was deciphered from the scanned QR code and additional information (e.g., a GPS location of the endpoint device of the consumer, a user ID of the consumer, and the like). In some

implementations, the transmission may be a wired or wireless transmission over the Internet and can be encrypted for security.

[0038] At block 410, the method 400 receives a confirmation that payment has been made to the party for a transaction based upon a match of the transaction information to additional transaction information that was sent from the party to the third party. For example, the retailer may also send transaction information to the third party financial service provider associated with the transaction. The third party financial service provider may compare the received transaction information to determine that the transaction information matches (e.g., within a threshold value for some transaction information). If the transaction information matches, the third party financial service provider may transfer funds from a financial account associated with the consumer to a financial account associated with the retailer and send the confirmation that the funds have been transferred. At block 412, the method 400 ends.

[0039] FIG. 5 illustrates a flow diagram of an example method 500 for matching transaction information for payment from a perspective of a retailer. In one example, the blocks of the method 500 may be performed by the POS device 1 10 at the retailer 108.

[0040] At block 502, the method 500 begins. At block 504, the method 500 scans at least one item selected for purchase by a party (e.g., a consumer). For example, the item or services can be scanned by the POS device or selected for an online transaction where the POS device is a website that hosts the webpage.

[0041] At block 506, the method 500 generates a machine readable code that includes transaction information for the at least one item. For example, the machine readable code may be a QR code. The machine readable code that is generated may be printed on a receipt, displayed on a display of the POS device, or displayed on a webpage of an online transaction such that the machine readable code can be scanned by an endpoint device of the consumer. In some implementations, the machine readable code may be electronically, or wirelessly, transmitted to the endpoint device.

[0042] At block 508, the method 500 transmits the transaction information to a third party (e.g., a third party financial service provider). In one example, the transaction information sent by the retailer may include a store identification, a store location, a transaction identification, an amount, and the like. The transaction information may also include financial account information associated with the retailer to receive fund or payment.

[0043] At block 510, the method 500 receives a confirmation that payment has been received for the at least one item based upon a match of the transaction information to scanned transaction information that was sent from an endpoint device of the party to the third party. For example, the consumer may also send transaction information to the third party financial service provider associated with the transaction. The third party financial service provider may compare the scanned transaction information from the consumer to determine that the transaction information matches (e.g., within a threshold value for some transaction information). If the transaction information matches, the third party financial service provider may transfer funds from a financial account associated with the consumer to a financial account associated with the retailer and send the confirmation that the funds have been transferred. At block 512, the method 500 ends.

[0044] FIG. 6 illustrates a flow diagram of an example method 600 for matching transaction information for payment from a perspective of a third party financial service provider. In one example, the blocks of the method 600 may be performed by the AS 104 at the TPFSP 102.

[0045] At block 602, the method 600 begins. At block 604, the method 600 receives transaction information from a mobile endpoint device of a first party (e.g., a consumer). For example, the consumer may scan a machine readable code generated by a POS device of the retailer with an endpoint device. The endpoint device may decipher the machine readable code to obtain the transaction information and transmit the transaction information to the third party financial service provider.

[0046] At block 606, the method 600 receives additional transaction information from a second party (e.g., a retailer). For example, the retailer may transmit transaction information to the third party financial service provider independent from the consumer after all items are scanned or all services are rendered.

[0047] At block 608, the method 600 determines that the transaction information matches the additional transaction information. For example, the transaction information from the consumer may include a GPS location of the endpoint device, a store identification, a transaction identification, an amount, and the like. The transaction information from the retailer may include a store identification, a store location, a transaction identification, an amount, and the like. The third party financial service provider may compare each portion of the transaction information from the consumer and the retailer to confirm that each portion of the transaction information from the consumer and the retailer matches. In some implementations, threshold values may be used to provide some tolerance from an exact match. For example, the GPS location of the endpoint device and the store location may not be an exact match, but rather within a predefined threshold value.

[0048] At block 610, the method 600 transfer funds from the first party to the second party. For example, when the transaction information from the consumer and the additional transaction information from the retailer matches, the third party financial service provider may transfer funds. The transfer of funds may be from a financial account associated with the consumer to a financial account associated with the retailer.

[0049] At block 612, the method 600 may send a confirmation that payment has been transferred to the endpoint of the first party and the second party. For example, a confirmation may be sent to the endpoint device of the consumer and another confirmation may be sent to the POS device of the retailer. The confirmation may be sent via a wired or wireless connection. At block 614, the method 600 ends.

[0050] FIG. 7 illustrates a flow diagram of an example method 700 for prepaying a retailer for an item. In one example, the blocks of the method 700 may be performed by the endpoint device 1 14 or the apparatus 300.

[0051] At block 702, the method 700 begins. At block 704, the method 700 sends a request to a third party (e.g., a third party financial service provider) for pre-payment to a party (e.g., a retailer). The request may include a name of the retailer, the location of the retailer, an amount, and the like. In one

implementation, the third party service provider may contact the retailer to obtain financial account information of the retailer. The amount associated with the request for pre-payment may be transferred from a financial account associated with the consumer to the financial account associated with the retailer.

[0052] At block 706, the method 700 receives a machine readable code containing a confirmation of the pre-payment to the party. For example, the machine readable code may be a QR code.

[0053] At block 708, the method 700 displays the machine readable code to be scanned by the party indicating that the pre-payment was sent to the party for at least one item for purchase. For example, the retailer may scan and decipher the machine readable code to see that the pre-payment was confirmed. The items or services may then be provided to the consumer. At block 710, the method 700 ends.

[0054] It will be appreciated that variants of the above-disclosed and other features and functions, or alternatives thereof, may be combined into many other different systems or applications. Various presently unforeseen or unanticipated alternatives, modifications, variations, or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the following claims.