Transaction bootstrapping to create relationships

• US 10,339,549 B1
• Filed: 06/22/2010
• Issued: 07/02/2019
• Est. Priority Date: 03/23/2010
• Status: Expired due to Fees

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Ramalingam, Harsha, Walsh, Paul J., Carr, Michael, Liden, Lars H., Mittal, Nishant
• Primary Examiner(s): Refai, Sam
• Application Number:
  US12/820,913
• Time in Patent Office: 3,297 Days
• Field of Search: 705 734, 705 263, 705 141- 1473
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/229 Hierarchy of users of accounts
• CPC Class Codes: G06Q 20/2295 Parent-child type, e.g. where parent has control on child rights
• CPC Class Codes: G06Q 20/325 using wireless networks
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/409 Device specific authentication in transaction processing
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 30/0201 Market modelling; Market analysis; Collecting market data
• CPC Class Codes: G06Q 30/0205 Location or geographical consideration
• CPC Class Codes: G06Q 30/0207 Discounts or incentives, e.g. coupons or rebates
• CPC Class Codes: G06Q 30/0222 During e-commerce, i.e. online transactions
• CPC Class Codes: G06Q 30/0239 Online discounts or incentives
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G06Q 30/0253 During e-commerce, i.e. online transactions
• CPC Class Codes: G06Q 30/0255 : based on user history
• CPC Class Codes: G06Q 30/0256 : User search
• CPC Class Codes: G06Q 30/0259 : based on store location
• CPC Class Codes: G06Q 30/0261 : based on user location
• CPC Class Codes: G06Q 30/0267 : Wireless devices
• CPC Class Codes: G06Q 30/0269 : based on user profile or attribute
• CPC Class Codes: G06Q 30/0273 : Determination of fees for advertising
• CPC Class Codes: G06Q 30/0275 : Auctions
• CPC Class Codes: G06Q 30/0601 : Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0609 : Buyer or seller confidence or verification
• CPC Class Codes: G06Q 30/0639 : Item locations
• CPC Class Codes: G06Q 30/0641 : Shopping interfaces
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0861 : using biometrical features, e.g. fingerprint, retina-scan cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231
• CPC Class Codes: H04L 63/107 : wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04M 1/72454 : according to context-related or environment-related conditions
• CPC Class Codes: H04M 1/724631 : by limiting the access to the user interface, e.g. locking a touch-screen or a keypad
• CPC Class Codes: H04M 2203/6054 : Biometric subscriber identification
• CPC Class Codes: H04W 12/00 : Security arrangements; Authentication; Protecting privacy or anonymity
• CPC Class Codes: H04W 12/02 : Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/08 : Access security
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/021 : Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 4/029 : Location-based management or tracking services
• CPC Class Codes: H04W 48/04 : based on user or terminal location or mobility data, e.g. moving direction, speed

Abstract

Techniques for providing friction-free transactions using geolocation and user identifiers are described herein. These techniques may ascertain a user'"'"'s location based on a location of a mobile device. A transaction between the user and a merchant may be completed with zero or minimal input from the user based on the geolocation of the mobile device and the user identifiers. In some implementations, a transaction initiated earlier is completed when the mobile device arrives at the merchant. Additionally, a parent-child or similar relationship may be established between multiple devices. Security on the mobile device based may be provided by biometric identification and calculation of variance from regular movement patterns. Advertisements may be sent to the mobile device based on bids from merchants near to the mobile device. A relationship between the mobile device an a merchant may be bootstrapped from previous transactions that did not use the mobile device.

Claims

1. A computer-implemented method comprising:

accessing, by at least one of one or more computing devices, user information associated with a user, the user information including payment information;

determining, by at least one of the one or more computing devices and based at least in part on location data generated by a location sensor associated with a mobile device associated with the user, that the mobile device is within a threshold distance of a merchant location associated with a merchant device of a merchant;

accessing, by at least one of the one or more computing devices, transaction information associated with a plurality of purchases completed by a plurality of entities with the merchant over a past period of time, the transaction information accessed in response to the mobile device being within the threshold distance of the merchant location and based at least in part on a length of the past period of time, the length of the past time period defined based at least in part on a frequency of the plurality of purchases or a behavior of the mobile device relative to the merchant location;

determining, by at least one of the one or more computing devices, a match between the payment information associated with the user and the transaction information associated with the plurality of purchases;

causing, by at least one of the one or more computing devices and based at least in part on the match, a user interface to be displayed on the mobile device, the user interface configured to display a message inviting the user to designate the merchant as a trusted merchant, the display of the message via the user interface activating the mobile device to display the message via the user interface based at least in part on a setting stored at the mobile device for activating a messaging functionality of the mobile device;

receiving, by at least one of the one or more computing devices from the mobile device, a selection designating the merchant as the trusted merchant based at least in part on the message;

causing, by at least one of the one or more computing devices and based at least in part on the setting for the messaging functionality of the mobile device, a display via the user interface of one or more messages inviting the user to assign a trust level from a plurality of trust levels to the trusted merchant and to store the payment information for use with a next transaction between the mobile device and the merchant device;

receiving, by at least one of the one or more computing devices from the mobile devices and based at least in part on the one or more messages, information associated with the trust level and with storing the payment information for use with the next transaction;

storing, by at least one of the one or more computing devices, the payment information for use with the next transaction based at least in part on the information;

selecting, by at least one of the one or more computing devices, an amount of interaction between the mobile device and the merchant device to complete the next transaction, the amount of interaction selected from a zero interaction, a single interaction, and multiple interactions based at least in part on the trust level and the payment information;

associating, by at least one of the one or more computing devices, one or more indications with the user information, the one or more indications assigning the trust level to the trusted merchant and assigning the amount of interaction and the payment information to the mobile device and the trusted merchant;

determining, by at least one of the one or more computing devices, an initiation of the next transaction between the mobile device and the merchant device;

authenticating, by at least one of the one or more computing devices, the user based at least in part on a handshake with a security module of the mobile device, the handshake based at least in part on a unique identifier of the user and on a history of interactions between the one or more computing devices and the mobile device; and

causing, by at least one of the one or more computing devices and based at least in part on the user being authenticated, a display via the user interface of a second message about completing the next transaction based at least in part on the amount of interaction and the payment information.

2. The method as recited in claim 1, wherein the payment information associated with the user comprises partial payment information that is insufficient to charge an underlying payment account associated with the user.

3. The method as recited in claim 1, wherein the payment information associated with the user comprises a partial credit card number.

4. The method as recited in claim 1, wherein causing the display of the one or more messages further comprises, determining that the mobile device is within the threshold distance of the merchant location by comparing a detected location of the mobile device with a stored location of the merchant, wherein the detected location of the mobile device is determined based at least in part on the location data that is received from the location sensor associated with the mobile device.

5. The method as recited in claim 1, wherein the user interface includes an option to decline designating the merchant as a trusted merchant.

6. The method as recited in claim 1, further comprising:

receiving, by at least one of the one or more computing devices, purchase information for a purchase that was paid for using the payment information associated with the user, wherein the one or more messages prompt the user to indicate whether to store the purchase information in a purchase record; and

responsive to receiving an indication to store the purchase information in the purchase record, storing, by at least one of the one or more computing devices, the purchase information in the purchase record.

7. The method as recited in claim 6, further comprising:

at a later time, responsive to determining that the mobile device is within the threshold distance of the merchant location, sending, by at least one of the one or more computing devices, another message to the mobile device prompting an indication asking whether to conduct another purchase based at least in part on the purchase information stored in the purchase record.

19. The method as recited in claim 1, wherein an individual trust level of the plurality of trust levels indicates that future electronic transactions between the mobile device and the trusted merchant are to be completed automatically without user interaction when the mobile device is within a threshold distance of a location associated with the trusted merchant.

21. The method as recited in claim 1, wherein the length of the past period of time is lengthened with an increase in the frequency of the plurality of purchases.

22. The method as recited in claim 1, wherein the length of the past period of time is further defined based at least in part on a period of time during which the mobile device is within the threshold distance of the merchant location.

8. One or more non-transitory computer-readable storage media storing computer-executable instructions that, when executed by one or more processors, instruct a one or more computer systems to perform operations comprising:

obtaining identification information associated with a user;

correlating a location of a mobile device associated with the user with a location of a merchant device of a merchant, the location of the mobile device determined based at least in part on location data generated by a location sensor associated with the mobile device;

at least partly in response to the correlating, accessing customer identification information associated with a plurality of previous purchases completed by a plurality of entities with the merchant over a period of time, the period of time having a length that is defined based at least in part on a frequency of the plurality of previous purchases or a behavior of the mobile device relative to the location of the merchant device;

determining a match between the identification information associated with the user and the customer identification information associated with the plurality of entities;

causing, based at least in part on the match, a user interface to be presented on the mobile device associated with the user, the user interface configured to present a first message that prompts the user to designate the merchant as a trusted merchant, presenting the first message comprising activating the mobile device to present the first message via the user interface based at least in part on a setting stored at the mobile device for activating a messaging functionality of the mobile device;

receiving a selection via the user interface designating the merchant as the trusted merchant;

causing presentation of one or more messages via the user interface inviting the user to assign a trust level from a plurality of trust levels to the trusted merchant and to associate the identification information with future electronic transactions between the mobile device and the merchant device;

selecting an amount of interaction between the mobile device and the merchant device for the future electronic transactions based at least in part on the trust level and an association of the identification information with the future electronic transactions, the amount of interaction selected from a zero interaction, a single interaction, and multiple interactions;

associating the mobile device with one or more indications assigning the trust level to the trusted merchant and assigning the amount of interaction to the mobile device and the trusted merchant;

authenticating the user based at least in part on a handshake with a security module of the mobile device, the handshake based at least in part on a unique identifier of the user and on a history of interactions between the one or more computer systems and the mobile device; and

causing, based at least in part on the user being authenticated, a display via the user interface of a second message about completing a future transaction based at least in part on the amount of interaction and the identification information.

9. The one or more non-transitory computer-readable storage media as recited in claim 8, wherein correlating the location of the mobile device with the location of the merchant includes comparing measured coordinates of the mobile device with stored coordinates of the merchant and determining that the measured coordinates of the mobile device are within a predetermined distance of the stored coordinates of the merchant.

10. The one or more non-transitory computer-readable storage media as recited in claim 8, wherein the merchant information comprises a point-of-sale device, wherein accessing the customer identification information comprises accessing the customer identification information on the point-of-sale device.

11. The one or more non-transitory computer-readable storage media as recited in claim 8, wherein the identification information associated with the user comprises payment information.

12. The one or more non-transitory computer-readable storage media as recited in claim 11, wherein the payment information associated with the user comprises a final four digits of a credit card number.

13. The one or more non-transitory computer-readable storage media as recited in claim 11, wherein the operations further comprise receiving purchase information for a purchase that was paid for using the payment information associated with the user.

14. The one or more non-transitory computer-readable storage media as recited in claim 8, wherein the operations further comprise, in response to the selection designating the merchant as the trusted merchant, automatically storing the identification information in a transaction record associated with the user.

15. The one or more non-transitory computer-readable storage media as recited in claim 8, wherein the operations further comprise receiving authorization from the user prior to obtaining the identification information associated with the user.

16. A computing device comprising:

one or more processors; and

a memory coupled to the one or more processors, the memory including one or more modules that are executable by the one or more processors to;

store a user identifier that is associated with a user, a mobile device, and payment information;

store an indication of a merchant and a merchant geolocation associated with a merchant device of the merchant;

compare a detected geolocation of the mobile device with the merchant geolocation, the detected geolocation of the mobile device based at least in part on a location sensor associated with the mobile device;

determine that the mobile device is located within a predetermined threshold distance of the merchant geolocation based at least in part on an outcome of the compare;

access customer identification information associated with a plurality of previous purchases completed by a plurality of entities with the merchant over a period of time, the period of time having a length that is defined based at least in part on a frequency of the plurality of previous purchases or a behavior of the mobile device relative to the location of the merchant device;

determine that a match exists between the customer identification information associated with the plurality of previous purchases and the user identifier;

cause, based at least in part on the match, a user interface to be presented on the mobile device associated with the user, the user interface configured to present a first message inviting the user to designate the merchant located at the merchant geolocation as a trusted merchant, presenting the first message comprising activating the mobile device to present the first message via the user interface based at least in part on a setting stored at the mobile device for activating a messaging functionality of the mobile device;

receive a response via the user interface designating the merchant as the trusted merchant;

cause presentation of a second message via the user interface inviting the user to assign a trust level from a plurality of trust levels to the trusted merchant;

add the merchant to a list of trusted merchants and assign the trust level to the trusted merchant based at least in part on a response to the second message;

select an amount of interaction between the mobile device and the merchant device to complete a next transaction, the amount of interaction selected from a zero interaction, a single interaction, and multiple interactions based at least in part on the trust level;

associate the amount of interaction to the mobile device and the trusted merchant;

determining an initiation of the next transaction between the mobile device and the merchant device;

authenticating the user based at least in part on a handshake with a security module of the mobile device, the handshake based at least in part on a unique identifier of the user and on a history of interactions between the computing device and the mobile device; and

cause, based at least in part on the user being authenticated, a display via the user interface of a third message about completing the next transaction based at least in part on the amount of interaction being associated to the mobile device and the trusted merchant.

17. The computing device as recited in claim 16, wherein the one or more modules are further executable by the one or more processors to receive, from the merchant, purchase information about a purchase made using the payment information associated with the user identifier.

18. The computing device as recited in claim 16, wherein the one or more modules are further executable by the one or more processors to facilitate, at a later time, a purchase between the user and the trusted merchant in response to determining that the mobile device is located at the merchant geolocation.

20. The computing device as recited in claim 16, wherein the one or more modules are further executable by the one or more processors to receive, from the mobile device, repeat purchase information to facilitate an automatic purchase between the mobile device and the merchant device in response to the detected geolocation of the mobile device being within the predetermined threshold distance of the merchant geolocation.