Point of sale system

Abstract
A point-of-sale system is a dual-screen stand assembly that includes a merchant terminal and a consumer terminal. The merchant terminal and the consumer terminal can be mated together in a fixed position to form a single unitary stand, or can be separated from each other in a separated position with each terminal serving as its own separate stand. The merchant terminal supports a merchant computing device and is oriented in a merchant-facing direction. The consumer terminal is detachably mated to the merchant terminal and supports a consumer computing device that is oriented in a consumer-facing direction. The point-of-sale system also includes a card reader as part of the customer terminal to perform a payment. The card reader is configured to accepting swipe cards, chip cards or contactless (EMV or NFC) payments.
Description
BACKGROUND

Consumers can interact with merchants to conduct various financial payment transactions. For example, a consumer can conduct a transaction with a merchant at a point-of-sale system using cash, a transaction card, or other transaction instrument. Conventional systems can include expensive and bulky specialized equipment and financial transaction electronics, as may include a card reader for payment cards (e.g., debit or credit cards), a cash drawer, monitors, keyboards, and various other electronic devices. Oftentimes, however, this equipment can be costly and large, requiring additional space and resources. Further, in retail stores where space is limited, a merchant may not require all components that come with a conventional point-of-sale system or at least may find it desirable to piece together a modular or mobile system to streamline the checkout experience. Further still, merchants may find approaches to conducting a financial transaction using conventional systems burdensome, where during a transaction, if a customer pays by credit card, the merchant has to enter a transaction amount and the merchant or the customer has to swipe the credit card in the card reader. Further, many transactions require that the customer sign a physical receipt, electronically approve a transaction, e.g., by pressing an approve button on a user interface, electronically sign for the transaction, e.g., with a stylus or finger on an electronic signature capture device with a touch sensitive pad, or enter an authorizing personal identification number (PIN), many of which techniques require additional financial transaction electronics and time.





BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which features of the disclosure can be obtained, a more particular description of the principles will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:



FIG. 1 illustrates an example block diagram showing a first terminal and a second terminal used in a point-of-sale system in accordance with various embodiments;



FIG. 2 illustrates an example schematic diagram of components of each terminal in the point-of-sale system in accordance with an embodiment;



FIG. 3 illustrates an example process for conducting a financial payment transaction in accordance with various embodiments;



FIG. 4 illustrates an example diagram of flow of data between the components of the point-of-sale system in accordance with an embodiment;



FIG. 5 illustrates an example point-of-sale system as viewed from a front perspective view, including a first terminal and a second terminal that are detachably mated together and shown in a fixed position, in accordance with an embodiment;



FIG. 6 illustrates the example point-of-sale system of FIG. 5 as viewed from a back perspective view, in accordance with an embodiment;



FIG. 7 illustrates the example point-of-sale system of FIG. 5 as viewed from the back perspective view, and showing the second terminal being separated from the first terminal, in accordance with an embodiment;



FIG. 8 illustrates the example point-of-sale system of FIG. 5 as viewed from a side perspective view and showing the second terminal completely separated from the first terminal, in accordance with an embodiment;



FIG. 9 illustrates another example point-of-sale system as viewed from a front perspective view, including a first terminal and a second terminal that are detachably mated together and shown in a fixed position, in accordance with an embodiment;



FIG. 10 illustrates the example point-of-sale system of FIG. 9 as viewed from a back perspective view, in accordance with an embodiment;



FIG. 11 illustrates the example point-of-sale system of FIG. 9 as viewed from the back perspective view, and showing the second terminal being separated from the first terminal, in accordance with an embodiment;



FIG. 12 illustrates the example point-of-sale system of FIG. 9 as viewed from a side perspective view and showing the second terminal completely separated from the first terminal with the point-of-sale system in a separated position, in accordance with an embodiment;



FIG. 13 illustrates another example point-of-sale system as viewed from a front perspective view, including a first terminal and a second terminal that are detachably mated together and shown in a fixed position, in accordance with an embodiment;



FIG. 14 illustrates the example point-of-sale system of FIG. 13 as viewed from a back perspective view, in accordance with an embodiment;



FIG. 15 illustrates the example point-of-sale system of FIG. 13 as viewed from a side perspective view and showing the second terminal completely independent from the first terminal, in a separated position in accordance with an embodiment;



FIG. 16 illustrates the example point-of-sale system of FIG. 13 as viewed from the back perspective view and showing the second terminal completely independent from the first terminal, in accordance with an embodiment;



FIG. 17 illustrates another example point-of-sale system as viewed from a front perspective view showing a first terminal and including a second terminal not visible in FIG. 17 that is detachably mated to the first terminal, in accordance with an embodiment;



FIG. 18 illustrates the example point-of-sale system of FIG. 17 as viewed from a side perspective view showing the first terminal with the second terminal detachably mated thereto, in accordance with an embodiment;



FIG. 19 illustrates the example point-of-sale system of FIG. 17 as viewed from a rear perspective view with the second terminal detachably mated to the first terminal, in accordance with an embodiment;



FIG. 20 illustrates the example point-of-sale system of FIG. 17 as viewed from a rear perspective view, with the second terminal separated from the first terminal in a separated position, in accordance with an embodiment;



FIG. 21 illustrates the example point-of-sale system of FIG. 17 as viewed from a side perspective view with the second terminal and the first terminal in the separated position, in accordance with an embodiment;



FIG. 22 illustrates another example point-of-sale system as viewed from a front perspective view with a first terminal detachably mated to a second terminal, and shown in a fixed position, in accordance with an embodiment;



FIG. 23 illustrates the example point-of-sale system of FIG. 22 as viewed from a rear perspective view, in accordance with an embodiment;



FIG. 24 illustrates the example point-of-sale system of FIG. 22 as viewed from a front perspective view with the first terminal separated from and completely independent of the first terminal, shown in a separated position, in accordance with an embodiment;



FIG. 25 illustrates the example point-of-sale system of FIG. 22 as viewed from a rear perspective view with the first terminal and the second terminal shown in the separated position, in accordance with an embodiment;



FIG. 26 illustrates another example point of sale system as viewed from a front perspective view with a first terminal detachably mated to a second terminal, and shown in a fixed position, in accordance with an embodiment;



FIG. 27 illustrates the example point-of-sale system of FIG. 26 as viewed from a rear perspective view, in accordance with an embodiment;



FIG. 28 illustrates the example point-of-sale system of FIG. 26 as viewed in partial cut-out detailing the card reader and showing a payment card inserted in the card reader, in accordance with an embodiment;



FIG. 29 illustrates the example point-of-sale system of FIG. 26 as viewed from a rear perspective view with the first terminal separated from and completely independent of the first terminal, shown in a separated position, in accordance with an embodiment;



FIG. 30 illustrates the example point-of-sale system of FIG. 26 as viewed from a side perspective view with the first terminal and the second terminal shown in the separated position, in accordance with an embodiment;



FIG. 31 illustrates an example environment for conducting a financial payment transaction in accordance with an alternate embodiment; and



FIG. 32 illustrates an example environment for implementing a merchant payment system.





DETAILED DESCRIPTION

Systems and methods in accordance with various embodiments of the present disclosure overcome one or more of the above-referenced and other deficiencies in conventional approaches to conducting financial transactions. In particular, in accordance with various embodiments, approaches provide for a point-of-sale system configured to enhance financial transactions by streamlining and simplifying components needed in performing a financial transaction. The point-of-sale system includes a secure enclave for accurately receiving and handling secure data provided into the point-of-sale system.


For example, in accordance with various embodiments, the point-of-sale system is a dual-screen stand assembly that includes a merchant terminal and a consumer (or “customer” as used interchangeably herein) terminal. The merchant terminal and the consumer terminal can be mated together in a fixed position to form a single unitary point of sale system including a merchant facing terminal and a consumer facing terminal, or terminals can be separated from each other and arranged in a separated position with each terminal being physically independent of the other. The merchant terminal supports a merchant computing device and is oriented in a merchant-facing direction. The consumer terminal is detachably mated to the merchant terminal and supports a consumer computing device that is oriented in a consumer-facing direction. The point-of-sale system also includes a card reader as part of the customer terminal to perform a payment. The card reader is configured to acceptswipe cards, chip cards (Europay, MasterCard and Visa hereinafter “EMV”) or contactless (low power bluetooth or near-field communication, hereinafter “NFC”) payments.


The point-of-sale system is configured to present an interface to the merchant terminal. Information regarding an item for sale or a service being provided is received at the merchant terminal. The information is then sent to the consumer terminal and a check-out procedure is initiated. The payment total is sent to the consumer terminal and a payment card can be inserted into the consumer terminal. The consumer terminal has a display that is specific to the type of payment card used so that when a swipe card is inserted, the display provides the appropriate signature, and when a chip-type card is inserted, an appropriate PIN display is provided on the consumer terminal. A secure enclave can be provided to securely store entries that are, for example, entered into a secure enclave of a portable computing device at the consumer terminal. Payment information acquired from the payment card, and the appropriate verification thereof, is provided to a payment system. Payment confirmation is received from the payment system, which can be displayed on one or both of the merchant terminal and the consumer terminal.


Other advantages, variations, and functions are described and suggested below as may be provided in accordance with the various embodiments. Reference is now made to FIG. 1 illustrating an example point-of-sale system 100 including a first terminal 110 including a first computing device 115 (e.g., a tablet computer, a mobile phone, etc.). The computing device can be integrally provided as a component of the first terminal to form a unitary structure or a computing device provided by a manufacturer that is separately provided and inserted into the terminal by the appropriate user. The computing device can include, for example, a processor, a touch-screen display, and a wireless local area network receiver, a physical interface for electronic communication, and a physical interface to receive power (which can be integrated with the physical interface for electronic communication, e.g., in a Universal Serial Bus (USB) connector or other proprietary connector). The first terminal 110 is detachably mated to a second terminal 120.


The computing device can run a merchant application or other financial transaction software that can provide functionality to facilitate a point-of-sale such as by enabling payment transactions. For example, in accordance with various embodiments, the merchant application can be downloaded and installed on the computing device. The software can be configured to operate with a card reader, where an individual can complete a financial transaction by swiping a magnetic stripe card through the card reader or dipping a chip-type card into the card reader that is connected to the computing device. In this example, the financial transaction can be any transaction that involves receiving or sending payment from one person or entity to another. The magnetic stripe card can be, for example, a credit card, a debit card, or other types of payment authenticating pieces having a magnetic stripe storing information sufficient to carry out the financial transaction. In accordance with various embodiments, the card reader can be integrated into the consumer terminal to allow the consumer to properly provide the payment card. However, in some embodiments, a separate card reader can be used, such as a miniaturized card reader that is easily connectable to the computing device.


The first terminal 110 and second terminal 120 can be in communication with each other via wired or wireless link. In this example, the first terminal 110 represents a terminal used by a merchant conducting a transaction at a point-of-sale system with a consumer using, for example, a payment card via the second terminal 120. It is noted that although a payment card is used in some embodiments, transactions can also be conducted through a card-less payment account that is linked to the payment card. Other transactions include person-to-person, account-to-account, electronic cash, among others. It should be further noted that although a credit card is shown to conduct transactions, approaches described herein apply to other types of financial payment instruments including, for example, debit cards, chip-type cards, and card-less payment accounts. As described, in conventional point-of-sale systems, the equipment can be costly and large, requiring additional space and resources. Further, in retail stores where space is limited, a merchant may find it less desirable to have such a large system. Accordingly, in accordance with various embodiments, approaches provide for a streamlined point-of-sale system with a merchant terminal and a consumer terminal detachably mated from the merchant terminal. It is further desirable to securely process and store entries securely entered into the consumer terminal.


The second terminal 120 supports a second computing device 122. The second computing device 122 is shown integrally formed within the second terminal 120 to provide a single one-piece structure. In some embodiments, another tablet provided separately by the same or another manufacturer, can be inserted into the second terminal 120. The second terminal 120 includes a secure enclave 124 for securely processing and storing entries into the second terminal 120, as described in greater detail herein. The second terminal 120 also includes a card reader 126 configured to read both magnetic swipe cards and chip-type cards. Although shown here as a single hybrid slot capable of reading both card types, two readers, in the form of two separate slots, can be provided with one “swipe” slot for receiving a magnetic swipe-type card and a “dip” slot for receiving a chip-type card.


Reference is now made to FIG. 2 illustrating an example schematic diagram of components of each terminal in the point-of-sale system in accordance with an embodiment. The point-of-sale system 200 includes a merchant terminal 210 and a consumer terminal 212. The merchant terminal 210 includes a SoC (System-on-chip) processor 220 and associated flash memory 222 and RAM 224. A USB-A port 226 is provided for connecting other devices or components to the merchant terminal 210 as appropriate. A USB+Power port 228 is provided connected to a 5-port USB Hub 230 for various peripherals associated with a point-of-sale system, including a receipt printer, cash drawer, barcode scanner, scale, keyboard, USB-ethernet dongle/USB mifi, and other point-of-sale peripheral components known in the art. While both a USB-A port and a USB+Power port are separately identified, such should not be considered limitation. Merchant terminal can have any number of USB ports, and the ports can be of any suitable characteristics. A power supply 232 can be provided as power through the hub H3230 via connector 228 on the merchant terminal 210. A debug module 236 is provided for appropriate debugging of the merchant terminal 210 and the various components thereof. An audio amplifier 238 is provided and a speaker 240 for providing the appropriate audio for the merchant terminal 210. A display 242 can be connected to the processor 220, for example a 13.3-inch LDC display having a resolution of 1920×1080 IPS 166 PPI. The display 242 provides the interfaces and outputs to the merchant terminal 210 to be viewed by a merchant. A wifi receiver 244 is in communication with the processor 220 to perform the wireless communication, for example, with the consumer terminal and other point-of-sale system components, or for example a payment system. And a USB port 246 is provided for detachably connecting the merchant terminal 210 to the consumer terminal 212. The term “detachably” is intended to refer to the ability for the merchant terminal to be connected to the consumer terminal but also configured to being detached from the consumer terminal when desired for storage, upgrades, or other uses. This mating between the terminals can be through wired connections shown or wirelessly, in some embodiments.


The consumer terminal 212 includes a SoC processor 250 connected to the micro USB 252 for communication with the merchant terminal 210. A Power Management Integrated Circuit (PMIC) 254 is in communication with the micro USB connector 252. A PMIC is an integrated circuit for managing power requirements of the host system. A debug module 256 is provided for the processor 250 for the appropriate debugging of the consumer terminal 212 and the various components thereof. The processor 250 is coupled to flash memory 258 and RAM 260 for appropriate storage and processing of data. An audio amplifier 262 and speaker 264 is provided for any audio for the customer on the customer terminal 212. A display 266 is provided, such as a 7-inch LCD touch-screen display having a resolution of 1280×800 IPS 216 PPI. The display 266 provides interfaces and the outputs of the point-of-sale system to the consumer terminal 212. A secure enclave 270 is included in the consumer terminal 212. The secure enclave includes a secure MCU 272, an anti-tamper battery 274, and a secure debug module 276. The MCU 272 receives inputs from the Magnetic Stripe Reader (MSR) 278 which are read by a magnetic head reader 280. Inputs are also received from EMV contact 282 and processed by an EMV contact block 284. Inputs from a contactless EMV are received from an EMV contactless antenna 288 and processed by the EMV contactless block 286. The contactless antenna 288 is dual-use in some embodiments, and configured to receive input from EMV cards and NFC (near field communication) cards, as well as other NFC devices, such as smart phones or other devices configured to process payment transactions. All inputs received by the consumer terminal at the touch controller 292 (for example, as entries into a payment application or a register-buddy application in communication with the merchant terminal), are sent to the secure enclave and the multiplexer 290 determines if the entries should go directly to the non-secure processor, or if further processing (for example, encryption) is needed, and the entries are sent to secure processor. A multiplexer 290 receives inputs from a touch controller 292 and directs inputs received in a non-secure portion of the GUI to the non-secure processor, and directs inputs received in a secure portion of the GUI to the secure processor. In some embodiments, the main processor on the merchant terminal and the consumer terminal will each run their own operating system (including possibly two different copies of the same operating system, different versions of the same operating system, or different operating systems altogether, etc.).


In an embodiment, a point-of-sale system is used in performing a point-of-sale transaction between a merchant and a consumer. The system includes a merchant terminal including a first display that is oriented in a merchant-facing direction. The merchant terminal further includes: non-transitory computer readable instructions that when interpreted by a merchant terminal processor causes the merchant terminal processor to display a series of screens in a merchant facing graphical user interface for guiding a merchant through a point of sale transaction, a first merchant terminal communication interface configured to communicate with a financial transaction server, and a second merchant terminal communication interface configured to communicate with a consumer terminal. The system also includes a consumer terminal including a second display that is oriented in a consumer-facing direction. The consumer terminal further includes electronics in a physically secure area and electronics in a non-secure area. The electronics in the non-secure area include: non-transitory computer readable instructions that when interpreted by a non-secure consumer terminal processor causes the non-secure consumer terminal processor to display a series of screens in a consumer facing graphical user interface for guiding a consumer through a point of sale transaction, and a consumer terminal communication interface configured to communicate with the merchant terminal. The electronics in the physically secure area include: an input controller within the secure area configured to receive consumer inputs received in the consumer facing graphical user interface, and a secure processor within the secure area configured to receive consumer inputs from the input controller, to encrypt the inputs, and to send the inputs to the non-secure consumer terminal processor for transmission of the encrypted inputs using the consumer terminal communication interface. The merchant terminal configured to receive the encrypted data over the second merchant terminal communication interface, and transmit the encrypted data to the financial transaction server over the first merchant terminal communication interface.



FIG. 3 illustrates an example process for conducting a financial payment transaction in accordance with various embodiments. In the example process 300, a merchant interface is presented 310 and information regarding an item or a service being purchased is received 312. Information is sent to a consumer terminal 314 and a check-out procedure is initiated 316. The payment total is sent to the consumer terminal 318 (for example, displayed on display 266) and the payment card is received in the consumer terminal 320. The type of card (swipe, EMV, NFC, etc) being used is determined 322. A payment interface is presented to the consumer on the consumer terminal based upon the type of payment card used. Accordingly, for example, if a magnetic-stripe swipe-type card is used, then 324 an interface is presented to the user to allow for signature entry, and if a chip-type card is used, then 326 an interface is presented to the user to allow for PIN entry or other secure verification of the use of the card. Payment information is provided to a payment system 328 and a payment confirmation is received at 330. This can occur via Wifi (244) or direct connection via USB (for example 228 in FIG. 2) in some embodiments. Note that the payment confirmation could also be a confirmation that the payment has been denied. The merchant interface is notified of the completed transaction 332. The consumer interface can also be notified of the completed transaction in some embodiments.



FIG. 4 illustrates an example diagram of flow of data between the components of the point-of-sale system in accordance with an embodiment. The flow of data between the merchant terminal 410, the consumer terminal 412 and the payment system 414 are shown. The consumer terminal 412 includes the flow of data to and from both the non-secure processor 416 and the secure processor 418. The non-secure processor 416, for example, can be the processor 250 of FIG. 2, and the secure processor, for example, can be the secure MCU 272 in FIG. 2.


In accordance with the example diagram, a merchant interface is presented 420 at the merchant terminal 210. The item or service information is received 422 at the merchant terminal 410 and then provided to the non-secure processor 416 to display the information 424 on the consumer terminal 412. The check-out procedure 426 is initiated by the merchant terminal 410 once all items and/or services have been entered. The payment total 428 is then provided to the non-secure processor 416 to be displayed on the consumer terminal 412. A payment card is received 430 and the type of card is determined 432. If the payment card is an EMV card, the payment information is encrypted 434 by the secure processor 418. The encrypted payment information 404 is then sent to the non-secure processor 416 to be provided either directly 440 to the payment system 414, or indirectly send the payment information 438 via the merchant terminal 410 to the payment system 414. A payment confirmation is generated 442 by the payment system 414 and this payment confirmation is provided 444 to the merchant terminal 410.



FIGS. 5-8 illustrate a first example point-of-sale system 500. FIG. 5 illustrates an example point-of-sale system 500 as viewed from a front perspective view, including a first terminal and a second terminal that are detachably mated together and shown in a fixed position, in accordance with an embodiment. The point-of-sale system 500 includes a first terminal 510 configured, for example, to be a merchant terminal in a merchant-facing direction. The first terminal 510 includes a first computing device 512 and a base 514 into which the second terminal is detachably received. The first computing device 512 can be a separate device that is inserted into the terminal or formed integral into the terminal as a single, unitary structure.



FIG. 6 illustrates the example point-of-sale system of FIG. 5 as viewed from a back perspective view, in accordance with some embodiments. The base 514 of the first terminal 510 detachably receives the second terminal 610. The second terminal 610 can include a first “dip slot” card reader 620 configured to read chip-type cards and a second “swipe slot” card reader 630 configured to read magnetic swipe-type cards. The term “dip slot” refers to a slot or other opening configured to receive or otherwise read a chip-type card via contact or contact-less EMV or NFC communication. The term “swipe slot” refers to a slot or other opening configured to receive a magnetic swipe-type card. In some embodiments, the card reader 620 and the card reader 630 can be replaced with a single hybrid card reader configured to accept both chip-type card and magnetic stripe-type cards.



FIG. 7 illustrates the example point-of-sale system of FIG. 5 as viewed from the back perspective view, and showing the second terminal 610 being separated with ease from the first terminal 610, as shown by arrow 710.



FIG. 8 illustrates the example point-of-sale system of FIG. 5 as viewed from a side perspective view and showing the second terminal completely separated from the first terminal. In this view, each terminal can be physically independent of the other and arranged in a separated position, or mated together as shown in FIG. 5. When separated as shown in FIG. 8, the first terminal and the second terminal are in communication with each other or otherwise mated together via wired or wireless communication. As shown in FIG. 8, the first terminal 510 includes a base 514 having a substantially flat portion 810 that contacts a surface for supporting the first terminal 510 and an upper portion 812. A payment card 820 is shown inserted in the card reader 620 of the second terminal 620. The thin wedge shape of the second terminal 620 welcomes customers to pick up and hold the second terminal 620 for usage of the terminal.



FIGS. 9-12 illustrate an example embodiment of a point-of-sale system 900. FIG. 9 the point-of-sale system 900 as viewed from a front perspective view, including a first terminal and a second terminal that are detachably mated together and shown in a fixed position. The first terminal 910 supports a computing device 912 (e.g., a tablet computer or a mobile device, etc.), or in some embodiments has the computing device formed integrally herewith to form a unitary structure. The first terminal 910 also has a base 914 that detachably receives the second terminal.



FIG. 10 illustrates the example point-of-sale system of FIG. 9 as viewed from a back perspective view. The point-of-sale system includes the first terminal 910 and a second terminal 1010. In an example embodiment the first terminal 910 is a merchant terminal oriented in a merchant-facing direction and the second terminal 1010 is a consumer terminal oriented in a consumer-facing direction. The second terminal 1010 supports a second computing device 1012, which can be a separate component or integrated directly into the second terminal to form a unitary structure.



FIG. 11 illustrates the example point-of-sale system of FIG. 9 as viewed from the back perspective view, and showing the second terminal 1010 being separated from the first terminal 910. The second terminal 1020 can include a hybrid card reader 1120 for receiving a payment card 1110 and can have a groove to facilitate the insertion and removal of the payment card 1110. The hybrid card reader 1120 is configured to read both chip-type card and magnetic strip-type cards. When in the separated position shown in FIG. 11, each terminal functions as its own stand for the point-of-sale system, or optionally can function as a single stand as shown in FIG. 8.



FIG. 12 illustrates the example point-of-sale system of FIG. 9 as viewed from a side perspective view and showing the second terminal 1010 completely separated from the first terminal 910 in a separated position. The first terminal 910 includes a base 910 having a substantially flattened portion 1210 having a base 1212 that contacts a surface for supporting the first terminal 910. The first terminal 910 also includes a portion 1214 that connects the base to the device-holding or device-integrated portion of the terminal. The base 1212 engages with the legs 1220 and 1222 of the second terminal 1010.



FIGS. 13-16 illustrate an example embodiment of a point-of-sale system 1300. FIG. 13 illustrates an example point-of-sale system 1300 as viewed from a front perspective view, including a first terminal 1310 and a second terminal 1320 that are detachably mated together and shown in a fixed position. In an example embodiment, the first terminal 1310 is configured to be a merchant terminal oriented in a merchant-facing direction and the second terminal 1320 is configured to be a consumer terminal oriented in a consumer-facing direction. The first terminal 1310 includes a first computing device 1312 and a base 1314 into which the second terminal 1320 is detachably received.



FIG. 14 illustrates the example point-of-sale system of FIG. 13 as viewed from a back perspective view. The second terminal 1320 is received within the base 1314 of the first terminal 1310. The second terminal 1320 includes a first “dip slot” card reader 1410 configured to read EMV chip-type cards a second “swipe slot” card reader 1420 configured to read magnetic stripe-type cards. One or both of the card readers 1410, 1420 can be configured to read contact-less payment cards. In some embodiments, the two card readers 1410, 1420 can be replaced with a single hybrid card reader configured to read both chip-type cards and magnetic strip-type cards. The second terminal 1320 also includes, as a separate component or formed integrally within the terminal, a computing device 1420 configured to perform the processing of information during the transactions performed by the point-of-sale system.



FIG. 15 illustrates the example point-of-sale system of FIG. 13 as viewed from a side perspective view and showing the second terminal 1320 physically independent of the first terminal 1310 and arranged in a separated position. The first terminal 1310 includes a base 1314 having a substantially flat portion 1510 for contacting a surface that supports the terminal 1310 and an upright portion 1512 that supports the computing device portion of the terminal 1310. The second terminal 1320 has sidewalls 1520 and 1522 that provide privacy for the display of the computing device 1420 when being used by a consumer.



FIG. 16 illustrates the example point-of-sale system of FIG. 13 as viewed from the back perspective view and showing the second terminal completely separated from the first terminal. The tapered surface of the second terminal 1320 and the sides 1520, 1522 provide for privacy for use of the stand by consumers as appropriate.



FIG. 17 illustrates another example point-of-sale system as viewed from a front perspective view showing a first terminal and including a second terminal not visible in FIG. 17 that is detachably mated to the first terminal, in accordance with an embodiment. The point-of-sale system includes a first terminal 1710. The first terminal 1710 is configured, for example, to be a merchant terminal in a merchant-facing direction. As shown, the merchant-facing direction shows only the display of the terminal 1710, and the second terminal is not visible in this view. The first terminal 1710 includes a first computing device 1712 and has a base (1810 in FIG. 18) into which a second terminal (1820 of FIG. 18) is detachably received. The first computing device 1712 can be integrally provided with the first terminal or another computing device that is separately provided and inserted into the terminal.



FIG. 18 illustrates the example point-of-sale system of FIG. 17 as viewed from a side perspective view showing the first terminal with the second terminal detachably mated thereto, in accordance with an embodiment. The second terminal can, for example, be configured in a consumer-oriented direction. The first terminal 1710 has a base 1810 onto which the second terminal 1820 is detachably mated.



FIG. 19 illustrates the example point-of-sale system of FIG. 17 as viewed from a rear perspective view with the second terminal detachably mated to the first terminal, in accordance with an embodiment. The second terminal 1820 includes a leg portion 1910 that, when the second terminal 1820 is separated from the first terminal 1710, can be rotated (in the direction of arrow 1920, for example), so that the second terminal can be independent of the first terminal, as shown, for example, in FIG. 20. The screen of the second terminal 1820 has a low angle to provide improved privacy for consumers. A minimalist system is also provided so that the consumer views only the single slab of the consumer terminal 1820 when viewed from the consumer-facing direction.



FIG. 20 illustrates the example point-of-sale system of FIG. 17 as viewed from a rear perspective view, with the second terminal separated from the first terminal in a separated position, in accordance with an embodiment. The second terminal 1820 is completely independent of the first terminal 1810 and supported by the leg portion 1910. The base 1810 is more clearly visible in this view, the base 1810 providing support for the first terminal 1710 as well as a place for the second terminal to be mated to when in the fixed position as shown in FIGS. 17-19. As shown in FIG. 20, a payment card 2010 is inserted into a payment card reader 2012, which is a chip-type card reader in this embodiment. A swipe slot card reader 2020 is also provided on the second terminal 1820. In this embodiment, the payment card 2010 is a chip-type card that is inserted into the dip slot card reader 2012.



FIG. 21 illustrates the example point-of-sale system of FIG. 17 as viewed from a side perspective view with the second terminal and the first terminal in the separated position, in accordance with an embodiment. In this example embodiment, a swipe-type payment card 2110 is shown inserted in the swipe slot card reader 2020.



FIG. 22 illustrates another example point-of-sale system as viewed from a front perspective view with a first terminal detachably mated to a second terminal, and shown in a fixed position, in accordance with an embodiment. In the point-of-sale system 2200, a first terminal 2210 includes a first computing device 2212, which can be an integrally-provided computing device or a separate component inserted into the terminal 2210. The first terminal 2210 is configured to be a merchant-facing terminal having a base 2215 that supports a second terminal 2220 configured to be a consumer-facing terminal.



FIG. 23 illustrates the example point-of-sale system of FIG. 22 as viewed from a rear perspective view, in accordance with an embodiment. The second terminal 2220 is detachably mated to the first terminal 2210 and received on the base 2215 of the first terminal 2210. The second terminal 2220 includes a hybrid card reader 2310 configured to read both magnetic stripe-type cards and chip-type cards.



FIG. 24 illustrates the example point-of-sale system of FIG. 22 as viewed from a front perspective view with the first terminal separated from and completely independent of the first terminal, shown in a separated position, in accordance with an embodiment. The second terminal 2220 has been separated from the base 2215 of the first terminal 2210 and is now shown supported on its own base 2410.



FIG. 25 illustrates the example point-of-sale system of FIG. 22 as viewed from a rear perspective view with the first terminal and the second terminal shown in the separated position, in accordance with an embodiment. The second terminal 2220 includes the card reader 2310 and is supported by base 2410.



FIG. 26 illustrates another example point of sale system as viewed from a front perspective view with a first terminal detachably mated to a second terminal, and shown in a fixed position, in accordance with an embodiment. The point-of-sale system 2600 includes a first terminal 2610 that can be configured, for example, to be a merchant-facing terminal, that is detachably mated to a second terminal 2620 that can be configured, for example, to be a consumer-facing terminal. The first terminal 2610 includes a first computing device 2612 that, for example, can be a tablet computer, a mobile phone, or a device integrally provided with the first terminal.



FIG. 27 illustrates the example point-of-sale system of FIG. 26 as viewed from a rear perspective view, in accordance with an embodiment. The first terminal 2610 includes a base 2710 that support the first terminal 2610 and also detachably receives the second terminal 2620. With reference to FIG. 28, the hybrid card reader 2720 is shown in greater detail. The hybrid card reader 2720 includes a dip slot opening 2810 configured to receive a chip-type card, and a swipe slot 2820 configured to read magnetic stripe-type cards. As shown in FIG. 28, the card reader 2810 has a payment card 2800 received therein. Note that the card readers are accessible by both the consumers and the merchants in this embodiment when in the fixed position, and thereby a payment card can be inserted and processed by either the merchant or the consumer or both. FIG. 29 shows a swipe-type card inserted into the card reader 2820 and FIG. 30 shows a chip-type card inserted into the card reader 2810.



FIG. 29 illustrates the example point-of-sale system of FIG. 26 as viewed from a rear perspective view with the first terminal separated from and completely independent of the first terminal, shown in a separated position, in accordance with an embodiment. The second terminal 2620 has a swipe-type payment card 2910 inserted into the swipe card reader 2820.



FIG. 30 illustrates the example point-of-sale system of FIG. 26 as viewed from a side perspective view with the first terminal and the second terminal shown in the separated position, in accordance with an embodiment. The second terminal 2620 has a chip-type payment card 2912 inserted in the dip slot card reader 2810.


Having now described various example embodiments of the point-of-sale system using in a point-of-sale transaction, some example environments for conducting a financial transaction at a point-of-sale system will now be described. Other environments and applications of the point-of-sale system should be apparent to those ordinarily skilled in the art.



FIG. 31 illustrates an example environment for conducting a financial transaction at a point-of-sale system in accordance with various embodiments. In this example, the exemplary environment 3100 includes a merchant payment system 3102 for processing transactions between a customer and a merchant. The merchant payment system includes, for example, a data processing server 3104 and a payment server 3106. The data processing server can be implemented as computer programs on one or more computers in one or more locations, in which the systems, components, and techniques described herein can be implemented. The operation of the payment server is described below in reference to FIG. 32. The example environment also includes computing devices, e.g., transaction registers or other point-of-sale systems, corresponding to the merchant 3110 and 3111.


As described, the point-of-sale systems 3110 and 3111 can include the computing device, where the computing device can be coupled to or in communication with the merchant payment system through a data communication network 3108, e.g., the Internet. These devices each generally include a memory, e.g., a random access memory (RAM), for storing instructions and data, and a processor for executing stored instructions. The devices and can each include one or more components, e.g., software or hardware, that are operable to send and receive requests, messages, or other types of information over the network. Some examples of computing devices include personal computers, cellular phones, handheld messaging devices, laptop computers, personal data assistants, tablet devices, and the like.


The network 3108 can include any appropriate network, including an intranet, the Internet, a cellular network, a local area network, a wide area network, or any other such network, or combination thereof. Components used for such a system can depend at least in part upon the type of network, the environment selected, or both. Protocols and components for communicating over such a network are well known and will not be discussed herein in detail. The devices and the referral system can communicate over the network using wired or wireless connections, and combinations thereof.


Each of the computing devices is configured to send to the merchant payment system respective financial data that corresponds to a financial transaction that was processed by the computing device. The financial data can include, for example, data stored in a financial payment card, e.g., Track 1 data, receipt email addresses, and information describing a card-less payment account. Other examples of financial data that can be captured includes purchase data, e.g., an itemized listing of purchases, card mix data, geolocation data indicating a geographic location of a particular transaction, online/offline card data, data describing the merchant, e.g., merchant category codes (MCCs), and any type of data that is received upon a customer's authentication into a social network.



FIG. 32 illustrates an example of an environment 3200 for implementing a payment service network. Although a mobile device environment is described for purposes of explanation, different environments may be used, e.g., a web-based environment, to implement various embodiments. The example environment includes a payment system 3208, which can be implemented as computer programs on one or more computers in one or more locations, in which the systems, components, and techniques described below can be implemented. The example environment also includes a user device 3202 and a merchant device 3205.


The user device and the merchant device can each be a computer coupled to the payment system through a data communication network 3250, e.g., the Internet. The user device and the merchant device each generally include a memory, e.g., a random access memory (RAM), for storing instructions and data, and a processor for executing stored instructions. The user device and the merchant device can each include one or more components, e.g., software or hardware, that are configured to respectively determine a geographic location of the user device or the merchant device, using, for example, various geolocation techniques, e.g., a global positioning system (GPS). Further, the user device and the merchant device can each be any appropriate device operable to send and receive requests, messages, or other types of information over the network. Some examples of user devices include personal computers, cellular phones, handheld messaging devices, laptop computers, personal data assistants, tablet devices, and the like.


The network can include any appropriate network, including an intranet, the Internet, a cellular network, a local area network, a wide area network, or any other such network, or combination thereof. Components used for such a system can depend at least in part upon the type of network, the environment selected, or both. Protocols and components for communicating over such a network are well known and will not be discussed herein in detail. The payment system, the merchant device, and the user device can communicate over the network using wired or wireless connections, and combinations thereof.


As used in this specification, a financial transaction is a transaction that is conducted between a customer and a merchant at a point-of-sale. When paying for a financial transaction, the customer can provide the merchant with cash, a check, or credit card for the amount that is due. The merchant can interact with a point-of-sale device, e.g., merchant device, to process the financial transaction. During financial transactions, the point-of-sale device can collect data describing the financial transaction, including, for example, the amount of payment received from customers.


In some implementations, the payment system is configured to accept card-less payment transactions from customers, e.g., the customer. As used in this specification, a card-less payment transaction is a transaction conducted between the customer and a merchant at the point-of-sale during which a financial account of the customer is charged without the customer having to physically present a financial payment card to the merchant at the point-of-sale. That is, the merchant need not receive any details about the financial account, e.g., the credit card issuer or credit card number, for the transaction to be processed.


In some embodiments, before conducting card-less payment transactions, the customer typically creates a user account with the payment system. The customer can create the user account, for example, by interacting with a user application that is configured to perform card-less payment transactions and that is running on the user device. When creating a user account with the payment system, the customer will provide information of the customer, data describing a financial account of the customer, e.g., credit card number, expiration date, and a billing address. This user information can be securely stored by the payment system, for example, in a user information database. To accept card-less payment transactions, the merchant typically creates a merchant account with the payment system by providing information describing the merchant including, for example, a merchant name, contact information, e.g., telephone numbers, the merchant's geographic location address, and one or more financial accounts to which funds collected from users will be deposited. This merchant information can be securely stored by the payment system, for example, in a merchant information database.


The payment system can be configured to perform card-less payment transactions. The payment system can include one or more servers that are configured to securely perform electronic financial transactions, e.g., electronic payment transactions, between a customer and a merchant, for example, through data communicated between the user device and the merchant device. Generally, when a customer and a merchant enter into an electronic financial transaction, the transaction is processed by transferring funds from a financial account associated with the user account to a financial account associated with the merchant account.


The payment system is configured to send and receive data to and from the user device and the merchant device. For example, the payment system can be configured to send data describing merchants to the user device using, for example, the information stored in the merchant information database 3212. For example, the payment system can communicate data describing merchants that are within a threshold geographic distance from a geographic location of the user device, as described in this specification. The data describing merchants can include, for example, a merchant name, geographic location, contact information, and an electronic catalogue, e.g., a menu, that describes items that are available for purchase from the merchant.


In some embodiments, the payment system is configured to determine whether a geographic location of the user device is within a threshold geographic distance from a geographic location of the merchant device. The payment system can determine a geographic location of the user device using, for example, geolocation data provided by the user device. Similarly, the payment system can determine a geographic location of the merchant device using, for example, geolocation data provided by the merchant device or using a geographic address, e.g., street address, provided by the merchant. Depending on the implementation, the threshold geographic distance can be specified by the payment system or by the merchant.


Determining whether the user device is within a threshold geographic distance of the merchant device can be accomplished in different ways including, for example, determining whether the user device is within a threshold geographic radius of the merchant device, determining whether the user device is within a particular geofence, or determining whether the user device can communicate with the merchant device using a specified wireless technology, e.g., Bluetooth or Bluetooth low energy (BLE). In some embodiments, the payment system restricts card-less payment transactions between the customer and the merchant to situations where the geographic location of the user device is within a threshold geographic distance from a geographic location of the merchant device.


The payment system can also be configured to communicate with a computer system 3216 of a card payment network, e.g., Visa or MasterCard, over the network, or over a different network, for example, to conduct electronic financial transactions. The computer system of the card payment network can communicate with a computer system 3216 of a card issuer, e.g., a bank. There may be computer systems of other entities, e.g., the card acquirer, between the payment system and the computer system of the card issuer.


The customer operating the user device that is within a threshold geographic distance of the merchant can interact with a user application running on the user device to conduct a card-less payment transaction with the merchant. While interacting with the user application, the customer can select the merchant, from a listing of merchants, with whom the customer wants to enter into a card-less payment transaction. The user can select the merchant, for example, by selecting a “check in” option associated with the merchant. The user device can communicate data to the payment system indicating that the customer has checked in with the merchant. In response, the payment system can communicate data to notify the merchant device that the user has checked in. A merchant application running on the merchant device can notify the merchant that the user has electronically checked in with the merchant through a display screen of the merchant device.


Once checked in, the customer can collect, or request, items that are available for purchase from the merchant. When the customer is ready to enter into the card-less payment transaction, the customer can, for example, approach a point-of-sale for the merchant and identify him or herself. For example, the customer can verbally notify the merchant that the customer wants to enter into a card-less payment transaction and can provide the merchant with the customer's name. The merchant can then interact with the merchant application to select the customer, from a listing of customers that have checked in with the merchant, to initiate a card-less payment transaction for the items being purchased by the customer. For example, the merchant can determine a total amount to bill the customer for the items being purchased. The customer can verbally approve the total amount to be billed and, in response, the merchant can submit a request for a card-less payment transaction for the total amount to the payment system. In response, the payment system can obtain, for example, from the user information database, data describing a financial account associated with a user account of the customer to which the total amount will be billed.


The payment system can then communicate with the computer system of a card payment network to complete an electronic financial transaction for the total amount to be billed to the customer's financial account. Once the electronic financial transaction is complete, the payment system can communicate data describing the card-less payment transaction to the user device, e.g., an electronic receipt, which can, for example, notify the customer of the total amount billed to the user for the card-less payment transaction with the particular merchant.


For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.


In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.


Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.


Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.


The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.


Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.

Claims
  • 1. A point-of-sale system used in performing a point-of-sale transaction between a merchant and a consumer, the system comprising: a merchant terminal including a first display that is oriented in a merchant-facing direction, the merchant terminal further including: non-transitory computer readable instructions that, when interpreted by a merchant terminal processor, cause the merchant terminal processor to display a series of screens in a merchant facing graphical user interface for guiding a merchant through a point of sale transaction,a first merchant terminal communication interface, anda second merchant terminal communication interface;a consumer terminal including a second display that is oriented in a consumer-facing direction, the consumer terminal further including electronics in a physically secure area and electronics in a non-secure area, the electronics in the non-secure area comprising: non-transitory computer readable instructions that, when interpreted by a non-secure consumer terminal processor, cause the non-secure consumer terminal processor to display a series of screens in the second display for guiding a consumer through a point of sale transaction, anda consumer terminal communication interface; andthe electronics in the physically secure area comprising: an input controller within the secure area and coupled to the second display to receive consumer inputs received in the second display, the input controller configured to determine if the received consumer inputs require processing by a secure processor, and wherein the input controller comprises a touch controller to receive the consumer inputs and a multiplexer configured to send a first set of consumer inputs requiring further processing by the secure processor to the secure processor and to send the second set of consumer inputs that do not require further processing by the secure processor to the non-secure consumer terminal processor, andthe secure processor within the secure area configured (a) to receive the first set of consumer inputs from the input controller, (b) to encrypt the first set of consumer inputs, and (c) to send the encrypted inputs to the non-secure consumer terminal processor for transmission of the encrypted inputs using the consumer terminal communication interface,the second merchant terminal communication interface linked to the consumer terminal communication interface by one of a wired or wireless link to receive the encrypted inputs from the consumer terminal communication interface, and the first merchant terminal communication interface configured to transmit the encrypted inputs to a financial transaction server.
  • 2. The point-of-sale system of claim 1 wherein the non-secure consumer terminal processor is configured to send a stripe-card-specific GUI to the consumer terminal when a magnetic stripe-type card is used in payment during the point-of-sale transaction.
  • 3. The point-of-sale system of claim 1 wherein the non-secure consumer terminal processor is configured to send a chip-type-card-specific GUI to the consumer terminal when a chip-type card is used in payment during the point-of-sale transaction.
  • 4. The point-of-sale system of claim 1 further comprising a hybrid card reader configured to receive a payment card used during the point-of-sale transaction, the payment card being a magnetic stripe-type card or an IC chip-type card, the hybrid card reader being coupled to the consumer terminal to perform a payment transaction during the point-of-sale transaction between the merchant and the consumer.
  • 5. The point-of-sale system of claim 1 wherein a confirmation of payment is presented to the merchant terminal merchant facing graphical user interface upon receipt of confirmation of available funds from the financial transaction server.
  • 6. The point-of-sale system of claim 1 wherein the physically secure area further comprises an anti-tamper battery.
  • 7. The point-of-sale system of claim 1 wherein the physically secure area further comprises a debug module.
  • 8. The point-of-sale system of claim 1 wherein the first display comprises a touch screen display.
  • 9. The point-of-sale system of claim 1 wherein the input controller is configured to send consumer inputs received in a secure portion of the second display to the secure processor.
  • 10. The point-of-sale system of claim 1 wherein the physically secure area further comprises a magnetic stripe reading interface, an EMV contact interface and an EMV contactless interface.
  • 11. The point-of-sale system of claim 1 wherein the second display includes a secure graphical user interface portion and a non-secure graphical user interface portion.
  • 12. The point-of-sale system of claim 11 wherein each of the first set of consumer inputs is received by the secure graphical user interface portion and each of the second set of consumer inputs is received by the non-secure graphical user interface portion.
  • 13. The point-of-sale system of claim 1 wherein the physically secure area comprises a secure enclave.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 14/592,255, entitled, “POINT OF SALE SYSTEM”, filed on Jan. 8, 2015, which claims the benefit of U.S. Provisional Patent Application No. 62/053,029, entitled “POINT OF SALE SYSTEM”, filed on Sep. 19, 2014; both of which are hereby expressly incorporated herein by reference in their entireties.

US Referenced Citations (217)
Number Name Date Kind
3128349 Boesch et al. Apr 1964 A
4150784 Moorman et al. Apr 1979 A
4304385 Farouche et al. Dec 1981 A
4776003 Harris Oct 1988 A
4860336 D'Avello et al. Aug 1989 A
5221838 Gutman et al. Jun 1993 A
5331138 Saroya Jul 1994 A
5351296 Sullivan Sep 1994 A
5388155 Smith Feb 1995 A
5408513 Busch, Jr. et al. Apr 1995 A
5494136 Humble Feb 1996 A
5714741 Pieterse et al. Feb 1998 A
5729591 Bailey Mar 1998 A
5740232 Pailles et al. Apr 1998 A
5838773 Eisner et al. Nov 1998 A
5850599 Seiderman Dec 1998 A
5867795 Novis et al. Feb 1999 A
5940510 Curry et al. Aug 1999 A
5963647 Downing Oct 1999 A
5970146 McCall Oct 1999 A
6010067 Elbaum Jan 2000 A
6062477 Wike, Jr. May 2000 A
6098881 Deland, Jr. et al. Aug 2000 A
6098888 Praden Aug 2000 A
6144336 Preston et al. Nov 2000 A
6157966 Montgomery Dec 2000 A
6234389 Valliani et al. May 2001 B1
6278779 Bryant et al. Aug 2001 B1
6321339 French Nov 2001 B1
6481623 Grant et al. Nov 2002 B1
6766994 Serbinski Jul 2004 B2
6990683 Itabashi Jan 2006 B2
7003316 Elias et al. Feb 2006 B1
7004385 Douglass Feb 2006 B1
7048184 Persky May 2006 B2
7066382 Kaplan Jun 2006 B2
7083090 Zuili Aug 2006 B2
7163148 Durbin et al. Jan 2007 B2
7210627 Morley et al. May 2007 B2
7363054 Elias et al. Apr 2008 B2
7370804 Ishii May 2008 B2
7424732 Matsumoto et al. Sep 2008 B2
7433452 Taylor et al. Oct 2008 B2
7591425 Zuili et al. Sep 2009 B1
7597250 Finn Oct 2009 B2
7673799 Hart et al. Mar 2010 B2
7712670 Sauerwein, Jr. et al. May 2010 B2
7810729 Morley, Jr. Oct 2010 B2
7866546 Vance Jan 2011 B1
7896248 Morley, Jr. Mar 2011 B2
8086531 Litster et al. Dec 2011 B2
8117125 Kawan et al. Feb 2012 B1
8126734 Dicks et al. Feb 2012 B2
8261064 Ditzman Sep 2012 B2
8265553 Cheon et al. Sep 2012 B2
8397988 Zuili Mar 2013 B1
8558685 Long Oct 2013 B2
8768838 Hoffman Jul 2014 B1
8944322 White Feb 2015 B2
8988354 Milhe Mar 2015 B2
9020853 Hoffman et al. Apr 2015 B2
9047639 Quintiliani Jun 2015 B1
9092766 Bedier Jul 2015 B1
9129274 Mocko Sep 2015 B1
9286494 Lamfalusi Mar 2016 B1
9367842 Quigley Jun 2016 B2
9589428 Edwards Mar 2017 B2
9679286 Colnot et al. Jun 2017 B2
9704355 Beatty Jul 2017 B2
9741211 Skiles Aug 2017 B2
9792783 Beatty Oct 2017 B1
9881288 Bell Jan 2018 B1
9911266 Weston Mar 2018 B2
9916570 Edwards et al. Mar 2018 B2
9946506 Ting Apr 2018 B2
9965116 Wolter May 2018 B1
10019605 Boysen Jul 2018 B2
10140604 Douthat Nov 2018 B1
10318953 Binder Jun 2019 B2
10475024 Behren Nov 2019 B1
10504096 Hafemann Dec 2019 B1
10579989 Binder Mar 2020 B1
10713904 Beatty Jul 2020 B2
10733588 Mocko et al. Aug 2020 B1
10762196 Cat Sep 2020 B2
10783509 Pattarawuttiwong Sep 2020 B2
20020082993 Hoyos Jun 2002 A1
20020091633 Proctor Jul 2002 A1
20020153414 Stoutenburg et al. Oct 2002 A1
20020166891 Stoutenburg Nov 2002 A1
20030004876 Jacobson Jan 2003 A1
20030066893 Yap Apr 2003 A1
20030135406 Rowe Jul 2003 A1
20030135418 Shekhar et al. Jul 2003 A1
20030135751 O'Donnell Jul 2003 A1
20030154414 von Mueller et al. Aug 2003 A1
20030164398 Walker et al. Sep 2003 A1
20030183691 Lahteenmaki et al. Oct 2003 A1
20030191713 Yap Oct 2003 A1
20040012875 Wood Jan 2004 A1
20040034564 Liu Feb 2004 A1
20040041911 Odagiri et al. Mar 2004 A1
20040043650 Yang et al. Mar 2004 A1
20040059682 Hasumi et al. Mar 2004 A1
20040167820 Melick et al. Aug 2004 A1
20040204082 Abeyta Oct 2004 A1
20050039052 O'Donnell Feb 2005 A1
20050097015 Wilkes et al. May 2005 A1
20050109841 Ryan et al. May 2005 A1
20050116840 Simelius Jun 2005 A1
20050236480 Vrotsos et al. Oct 2005 A1
20050283403 Ramirez Dec 2005 A1
20060032905 Bear et al. Feb 2006 A1
20060049255 von Mueller et al. Mar 2006 A1
20060168663 Viljoen Jul 2006 A1
20060223580 Antonio et al. Oct 2006 A1
20060226224 Henry Oct 2006 A1
20060242696 Cruzado Oct 2006 A1
20070067833 Colnot Mar 2007 A1
20070136216 Simcik Jun 2007 A1
20070168300 Quesselaire et al. Jul 2007 A1
20070194104 Fukuda et al. Aug 2007 A1
20070198436 Weiss Aug 2007 A1
20070251997 Brown Nov 2007 A1
20070257110 Schmidt et al. Nov 2007 A1
20080016456 Friedland et al. Jan 2008 A1
20080091617 Hazel et al. Apr 2008 A1
20080209212 Ditzman Aug 2008 A1
20080215887 Hart et al. Sep 2008 A1
20090006262 Brown Jan 2009 A1
20090070583 von Mueller et al. Mar 2009 A1
20090102813 Mamba Apr 2009 A1
20090112768 Hammad et al. Apr 2009 A1
20090119221 Weston May 2009 A1
20090164326 Bishop et al. Jun 2009 A1
20090173790 Hart Jul 2009 A1
20090222383 Tato Sep 2009 A1
20090307142 Mardikar Dec 2009 A1
20100020971 Hanks Jan 2010 A1
20100057620 Li Mar 2010 A1
20100057624 Hurt Mar 2010 A1
20100211469 Salmon Aug 2010 A1
20100243732 Wallner Sep 2010 A1
20100262504 Tamura Oct 2010 A1
20110176004 Chaussade Jul 2011 A1
20110199308 Nativel Aug 2011 A1
20110321173 Weston Dec 2011 A1
20120023026 Chen Jan 2012 A1
20120066079 Falzone Mar 2012 A1
20120197744 Rose Aug 2012 A1
20120242526 Perez Sep 2012 A1
20120254038 Mullen Oct 2012 A1
20120286040 Ko Nov 2012 A1
20120290420 Close Nov 2012 A1
20130006847 Hammad Jan 2013 A1
20130050084 Soffer Feb 2013 A1
20130144731 Baldwin Jun 2013 A1
20130153656 Skiles Jun 2013 A1
20130155595 Herring Jun 2013 A1
20130198086 Mardikar Aug 2013 A1
20130246171 Carapelli Sep 2013 A1
20130282501 Edwards et al. Oct 2013 A1
20130299574 Theobald Nov 2013 A1
20140022211 Karpin Jan 2014 A1
20140047390 Thorsander Feb 2014 A1
20140071043 Jung Mar 2014 A1
20140078070 Armstrong-Muntner Mar 2014 A1
20140089174 Carapelli et al. Mar 2014 A1
20140095387 Colnot Apr 2014 A1
20140096222 Colnot Apr 2014 A1
20140097249 Gomez Apr 2014 A1
20140101035 Tanner Apr 2014 A1
20140143089 Campos May 2014 A1
20140172607 Skiles Jun 2014 A1
20140183260 Sancak Jul 2014 A1
20140214688 Weiner et al. Jul 2014 A1
20140252089 Bostwick Sep 2014 A1
20140256251 Caceres et al. Sep 2014 A1
20140283857 Liu Sep 2014 A1
20150095133 Parker et al. Apr 2015 A1
20150095134 Parker Apr 2015 A1
20150095241 Edwards Apr 2015 A1
20150100498 Edwards Apr 2015 A1
20150161601 Matsumoto Jun 2015 A1
20150199882 Fernando Jul 2015 A1
20150261314 Herring Sep 2015 A1
20150324781 Saitoh Nov 2015 A1
20150363757 Mocko et al. Dec 2015 A1
20160005020 Fernando Jan 2016 A1
20160012465 Sharp Jan 2016 A1
20160026990 Rezayee Jan 2016 A1
20160051067 Law Feb 2016 A1
20160070964 Conrad Mar 2016 A1
20160117529 Bedier Apr 2016 A1
20160117659 Bedier et al. Apr 2016 A1
20160117662 Bedier et al. Apr 2016 A1
20160124627 Beatty May 2016 A1
20160125181 Dai Zovi May 2016 A1
20160125376 Beatty May 2016 A1
20160148023 Lamfalusi May 2016 A1
20160275478 Li et al. Sep 2016 A1
20160335461 Lamfalusi et al. Nov 2016 A1
20160335462 Lamfalusi et al. Nov 2016 A1
20170154334 Lewis Jun 2017 A1
20170185363 Ting Jun 2017 A1
20170221035 Edwards et al. Aug 2017 A1
20170308882 Bedier Oct 2017 A1
20170309135 Beatty Oct 2017 A1
20170311737 Law et al. Nov 2017 A1
20170364888 Bell Dec 2017 A1
20180005224 Binder Jan 2018 A1
20180033255 Beatty Feb 2018 A1
20180039965 Han Feb 2018 A1
20180150818 Mocko May 2018 A1
20180174013 Lee Jun 2018 A1
20180174391 Weston Jun 2018 A1
20180316815 Douthat Nov 2018 A1
Foreign Referenced Citations (64)
Number Date Country
2324402 Jun 2002 AU
2015349752 Jul 2017 AU
2 955 454 Jan 2016 CA
106716470 May 2017 CN
20320080 Apr 2004 DE
0 895 203 Feb 1999 EP
1 874 014 Jan 2008 EP
2 812 744 Feb 2002 FR
2 812 745 Feb 2002 FR
2 834 156 Jun 2003 FR
2 427 059 Dec 2006 GB
H09231285 Sep 1997 JP
2000-030146 Jan 2000 JP
2000-276539 Oct 2000 JP
2001-222595 Aug 2001 JP
2002-074507 Mar 2002 JP
2002-123771 Apr 2002 JP
2002-279320 Sep 2002 JP
2002-352166 Dec 2002 JP
2002-358285 Dec 2002 JP
2003-108777 Apr 2003 JP
2003-281453 Oct 2003 JP
2003-308438 Oct 2003 JP
2004-054651 Feb 2004 JP
2004-062733 Feb 2004 JP
2004-078553 Mar 2004 JP
2004-078662 Mar 2004 JP
2004-199405 Jul 2004 JP
4248820 Apr 2009 JP
10-1999-0066397 Aug 1999 KR
10-1999-0068618 Sep 1999 KR
200225019 Mar 2001 KR
10-2003-0005936 Jan 2003 KR
10-2003-0005984 Jan 2003 KR
10-2003-0012910 Feb 2003 KR
200333809 Nov 2003 KR
10-2004-0016548 Feb 2004 KR
100447431 Aug 2004 KR
200405877 Jan 2006 KR
100649151 Nov 2006 KR
10-2007-0107990 Nov 2007 KR
100842484 Jun 2008 KR
2284578 Sep 2006 RU
1998012674 Mar 1998 WO
2000011624 Mar 2000 WO
2000025277 May 2000 WO
2001086599 Nov 2001 WO
2002033669 Apr 2002 WO
2002043020 May 2002 WO
2002082388 Oct 2002 WO
2002084548 Oct 2002 WO
2003044710 May 2003 WO
2003079259 Sep 2003 WO
2004023366 Mar 2004 WO
2006131708 Dec 2006 WO
2011051757 May 2011 WO
2012078990 Jun 2012 WO
2013051032 Apr 2013 WO
2015001468 Jan 2015 WO
2015191468 Dec 2015 WO
2016014346 Jan 2016 WO
2016069775 May 2016 WO
2016081804 May 2016 WO
2017222696 Dec 2017 WO
Non-Patent Literature Citations (65)
Entry
Restriction Requirement dated Feb. 27, 2015, for U.S. Appl. No. 14/592,102, of Chen, Y., et al., filed Jan. 8, 2015.
Non-Final Office Action dated Mar. 13, 2015, for U.S. Appl. No. 14/572,692, of Bell, B., et al., filed Dec. 16, 2014.
Non-Final Office Action dated May 21, 2015, for U.S. Appl. No. 14/592,102, of Chen, Y., et al., filed Jan. 8, 2015.
Final Office Action dated Jul. 10, 2015, for U.S. Appl. No. 14/572,692, of Bell, B., et al., filed Dec. 16, 2014.
Non-Final Office Action dated Sep. 16, 2015, for U.S. Appl. No. 14/549,338, of Lamfalusi, M.C., et al., filed Nov. 20, 2014.
Notice of Allowance dated Nov. 10, 2015, for U.S. Appl. No. 14/549,338, of Lamfalusi, M.C., et al., filed Nov. 20, 2014.
Final Office Action dated Dec. 9, 2015, for U.S. Appl. No. 14/592,102, of Chen, Y., et al., filed Jan. 8, 2015.
Non-Final Office Action dated Jan. 14, 2016, for U.S. Appl. No. 14/947,162, of Lamfalusi, M.C., et al., filed Nov. 20, 2015.
Restriction Requirement dated Jan. 22, 2016, for U.S. Appl. No. 14/848,123, of Guise, M., et al., filed Sep. 8, 2015.
International Search Report and Written Opinion for PCT Application No. PCT/US2015/051082 dated Dec. 18, 2015.
International Search Report and Written Opinion for PCT Application No. PCT/US2015/051090 dated Dec. 21, 2015.
International Search Report and Written Opinion for PCT Application No. PCT/US2015/061771 dated Jan. 29, 2016.
Notice of Acceptance for Australian Patent Application No. 2015349752, dated Jul. 3, 2017.
Examination Report No. 1 for Australian Patent Application No. 2017245444, dated Dec. 1, 2017.
Notice of Allowance dated Jan. 5, 2017, for U.S. Appl. No. 15/220,262, of Lamfalusi, M.C., et al., filed Jul. 26, 2016.
Final Office Action dated Jan. 27, 2017, for U.S. Appl. No. 14/848,123, of Guise, M., et al., filed Sep. 8, 2015.
Non-Final Office Action dated Aug. 25, 2016, for U.S. Appl. No. 15/220,262, of Lamfalusi, M.C., et al., filed Jul. 26, 2016.
Non-Final Office Action dated Aug. 25, 2016, for U.S. Appl. No. 15/221,383, of Lamfalusi, M.C., et al., filed Jul. 27, 2016.
Non-Final Office Action dated Mar. 11, 2016, for U.S. Appl. No. 14/572,692, of Bell, B., et al., filed Dec. 16, 2014.
Notice of Allowance dated Mar. 25, 2016, for U.S. Appl. No. 14/947,162, of Lamfalusi, M.C., et al., filed Nov. 20, 2015.
International Search Report and Written Opinion for International Application No. PCT/US2017/033370, dated Jul. 21, 2017.
“At a Glance PCI Data Storage, PCI Data Storage Do's and Don'ts,” PCI Security Standards Council Llc, dated Dec. 31, 2008, Retrieved from the Internet URL: http://web.archive.org/web/20140704155237/https://www.pcisecuritystandards.org/pdfs/pci_fs_data_storage.pdf, on Feb. 8, 2017, pp. 1-2.
Notice of Allowance dated Apr. 21, 2017, for U.S. Appl. No. 15/221,383, of Lamfalusi, M.C., et al., filed Jul. 26, 2016.
International Search Report and Written Opinion for PCT Application No. PCT/US2016/068914 dated Feb. 16, 2017.
Non-Final Office Action dated Jul. 20, 2016, for U.S. Appl. No. 14/848,123, of Guise, M., et al., filed Sep. 8, 2015.
Non-Final Office Action dated Mar. 11, 2016, for U.S. Appl. No. 14/752,698, of Rezayee, A., et al., filed Jun. 26, 2015.
Non-Final Office Action dated Apr. 12, 2016, for U.S. Appl. No. 14/982,840, of Edwards, T., et al., filed Dec. 29, 2015.
Final Office Action dated Sep. 23, 2016, for U.S. Appl. No. 14/752,698, of Rezayee, A., et al., filed Jun. 26, 2015.
Notice of Allowance dated Oct. 24, 2016, for U.S. Appl. No. 14/982,840, of Edwards, T., et al., filed Dec. 29, 2015.
Non-Final Office Action dated Mar. 31, 2017, for U.S. Appl. No. 15/241,901, of Edwards, T., et al., filed Aug. 19, 2016.
Non-Final Office Action dated Sep. 8, 2017, for U.S. Appl. No. 14/752,698, of Rezayee, A., et al., filed Jun. 26, 2015.
Notice of Allowance dated Oct. 30, 2017, for U.S. Appl. No. 15/241,901, of Edwards, T., et al., filed Aug. 19, 2016.
Non-Final Office Action dated Feb. 20, 2018, for U.S. Appl. No. 15/793,187, of Mocko, C.L., et al., filed Oct. 25, 2017.
Final Office Action dated Apr. 25, 2018, for U.S. Appl. No. 14/752,698, of Rezayee, A., et al., filed Jun. 26, 2015.
Notice of Allowance dated Jun. 18, 2018, for U.S. Appl. No. 15/793,187, of Mocko, C.L., et al., filed Oct. 25, 2017.
Non-Final Office Action dated Jun. 29, 2018, for U.S. Appl. No. 15/003,580, of Chen, Y., et al., filed Jan. 21, 2016.
Advisory Action dated Jul. 5, 2018, for U.S. Appl. No. 14/752,698, of Rezayee, A., et al., filed Jun. 26, 2015.
International Search Report and Written Opinion for International Application No. PCT/US2015/040819, dated Oct. 13, 2015.
Extended European Search Report for European Patent Application No. 15825575.2, dated Nov. 28, 2017.
Office Action for European Patent Application No. 15 825 575.2, dated Oct. 1, 2018.
Non-Final Office Action dated Jan. 10, 2019, for U.S. Appl. No. 14/752,698, of Rezayee, A., et al., filed Jun. 26, 2015.
Non-Final Office Action dated Feb. 26, 2019, for U.S. Appl. No. 16/051,381, of Chen, Y., et al., filed Jul. 31, 2018.
Summons to Oral Proceeding for European Patent Application No. 15825575.2, mailed Mar. 6, 2019.
Non-Final Office Action dated Apr. 2, 2019, for U.S. Appl. No. 15/003,580, of Chen, Y., et al., filed Jan. 21, 2016.
Loisel Y., “Designing Next-Generation Payment Terminals That Meet PCI PTS 3.x Requirements,” Application note 4809, Maxim Integrated, Retrieved from URL: https://www.maximintegrated.com/en/app-notes/index.mvp/id/4809, dated May 19, 2011.
Notice of Allowance dated Jul. 19, 2019, for U.S. Appl. No. 14/752,698, of Rezayee, A., et al., filed Jun. 26, 2015.
Non-Final Office Action dated Sep. 5, 2019, for U.S. Appl. No. 16/051,381, of Chen, Y., et al., filed Jul. 31, 2018.
“Connection of Terminal Equipment to the Telephone Network,” FCC 47 CFR Part 68, Retrieved from the URL: http://www.tscm.com/FCC47CFRpart68.pdf, on Sep. 24, 2019 Oct. 1, 1999 Edition.
“EMBEDDED FINancial transactional IC card READer,” Retrieved from the URL: https://cordis.europa.eu/project/rcn/58338/factsheet/en.
Geethapriya Venkataramani and Srividya Gopalan., “Mobile phone based RFID architecture for secure electronic payments using RFID credit cards,” 2007 IEEE, (ARES'07).
“Guideline for the Use of Advanced Authentication Technology,” FIPS 190, Sep. 28, 1994.
“Identification cards—Recording technique—Part 4—Location of read-only magnetic tracks—Track 1 and 2,” ISO/IEC7811-4:1995, International Organization for Standardization, Aug. 1995.
Jerome Svigals., “The Long Life and Imminent Death of the Mag-stripe Card,” IEEE Spectrum, vol. 49, Issue 61, Jun. 2012.
“Magensa's Decryption Services and MagTek's MagneSafe™ Bluetooth Readers Selected by eProcessing Network to Implement Secure Customer Card Data with Mobile Devices,” Retrieved from the URL: https://www.magnensa.net/aboutus/articles/eProcessing-rev1.pdf Apr. 14, 2008.
Martha E. Haykin et al., “Smart Card Technology: New Methods for Computer Access Control,” NIST Special Publication 500-157, Sep. 1988.
“MSP430x1xx Family User's Guide,” (including 2016 correction sheet at 2), Texas Instruments Inc., 2006.
Spegele, Joseph Brain., “A Framework for Evaluating Application of Smart Cards and Related Technology Within the Department of Defense,” Naval Postgraduate School, Jan. 1995.
Stephen A. Sherman et al., “Secure Network Access Using Multiple Applications of AT&T's Smart Card,” AT&T Technical Journal, Sep./Oct. 1994.
Final Office Action dated Oct. 18, 2019, for U.S. Appl. No. 15/003,580, of Chen, Y., et al., filed Jan. 21, 2016.
Non-Final Office Action dated Dec. 12, 2019, for U.S. Appl. No. 16/146,943, of Mocko, C.L., et al., filed Sep. 28, 2018.
Advisory Action dated Jan. 6, 2020, for U.S. Appl. No. 15/003,580, of Chen, Y., et al., filed Jan. 21, 2016.
Non-Final Office Action dated Feb. 27, 2020, for U.S. Appl. No. 16/051,381, of Chen, Y., et al., filed Jul. 31, 2018.
Notice of Allowance dated Mar. 25, 2020, for U.S. Appl. No. 16/146,943, of Mocko, C.L., et al., filed Sep. 28, 2018.
Final Office Action dated Jun. 23, 2020, for U.S. Appl. No. 16/051,381, of Chen, Y., et al., filed Jul. 31, 2018.
Advisory Action dated Sep. 1, 2020, for U.S. Appl. No. 16/051,381, of Chen, Y., et al., filed Jul. 31, 2018.
Provisional Applications (1)
Number Date Country
62053029 Sep 2014 US
Continuations (1)
Number Date Country
Parent 14592255 Jan 2015 US
Child 15003649 US