US 12,651,237 B2Grant
Acquisition of card information to enhance user experience
Issue Date:2026-06-09
•20 Claims
•21 Drawing Sheets
Abstract
A payment processing service (PPS) can receive, during a transaction, and from a mobile device, tokenized data associated with a customer's payment instrument. The PPS can determine that a first application on the mobile device, and a second application on a second mobile device of a second user, both have connectivity to the PPS. The PPS can register an association between the applications and determine a service offered by the second user. Using the tokenized data, the PPS can determine historical transaction data associated with the payment instrument. The PPS can send personalized content to the mobile device and receive an authorization request and transaction data for the transaction from the mobile device, which the mobile device receives from the second mobile device. The PPS can process payment for the transaction and send to the second application an indication of the authorization, without providing access to card information.
Metadata
Assignee
- Block, Inc.
Inventors
- Paul Aaron
- Shawn Morel
Application Information
Application Number:US 17/669,276
Filing Date:2022-02-10
Priority Date:2012-01-18
Art Unit:3696
Classifications
IPC:
G06Q20/02G06Q20/22G06Q20/32G07B13/00
Patent Drawings (21 sheets)
Description
Related Applications
[0001] This application claims priority to and is a continuation of U.S. patent application Ser. No. 15/728,115, filed on Oct. 9, 2017, which claims priority to and is a continuation of U.S. patent application Ser. No. 13/353,250, filed on Jan. 18, 2012, now known as U.S. Pat. No. 9,785,920, issued on Oct. 10, 2017, the entire contents of which are incorporated herein by reference.
Technical Field
[0002] This disclosure relates to mobile card processing using multiple wireless devices, to acquisition of card information to enhance user experience, and to secure communications between devices.
Background
[0003] In a conventional point-of-sale electronic credit card transaction, the transaction is authorized and captured. In the authorization stage, a physical credit card with a magnetic stripe is swiped through a merchant's magnetic card reader, e.g., as part of a point-of-sale device. A payment request is sent electronically from the magnetic card reader to a credit card processor. The credit card processor routes the payment request to a card network, e.g., Visa or Mastercard, which in turn routes the payment request to the card issuer, e.g., a bank. Assuming the card issuer approves the transaction, the approval is then routed back to the merchant. In the capture stage, the approved transaction is again routed from the merchant to the credit card processor, card network and card issuer, and the payment request can include the cardholder's signature (if appropriate). The capture state can trigger the financial transaction between the card issuer and the merchant, and optionally creates a receipt. There can also be other entities, e.g., the card acquirer, in the route of the transaction. Debit card transactions have a different routing, but also require swiping of the card.
[0004] Mobile card readers are available. Some mobile card readers use WiFi technology to communicate with the credit card processor via a wireless network access point. Some mobile card readers, e.g., in taxies, use cellular technology to communicate wirelessly with the credit card processor.
Summary
[0005] Although mobile card readers are available, e.g., in taxies, such systems are often expensive, difficult to install, or do not significantly enhance the user experience. This specification relates to technologies that allow devices to securely communicate with each other, e.g., via a WiFi hotspot.
[0006] According to one aspect of the subject matter described in this specification, different aspects of card transaction can be divided between different mobile devices. For example, one mobile device can receive transaction details, e.g., as received from a merchant or from a meter in a taxi, whereas a customer can swipe a card and approve the transaction on another mobile device. The devices communicate wirelessly with each other on a wireless network, e.g., a WiFi hotspot, and can communicate with a payment service system, e.g., over the Internet via the WiFi hotspot. Secure communication can be established between the mobile devices on the wireless network without necessarily having access to an external network, e.g., the Internet. Secure communication between mobile card readers, mobile devices, and a payment processing system can be established and maintained throughout processing of the transaction. Thus a customer can securely conduct a distributed payment transaction even though multiple mobile devices are employed. Card information obtained from the swipe can be used to enhance the user experience, e.g., by displaying targeted advertising on one of the mobile devices.
[0007] In one aspect, a method for a transaction with a taxi includes establishing secure communication between a first computing device in a driver section of a vehicle and a second computing device in a passenger section of a vehicle, receiving in the second computing device a card number from a card reader coupled to the second computing device before receiving a signal from a meter indicating an end of a trip for the passenger, after receiving the card number submitting the transaction for authorization from at least one of the first device or the second device, after receiving a signal from the meter indicating the end of the trip for the passenger, displaying an amount of a fare for the trip on a display, and receiving an indication that the transaction is authorized.
[0008] Implementation may include one or more of the following. The first computing device may receive the amount of the fare from a meter in the vehicle. The second computing device may receive the amount of the fare from the first computing device. The second computing device may include the display and may be configured displays the amount of the fare on the display. The second computing device may submit the transaction for authorization. The second computing device may send the card number to the first computing device, and the first mobile computing device may submit the transaction for authorization. Whether the amount exceeds a threshold value may be determined. A request for approval of the transaction on the display may be displayed if the amount exceeds the threshold value. The transaction may be submitted for authorization without displaying a request for approval of the transaction on the display if the amount does not exceed the threshold value. A graphical user interface configured to receive passenger input identifying a tip may be displayed on the display. The transaction may be submitted for authorization after receiving the signal from the meter indicating the end of the trip for the passenger. Card information may be sent to a server via a wireless connection to the Internet, one or more prior destinations associated with a user of the card may be received from the server, and the prior destinations may be displayed on the display. Card information may be sent to a server via the wireless connection to the Internet, data containing an advertisement personalized based on the card information may be received from the server, and the advertisement may be displayed on the display. The card information may include a cardholder name taken from a scan of the card. The card information may include a card number taken from a scan of the card.
[0009] In another aspect, a method for displaying content in a taxi includes establishing secure communication between a first computing device in a driver section of a vehicle and a second computing device in a passenger section of a vehicle, displaying a request for a card scan on a display before receiving a signal from a meter indicating an end of a trip for the passenger, receiving in the second computing device card information from a card reader coupled to the second computing device before receiving the signal from a meter indicating the end of the trip for the passenger, sending the card information to a server a wireless connection to the Internet, and receiving from the server a data containing content personalized based on the card information and displaying the web page on the display.
[0010] Implementation may include one or more of the following features. Displaying the web page may include displaying one or more prior destinations associated with a user of the card. The display may be a touch screen display, and the first mobile device may be configured to receive from the display a passenger selection of one of the prior destinations. A request for permission to store a destination of the trip may be displayed. Displaying the data may include displaying a personalized advertisement.
[0011] In another aspect, a method of providing personalized content includes, before receiving a request for authorization for a transaction for a passenger fare from a mobile device in a vehicle, receiving a card number from the mobile device, generating a token from the card number, matching the token to a user token, generating a data containing content personalized based on the user characteristics associated with the user token, and sending the data to the mobile device.
[0012] Implementation may include one or more of the following features. Generating the token may include applying a one way hash function to the card number. The data may include one or more prior destinations associated with the user token. The web page may include a personalized advertisement. The request for authorization for the transaction for the passenger fare may be received from the mobile device.
[0013] In another aspect, a computer program product to perform a method of providing personalized content, tangibly embodied in a non-transitory computer readable media, comprising instructions for causing a processor to the methods above.
[0014] Advantages may include one or more of the following. A customer can conduct a point-of-sale electronic payment transaction with a merchant without giving the merchant a card. Instead, the customer can conduct a transaction by personally swiping a card. The customer can swipe a card on a mobile device that is wirelessly connected to other devices, enabling the customer to pay at physical locations convenient to the customer. A merchant-facing device can wirelessly and securely send transaction details to a customer-facing device that can process a swipe of a customer's card. In addition, the customer can swipe a card before receiving transaction details and can be provided with a personalized experience by a merchant or another third party. For example, if the customer swipes a card in a taxi on a customer-facing device, the customer-facing device can display the previous destinations of the customer.
Brief Description of the Drawings
[0015] FIG. 1 is a schematic illustration of an example system for communication between mobile devices over a wireless network.
[0016] FIG. 2A is a flow chart of an example pairing process.
[0017] FIG. 2B is a flow chart of an example process for establishing secure communications.
[0018] FIGS. 3A and 3B are views of example graphical user interfaces for two mobile devices.
[0019] FIG. 4 is a flow chart of an example process for establishing secure communication by checking capabilities between devices.
[0020] FIG. 5 is a schematic illustration of an example system for establishing secure communication between mobile devices over a wireless network using a trusted server.
[0021] FIG. 6 is a flow diagram of an example process for establishing secure communication between devices using a trusted server.
[0022] FIG. 7 is a schematic illustration of an example system for processing distributed payment transactions.
[0023] FIG. 8 is a schematic illustration of an example wireless payment system implemented for a taxi.
[0024] FIG. 9 is a flow chart of an example process conducted with the wireless payment system.
[0025] FIG. 10A is a flow chart of an example process conducted by a computer system of a dispatch service.
[0026] FIG. 10B is a flow chart of an example process conducted by a payment service system.
[0027] FIG. 11 is a flow chart of an example process 1300 conducted by a “swipe and ride” wireless payment system.
[0028] FIGS. 12A-17 are example views displayed by a customer application on the mobile device.
[0029] Like reference numbers and designations in the various drawings indicate like elements.
Detailed Description
[0030] Establishing secure communication between devices is useful for many applications, e.g., mobile card processing applications, distributed payment transaction applications, or applications that exchange personally-identifiable information such as a social network application, a chat client, or a file exchange application. By way of illustration, in mobile card processing, if various functions are to be divided between different mobile devices, the transaction may require a secure transfer of confidential information, e.g., a card number, between the mobile devices. Secure communication can be established in two different implementations: 1) by a pairing process in conjunction with a comparison of public keys, or 2) by a trusted server. FIGS. 1-4 concern establishing secure communication through a pairing process in conjunction with a comparison of public keys codes. FIGS. 5-8 concern establishing secure communication through a trusted server.
[0031] By having secure communication between devices, information can confidently be exchanged without fear of fraud or theft. In addition, devices can communicate in a secure manner without communicating through an external network, e.g., the Internet. By avoiding the Internet, the devices can quickly, reliably, and securely communicate with each other without relying on the availability or speed of an Internet connection.
[0032] FIG. 1 is a schematic illustration of an example system 100 for communication between mobile devices over a wireless network. The system 100 shown in FIG. 1 is an example of a system that can be configured to establish secure communication between mobile devices over a wireless network using a pairing process in conjunction with a comparison of public keys. The system 100 includes a first mobile device 102 and a second mobile device 106 that can communicate over wireless network 104. The system 100 can also include additional mobile devices. The system 100 and the wireless network 104 can be connected to an external network, e.g., the Internet 108. For example, the wireless network 104 can be a WiFi hot spot that includes a wireless access point for wireless connection to the mobile devices 102 and 106. The wireless network 104 can also include a wired or cellular, e.g., 3G or 4G, connection the Internet 108. Alternatively or in addition, one or both of the mobile devices 102, 106 could have a wireless connection to the Internet, e.g., over a cell network. However, the Internet 108 is not needed for the two devices 102 and 106 to establish secure communications. The two devices 102 and 106 can establish secure communication solely through the wireless network 104. Establishing secure communications through a pairing process and a comparison of public keys can be implemented with more than two devices.
[0033] In some implementations, described further below, the first device 102 serves as a customer-facing device, and the second device 106 serves as a merchant-facing device 106. A “customer facing” device is a device that is configured with applications to display messages to and receive input from the customer. A “merchant facing” device is a device that is configured with applications to display messages to and receive input from the merchant.
[0034] FIG. 2A is a diagram of an example flow chart of a pairing process 200. The pairing process is one step, e.g., an initial step, of a process conducted between a second device 106 and a first device 102 to establish secure communications. Both the second device 106 and the first device 102 are connected to the wireless network 104. This pairing process 200 can be applied to multiple devices connected to a wireless network, e.g., multiple customer-facing devices, multiple merchant-facing devices, and multiple third-party devices. The pairing process 200 also can be limited to only two devices connected to a wireless network, e.g., one customer-facing device and one merchant-facing device. Both devices run applications that enable the devices to undergo the pairing process 200.
[0035] Pairing two devices with the pairing process 200 indicates a user's intent to have the devices communicate with each other. Each device first generates encryption and decryption keys using a certificate, e.g., a Transport Layer Security (TLS) certificate (step 202, 210). In some implementations, the keys include a public key and a private key. The public key can be a public encryption key while the private key can be a private decryption key. Generally, the public key is widely distributed while the private key is known only to one entity (e.g., the device that generated the private key). Messages can be encrypted using the public key and can only be decrypted using the private key.
[0036] Both the first device 102 and the second device 104 can connect to the wireless network (steps 212, 204). Once each device connects to the wireless network, each device can publish its availability (e.g., whether it is available to communicate) on the wireless network 104 (steps 206, 214). In some implementations, the devices publish their availability through zero configuration networking (ZeroConf) or universal plug and play (UPnP).
[0037] In some implementations, each device publishes a description of its set of capabilities along with the device's availability. In some implementations, the devices exchange descriptions of their set of capabilities after the pairing process. For example, in a payment transaction setting, a set of capabilities can include a device's ability to accept signatures. Another set of capabilities can include a device's ability to accept a swiping of a card. Yet another set of capabilities can include a device's ability to both accept signatures and accept a swiping of a card. Another set of capabilities can include a device's ability to submit a transaction for authorization. One device can refuse to accept data or perform actions requested by the other device that do not correspond to the capabilities associated with the other device, which is further described below in FIG. 4 .
[0038] Each device can receive a list of available devices (steps 208, 216). The list of available devices can include devices that are capable of completing the pairing process. In some implementations, the list of available devices includes devices running a specific version of an application or a specific operating system version. In some implementations, the list of available devices includes a public key associated with each device. In some implementations, after receiving the list of available devices, each device stores the list into a database of known devices. For example, a merchant device can then retrieve a customer-facing device's public key from the database of known devices when the merchant device wishes to securely communicate with the customer-facing device. A first device receives a selection of one of the devices from the received list of available devices (step 218). For example, the first device 102 receives a selection of a second device 106 from the list of available devices. The first device sends a request to the selected device to pair the devices. In some implementations, the device receives input selecting multiple devices to pair together.
[0039] Upon receiving the request to pair the devices, the second device can display a prompt to a user. The prompt can ask whether the devices should be paired together. Once the second device receives input allowing the pairing to the first device (step 220), the second device can generate a pairing code (step 222). The second device then can display the pairing code (step 224). A user then can enter in the pairing code displayed on the second device into the first device (step 226). The entered pairing code is transmitted from the first device to the second device for verification. The second device can then verify that the transmitted code matches the pairing code that was displayed on the second device (step 228). Once the transmitted pairing code is confirmed to match the pairing code displayed in the second device, the second device sends a message to the first device that the pairing is accepted (step 230). The two devices are now paired and can now establish secure communication with each other. In particular, once paired, the devices exchange public keys, and the keys can be used to encrypt communications between the devices.
[0040] The first device can be the customer facing device and the second device can be the merchant facing device, but the roles of the customer facing device and merchant facing device could be reversed, e.g., if the merchant facing device first receives the selection of the customer facing device.
[0041] FIG. 2B is a flow chart of an example process for establishing secure communications when the devices have previously exchanged keys (e.g., using the method of FIG. 2A ). The configuration process can occur after devices are paired with each other. In some implementations, devices can broadcast their respective capabilities (e.g., as described above in FIG. 2A ) to each other or any other device connected to the network after the pairing process (steps 234, 236). In some implementations, the capabilities also include versions of the applications running on the devices, versions of the operating system, or features, e.g., software or hardware capabilities, of each device. The devices can broadcast their capabilities by communicating with each other through a wireless network. The devices then can receive a list of capabilities associated with one or more other devices (steps 238, 240). In some implementations, a device filters the list of capabilities received to include devices having a complementary list of capabilities (steps 242, 244). For example, a device that only has a capability of reading card swipes can limit the list of capabilities received to only include devices having a capability of processing card data.
[0042] Capabilities can be complementary such that the combination of the capabilities can cause an action. In general, one device provides some function or data that the other device requires to perform the action. The function can be performed or the data provided by the other device at the request of the one device. For example, a card reader can be complementary to a card processor, e.g., the card processor needs the card data in order to perform the transaction.
[0043] In some implementations, the process described in FIG. 2A occurs once during an initial setup of the devices. After the initial setup, subsequent secure communication can occur as long as a session between the devices exists. The session can exist as long as all devices are connected to a wireless network. In some implementations, the session exists as long as all devices are running a merchant or customer application. In other words, if a device disconnects from the wireless network or a device quits the application, the session ends and the devices can no longer securely communicate until another session is started.
[0044] In some implementations, before or after the process described in FIG. 2B , a new session is started through a handshake. For example, device A can generate a random number. Device A can retrieve Device B's public key from Device A's database of known devices and encrypt the random number using Device B's public key (previously received in the pairing process shown in FIG. 2A ). If Device B is trusted, Device B can decrypt the random number using its private key, increment the random number, retrieve Device A's public key from Device B's database of known devices, and re-encrypt the random number using Device A's public key (also previously received in the pairing process shown in FIG. 2A ). After Device B sends the data to Device A, Device A can decrypt the random number using its private key and ensure the random number was correctly incremented. At this point, Device A can trust Device B, a session is started between the two devices, and secure communication can commence using the keys to encrypt communications between the devices.
[0045] In some implementations, a session can be started by exchanging public keys. Each device can determine whether the other device is considered a trusted device, i.e., if the received public key matches a public key previously received from the pairing process. If the keys match then the devices are trusted, and secure communication can commence using the keys to encrypt communications between the devices. FIGS. 3A and 3B are views 300 of example graphical user interfaces for two mobile devices. For example, in reference to FIG. 2 (steps 214 and 216), a display 302 of the second device can display a pairing code while a touch-screen display 304 of the first device can receive user input of the pairing code. A user can read the pairing code from the display 302 of the second device and enter the pairing code into the display 304 of the first device. If the entered pairing code matches the transmitted pairing code, the devices can complete the pairing process. Pairing devices can indicate a user's intent for the devices to communicate with each other, but it does not, by itself, necessarily establish secure communication between the devices. The second device can be a merchant-facing device, and the first device can be a customer-facing device.
[0046] FIG. 4 is a flow chart of an example process 400 for establishing secure communication by checking capabilities between devices. The process 400 can for example be performed after devices complete a pairing process, e.g. pairing process 200 as shown in FIG. 2 . The process 400 can be applied to a payment transaction. In a payment transaction after a merchant initializes a transaction, a customer can swipe a card on a customer-facing device while a merchant-facing device can process the card for a transaction amount. A merchant-facing device can start a transaction (step 401). For example, the merchant-facing device can start a transaction when a merchant finalizes a transaction amount to be charged to the customer. The merchant-facing device can send a request for receiving a card swipe to a customer-facing device. The customer-facing device can receive the request and wait for a card swipe. Once the customer-facing device receives a card swipe from a customer (step 402), the customer-facing device can retrieve the merchant-facing device's public key from the database of known devices and encrypt data from a card swipe using the public key (step 404). The customer-facing device can then send the encrypted data to the merchant-facing device.
[0047] Upon receiving the encrypted data, the merchant-facing device can check the capabilities of the customer-facing device (step 406). The merchant-facing device can retrieve the set of capabilities of the customer-facing device from the database of known devices. If the set of capabilities includes the ability to receive card swipes, the merchant-facing device can decrypt the encrypted data using its private key and continue processing the transaction because the merchant-facing device trusts the customer-facing device to receive card swipes (step 408). However, if the set of capabilities does not include the ability to receive card swipes, the merchant-facing device can ignore the encrypted card swipe data because the merchant-facing device does not trust the customer-facing device to receive card swipes (e.g., the customer-facing device can be spoofed to appear legitimate) (step 410). In some implementations, the customer-facing device can check the capabilities of the merchant-facing device (e.g., from the database of known devices) before communicating with the merchant-facing device. For example, as applied in FIG. 4 , if the merchant-facing device did not have the capability of processing card swipes, the customer-facing device can choose not to send the encrypted card swipe data to the merchant-facing device.
[0048] Establishing secure communication through the pairing process in conjunction with a comparison of public keys can require each device to hold a certificate. However, establishing secure communication through a trusted server can require only the trusted server, and not the devices, to hold a certificate. Furthermore, in some implementations, if establishing secure communication through a trusted server, the devices need not undergo a pairing process, e.g. pairing process 200.
[0049] FIG. 5 is a schematic illustration of example system 500 configured to establish secure communication between mobile devices over a wireless network using a trusted server. System 500 is similar to system 100, but the mobile devices 102, 104 are configured to communicate with a trusted server 502. For simplicity, this system 500 is shown as including just the first mobile device 102 and the second mobile device 106 communicating over the wireless network 104, but the system 500 can include additional mobile devices. Establishing secure communications between devices through a trusted server can be implemented with more than two devices. For the purpose of some implementations described below, the first device 102 serves as the customer-facing device and the second device 106 serves as the merchant-facing device.
[0050] The system 500, and the wireless network 104 in particular, are connected to an external network, e.g., the Internet 108. For example, the wireless network 104 can be a WiFi hot spot that includes a wireless access point for wireless connection to the mobile devices 102, 106, and includes a wired or cellular, e.g., 3G or 4G, connection the Internet 108.
[0051] The mobile devices 102, 104 are configured to communicate with the trusted server 502 through the Internet 108. In some implementations, the trusted server 510 is a data processing apparatus having a digitally signed certificate. For example, the digitally signed certificate can be a Transport Layer Security (TLS) certificate.
[0052] FIG. 6 is a flow diagram of an example process 600 for establishing secure communication between devices using a trusted server. For simplicity, this process 600 is shown as including just a first mobile device, a second mobile device, and a trusted server as demonstrated in FIG. 5 , but the process 600 can include additional mobile devices. The first device can be an authenticated device. A device can be authenticated by signing into the trusted server with a user name and a password. In some implementations, the authenticated device is a merchant-facing device. The second device can be an untrusted remote mobile device requesting to be paired with the authenticated mobile device. In some implementations, the remote device is a customer-facing device or a customer's personal device. Both the first and second devices can inspect the trusted server's certificate and can verify the identity of the trusted server using a trusted scheme, e.g., TLS.
[0053] Once the trusted server has been verified, the authenticated device can search for remote devices. In some implementations, the authenticated device searches for remote devices connected to the wireless network 104. In some implementations, the authenticated device searches for remote devices through the trusted server 502. The authenticated device can be searching in the background until the authenticated device finds a remote device. Alternatively, the authenticated device also can enter in a searching mode, during which the authenticated device searches for remote devices in the foreground.
[0054] When an authenticated device locates a remote device, the authenticated device can send a request to start a session for secure communication. In some implementations, the request includes metadata indicating a location, a timestamp, and a random number. In some implementations, the request includes metadata indicating a unique identification of the authenticated device. The authenticated device can send the same request to both the trusted server (e.g., over the Internet 108) (step 604) and the remote device (e.g., over the wireless network 104) (step 602).
[0055] When the trusted server receives the request, the trusted server can generate a public and private key pair (step 605) and send the private key to the authenticated device (step 606). In some implementations, the trusted server generates the keys using its TLS certificate. The trusted server then can start a unique session with the authenticated device using the request information (e.g., location, time, and the random number).
[0056] When the remote device receives the request from the authenticated device, the remote device sends a session request to the trusted server that requests to have the remote device join the session between the trusted server and the authenticated device (step 608). The session request includes the request information received from the authenticated device (e.g., location, time, and the random number) so the trusted server can trust the remote device. In some implementations, once the trusted server receives the session request, the trusted server can verify the remote device is trusted by matching the location, time, and the random number received by the authenticated device (step 609). In some implementations, if the session request includes a unique identification of the authenticated device, the trusted server also matches the unique identification to a list of authenticated devices in a database. After verifying the remote device, the trusted server can join the remote device to the session and send the previously generated public key to the remote device (step 610).
[0057] After receiving the public key, the remote device can generate a unique session key (e.g., a secret key) (step 611). The remote device can encrypt the session key using the public key and send the encrypted key to the authenticated device (step 612). When the authenticated device receives the encrypted key, the authenticated device can decrypt the encrypted key using the private key received from the trusted server. Both the authenticated device and the remote device now have the same session key. From this point, the devices can securely communicate with each other by encrypting and decrypting data using the session key (step 614). Furthermore, the devices do not need to communicate with the trusted server any longer and can communicate through a wireless network 104. Because no private key was ever hardcoded on either mobile device, this process mitigates the risk of the private key being compromised. Furthermore, because every key (e.g., public, private, or session key) is unique for every session, this process minimizes risk exposure. In some implementations, the session key, public, and private key expire once the session ends (e.g., a device disconnects from the trusted server) or after a predetermined amount of time.
[0058] In some situations, e.g. mobile card processing, it may be advantageous to have different functions or steps of a card transaction be divided between different mobile devices. A system for processing distributed payment transactions allows a customer, also called a user or payer, to securely pay a merchant using a distributed payment. A distributed payment is one where a customer conducts the transaction with a merchant at a point of sale by swiping a card at a mobile customer-facing device that is wirelessly connected with the system. A “customer-facing” device is a device that is configured with applications to display messages to and receive input from the customer. The card can be a credit card, debit card, or pre-paid card.
[0059] The system includes a mobile merchant-facing device which communicates with the customer-facing device. The customer-facing device and the merchant-facing device can also connect to a payment service system which processes the transaction using the data from the card swiped by the customer. The system can send confirmation of the transaction to the merchant and/or the customer. The system can also send other data about the transaction to other computer systems, e.g., if the transaction is payment for a taxi ride, the data can include the distance travelled in a taxi.
[0060] FIG. 7 is a schematic illustration of the architecture 700 of an example system for processing distributed payment transactions. The system 700 includes a wireless payment system 702. The wireless payment system 702 includes multiple devices, e.g., a customer facing device 122 and a merchant facing device 126, connected to the wireless network 104. The wireless network 104 is connected at least intermittently to an external network 108, e.g., the Internet. The wireless network 104 can be a wireless access point. In some implementations, the wireless network 104 is a Wireless Fidelity hot spot (Wi Fi hotspot).
[0061] The system 100 or the system 500 can be used in implementing the wireless payment system 702. The customer facing device 122 can be implemented using the first device 102, but with additional programming to enable the device for use in the distributed payment transaction. Similarly, the merchant facing device 126 can be implemented using the second device 106, but with additional programming to enable the device for use in the distributed payment transaction. The wireless network 104 can be implemented using the wireless network 104.
[0062] In some implementations, devices connected to the wireless network 104 can securely communicate with each other, e.g., through a process of establishing secure communication as described above. In particular, once secure communication is established, the devices connected to the wireless network 104 can securely communicate with each other without data passing through the external network 108, e.g., through the Internet.
[0063] The customer facing device 122 can be a mobile computing device, i.e., a hand held computing device, capable of running a customer application. For example, the customer facing device 122 can be a smart phone, tablet computer, laptop, or other data processing apparatus. The customer facing device 122 can include a display, e.g., a touch screen display. In some implementations, the customer facing device 122 and the display are two devices connected to each other.
[0064] The customer facing device 122 can include or be attached a credit card reader 720. For example, the card reader can be attached to an input, e.g., an audio jack, of the customer facing device 122.
[0065] The merchant facing device 126 is also a mobile computing device, capable of running a merchant application. For example, the merchant facing device 126 can be a smart phone, tablet computer, laptop, or other data processing apparatus. The merchant facing device 126 can also include a display, e.g., a touch screen display. In some implementations, the wireless payment system 702 includes more than one customer facing device or more than one merchant facing device.
[0066] In some implementations, the merchant application has a login and logout functionality such that multiple merchants, each having a separate account with the payment processing system 708, can use the same device 126 for processing distributed payment transactions. Association by the payment processing system 708 of the device 126 with the appropriate merchant account can be done by conventional login techniques.
[0067] In some implementations, the system 700 includes a computer system 704 connected to the network 108. The computer system 704 can process or store data related to the transaction for analysis by the merchant or another third party that has a right to the data related to the transaction. For example, the merchant can be a franchisee and the third party can be the franchisor. As another example, third party can be responsible for coordinating jobs between various merchants who are themselves independent contractors, e.g., the merchant can be a taxi driver and the third party can be a dispatcher.
[0068] When a merchant submits a transaction to the payment service system 708, the transaction can include sufficient information, e.g., the name or id number of the merchant, to associate the merchant with the third party. The payment service system 708 can maintain a database associating merchants with third parties, and when the payment service system 708 receive this information, it can identify the associated third party from the information. This allows the payment service system 708 to send data about transactions to the computer system 704 of the associated third party.
[0069] For example, if the system 700 is implemented in a restaurant, a customer can pay a restaurant using the wireless payment system 702 after a waiter at the restaurant brings the customer the final tab of the meal. After conducting the transaction, the system can send data about the meal to a computer system 704, e.g., a meal tracking system. The data can include which items were ordered, the cost of the meal, the tip included, the date and time of the meal, or which waiter served the customer.
[0070] In some implementations, the customer facing device 122 receives transaction details from the merchant facing device 126 and displays the details on the display of the merchant facing device 126. In particular, the merchant facing device 106 can calculate an amount for the transaction, e.g., based on purchase of individual items, and the amount can be sent to the customer facing device 122 and displayed.
[0071] The wireless payment system 702 can communicate with a payment service system 708 using the network 108.
[0072] In some implementations, the merchant facing device 126 receives transaction details from the customer facing device 122 and communicates with the payment service system 708 to submit a request for authorization of the transaction. In particular, when the customer swipes the card through the card reader 720, the card information can be sent to the merchant facing device 126. Similarly, a signature, PIN, or other data required for authorization of the transaction can be input by the customer into the customer facing device 122, e.g., entered on the touch screen display, and this data can be sent to the merchant facing device 126.
[0073] In some implementations, the customer facing device 122 does not send transaction details to the merchant facing device 126. Instead, the customer facing device 122 receives the amount for the transaction from the merchant facing device 126, and receives the card information from the card reader 720 when the customer swipes the card. The customer facing device 122 communicates with the payment service system 708 to submit a request for authorization of the transaction.
[0074] The payment service system 708 includes a secure server 712 to processes all transactions from the wireless payment system 702. The secure server 712 handles secure information such as credit card numbers, debit card numbers, bank accounts, user accounts, user identifying information or other sensitive information.
[0075] The payment service system 708 can communicate electronically with a card payment network 716, e.g., Visa, Mastercard, or the like. The payment service system 708 can communicate with a card payment network 716 over the same network 108 used to communicate with the wireless payment system 702, or over a different network. The computer system 716 of the card payment network can communicate in turn with a computer system 718 of a card issuer, e.g., a bank. There can also be computer systems of other entities, e.g., the card acquirer, between the payment service system 708 and the card issuer.
[0076] Before a transaction between the user and the merchant can be performed using the wireless payment system 702, the merchant must create a merchant account with the payment service system 708. The merchant can sign up using a mobile application or using an online website, and can use a device within the wireless payment system 702 or another computing device, e.g., a home computer. At some point prior to the transaction, one or more applications are downloaded to the devices within the wireless payment system 702, e.g., a merchant facing device and a customer facing device. The merchant facing and customer facing devices may run the same application or customized applications to each device (e.g. a merchant application and a customer application). In some implementations, the applications are downloaded through an application store. Creation of the merchant account can be handled through the application, or through another application, e.g., a generic web browser. The merchant enters a name, account password, and contact information, e.g., email address, and physical location information (if applicable), e.g., an address, into the payment service system 708. The merchant can also provide other information, e.g., a list of goods or services available, operating hours, phone number, a small identifying image logo or mark, to the payment service system 708. The data associated with the merchant account 714 can be stored at the secure server 712, e.g., in a database. In some implementations, the merchant can provide information sufficient to establish communication with the computer system 704 and this information can be stored in the payment service system 708.
[0077] Eventually, in order to receive funds from the transaction, the merchant will need to enter financial account information into the payment service system 708 sufficient to receive funds. For example, in the case of a bank account, the user can enter the bank account number and routing number. However, the merchant's financial account can also be associated with a credit card account or another third party financial account. In addition, in some implementations, if the merchant has not entered the financial account information, the payment service system 708 can hold the received funds until the financial account information is provided.
[0078] FIG. 8 is a schematic illustration of a wireless payment system implemented in a taxi environment. The wireless payment system 102 includes a meter 802, a mobile driver side (i.e., merchant facing) device 126, a passenger side (i.e., customer facing) device 122, a card reader 810, and the wireless network 104. The wireless network 104 can include wireless access point mounted in the vehicle that provides a WiFi hot spot. The wireless network 104 can include a transceiver that provides a cellular connection, e.g., 3G or 4G, to the external network 108.
[0079] In some implementations, the driver side device 126 is physically connected to the meter 802, e.g., by a data cable, such as a USB cable. The driver side device 126 can be positioned next to the taxi driver in the front of the taxi. The driver side device 126 is wirelessly connected to the wireless network 104. The driver side device 126 can be a smart phone or tablet computer having a display onto which the driver has loaded an appropriate application. The driver side device 126 can also display a passenger fare for the taxi ride.
[0080] The passenger side device 122 can be positioned in the back of the taxi where a customer can interface with the device. For example, the passenger side device 122 can be affixed to the back of the taxi with the card reader 810 attached to an input, e.g., an audio jack, of the passenger side device 122. The passenger side device 122 is wirelessly connected to the wireless network 104. The passenger side device 122 can be a tablet computer onto which an appropriate application has been loaded. As a tablet computer, the passenger side device 122 includes a display, e.g., a touch screen display.
[0081] In some implementations, the driver application has a login and logout functionality such that multiple taxi drivers, each having a driver account, can use the same device 126 for processing distributed payment transactions. Association by the payment processing system 708 of the device 126 with the appropriate driver account can be done by conventional login techniques.
[0082] The driver side device 126 can read data from the meter 802, e.g. fare of a trip, while the passenger side device 122 can read card data, i.e., card information such as the card number, or cardholder name, from the card reader 810. The wireless payment system 102 can communicate with the payment service system 708 over the external network 108, e.g., the Internet.
[0083] The wireless payment system 102 can also communicate with a computer system 812, e.g., a dispatch system, of a dispatcher. The computer system 812 can process or store data about taxi rides, as discussed below.
[0084] In the taxi environment, when a driver submits a transaction to the payment service system 708, the transaction can include sufficient information, e.g., the name or id number of the driver, to associate the driver with the dispatcher. The payment service system 708 can maintain a database associating drivers with dispatchers, and when the payment service system 708 receive this information, it can identify the associated dispatcher from the information. This allows the payment service system 708 to send data about the taxi ride to the computer system 812 of the associated dispatcher.
[0085] For example, if the system 700 is implemented in a taxi, a customer can pay a taxi driver using the wireless payment system 702 after the taxi driver brings the customer to the customer's destination. After conducting the transaction, the system can send data about the taxi ride to a computer system 704, e.g., the computer system of the dispatcher. The data can include a start location and an end location of the taxi ride, the duration of the trip, the distance of the trip, the date and time of the trip, total cost of the trip (e.g., passenger fare and tip), or which taxi cab performed the service.
[0086] FIG. 9 is a diagram of an example flow chart of a process 900 conducted with the wireless payment system 102 implemented in a taxi environment. For example, a customer can enter a taxi and ask a taxi driver to take the customer to a destination. The taxi driver starts a meter that determines the fare of the trip based at least on the distance and duration of the trip. In some implementations, when the driver starts the meter, the meter generates a signal that is sent to the driver side device indicating that the ride has started.
[0087] Once the taxi driver arrives at the destination, the taxi driver stops the meter, which causes the meter to finalize the fare of the trip. The driver side device then receives the fare of the trip from the meter (step 902). The driver side device can send the fare of the trip to the passenger side device (step 904). In some implementations, the driver side device sends the fare to the passenger side device after receiving a signal from the meter (e.g., the driver stops the meter) indicating an end of the trip.
[0088] Once the passenger side device receives the fare of the trip through the wireless network, the passenger side device can display the fare of the trip (step 906) to the customer. The customer can pay by swiping a card through the card reader attached to the passenger side device. The passenger side device can receive card data, the card number, from the card reader (step 908). In some implementations, the passenger side device can receive card data from a customer that manually inputs in a card number. After receiving card data, the passenger side device can optionally display a request for a signature and receive a signature approving the transaction (step 910). The passenger side device can display a request to enter a tip amount, and can receive passenger input selecting a tip amount. The passenger side device can calculate a total transaction amount (the fare plus the tip) and display the total transaction amount. The passenger side device can also receive contact information for a receipt (step 912). The passenger side device can receive this information through customer input into the passenger side device, e.g., through a graphical user interface on the touch screen display.
[0089] In some implementations, the passenger side device initiates the request for authorization of the transaction. In this case, the passenger side device sends the payment information, which includes at least the transaction amount and the card data (e.g., the card number), but may also include the signature and contact information, directly to the payment service system.
[0090] In some implementations, the driver side device initiates the request for authorization of the transaction. In this case, the passenger side device sends the payment information, including at least the card data received from the card reader, to the driver side device (step 914). The signature, tip amount or total transaction amount, and contact information can also be sent to the driver side device. The driver side device can then send the payment information to the payment service system (step 916/1006).
[0091] FIG. 10B is a diagram of an example flow chart of a process 1014 conducted by a payment service system 708 after receiving a distributed payment transaction from the wireless payment system 102. The payment service system 708 can receive the distributed payment transaction from the wireless payment system (step 1006). The distributed payment transaction can include card data, a signature, and other payment information (e.g., payment amount) provided by the customer.
[0092] The payment service system 708 then processes the distributed payment transaction (step 1008) by sending a record to the computer system of the card payment network 716, e.g., Visa or MasterCard, and the card payment network 716 then sends the record to the card issuer, e.g., the bank, as described above in FIG. 1 .
[0093] If the transaction fails because it would exceed the credit limit or there are insufficient funds in the customer's financial account, the payment service system 708 notifies the application on whichever device (driver side or passenger side) that initiated the request for authorization. A notice of the failure of the transaction can be displayed on the passenger side device.
[0094] If the transaction succeeds and the payment service system 708 receives approval from the card payment network 716, the payment service system 708 communicates this to whichever device (driver side or passenger side) that initiated the request for authorization. The driver side and/or passenger side device then captures the transaction. In the capture stage, the approved transaction is again routed from the capturing device to the card processor, card network and card issuer. The record of the transaction in the capture stage can include the cardholder's signature (if appropriate), or other information. The capture state can trigger the financial transaction between the card issuer and the merchant. On receipt of an indication from the card network that the transaction has been captured, the payment service system 708 optionally creates receipts to send to the customer, e.g., through the customer application and/or through the previously provided contact email, and to the merchant. For example, if the wireless payment system 702 is implemented in a taxi environment, before signing for the transaction, the customer can input an email address to which the payment service system can send the receipt. Both devices can then display the receipt in each of their applications.
[0095] Furthermore, in some implementations, the driver side device or passenger side device sends data about the taxi trip to a dispatch system (step 918 in FIG. 9 ). The data about the taxi trip can be sent directly to the dispatch system, or the data can be sent to the payment service system which then routes the data about the taxi trip to the dispatch system. The data about the taxi trip can include a start location and an end location of the taxi ride, the distance of the trip, the duration of the trip, the date and time of the trip, fare of the trip, or which taxi cab performed the service.
[0096] In some implementations, the driver side device is configured to determine its location using a mobile device tracking function, e.g., GPS or cellular multilateration. The driver side device determines the start location upon receiving a signal indicating the start of a ride (e.g., a signal that the taxi driver started the meter), and determines an end location upon receiving a signal indicating the end of a ride (e.g., a taxi driver stopping the meter). In some implementations, the meter is configured to determine its location using a mobile device tracking function, e.g., GPS or cellular multilateration, and the meter provides the start location and end location to the driver side device. The driver side device sends the start location and the end location to the computer system of the dispatcher, e.g., directly or via the payment service system.
[0097] Since the meter measures the distance travelled, meter can provide the distance travelled to the driver side device. The driver side device can measure the duration of the trip and the date and time of the trip based on the start time and the end time of the signals received. The driver side device can store the fare of the trip by reading the data from the meter. The driver side device can also store which taxi cab performed the service based on personal information entered when installing the merchant application or a mobile device identification code that was assigned to the taxi cab when installing the merchant application. Because a mobile device identification code is unique, the mobile device identification code can be associated with a taxi driver and other ride information. In some implementations, the wireless network is assigned a unique wireless access point identification code, and this wireless access point identification code is sent to the dispatch system to be associated with the taxi driver and other data (e.g., start and end locations of the trip, a duration of the trip, fare of the trip, etc.).
[0098] In some implementations, the data about the taxi ride is sent by the driver side device upon receiving a signal indicating the end of the ride. In other implementations, the driver side device, the driver side device stores the data and sends the data to the computer system of the dispatch service at a later time (e.g., in a batch at the end of a workday).
[0099] FIG. 10A is a diagram of an example flow chart of a process 1000 conducted by a dispatch system after receiving a distributed payment transaction implemented in a taxi environment. The dispatch system can be a computer system that analyzes data. The dispatch system can receive data about the taxi ride (step 1002). The data can be sent by the wireless payment system 102 or the payment service system 708. The dispatch system can then store ride information in a database (step 1004).
[0100] FIG. 11 is a diagram of an example flow chart of a process 1100 conducted by a “swipe and ride” wireless payment system implemented in a taxi. A “swipe and ride” wireless payment system implemented in a taxi allows a customer to swipe a card at the beginning of a ride, e.g., upon a customer's entering a taxi, and to pay using the card at the end of the ride without having to swipe again. During the ride, the “swipe and ride” system can provide a personalized ride by displaying information specific to the customer.
[0101] The driver side device (i.e., merchant facing device) can receive a signal from a taxi driver indicating the start of a ride (step 1102) (e.g., the taxi driver starting the meter). This can trigger the passenger side device (i.e., customer facing device) to receive card data from a customer (step 1104). A customer can provide card data by manual input or by swiping a card at a card reader attached to the passenger side device. In some implementations, the card reader retrieves card data including the cardholder's name (e.g., customer's name) from the card. In some implementations, the card reader retrieves card data including the card number from the card. In some implementations, the customer can provide card data before the driver side device receives a start signal from the taxi driver. For example, the passenger side device can have a default display requesting that the user swipe a card through the card reader.
[0102] If a customer swipes a card before the end of the ride, the wireless payment system can establish an identity of the customer (step 1106). The wireless payment system can establish an identity of the customer by tokenizing the received card data and sending the tokenized card data to the payment service system 708. In some implementations, tokenizing the card data creates a unique hash of the card data that indicates a unique identity for the card owner. Tokenized card data can contain encrypted card data and therefore can be securely transmitted from the wireless payment system to the payment service system 708. The payment service system 708 receives the tokenized card data and determines whether the tokenized card data exists in an identity database. If the received tokenized card data does not exist in the identity database, the payment service system 708 can create an identity associated with the tokenized card data. In some implementations, if the payment service system 708 receives tokenized card data that already exists in an identity database, the payment service system 708 retrieves data about the identity, processes the data to create a response that includes a personalized experience, and sends the response back to the passenger side device of the wireless payment system.
[0103] A wide variety of data can be stored by the payment service system 708. For example, if a passenger indicates consent on the customer side device, then the end location of the trip can be stored by the payment service system 708 and associated with the tokenized card data. Thus, as the passenger takes multiple rides, the payment service system 708 will assemble a history of destinations of the customer.
[0104] In some implementations, the response includes a history of recent destinations, e.g., a customer's previous three destinations, or the most frequent destinations travelled to by the customer. The passenger side device can display the previous destinations to the customer. The passenger side device can receive a selection from the previous destinations that is chosen by the customer, e.g., through a tapping gesture on a touch screen display. The passenger side device then can transmit the selection to the driver side device through the wireless network. The driver side device then can receive the destination selected by the customer and display the destination. This can allow the driver to quickly understand where to take the customer.
[0105] In some implementations, the response includes an advertisement personalized to the identity of the passenger. For example, if the identity frequently visits a restaurant, the advertisement can be an offer to that restaurant or can be an offer to similar restaurants related to the frequently visited restaurant. The passenger side device can display the advertisement received to the customer.
[0106] The passenger side device can receive the response and personalize the ride by displaying the response to the customer (step 1108). In some implementations, if the tokenized card data is not yet associated with an identity in the payment service system 708, the payment service system 708 may not have enough information to generate a personalized ride and the passenger side device displays local events or news to the customer.
[0107] The customer can also provide a tip before arriving at a destination. In some implementations, the passenger side device displays an option to display a view for obtaining a tip through a graphical user interface. Upon receiving input to display the tip view, e.g., a tapping gesture on a touch screen display from the customer, the passenger side device displays the view as further described in FIG. 14 . Once the customer finalizes the tip amount, the passenger side device can add the tip amount specified by the customer to the fare of the ride once the ride ends.
[0108] Once the taxi arrives at the customer's destination, the taxi driver can stop the meter. In some implementations, stopping a meter generates an end signal that indicates the end of a ride. Once the driver side device receives this signal (step 1110), the driver side device communicates with the passenger side device to finalize the distributed payment transaction. The passenger side device can display the payment information received when the customer first swiped a card, e.g., upon entering the taxi, and can confirm the payment information with the customer. In some implementations, the passenger side device also displays a request for permission to store the destination of the trip. If the customer approves the request, the passenger side device can send the destination of the trip to the payment service system, which can associate the destination of the trip with the identity (i.e., tokenized card data) of the customer. On the passenger side device, the customer can confirm the transaction by either signing a digital receipt on the passenger side device or approving the transaction through the passenger side device. In some implementations, the customer does not have to sign a digital receipt if the fare and tip is less than a predetermined threshold, allowing the payment service system 708 can submit the transaction for authorization without a signature. Once the passenger side device receives approval of the transaction from the customer, the passenger side device can send the payment information to the driver side device (step 1112). The driver side device can then send a record of the distributed payment transaction to the payment service system (step 1116). The driver side device can also send ride information to a dispatch service (step 1118). As mentioned above, in some implementations, the passenger side device sends a record of the distributed payment transaction to the payment service system 708. Also, the payment service system 708 or the passenger side device can send ride information to a dispatch service.
[0109] The “swipe and ride” system is not limited to a taxi environment. For example, the “swipe and ride” system can be applied to a restaurant environment. Upon entering a restaurant, a customer can swipe a card at a customer facing device. After a swiping of the card, “swipe and ride” system can send the tokenized card data to the payment service system, either through a customer facing device or a merchant facing device. The payment service system can retrieve the identity associated with the tokenized card data and send data including a personalized experience to the customer facing device. For example, the “swipe and ride” system can provide the customer facing device with data that displays the customer's previously ordered items or the customer's most frequently ordered items at the restaurant.
[0110] FIG. 12A is a diagram of an example events view 1200 displayed by a customer application on the customer facing device. The customer application can cause the customer facing device to send the current time and location to the payment service system 708 or another system that can determine items of interest. The system that receives the request can process the request and send a list of relevant events to the customer facing device based at least on the current time and location of the customer facing device. For example, if the application is implemented in a taxi environment, the customer facing device can receive a list of relevant results and display the list through the events view 1200 of the customer application while the customer is riding the taxi en route to or arriving at a destination. This events view 1200 can display current events A 1212, B 1214, C 1216, D 1218, or E 1220 that are occurring on different days near the present date and time. By selecting any event, the customer can learn more information about the event. The customer facing device receives a selection of an event and sends a request for more information to the payment service system 708 or another system that has information about the event. The customer facing device can receive a response including more information about the event and can display more information about the event in a new view. The view 1200 can display the amount due 1202 which is set by the merchant. For example, if the application is implemented in a taxi environment, the amount due 1202 can be set when the taxi driver stops the meter from running. Alternatively, the amount due 1202 can be updated periodically when a new value is received from the merchant facing device. The events view 1200 also can provide options for the customer to change views from events 1204 to news 1206 or a map 1208. In some implementations, the customer facing device can display an option to view more information about the merchant or the driver of the taxi. The view also provides an option for the customer to “Pay Now” 1210. Invoking “Pay Now” 1210 can cause the application to display the views described in FIGS. 15 17.
[0111] FIG. 12B is a diagram of an example news view 1221 displayed by a customer application on the customer facing device. The news view 1221 can display a sports section 1222 with the most recent sports statistics or game information, a weather section 1224 with information about the local weather, or a news section 1226 with the most recent news. By selecting any entry in the sections, the customer can learn more information about the entry selected. The customer facing device receives a selection of an entry and sends a request for more information to the payment service system 708 or another system that has information about the entry. The customer facing device can receive a response including more information about the entry and can display more information about the entry in a new view. In some implementations, the customer can customize the sections displayed. For example, the customer can choose to view a stocks section or a social network section. In some implementations, if the customer “swipes and rides”, the application retrieves the customer's identity and loads the previously customized sections associated with the identity. The customer can also switch views and “Pay Now” as described above.
[0112] FIG. 12C is a diagram of an example maps view 1227 displayed by a customer application on the customer facing device. In some implementations, the customer facing device can obtain its location, e.g., using GPS. The maps view 1227 can display a map 1228 around the current location 1230 of the customer facing device. Once the maps view 1227 is selected, the customer facing device can send its location, e.g., using GPS, to the payment service system 708 or another system, e.g., a Maps Application Program Interface. The customer facing device can receive data that enables the device to display a map to a customer. For example, if the customer application is implemented in a taxi environment, the customer facing device can provide a map 1228 that displays a geographic region around the device's current location, which can be moving because the device is in a mobile vehicle. In some implementations, the map 1228 displays the cross streets of the current location (e.g., King Street & 4th Street) and the bus lines nearby (e.g., N, K, T). The customer can also interact with the map 1228 by zooming in or zooming out. The customer can also switch views and “Pay Now” as described above.
[0113] FIG. 13 is a diagram of an example tip view 1300 displayed by a customer application on the customer facing device for obtaining a tip. The tip view 1300 allows the customer to choose the amount of tip the customer wants to leave the merchant at the end of the transaction. An instruction 1302 saying “How much would you like to tip?” can direct the customer to select one of the options 1304 provided by the application. The customer can select 0%, 10%, 15%, 20%, or enter in a custom percentage. The application can display the actual amount of money the percentage tip translates to under the percentage amount. After selecting a tip amount, the customer can invoke the “Continue” button 1306 to continue the payment process. The customer facing device then calculates the additional tip (if any) and adds it to the original transaction amount to present a final payment amount to the customer.
[0114] FIG. 14 is a diagram of an example payment view 1400 displayed by a customer application on the customer facing device for obtaining payment. For example, if the customer application is implemented in a taxi environment, the payment view 1400 can include instructions to “Give the driver cash or swipe your card now” 1406. An animation 1404 can instruct the customer how to pay the merchant by displaying a physical swiping motion at the card reader. A status bar 1402 can display which steps have been completed by the customer. Upon swiping a card, the device processes the card data and can cause the customer application to display the next step in the payment process.
[0115] FIG. 15 is a diagram of an example signature view 1400 displayed by a customer application on the customer facing device for obtaining a signature. The signature view 1500 can instruct the customer to provide a signature on the customer facing device. For example, a customer named John Smith can sign the signature 1506 on the customer facing device, e.g., a tablet computer, using the customer's finger. Detailed information 1508 can be displayed under the signature 1506 to accurately confirm the customer's payment information. A status bar 1502 can display which steps have been completed by the customer. The customer can continue the payment process by invoking the “Continue” button 1504. The customer facing device can store the signature to be sent as part of the distributed payment transaction to the payment service system 708.
[0116] FIG. 16 is a diagram of an example receipt view 1600 displayed by a customer application on the customer facing device for obtaining a receipt. The re17ceipt view 1600 allows the customer to choose the preferred delivery method for the receipt for the transaction. An instruction “Would you like a receipt?” 1606 can direct the customer to select a delivery method for the receipt. In some implementations, a customer selects from four options 1608. The receipt can be sent via text message, email, physical paper, e.g., printed by the merchant, or the customer can opt out of receiving a receipt. A status bar 1602 can display which steps have been completed by the customer. The customer can continue the payment process by invoking the “Continue” button 1604. The customer facing device can then include this preferred delivery method in its communication with the payment service system 708.
[0117] FIG. 17 is a diagram of an example final view 1700 displayed by a customer application on the customer facing device for displaying confirmation of the transaction. The customer facing device can display the final view 1700 once the customer facing device receives confirmation from the payment service system 708 that the transaction is approved. The customer facing device can receive confirmation from the merchant facing device or directly from the payment service system 708. An indication that the payment is complete 1704 confirms to the customer that the distributed payment transaction has been approved. A status bar 1702 can display which steps have been completed by the customer. At this point, the customer has completed the payment process.
[0118] Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a non-transitory computer storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively or in addition, the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. A computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Moreover, while a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially-generated propagated signal. The computer storage medium can also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices).
[0119] The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.
[0120] The term “data processing apparatus” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations, of the foregoing The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.
[0121] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language resource), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
[0122] The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
[0123] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few. Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
[0124] To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending resources to and receiving resources from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.
[0125] Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components.
[0126] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server.
[0127] A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.
[0128] While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any inventions or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
[0129] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
[0130] In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.
[0131] Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. For example, usage of wireless payment system may not be limited to a taxi environment but could also be applied to other environments, such as a restaurant. Moreover, usage of the techniques to establish secure communication may not be limited to mobile devices, but could also be applied to non-mobile or wired devices connected to a network. Although the swiping of a card through a reader is described above, other techniques for scanning a card, e.g., chip reading or near field communication, could be used to read data from the card.
Claims
What is claimed is:
1. A method comprising:
receiving, by one or more servers of a payment processing service and from a first mobile device associated with a customer, tokenized data associated with a payment instrument of the customer presented for a payment in a transaction, and wherein the tokenized data is generated by the first mobile device;
determining, by the one or more servers, that a first application executing on the first mobile device and a second application executing on a second mobile device have connectivity to the payment processing service, the first application being associated with the customer and the second application being associated with a second user;
based at least in part on determining that the first application and the second application have connectivity to the payment processing service, registering, by the one or more servers, an association between the first application and the second application for processing of the payment in the transaction;
determining, by the one or more servers, a service that is offered by the second user to the customer;
determining, by the one or more servers and based at least in part on the tokenized data, first transaction data corresponding to historical transactions conducted using the payment instrument, wherein the first transaction data is stored in a database associated with the payment processing service;
determining, by the one or more servers and based at least in part on the first transaction data, one or more characteristics of the historical transactions;
generating, by the one or more servers and based at least in part on the one or more characteristics of the historical transactions, personalized content data personalized for the customer;
causing presentation, by the one or more servers and via a graphical user interface of the first mobile device, of the personalized content data;
receiving, by the one or more servers and from the first mobile device, a request for authorization of the transaction and second transaction data associated with the transaction, wherein the first mobile device receives the second transaction data from the second mobile device;
processing, by the one or more servers, the payment; and
sending, by the one or more servers and to at least the second application and without providing the second application with access to card information, an indication that the payment in the transaction is authorized.
2. The method of claim 1, wherein the tokenized data comprises card information associated with the payment instrument and includes at least one of a cardholder name or a card number taken from a scan of the payment instrument.
3. The method of claim 1, wherein the graphical user interface comprises a first graphical user interface, the method further comprising:
generating, by the one or more servers, a second graphical user interface configured to receive passenger input identifying a tip; and
sending, by the one or more servers and to the first mobile device, the second graphical user interface for display.
4. The method of claim 1, wherein the personalized content data comprises an advertisement personalized based at least in part on the payment instrument.
5. The method of claim 1, wherein the personalized content data is based at least in part on customer characteristics of the customer.
6. The method of claim 1, wherein the personalized content data is associated with a destination of the customer and one or more previous destinations associated with the tokenized data.
7. The method of claim 1, wherein the graphical user interface comprises a first graphical user interface, the method further comprising:
receiving, by the one or more servers, via the first graphical user interface, input identifying a tip; and
causing, by the one or more servers, a second graphical user interface to be displayed, the second graphical user interface comprising selectable options associated with one or more tip amounts.
8. A system comprising:
one or more processors; and
non-transitory computer-readable media storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
receive, by a payment processing service and from a first mobile device associated with a customer, tokenized data associated with a payment instrument of the customer presented for a payment in a transaction, and wherein the tokenized data is generated by the first mobile device;
determine that a first application executing on the first mobile device and a second application executing on a second mobile device have connectivity to the payment processing service, the first application being associated with the customer and the second application being associated with a second user;
based at least in part on determining that the first application and the second application have connectivity to the payment processing service, register an association between the first application and the second application for processing of the payment in the transaction;
determine a service that is offered by the second user to the customer;
determine, based at least in part on the tokenized data, first transaction data corresponding to historical transactions conducted using the payment instrument, wherein the first transaction data is stored in a database associated with the payment processing service;
determine, based at least in part on the first transaction data, one or more characteristics of the historical transactions;
generate, based at least in part on the one or more characteristics of the historical transactions, personalized content data personalized for the customer;
cause presentation, via a graphical user interface of the first mobile device, of the personalized content data;
receive, from the first mobile device, a request for authorization of the transaction and second transaction data associated with the transaction, wherein the first mobile device receives the second transaction data from the second mobile device;
process, by the payment processing service, the payment; and
send, to at least the second application and without providing the second application with access to card information, an indication that the payment in the transaction is authorized.
9. The system of claim 8, wherein the personalized content data is associated with a destination of the customer and one or more previous destinations associated with the tokenized data.
10. The system of claim 8, wherein the graphical user interface comprises a first graphical user interface, the operations further comprising:
generate a second graphical user interface configured to receive passenger input identifying a tip; and
send, to the first mobile device, the second graphical user interface for display.
11. One or more non-transitory computer readable media storing instructions that, when executed, cause one or more processors to perform acts comprising:
receiving, by a payment processing service and from a first mobile device associated with a customer, tokenized data associated with a payment instrument of the customer presented for a payment in a transaction, and wherein the tokenized data is generated by the first mobile device;
determining that a first application executing on the first mobile device and a second application executing on a second mobile device have connectivity to the payment processing service, the first application being associated with the customer and the second application being associated with a second user;
based at least in part on determining that the first application and the second application have connectivity to the payment processing service, registering an association between the first application and the second application for processing of the payment in the transaction;
determining a service that is offered by the second user to the customer;
determining, based at least in part on the tokenized data, first transaction data corresponding to historical transactions conducted using the payment instrument, wherein the first transaction data is stored in a database associated with the payment processing service;
determining, based at least in part on the first transaction data, one or more characteristics of the historical transactions;
generating, based at least in part on the one or more characteristics of the historical transactions, personalized content data personalized for the customer;
causing presentation, via a graphical user interface of the first mobile device, of the personalized content data;
receiving, from the first mobile device, a request for authorization of the transaction and second transaction data associated with the transaction, wherein the first mobile device receives the second transaction data from the second mobile device;
processing, by the payment processing service, the payment; and
sending, to at least the second application and without providing the second application with access to card information, an indication that the payment in the transaction is authorized.
12. The one or more non-transitory computer readable media of claim 11, wherein the tokenized data comprises card information associated with the payment instrument and includes at least one of a cardholder name or a card number taken from a scan of the payment instrument.
13. The one or more non-transitory computer readable media of claim 11, wherein the personalized content data is associated with a destination of the customer and one or more previous destinations associated with the tokenized data.
14. The one or more non-transitory computer readable media of claim 11, wherein the graphical user interface comprises a first graphical user interface, the acts further comprising:
receiving, via the first graphical user interface, input identifying a tip; and
causing presentation of a second graphical user interface, the second graphical user interface comprising selectable options associated with one or more tip amounts.
15. The method of claim 1, further comprising:
receiving, by the one or more servers and from the first mobile device, an indication of input to the graphical user interface, wherein the input comprises a request for customization of the personalized content data; and
based at least in part on the input, causing presentation, by the one or more servers, of an updated graphical user interface representing customized personalized content data.
16. The method of claim 1, further comprising:
receiving, by the one or more servers and from the first mobile device, an indication of input to the graphical user interface, wherein the input comprises a request for presentation of additional content; and
based at least in part on the input, causing presentation, by the one or more servers, of an updated graphical user interface including the additional content.
17. The method of claim 1, further comprising:
processing, by the one or more servers, the historical transactions based at least in part on the first transaction data.
18. The system of claim 8, the operations further comprising:
receiving, by the payment processing service and from the first mobile device, an indication of input to the graphical user interface, wherein the input comprises a request for customization of the personalized content data; and
based at least in part on the input, causing presentation, by the payment processing service, of an updated graphical user interface representing customized personalized content data.
19. The system of claim 8, the operations further comprising:
receiving, by the payment processing service and from the first mobile device, an indication of input to the graphical user interface, wherein the input comprises a request for presentation of additional content; and
based at least in part on the input, causing presentation, by the payment processing service, of an updated graphical user interface including the additional content.
20. The system of claim 8, the operations further comprising processing, by the payment processing service, the historical transactions based at least in part on the first transaction data.
Patent Citations (66)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5828738(A) | 1998-10-01 | Spaeth | Applicant |
| US5897626(A) | 1999-04-01 | Pomerantz | Applicant |
| US6289315(B1) | 2001-09-01 | Calvi | Applicant |
| US6347739(B1) | 2002-02-01 | Tamam | Applicant |
| US6600994(B1) | 2003-07-01 | Polidi | Applicant |
| US7991434(B2) | 2011-08-01 | Yen et al. | Applicant |
| US9785920(B2) | 2017-10-01 | Aaron et al. | Applicant |
| US9824504(B2) | 2017-11-01 | Aaron et al. | Applicant |
| US11257048(B2) | 2022-02-01 | Aaron et al. | Applicant |
| US2002/0052751(A1) | 2002-05-01 | Ebata | Applicant |
| US2002/0138423(A1) | 2002-09-01 | Takatori et al. | Applicant |
| US2002/0152179(A1) | 2002-10-01 | Racov | Applicant |
| US2002/0190118(A1) | 2002-12-01 | Davenport et al. | Applicant |
| US2003/0065556(A1) | 2003-04-01 | Takanashi et al. | Applicant |
| US2003/0068999(A1) | 2003-04-01 | Casali et al. | Applicant |
| US2003/0101137(A1) | 2003-05-01 | Wronski, Jr. | Applicant |
| US2003/0222134(A1) | 2003-12-01 | Boyd | Applicant |
| US2004/0087339(A1) | 2004-05-01 | Goldthwaite et al. | Applicant |
| US2004/0104268(A1) | 2004-06-01 | Bailey | Applicant |
| US2004/0112959(A1) | 2004-06-01 | Jun | Applicant |
| US2004/0127256(A1) | 2004-07-01 | Goldthwaite | Examiner |
| US2004/0185842(A1) | 2004-09-01 | Spaur et al. | Applicant |
| US2005/0216412(A1) | 2005-09-01 | Kalinichenko et al. | Applicant |
| US2006/0006226(A1) | 2006-01-01 | Fitzgerald | Examiner |
| US2008/0114707(A1) | 2008-05-01 | Steiner | Applicant |
| US2008/0195428(A1) | 2008-08-01 | O'Sullivan | Applicant |
| US2008/0208693(A1) | 2008-08-01 | Milstein | Examiner |
| US2009/0049119(A1) | 2009-02-01 | Marcinkiewicz et al. | Applicant |
| US2009/0070186(A1) | 2009-03-01 | Buiten et al. | Applicant |
| US2009/0187492(A1) | 2009-07-01 | Hammad | Examiner |
| US2010/0036717(A1) | 2010-02-01 | Trest | Applicant |
| US2010/0191466(A1) | 2010-07-01 | DeLuca et al. | Applicant |
| US2010/0243724(A1) | 2010-09-01 | Golla | Applicant |
| US2010/0299212(A1) | 2010-11-01 | Graylin | Examiner |
| US2010/0315678(A1) | 2010-12-01 | Smires et al. | Applicant |
| US2010/0320266(A1) | 2010-12-01 | White | Examiner |
| US2011/0053552(A1) | 2011-03-01 | Kim et al. | Applicant |
| US2011/0087531(A1) | 2011-04-01 | Winters et al. | Applicant |
| US2011/0099040(A1) | 2011-04-01 | Felt et al. | Applicant |
| US2011/0137804(A1) | 2011-06-01 | Peterson | Examiner |
| US2011/0218871(A1) | 2011-09-01 | Singh | Examiner |
| US2011/0238473(A1) | 2011-09-01 | Sankolli | Examiner |
| US2011/0301985(A1) | 2011-12-01 | Camp et al. | Applicant |
| US2011/0313804(A1) | 2011-12-01 | Camp et al. | Applicant |
| US2012/0036042(A1) | 2012-02-01 | Graylin | Examiner |
| US2012/0059758(A1) | 2012-03-01 | Carlson | Examiner |
| US2012/0109796(A1) | 2012-05-01 | Mashal et al. | Applicant |
| US2012/0130627(A1) | 2012-05-01 | Islam et al. | Applicant |
| US2012/0130903(A1) | 2012-05-01 | Dorsey | Examiner |
| US2012/0150687(A1) | 2012-06-01 | Hart | Examiner |
| US2012/0158581(A1) | 2012-06-01 | Cooley | Examiner |
| US2012/0203697(A1) | 2012-08-01 | Morgan et al. | Applicant |
| US2012/0203700(A1) | 2012-08-01 | Ornce | Examiner |
| US2012/0209749(A1) | 2012-08-01 | Hammad | Examiner |
| US2012/0290375(A1) | 2012-11-01 | Truong | Examiner |
| US2013/0041822(A1) | 2013-02-01 | Wagner | Examiner |
| US2013/0185124(A1) | 2013-07-01 | Aaron et al. | Applicant |
| US2013/0185208(A1) | 2013-07-01 | Aaron et al. | Applicant |
| US2014/0250019(A1) | 2014-09-01 | Causey et al. | Applicant |
| US2017/0193543(A1) | 2017-07-01 | Priebatsch | Examiner |
| EP1804210(A1) | 2007-07-01 | Applicant | |
| KR10-2003-0084178(A) | 2003-11-01 | Applicant | |
| KR10-2007-0080364(A) | 2007-08-01 | Applicant | |
| WO2004/107285(A1) | 2004-12-01 | Applicant | |
| WO2009/082748(A1) | 2009-07-01 | Applicant | |
| WO2013/109372(A1) | 2013-07-01 | Applicant |
Non-Patent Literature (24)
- “TaxiTech(TM) Approved to Provide Interactive Touch Screens for New York City Taxi Passengers” PR Newswire Association LLC., (Jun. 12, 2007), pp. 1-3.Applicant
- “Do you need to put in your PIN number for every debit card purchase I make?”, published by www.yahoo.com, (Sep. 26, 2011), pp. 1-2.Applicant
- Yuping et al., “Taxi O/D Charging System Based on Mobile Electronic Commerce”, 4th International Conference on Wireless Communications, Networking and Mobile Computing, (Oct. 12-14, 2008), pp. 1-4.Applicant
- Non-Final Office Action mailed Dec. 20, 2012, for U.S. Appl. No. 13/353,133, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Final Office Action mailed Jul. 3, 2013, for U.S. Appl. No. 13/353,133, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Non-Final Office Action mailed Jun. 16, 2014, for U.S. Appl. No. 13/353,250, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Non-Final Office Action mailed Dec. 9, 2014, for U.S. Appl. No. 13/353,133, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Non-Final Office Action mailed Dec. 29, 2014, for U.S. Appl. No. 13/353,238, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Final Office Action mailed Feb. 9, 2015, for U.S. Appl. No. 13/353,250, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Final Office Action mailed Jul. 29, 2015, for U.S. Appl. No. 13/353,133, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Non-Final Office Action mailed Oct. 8, 2015, for U.S. Appl. No. 14/804,627, of Aaron, P., et al., filed Jul. 21, 2015.Applicant
- Final Office Action mailed Jun. 6, 2016, for U.S. Appl. No. 14/804,627, of Aaron, P., et al., filed Jul. 21, 2015.Applicant
- Non-Final Office Action mailed Jun. 13, 2016, for U.S. Appl. No. 13/353,133, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Advisory Action mailed Aug. 17, 2016, for U.S. Appl. No. 14/804,627, of Aaron, P., et al., filed Jul. 21, 2015.Applicant
- Non-Final Office Action mailed Dec. 1, 2016, for U.S. Appl. No. 13/353,250, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Final Office Action mailed Dec. 13, 2016, for U.S. Appl. No. 13/353,133, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Non-Final Office Action mailed Jan. 13, 2017, for U.S. Appl. No. 14/804,627, of Aaron, P., et al., filed Jul. 21, 2015.Applicant
- Notice of Allowance mailed Jun. 6, 2017, for U.S. Appl. No. 13/353,250, of Aaron, P., et al., filed Jan. 18, 2012.Applicant
- Notice of Allowance mailed Jul. 19, 2017, for U.S. Appl. No. 14/804,627, of Aaron, P., et al., filed Jul. 21, 2015.Applicant
- Non-Final Office Action mailed Jun. 23, 2020, for U.S. Appl. No. 15/728,115, of Aaron, P., et al., filed Oct. 9, 2017.Applicant
- Final Office Action mailed Dec. 23, 2020, for U.S. Appl. No. 15/728,115, of Aaron, P., et al., filed Oct. 9, 2017.Applicant
- Advisory Action mailed Apr. 6, 2021, for U.S. Appl. No. 15/728,115, of Aaron, P., et al., filed Oct. 9, 2017.Applicant
- Notice of Allowance mailed Oct. 12, 2021, for U.S. Appl. No. 15/728,115, of Aaron, P., et al., filed Oct. 9, 2017.Applicant
- International Search Report and Written Opinion for International Application No. PCT/US2012/069908, mailed Apr. 25, 2013.Applicant