US 9,576,289 B2Grant
Authorization of cardless payment transactions
Issue Date:2017-02-21
•29 Claims
•8 Drawing Sheets
Abstract
A method of processing a transaction between a customer and a merchant includes receiving from a mobile device of the customer or from another device of the customer an indication of consent to perform a cardless payment transaction with the merchant, receiving from the mobile device an indication that the customer is within a predetermined distance of the merchant, after receiving both the indication of consent and the indication that the customer is within the predetermined distance, sending to a computer system of the merchant an indication of the presence of the customer and personal identifying information for the customer, receiving data indicating a transaction between the customer and the merchant, and submitting the transaction to a financial service for authorization.
Metadata
Assignee
- Square, Inc.
Inventors
- William Henderson
- Jack Dorsey
- Brian Grassadonia
- Mathew Wilson
Application Information
Application Number:US 14/017,940
Filing Date:2013-09-04
Priority Date:2011-11-22
Art Unit:3691
Classifications
IPC:
G06Q40/00G06Q20/40G06Q20/32
Field of Search:
G06Q 10/00G06Q 20/00G06Q 30/00G06Q 40/00
Patent Drawings (8 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is a continuation of U.S. patent application Ser. No. 13/683,841, filed Nov. 21, 2012, which claims the benefit under 35 U.S.C. §119(e) of U.S. patent application Ser. No. 61/563,022, filed Nov. 22, 2011, each of which is incorporated herein by reference in its entirety.
Technical Field
[0002] This disclosure relates to cardless payment transactions.
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] Many transactions require that the customer sign a physical receipt, electronically approve a transaction, e.g., by pressing an approve button on a user interface, electronically sign for the transaction, e.g., with a stylus or finger on an electronic signature capture device with a touch sensitive pad, or enter an authorizing personal identification number (PIN).
[0005] Another conventional purchasing technique is online shopping, e.g., using a web browser to view a merchant's web page. However, online shopping is generally not applicable if the customer is present in person at the merchant's store.
Summary
[0006] On the one hand, it would be generally convenient for a customer to dispense with swiping of a credit card. On the other hand, the risk of unauthorized transactions is a potential problem in cardless payment transaction. An approach for conducting an electronic payment transaction without swiping a card is for the customer to provide authorization that particular merchants can perform a cardless payment transaction, and for such transactions to only be authorized when the customer is within a predetermined distance of the merchant, e.g., as sensed by the customer's mobile device.
[0007] In one aspect, a method of processing a transaction between a customer and a merchant includes receiving from a mobile device of the customer or from another device of the customer an indication of consent to perform a cardless payment transaction with the merchant, receiving from the mobile device an indication that the customer is within a predetermined distance of the merchant, after receiving both the indication of consent and the indication that the customer is within the predetermined distance, sending to a computer system of the merchant an indication of the presence of the customer and personal identifying information for the customer, receiving data indicating a transaction between the customer and the merchant, and submitting the transaction to a financial service for authorization.
[0008] Implementations may include one or more of the following features. An indication may can be received from the financial service that the transaction is authorized. A record of the transaction may be sent to the computer system of the merchant. An indication of consent may be received from the merchant to perform cardless payment transactions with customers, and location information for the merchant may be received. An indication of a request to identify a merchant that will perform cardless payment transactions may be received from the mobile device of the customer. Location information for the customer from the mobile device of the customer may be received, the merchant may be selected from a plurality of merchants based on the location information for the customer and the location information for the merchant, and an identification of the merchant and the location information for the merchant may be sent to the mobile device of the customer. The indication of consent to perform the cardless payment transaction with the merchant is may be received before or after the indication that the customer is within the predetermined distance of the merchant is received. The indication of consent to perform the cardless payment transaction with the merchant may be received in the indication that the customer is within the predetermined distance of the merchant. The personal identifying information may be a name and/or a photograph of the customer.
[0009] Whether a value of the transaction exceeds a predetermined amount may be determined, and a request for approval of the transaction may be sent to the mobile device of the customer before submitting the transaction to the financial service. A PIN may be received from the mobile device in response to the request for approval, and the PIN may be compared to a previously received PIN. Whether a value of the transaction exceeds a predetermined amount may be determined, and a request for approval of the transaction by the customer may be sent to the computer system of the merchant before submitting the transaction to the financial service. A PIN may be received from the computer system of the merchant, and the PIN may be compared to a previously received PIN. A value of the transaction may be determined to not exceed a predetermined amount, and the transaction may be submitted to the financial service without sending to the mobile device of the customer a request for approval of the transaction. An identification of the financial institution and the personal information may be received from a mobile device of the customer or from another device of the customer. Data indicating a transaction between the customer may be received from the computer system of the merchant. A record of the transaction may be sent to the user device. The transaction may be submitted to a financial service for capture before sending the record of the transaction.
[0010] In another aspect, a method of performing a transaction with a merchant includes receiving in a mobile device a location of a merchant, determining in the mobile device whether the mobile device is within a predetermined distance of the location of the merchant, sending from the mobile device to a computer system of a third party an indication that the customer is within a predetermined distance of the merchant, sending from the mobile device to the computer system of the third party an indication of consent to perform a cardless payment transaction with the merchant, and receiving in the mobile device from the computer system of the third party a record of a transaction with the merchant.
[0011] Implementations may include one or more of the following features. The record of the transaction may be received without having transmitted an approval for the amount of the transaction. A request for approval of the transaction may be received in the mobile device, and the request may include the amount of the transaction. A PIN may be sent from the mobile device to the computer system of the third party in response to the request for approval. Location information for a plurality of merchants may be received, input from the customer may be received selecting the merchant from the plurality of merchants, and an identification of the merchant may be sent to the computer system of the third party.
[0012] In another aspect, a method of performing a transaction with a customer includes receiving an indication from a computer system of a third party that a customer is present within a predetermined distance and personal identifying information for the customer, displaying an option to perform a cardless payment transaction with the customer and displaying the personal identifying information, receiving user input selecting the option, receiving user input identifying a transaction with the customer including at least an amount of the transaction, sending data indicating the transaction to the computer system of the third party, and receiving from the computer system of the third party a record of a transaction.
[0013] Implementations may include one or more of the following features. An amount of the transaction may be determined to exceed a threshold or receiving a request for approval of the transaction, and requesting input from the customer approving the transaction. Requesting input may include requesting a PIN, and the PIN may be sent to the computer system of the third party. Whether the amount of the transaction exceeds the threshold may be determined.
[0014] In another aspect, a computer program product, tangibly embodied in a machine readable storage media, includes instructions for causing a processor to perform any of the methods described above.
[0015] In another aspect, a system for processing a transaction between a customer and a merchant includes a customer mobile device, a merchant computer system, and a server system. The customer mobile device, merchant computer system and server system are configured to perform an operation in which the mobile device receives customer input indicating consent to perform a cardless payment transaction with the customer and sends to the server system an indication of the consent, the mobile device receives a location of a merchant, determines whether the mobile device is within a predetermined distance of the location of the merchant, and if the mobile device is within the predetermined distance send to the server system an indication that the customer is within the predetermined distance, after receiving both the indication of consent and the indication that the customer is within the predetermined distance, the server system sends to the merchant computer system an indication of the presence of the customer and personal identifying information for the customer, the merchant computer system displays an option to perform a cardless payment transaction with the customer and displays the personal identifying information, receives merchant input identifying a transaction with the customer including at least an amount of the transaction, and sends data indicating the transaction to the server system, the server system submits the transaction to a financial service for authorization, receives an indication from the financial service that the transaction is authorized, and sends a record of the transaction to the mobile device and to the merchant computer system.
[0016] Advantages may include one or more of the following. A customer can conduct a point-of-sale electronic payment transaction with a merchant without swiping a card. In addition, the customer can verbally notify the merchant to perform a transaction, and the customer can conduct the transaction without having to access his or her own wallet or mobile phone. In addition, in some implementations the customer need not interact with a point-of-sale device, e.g., need not press an approve button on a user interface of the point-of-sale device or electronically sign. Consent to a cardless payment transaction can be given by the customer before the customer physically arrives at the merchant or at the merchant's point-of-sale device.
Brief Description of the Drawings
[0017] FIG. 1 is a schematic illustration of an example cardless payment system architecture.
[0018] FIG. 2 is a diagram of an example implementation of the cardless payment system.
[0019] FIG. 3 is a diagram of an example flow chart of the cardless payment system.
[0020] FIG. 4 is a diagram of an example view of the application's main page on the user's mobile device.
[0021] FIG. 5 is a diagram of an example application view of a user that has opened a tab at a merchant inside the predetermined distance from the merchant.
[0022] FIG. 6 is a diagram of an example application view with a user that has attempted to open a tab at a merchant outside the predetermined distance from the merchant.
[0023] FIG. 7 is a diagram of an example view of a merchant device's application.
[0024] Like reference numbers and designations in the various drawings indicate like elements.
Detailed Description
[0025] As an overview, the system allows a user (also called a customer or payer) to purchase items from a merchant while physically present at the merchant, e.g., at the point of sale, but using a cardless payment transaction. A cardless payment transaction is one where a user conducts the transaction with a merchant at a point of sale using a financial account without physically presenting a payment card to the merchant at the point of sale. In fact, the merchant need not receive any details about the financial account, e.g., the credit card issuer, credit card number, and the like is not provided to the merchant.
[0026] From the user's perspective, the user first signs up for an account with the cardless payment system. The sign-up process requires certain information, such as information about a financial account sufficient to perform a transaction with the account. For example, if the financial account is a credit card account, then credit card information can be provided, e.g., credit card number and expiration date. The user can also sign up with other payment methods such as debit cards, pre-paid cards, bank accounts, or other third party financial accounts. The sign up process can also require contact information for the user, e.g., mailing address and email, and other personal identifying information, e.g., a photograph of the user. After creating an account, the user can select a merchant that also has an account with the cardless payment system. The user can give consent to perform a cardless payment transaction with the merchant if the user is within a predetermined distance from the merchant. After the user gives consent, the merchant can, without a presentment of the physical payment card, charge (in the case of credit cards) or debit (in the case of debit cards) the user's financial account for items the user wants to buy. Because the user's payment card is already on file with the cardless payment system, the user does not need to physically present a credit card to the merchant.
[0027] FIG. 1 is a schematic illustration of the architecture of an example cardless payment system 100. The overall system 100 includes a user device 102 and merchant device 104 connected to a network, e.g., the Internet 106. The user device 102 is a mobile computing device, i.e., a hand-held computing device, capable of running a user application. For example, the user device 102 can be a smartphone or tablet computer. The merchant device 104 is also a computing device, capable of running a merchant application. The merchant device 104 can be a mobile device, or it can be a desktop computer, a laptop computer, a dedicated point of sale system, or other data processing apparatus.
[0028] A cardless payment processor operates a payment service system 108. The user and merchant devices can communicate with the payment service system 108 using the network 106. The payment service system 108 includes an application server 110 and a secure server 112 to processes all transactions between the user device 102 and merchant device 104. In general, the application server 110 handles non-secure information. For example, it can store public merchant information such as the merchant's address or phone number. The application server 110 can also be responsible for transferring or updating the user application to the user's mobile device or transferring or updating the merchant application to the merchant's computing device. In particular, the application server 112 can be responsible for sending information about merchants that have accounts with the cardless payment system to the user device 102. The secure server 112 handles secure information such as credit card numbers, debit card numbers, bank accounts, user accounts, user identifying information or other sensitive information.
[0029] The payment service system 108 can communicate electronically with a card payment network 116, e.g., Visa, Mastercard, or the like. The payment service system 108 can communicate with a computer system 116 of a card payment network, e.g., Visa or MasterCard. The payment service system 108 can communicate with a computer system 116 over the same network 106 used to communicate with the user device 102, or over a different network. The computer system 116 of the card payment network can communicate in turn with a computer system 118 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 108 and the card issuer.
[0030] Before a transaction between the user and the merchant can be performed using the cardless payment system, the user must create a user account with the payment service system 108 and the merchant must create a merchant account with the payment service system 108.
[0031] The user can sign up using a mobile application or using an online website, and can use the mobile device 102 or another computing device, e.g., a home computer. At some point prior to the transaction, a user application is downloaded to the user device 102, e.g., through an application store. Creation of the user account can be handled through the user application, or through another application, e.g., a generic web browser. The user enters a name, account password, and contact information, e.g., email address. Before a transaction can be performed, the user also enters financial account information sufficient to conduct the transaction into the payment service system 108. For example, in the case of a credit card account, the user can enter the credit card issuer, credit card number and expiration date into the payment service system 108; the card validation value and mailing address may also be required. However, the financial account could also be associated with a debit card or pre-paid card, or another third party financial account.
[0032] In some implementations, the payment service system 108 requires additional personal identifying information before a transaction can be performed. For example, the payment service system 108 may require a photo of the user before a transaction can be performed. The photo of the user would be provided to the merchant so that the merchant can compare the photo to the person. In addition, the payment service system 108 can require a personal identification number (PIN) be entered by the user. Other requirements can also be added to increase security. The data associated with a user account 114 can be stored at the secure server 112, e.g., in a database.
[0033] If the user is signing up with a mobile application, the user's financial account information can be entered by swiping the financial transaction card through a slot of a card reader coupled to the mobile device. Alternatively, the user can enter in financial account information by typing in information at the mobile device 102, selecting a card from an application on the mobile device, from an online entity, or others. In some implementations, another external application generates a receipt that is sent to the user. The receipt then includes a hypertext link that allows a user to easily create a user account in the cardless payment system. For example, activating the link in the receipt can automatically create a user account with a payment card prefilled with the card used in the receipt to reduce effort by the user. In effect, activating a new account using a receipt auto-verifies the user into the cardless payment system.
[0034] The merchant can sign up for an account using the merchant device 104 or another device. The merchant enters a name, account password, and contact information, e.g., email address, and physical location information, e.g., an address, into the payment service system 108. 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 108. The data associated with the merchant account 114 can be stored at the secure server 112, e.g., in a database.
[0035] At some point prior to the transaction, a merchant application is downloaded to the merchant device 102, e.g., through an application store. Creation of the merchant account can be handled through the merchant application, or through another application, e.g., a generic web browser.
[0036] Eventually, in order to receive funds from the transaction, the merchant will need to enter financial account information into the payment service system 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 cardless payment processor can hold the received funds until the financial account information is provided.
[0037] FIG. 2 is a diagram that outlines an example implementation of the cardless payment system 100. A user carries a mobile device 102 with the user application installed, and a merchant has a device 104 with the merchant application installed. Users and merchants each have an association, e.g., an account, with the payment service system 108.
[0038] The system can predetermine a geo-location distance 206, e.g., a radius, around the location of the merchant. In some implementations, the geo-location distance 206 is 500 feet. In some implementations, the geo-location distance 206 can be set by the merchant, e.g., the payment service system 108 receives input from the merchant device 104 or another computer system of the merchant setting the location radius. In some implementations, the payment service system 108 may limit the radius set by the merchant to a maximum location radius.
[0039] If the user device is located outside the geo-location radius 206 of the merchant, the merchant application does not provide an option to conduct a cardless payment transaction with the user. In this case, the user device 102 will indicate it is outside the geo-location radius 206 of the merchant, and the merchant device 104 will be unable to charge the user's financial account, as further described in FIG. 3 and FIG. 6 .
[0040] However, a user can create or configure a tab with the merchant at any geographical location using an application on the user device 102, or on another device, e.g., another mobile device or on a home computer, that is granted access to the user's account. A tab is a relationship between the user, the payment service system 108, and the merchant. Once a tab is created, the user device 102 saves the merchant's information, e.g., the name and location of the merchant, and the user device 102 can display information about the merchant a main view of the application as further described in FIG. 4 when the application is active. If the tab is created by the user using a device other than the user device 102, then the payment service system 108 will provide the merchant information to the user device 102.
[0041] If the user device 102 is located within the geo-location radius 206 of the merchant , the user can “open a tab” with the merchant using an application on the user device 102 as further described in FIG. 3 and FIG. 5 . The user can configure the tab to “auto-open” the tab once the user is within the geo-location radius 206 of the merchant, which will be further described below. In some implementations, the user can configure a tab to set a maximum amount that can be charged per transaction with the merchant.
[0042] Opening a tab with a merchant allows the merchant application to display an option to charge the user's financial account using a cardless payment transaction. In essence, opening the tab constitutes a consent by the user to conducting a cardless transaction with the merchant. This consent differs from actual authorization of the transaction, which the user would provide, e.g., verbally, upon learning the amount of the transaction.
[0043] In some implementations, in order to determine whether user device 102 is within the geo-location radius 206 of the merchant device 104, the merchant's location, e.g., address, and the geo-location radius 206 for the merchant are provided to the user device 102. The user device 102 can then use a geofencing function. For example, the user device 102 determines its own location, e.g., based on GPS information, cellphone data, wireless network data, or the like, and then determines whether its own location is within the geo-location radius 206 of the merchant location.
[0044] FIG. 3 is a diagram of an example flow chart of process conducted with the cardless payment system 100. The process conducted with the cardless payment system 100 involves relationships between a user's mobile device, a server system, and a merchant's device. The server system can reside in the payment service system 108 and be configured to send and receive communications between the user device and the merchant device. The server system can include the application server 110 and/or the secure server 112. The communications can be encrypted using secure protocols built into the user device, server system, and merchant device. In some implementations, this process is implemented through the applications installed on both the user's mobile device and the merchant's device.
[0045] In a typical situation, the user enters a request into the mobile device 102 to identify a merchant that will perform cardless payment transactions. The mobile device 102 directs the request to the server system. The request can be accompanied by location information, e.g., as determined by the mobile device 102. The server system receives the request, and selects one or more merchants based on the location information from the customer and the stored location information for the merchant. At least an identification of the merchant and the location information for the merchant is sent to the mobile device 102.
[0046] The user may input a request for further information about a merchant, e.g., press a “details” button on the user interface of the user application. In response, the user device can display further information received from the merchant, e.g., the list of goods or services available, operating hours, and phone number.
[0047] The user sends an indication of consent to perform a cardless payment transaction with the merchant to the server system. For example, the user can request to “open a tab” at a merchant by interfacing with the user application on the user device (step 302); this request can constitute the indication of consent.
[0048] Alternatively, the request to identify a merchant, the display of information concerning the merchant, and/or the indication of consent, could be entered into a computer other than the user device 102, e.g., the user's home computer, that is logged in to the user's account on the payment service system 108. In any event, should the user indicate consent to perform the transaction, at least an identification of the merchant and the location information for the merchant is sent to the mobile device 102.
[0049] The mobile device determines whether it is within the predetermined distance from the merchant (step 304). In some implementations, if the mobile device does not have the current location of the merchant, or if the merchant updated its location information, the merchant location can be pushed or pulled into the mobile device. Alternatively, if the user opts in to sharing of location information, the location information of the mobile device can be provided to the server of the payment service system 108, and the server determines the distance between the merchant and the mobile device.
[0050] As described above, if the mobile device determines the user's mobile device is not within a predetermined distance (e.g. 500 feet), the mobile device displays a message indicating its inability to open a tab and rejecting the user's request (step 308). In this case, the mobile device can create or configure a tab, but cannot open a tab. In other words, the merchant cannot charge the user's financial account using a cardless payment transaction until the user is within the predetermined distance and the merchant has the user's consent. This is further described in FIG. 6 .
[0051] On the other hand, if the mobile device is within the predetermined distance, the mobile device sends an indication of proximity to the server of the payment service system (step 306). In some implementations, the user can “auto-open” a tab. For example, the user first requests that a tab be “auto-opened.” While a tab is configured to be “auto-opened”, the mobile device can automatically detect when it is within the predetermined distance and send the indication of proximity, which will be described further in FIG. 5 . The indication of proximity can be determined using wireless network geo-fencing or GPS signals. In some implementations, if the mobile device is not within the predetermined distance, the user application will not permit the indication of consent to be input. In some implementations, if the mobile device is not within the predetermined distance when an indication of consent is input, the user application will require that the user again input an indication of consent when the mobile device is within the predetermined distance.
[0052] After the server receives this indication of proximity, the server system sends the indication of the mobile device's presence and personal identifying information to the merchant device (step 310). In some implementations, personal identifying information includes the user's name and picture. Upon receipt of this information, the merchant device displays a tab (step 312) and the user's identifying information (step 314) on the graphical user interface (GUI) of the merchant application. In some implementations, through the GUI of the merchant application, the merchant can select items that the user has sought to purchase. The application can be configured to associate individual prices with each of the merchant's items, and the application can automatically sum the total transaction amount that the user owes. In some implementations, the merchant can enter into the application a total sum of prices for all the items the user wishes to purchase, as well as tax or tip. A user can authorize payment for a tab by verbally notifying the merchant. For example, a user named John Smith can tell the merchant, “Put this on John Smith.” Before or after the user authorizes payment for the tab, the merchant verifies the user's identity (step 316). In some implementations, the merchant ensures the image displayed on the merchant device matches the user who is present in person. Assuming that the image matches, the merchant selects the user's tab using the GUI of the merchant application. In some implementations, the merchant can ask the user for more identifying information before processing the transaction such as the user's birthday, address, or other personal identifying information. After verifying the user's identity, the merchant interfaces with the merchant application to start processing the transaction.
[0053] In some implementations, the amount to be charged exceeds a predetermined amount set by the user, the merchant or the cardless payment processor. In this case, the user enters in a PIN associated with the user's account into the merchant device. The merchant device verifies the PIN with the server. Alternatively, the server system may communicate with the user device and cause the user device to requested that the user enter the PIN into the user device. In yet another alternative, the server system can ask the user to confirm the payment on the user device, removing the need to enter a PIN.
[0054] The merchant's device sends a record of the requested transaction to the server (step 318). The server system continues processing the requested transaction (step 320) by sending the record to the computer system of the card payment network 116, e.g., Visa or MasterCard, and the card payment network 116 then sends the record to the card issuer, e.g., the bank, as described above.
[0055] If the transaction fails because it would exceed the credit limit or there are insufficient funds in the financial account, the server notifies the merchant application. In some implementations, the server can notify both the merchant application and user application.
[0056] If the transaction succeeds and the server system receives approval from the card payment network 116, the server system communicates this to the merchant device. The merchant device then captures the transaction. In the capture stage, the approved transaction is again routed from the merchant to the credit card processor, card network and card issuer. The record of the transaction in the capture stage can 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 server system optionally creates receipts to send to the user, e.g., through the user application and/or through the previously provided contact email, and to the merchant (step 322). Both devices then display the receipt in each of their applications (steps 324, 326). Optionally, the user may be permitted to opt out of notification.
[0057] FIG. 4 is a diagram of an example view of the application's main page on the user's mobile device 402. In some implementations, each entity (e.g. user or merchant) is represented as a card and relationships between the user and user-selected merchants are represented as cards stored in a card case 422. The card case 422 can display the user's initials 424. The edges of the card case 422 can be a dashed line to mimic stitching of a wallet. Each card can contain a picture representing a logo or a profile picture 412, 414, 416, 418. For example, a user named John Smith can access his user account information by tapping the John Smith card 404. Each merchant can be represented with a custom-designed card. In some implementations, tapping the card of Merchant 1 406, Merchant 2 108, or Merchant 3 410 will cause the mobile device 402 to display an option to either “Open a tab” or “Show details” regarding the merchant. In some implementations, directing the user device to open a tab will follow the process of FIG. 3 . In some implementations, showing more details will display a custom merchant page indicating information regarding the merchant. For example, the mobile device can display a map around the merchant's area, the merchant's phone number, the merchant's operating hours, or other merchant information. The application also allows the user to “Explore Places” 420. In some implementations, this opens a list of nearby or featured merchants that are associated with the cardless payment system. A user then has an option to add one of the merchants in the list to the “card case” view of the user's application.
[0058] FIG. 5 is a diagram of an example application view 504 of a user that has opened a tab at a merchant inside the predetermined distance from the merchant. This view can show the name of the merchant or the merchant's logo 506. In some implementations, because the user's credit card is already in the cardless payment system, the user does not need to physically give a credit card to the merchant. For example, once a user named John Smith wants to checkout with a few items, John Smith can pay by verbally telling a cashier “Put it on John Smith” 508. The cashier can verify John's identity as described above. A user can also press a “Cancel Payment” button 510 to close the tab for the merchant. Closing the tab will prevent the merchant and the merchant's device from charging the user using a cardless payment transaction. In some implementations, merchants can also close the tab on the merchant device; information that the tab is closed is transmitted to the server system and then to the mobile device, causing the tab (if being displayed) to close on the mobile device as well. In some implementations, tabs automatically close after a transaction has been approved. In some implementations, tabs automatically close after a preset amount of time, e.g., if no transaction has occurred. In some implementations, a tab can be auto-opened 512. If this is turned on, the user has given consent to open a tab automatically whenever the user's mobile device is within the predetermined distance from the merchant. The mobile device then can automatically detect in the background when it is within the predetermined distance and automatically sends, also in the background, an indication of proximity to a server in the payment service system as described above. The user can choose to engage in a cardless payment transaction with the merchant without ever bringing the application to the foreground. Therefore, in some implementations, this removes the need to run the application on a main thread of the device's processor. In other words, the user does not need to start the application when inside the predetermined distance and tap “Open a tab”. In practice, with Auto Open Tab turned on, John Smith, holding his mobile device 502, can walk to a merchant from outside the predetermined distance, order an item for sale, and pay using the cardless payment system without interfacing with his mobile device 502 at the point of sale. In some implementations, the cardless payment system can limit the “auto-open” functionality to merchants with a fixed location for security reasons.
[0059] FIG. 6 is a diagram 600 of an example application view 604 with a user that has attempted to open a tab at a merchant outside the predetermined distance from the merchant 610. In some implementations, the view shows a map 614 of the user's current location 612 and the location of the merchant 608 with a predetermined distance surrounding the merchant 610. In some implementations, the device can provide directions from the user's location 612 to the merchant's location 608. The device can also calculate or display how far away the user's current location 612 is from the merchant's location 608. For example, the text can read “0.4 mi away, too far to open tab” 616. In this case, because the user's mobile device 602 is outside the predetermined distance from the merchant, the user and the merchant cannot engage in a cardless payment transaction. Pressing the Done button can close this view 606. In some implementations, this view of the application also allows the user to “Always Auto Open Tab” 618 as described above.
[0060] FIG. 7 is a diagram of an example view 700 of a merchant device's application 702. If a user is associated with the cardless payment system and is within the predetermined distance from the merchant, the device can display the user's identifying information in the application. In some implementations, the identifying information includes the user's name 710, picture 708, phone number, email address, or other personal identifying information. In some implementations, after verifying the user's identity using the identifying information, the merchant enters in a tab 706 into the application using the keypad 704, shows the user the amount to be charged, and taps the “Ok” button 712 to cause the device to process the transaction.
[0061] 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).
[0062] 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.
[0063] 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.
[0064] 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.
[0065] 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).
[0066] 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.
[0067] 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.
[0068] 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. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
[0069] 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.
[0070] 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.
[0071] 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.
[0072] 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.
[0073] Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. 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.
Claims
What is claimed is:
1. A method of conducting a transaction between a customer and a merchant, comprising:
determining a current geolocation of a customer mobile device using a global positioning system (GPS) receiver of the customer mobile device;
at least partly in response to determining that the current geolocation of the customer mobile device is outside a geofence of a merchant point-of-sale (POS) device and at least partly in response to selection of an icon representing the merchant displayed on the customer mobile device, displaying an indication on the customer mobile device that the customer and the merchant cannot conduct a cardless payment transaction;
at least partly in response to determining that the current geolocation of the customer mobile device is within the geofence of the merchant POS device,
sending an indication that the customer mobile device is in proximity to the merchant POS device;
receiving, from the customer mobile device, permission for personal identifying information of the customer to be displayed at the merchant POS device;
displaying the identifying information of the customer within a customer display area of a display of the merchant POS device, the personal identifying information including at least a customer name of the customer;
receiving an indication of the customer's consent to enter into a financial transaction with the merchant;
receiving, at the merchant POS device, a selection of the customer's personal identifying information from the customer display area, the selection confirming that the financial transaction is to be associated with the customer; and based at least in part on the received selection of the customer's personal identifying information in the merchant POS device, submitting the financial transaction to a financial service for authorization.
2. The method of claim 1, further comprising displaying the personal identifying information in a tab for the customer on the display of the merchant's POS device, wherein the selection from the merchant of the customer's personal identifying information comprises a selection of the tab.
3. The method of claim 1, wherein the personal identifying information displayed in the customer display area includes an image of the customer.
4. The method of claim 3, wherein the personal identifying information displayed in the customer display area comprises additional identifying information, and wherein the merchant requests the additional identifying information before submitting the financial transaction to the financial service.
5. The method of claim 4, wherein the additional identifying information comprises at least one of a birthday or a phone number of the customer.
6. The method of claim 1, further comprising determining whether an amount for the transaction exceeds a threshold set by the customer.
7. A method of conducting a transaction with a customer, comprising:
receiving at a merchant device of a merchant an indication of a customer's consent to enter into a financial transaction with the merchant, receipt of the indication being based at least in part on a geolocation of the mobile device of the customer being determined to be within a geofence of the merchant device, wherein the mobile device includes a global positioning system (GPS) receiver for determining the geolocation of the mobile device;
in response to receiving the indication, displaying identifying information of the customer on a display of the merchant device, the identifying information including at least a personal identifier;
receiving, at the merchant device, a request to process a financial transaction; receiving input at the merchant device indicating that the customer has approved the financial transaction based at least in part on the customer providing the personal identifier;
displaying a user input option to prevent the merchant device from conducting a cardless payment transaction between the customer and the merchant; and submitting the financial transaction for authorization.
8. The method of claim 7, wherein the providing the personal identifier is provided without inputting the identifier into the merchant device.
9. The method of claim 8, wherein the personal identifier is provided verbally.
10. The method of claim 7, wherein the personal identifier comprises a name of the customer.
11. The method of claim 7, wherein the identifying information includes an image of the customer.
12. The method of claim 11, further comprising receiving input in the merchant device indicating that the image of the customer matches the customer.
13. The method of claim 7, further comprising displaying the identifying information of the customer within a customer display area of the display on the merchant device, the customer display area including identifying information of one or more customers that are located proximate to the merchant.
14. The method of claim 13, wherein receiving the input indicating that the customer has approved the transaction includes receiving a selection, at the merchant device, of the identifying information in the customer display area.
15. The method of claim 14, wherein the selection is received after the customer has provided the personal identifier.
16. The method of claim 14, further comprising displaying the identifying information in a tab for the customer on the display of the merchant device, wherein the selection from the merchant of the customer's personal identifying information comprises receiving input in the merchant device from the merchant selecting the tab for the customer.
17. The method of claim 7, further comprising receiving an indication that an amount for the transaction exceeds a threshold, and wherein additional information is received from the customer before submitting the financial transaction for authorization.
18. The method of claim 17, wherein receiving the additional information comprises receiving input in the merchant device from the customer of a personal identification number (PIN).
19. A computer program product, tangibly embodied in a machine readable computer storage media, comprising instructions for causing a processor to:
determine a current geolocation of a customer mobile device using a global positioning system (GPS) receiver of the customer mobile device;
at least partly in response to determining that the current geolocation of the customer mobile device is outside a geofence of a merchant point-of-sale (POS) device of a merchant, and at least partly in response to selection of an icon representing the merchant displayed on the customer mobile device, display an indication on the customer mobile device that the customer and the merchant cannot conduct a cardless payment transaction;
at least partly in response to determining that the current geolocation of the customer mobile device is within the geofence of the merchant POS device,
send an indication that the customer mobile device is in proximity to the merchant POS device;
receive, at the merchant device, an indication of the customer's consent to enter into a financial transaction with the merchant, wherein the mobile device includes a global positioning system (GPS) receiver for determining the geolocation of the mobile device;
in response to receiving the indication, display identifying information of the customer on a display of the merchant device, the identifying information including at least a personal identifier;
receive, at the merchant device, a request to process a financial transaction; receive input at the merchant device indicating that the customer has approved the financial transaction based at least in part on the customer providing the personal identifier; and
submit the financial transaction for authorization.
20. The computer program product of claim 19, wherein the personal identifier is provided without inputting the identifier into the merchant device.
21. The computer program product of claim 19, wherein the personal identifier comprises a name of the customer.
22. The computer program product of claim 19, wherein the identifying information includes an image of the customer.
23. The computer program product of claim 19, comprising displaying the identifying information of the customer within a customer display area of the display on the merchant device, the customer display area including identifying information of one or more customers that are located proximate to the merchant.
24. The computer program product of claim 23, wherein receiving the input indicating that the customer has approved the transaction includes receiving a selection, at the merchant device, of the identifying information in the customer display area.
25. A method of conducting a transaction with a customer, comprising:
receiving, at a merchant's point of sale (POS) device, an indication of a customer's consent to enter a financial transaction with the merchant, receipt of the indication being based at least in part on a geolocation of the mobile device of the customer being determined to be within a geofence of the merchant's POS device, wherein the mobile device includes a global positioning system (GPS) receiver for determining the geolocation of the mobile device;
in response to receiving the indication, displaying identifying information associated with the customer in a customer display area on a display of the merchant's POS device; receiving an identification and selection of the customer's identifying information from the customer display area; and
in response to the selection of the customer's identifying information from the customer display area,
displaying a user input option on the merchant device to prevent the merchant device from conducting a cardless payment transaction between the customer and the merchant; and
processing the financial transaction upon receiving user input at the merchant device to process the financial transaction.
26. The method of claim 25, further comprising receiving the identifying information from the customer.
27. The method of claim 26, wherein the identifying information comprises the name of the customer.
28. The method of claim 25, further comprising obtaining an indication of the identifying information by viewing the customer.
29. The method of claim 28, wherein the identifying information comprises an image of the customer.
Patent Citations (136)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US6026375(A) | 2000-02-01 | Hall et al. | Applicant |
| US6587835(B1) | 2003-07-01 | Treyz et al. | Applicant |
| US7004382(B2) | 2006-02-01 | Sandru | Applicant |
| US7792709(B1) | 2010-09-01 | Trandal et al. | Applicant |
| US7831246(B1) | 2010-11-01 | Smith et al. | Applicant |
| US7848765(B2) | 2010-12-01 | Phillips et al. | Applicant |
| US8090351(B2) | 2012-01-01 | Klein | Applicant |
| US8135624(B1) | 2012-03-01 | Ramalingam et al. | Applicant |
| US8140418(B1) | 2012-03-01 | Casey et al. | Applicant |
| US8160959(B2) | 2012-04-01 | Rackley, III | Examiner |
| US8239276(B2) | 2012-08-01 | Lin et al. | Applicant |
| US8285604(B1) | 2012-10-01 | Trandal et al. | Applicant |
| US8369842(B2) | 2013-02-01 | Proctor, Jr. et al. | Applicant |
| US8396808(B2) | 2013-03-01 | Greenspan | Applicant |
| US8417258(B2) | 2013-04-01 | Barnes, Jr. | Applicant |
| US8463295(B1) | 2013-06-01 | Caralis et al. | Applicant |
| US8510220(B2) | 2013-08-01 | Rackley, III | Examiner |
| US8554670(B1) | 2013-10-01 | Blank et al. | Applicant |
| US8635157(B2) | 2014-01-01 | Smith et al. | Applicant |
| US8655782(B2) | 2014-02-01 | Poon et al. | Applicant |
| US8659427(B2) | 2014-02-01 | Brown et al. | Examiner |
| US2002/0111907(A1) | 2002-08-01 | Ling | Applicant |
| US2002/0194121(A1) | 2002-12-01 | Takayama | Applicant |
| US2004/0093281(A1) | 2004-05-01 | Silverstein et al. | Applicant |
| US2006/0093998(A1) | 2006-05-01 | Vertegaal | Applicant |
| US2006/0138219(A1) | 2006-06-01 | Brzezniak et al. | Applicant |
| US2007/0022375(A1) | 2007-01-01 | Walker | Applicant |
| US2007/0203801(A1) | 2007-08-01 | Istfan | Applicant |
| US2008/0080682(A1) | 2008-04-01 | Ogunwale et al. | Applicant |
| US2008/0142599(A1) | 2008-06-01 | Benillouche et al. | Applicant |
| US2008/0172733(A1) | 2008-07-01 | Coriaty et al. | Applicant |
| US2008/0207296(A1) | 2008-08-01 | Lutnick et al. | Applicant |
| US2008/0319843(A1) | 2008-12-01 | Moser et al. | Applicant |
| US2009/0030787(A1) | 2009-01-01 | Pon et al. | Applicant |
| US2009/0076896(A1) | 2009-03-01 | DeWitt et al. | Applicant |
| US2009/0076925(A1) | 2009-03-01 | DeWitt et al. | Applicant |
| US2009/0125429(A1) | 2009-05-01 | Takayama | Applicant |
| US2009/0177581(A1) | 2009-07-01 | Garcia et al. | Applicant |
| US2009/0187492(A1) | 2009-07-01 | Hammad et al. | Applicant |
| US2009/0204492(A1) | 2009-08-01 | Scifo et al. | Applicant |
| US2009/0264070(A1) | 2009-10-01 | Lim | Applicant |
| US2009/0298514(A1) | 2009-12-01 | Ullah | Applicant |
| US2009/0313138(A1) | 2009-12-01 | Ratnakar | Applicant |
| US2009/0313165(A1) | 2009-12-01 | Walter | Applicant |
| US2010/0010906(A1) | 2010-01-01 | Grecia | Applicant |
| US2010/0063889(A1) | 2010-03-01 | Proctor, Jr. et al. | Applicant |
| US2010/0070369(A1) | 2010-03-01 | Fenton et al. | Applicant |
| US2010/0070378(A1) | 2010-03-01 | Trotman et al. | Applicant |
| US2010/0076853(A1) | 2010-03-01 | Schwarz | Applicant |
| US2010/0082445(A1) | 2010-04-01 | Hodge et al. | Applicant |
| US2010/0082455(A1) | 2010-04-01 | Rosenblatt et al. | Applicant |
| US2010/0082487(A1) | 2010-04-01 | Nelsen | Applicant |
| US2010/0121726(A1) | 2010-05-01 | Coulter et al. | Applicant |
| US2010/0125495(A1) | 2010-05-01 | Smith et al. | Applicant |
| US2010/0125510(A1) | 2010-05-01 | Smith et al. | Applicant |
| US2010/0174596(A1) | 2010-07-01 | Gilman | Examiner |
| US2010/0216396(A1) | 2010-08-01 | Fernandez et al. | Applicant |
| US2010/0250410(A1) | 2010-09-01 | Song et al. | Examiner |
| US2010/0306080(A1) | 2010-12-01 | Trandal et al. | Applicant |
| US2010/0312385(A1) | 2010-12-01 | Deuber | Applicant |
| US2011/0016051(A1) | 2011-01-01 | Trifiletti et al. | Applicant |
| US2011/0059784(A1) | 2011-03-01 | Lutnick et al. | Applicant |
| US2011/0153440(A1) | 2011-06-01 | Singhal | Applicant |
| US2011/0231292(A1) | 2011-09-01 | McCown | Applicant |
| US2011/0238476(A1) | 2011-09-01 | Carr et al. | Applicant |
| US2011/0251892(A1) | 2011-10-01 | Laracey | Applicant |
| US2011/0258058(A1) | 2011-10-01 | Carroll et al. | Applicant |
| US2011/0276418(A1) | 2011-11-01 | Velani | Applicant |
| US2011/0276419(A1) | 2011-11-01 | Johnson et al. | Applicant |
| US2011/0313867(A9) | 2011-12-01 | Silver | Applicant |
| US2012/0016731(A1) | 2012-01-01 | Smith et al. | Applicant |
| US2012/0072350(A1) | 2012-03-01 | Goldthwaite et al. | Applicant |
| US2012/0078751(A1) | 2012-03-01 | MacPhail et al. | Applicant |
| US2012/0089461(A1) | 2012-04-01 | Greenspan | Applicant |
| US2012/0089470(A1) | 2012-04-01 | Barnes, Jr. | Applicant |
| US2012/0109749(A1) | 2012-05-01 | Subramanian et al. | Applicant |
| US2012/0109752(A1) | 2012-05-01 | Strutton et al. | Applicant |
| US2012/0130790(A1) | 2012-05-01 | Lyons et al. | Applicant |
| US2012/0130794(A1) | 2012-05-01 | Strieder | Applicant |
| US2012/0150605(A1) | 2012-06-01 | Isaacson et al. | Applicant |
| US2012/0150611(A1) | 2012-06-01 | Isaacson et al. | Applicant |
| US2012/0179516(A1) | 2012-07-01 | Fakhrai et al. | Applicant |
| US2012/0190386(A1) | 2012-07-01 | Anderson | Applicant |
| US2012/0197724(A1) | 2012-08-01 | Kendall | Applicant |
| US2012/0197743(A1) | 2012-08-01 | Grigg et al. | Applicant |
| US2012/0209657(A1) | 2012-08-01 | Connolly | Applicant |
| US2012/0209685(A1) | 2012-08-01 | Nealer et al. | Applicant |
| US2012/0221421(A1) | 2012-08-01 | Hammad | Applicant |
| US2012/0232994(A1) | 2012-09-01 | Kim et al. | Applicant |
| US2012/0252418(A1) | 2012-10-01 | Kandekar et al. | Applicant |
| US2012/0271692(A1) | 2012-10-01 | Huang et al. | Applicant |
| US2012/0290376(A1) | 2012-11-01 | Dryer et al. | Applicant |
| US2012/0290421(A1) | 2012-11-01 | Qawami et al. | Applicant |
| US2012/0290422(A1) | 2012-11-01 | Bhinder | Applicant |
| US2012/0303425(A1) | 2012-11-01 | Katzin et al. | Applicant |
| US2012/0330769(A1) | 2012-12-01 | Arceo | Applicant |
| US2013/0013499(A1) | 2013-01-01 | Kalgi | Applicant |
| US2013/0030913(A1) | 2013-01-01 | Zhu et al. | Applicant |
| US2013/0036048(A1) | 2013-02-01 | Campos et al. | Applicant |
| US2013/0036051(A1) | 2013-02-01 | Giordano et al. | Applicant |
| US2013/0046589(A1) | 2013-02-01 | Grigg et al. | Applicant |
| US2013/0054367(A1) | 2013-02-01 | Grigg et al. | Applicant |
| US2013/0060623(A1) | 2013-03-01 | Walker et al. | Applicant |
| US2013/0085860(A1) | 2013-04-01 | Summers et al. | Applicant |
| US2013/0103760(A1) | 2013-04-01 | Golding et al. | Applicant |
| US2013/0110658(A1) | 2013-05-01 | Lyman et al. | Applicant |
| US2013/0117155(A1) | 2013-05-01 | Glasgo | Applicant |
| US2013/0132140(A1) | 2013-05-01 | Amin et al. | Applicant |
| US2013/0132246(A1) | 2013-05-01 | Amin et al. | Applicant |
| US2013/0132274(A1) | 2013-05-01 | Henderson et al. | Applicant |
| US2013/0132887(A1) | 2013-05-01 | Amin et al. | Applicant |
| US2013/0138500(A1) | 2013-05-01 | Charaniya et al. | Applicant |
| US2013/0144674(A1) | 2013-06-01 | Kim et al. | Applicant |
| US2013/0144702(A1) | 2013-06-01 | Tabor et al. | Applicant |
| US2013/0151419(A1) | 2013-06-01 | Hitchcock | Applicant |
| US2013/0159086(A1) | 2013-06-01 | Richard | Applicant |
| US2013/0159119(A1) | 2013-06-01 | Henderson et al. | Applicant |
| US2013/0191199(A1) | 2013-07-01 | Corner | Applicant |
| US2013/0198076(A1) | 2013-08-01 | Zambelli Hosmer et al. | Applicant |
| US2013/0218683(A1) | 2013-08-01 | Hannan | Applicant |
| US2013/0246207(A1) | 2013-09-01 | Novak et al. | Applicant |
| US2013/0246301(A1) | 2013-09-01 | Radhakrishnan et al. | Applicant |
| US2013/0282490(A1) | 2013-10-01 | Kramer et al. | Applicant |
| US2014/0012757(A1) | 2014-01-01 | Henderson et al. | Applicant |
| US2014/0108173(A1) | 2014-04-01 | Cooper et al. | Applicant |
| US2014/0129135(A1) | 2014-05-01 | Holden et al. | Applicant |
| US2014/0129302(A1) | 2014-05-01 | Amin et al. | Applicant |
| US2014/0129951(A1) | 2014-05-01 | Amin et al. | Applicant |
| US2014/0156531(A1) | 2014-06-01 | Poon et al. | Applicant |
| US2014/0278609(A1) | 2014-09-01 | Capps | Applicant |
| US2014/0310182(A1) | 2014-10-01 | Cummins | Examiner |
| US2015/0031393(A1) | 2015-01-01 | Post et al. | Applicant |
| US2015/0046339(A1) | 2015-02-01 | Wong | Examiner |
| US2015/0120509(A1) | 2015-04-01 | Moring et al. | Applicant |
| US2015/0339648(A1) | 2015-11-01 | Kushevsky | Examiner |
| US2016/0210606(A1) | 2016-07-01 | Henderson et al. | Applicant |
Non-Patent Literature (32)
- U.S. Appl. No. 13/627,602, filed Sep. 2012, Ranking of Merchants for Cardless Payment Transactions, Henderson et al.Applicant
- U.S. Appl. No. 13/627,615, filed Sep. 2012, Ranking of Merchants for Cardless Payment Transactions, Henderson et al.Applicant
- U.S. Appl. No. 14/017,247, filed Sep. 2013, Authorization of Cardless Payment Transactions, Henderson et al.Applicant
- Hachman, Mark. MobilePay: Your Phone Is Your Credit Card. PCMag. Published Sep. 28, 2010. Retrieved on Sep. 25, 2013. Retrieved from the internet: URL<http://www.pcmag.com/article2/0,2817,2369877,00.asp/>. 1 page.Applicant
- Siegler, MG. MobilePay May Be the Death of the Wallet. Yes, for Real This Time. TechCrunch. Published Sep. 28, 2010. Retrieved on Sep. 22, 2013. Retrieved from the internet: URL<http://techcrunch.com/2010/09/28/mobilepayusa/>. 12 pages.Applicant
- Uber. Google Play. Published on Nov. 10, 2014. Retrieved from the internet on Nov. 12, 2014. Retrieved from the internet: URL<https://play.google.com/store/apps/details?id=com.ubercab&h1=en>. 2 pages.Applicant
- Final Office Action mailed Nov. 5, 2015, for U.S. Appl. No. 13/683,879, of Henderson, W., et al., filed Nov. 21, 2012.Applicant
- Justin, “Visa Enters the Location-Based Mobile Marketing Space With New iPhone App,” dated Dec. 14, 2010, Retrieved from the Internet URL: http://www.mobilemarketingwatch.com/visa-enters-the-location-based-mobile-marketing-space-with-new-iphone-app-11875/, on Feb. 23, 2015, p. 1.Applicant
- Non-Final Office Action mailed Aug. 23, 2013, for U.S. Appl. No. 13/627,615, of Henderson, W., et al., filed Sep. 26, 2012.Applicant
- Non-Final Office Action mailed Oct. 25, 2013, for U.S. Appl. No. 13/683,841, of Henderson, W., et al., filed Nov. 21, 2012.Applicant
- Final Office Action mailed Dec. 23, 2013, for U.S. Appl. No. 13/627,615, of Henderson, W., et al., filed Sep. 26, 2012.Applicant
- Non-Final Office Action mailed May 29, 2014, for U.S. Appl. No. 14/017,247, of Henderson, W., et al., filed Sep. 3, 2013.Applicant
- Non-Final Office Action mailed Sep. 23, 2014, for U.S. Appl. No. 13/627,615, of Henderson, W., et al., filed Sep. 26, 2012.Applicant
- Final Office Action mailed Dec. 18, 2014, for U.S. Appl. No. 13/627,615, of Henderson, W., et al., filed Sep. 26, 2012.Applicant
- Notice of Allowance mailed Mar. 1, 2016, for U.S. Appl. No. 13/627,615, of Henderson, W., et al., filed Sep. 26, 2012.Applicant
- Non-Final Office Action mailed Apr. 22, 2016, for U.S. Appl. No. 13/683,879, of Henderson, W., et al., filed Nov. 21, 2012.Applicant
- Non-Final Office Action mailed Apr. 22, 2016, for U.S. Appl. No. 13/683,841, of Henderson, W., et al., filed Nov. 21, 2012.Applicant
- Non-Final Office Action mailed Apr. 22, 2016, for U.S. Appl. No. 14/498,975, of Varma, A.K., et al., filed Sep. 26, 2014.Applicant
- Final Office Action mailed Apr. 27, 2016, for U.S. Appl. No. 14/017,247, of Henderson, W., et al., filed Sep. 3, 2013.Applicant
- Advisory Action mailed Aug. 5, 2016, for U.S. Appl. No. 141017,247, of Henderson, W., et al., filed Sep. 3, 2013.Applicant
- Final Office Action mailed Dec. 4, 2015, for U.S. Appl. No. 13/627,602, of Henderson, W., et al., filed Sep. 26, 2012.Applicant
- Non-Final Office Action mailed Jan. 9, 2015, for U.S. Appl. No. 14/498,975, of Varma, A., K., et al., filed Sep. 26, 2014.Applicant
- Non-Final Office Action mailed Mar. 17, 2015, for U.S. Appl. No. 13/683,879, of Henderson, W., et al., filed Nov. 21, 2012.Applicant
- Advisory Action mailed May 4, 2015, for U.S. Appl. No. 13/627,615, of Henderson, W., et al., filed Sep. 26, 2012.Applicant
- Non-Final Office Action mailed May 29, 2015, for U.S. Appl. No. 13/627,602, of Henderson, W., et al., filed Sep. 26, 2012.Applicant
- Final Office Action mailed Jul. 8, 2015, for U.S. Appl. No. 14/498,975, of Varma, A., K., et al., filed Sep. 26, 2014.Applicant
- Non-Final Office Action mailed Aug. 12, 2015, for U.S. Appl. No. 13/627,615, of Henderson, W., et al., filed Sep. 26, 2012.Applicant
- Non-Final Office Action mailed Aug. 26, 2015, for U.S. Appl. No. 14/017,247, of Henderson, W., et al., filed Sep. 3, 2013.Applicant
- International Search Report and Written Opinion for International Application No. PCT/US2014/062697, mailed on Feb. 10, 2015.Applicant
- U.S. Appl. No. 14/498,975, filed Sep. 26, 2014, Customer Authentication for an Order, Varma et al.Applicant
- Non-Final Office Action mailed Aug. 29, 2016, for U.S. Appl. No. 13/627,602, of Henderson, W., et al., filed Sep. 26, 2012.Applicant
- Notice of Allowance mailed Oct. 24, 2016, for U.S. Appl. No. 13/683,879, of Henderson, W., et al., filed Nov. 21, 2012.Applicant