Verified purchasing by email

• US 9,922,324 B2
• Filed: 05/21/2014
• Issued: 03/20/2018
• Est. Priority Date: 05/21/2014
• Status: Active Grant

• Current Assignee: Block, Inc. (f/k/a Square, Inc.)
• Original Assignee: Block, Inc. (f/k/a Square, Inc.)
• Inventors: Wilson, Jesse, Grassadonia, Brian, Rhodes, Matthew
• Primary Examiner(s): Robinson, Kito R
• Assistant Examiner(s): Tibljas, Shacole C
• Application Number:
  US14/284,224
• Publication Number:
  US 20150339666A1
• Time in Patent Office: 1,399 Days
• Field of Search: None
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• 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

Abstract

Disclosed are system and methods for purchasing items on a website or a mobile application using a single verification action. The disclosed technique allows a user to initiate a purchase transaction with a merchant via a mobile application on a mobile device and select a mobile payment application associated with a payment service system as a payment method. The mobile application then passes at least a transaction amount and a merchant identifier to the mobile payment application to handover processing of the purchase transaction to the mobile payment application. The mobile payment application, based on preference settings, if any, and otherwise default settings, determines whether to request a confirmation from the user to proceed with the purchase transaction. Once a decision to proceed with the purchase transaction is made, the mobile payment application sends a request to the payment service system to complete the purchase transaction by paying the merchant.

Claims

1. A method of processing a purchase transaction initiated at a mobile application that invokes a payment application associated with a payment service system to complete the purchase transaction, the method comprising:

receiving, by the payment application executing on a mobile device, a request from the mobile application on the mobile device to pay for the purchase transaction initiated at the mobile application,

wherein the purchase transaction is between a user and a merchant,

wherein the request is generated in response to the user selecting the payment application as a payment method for the purchase transaction,

wherein the request includes at least a transaction amount and a merchant identifier associated with the merchant, and

wherein when the user selects the payment application as the payment method, the payment application is displayed on the foreground of the mobile device while the mobile application is executed in the background;

generating, by the payment application executing on the mobile device, a confirmation message for presentation to the user;

obtaining, by the payment application executing on the mobile device, an indication of an interaction with the confirmation message that represents a confirmation from the user to proceed with the purchase transaction;

generating, by the payment application executing on the mobile device and using an email application installed on the mobile device and running in the background, a payment request email by generating an email using the email application installed on the mobile device,

wherein the payment request email comprises the transaction amount in a header portion, the payment request email is addressed to an email address associated with the merchant corresponding to the merchant identifier and addressed to a payment service email address corresponding to the payment service system, and the payment request email containing information identifying an account for the payment service system that is associated with the user, and

wherein the payment request email is not displayed to the user;

sending the payment request email to the payment service system to prompt the payment service system to identify a user financial account associated with the user and a merchant financial account associated with the merchant and initiate a transfer of the transaction amount from the user financial account to the merchant financial account to complete the purchase transaction;

obtaining, by the payment application executing on the mobile device, a confirmation of completion of the purchase transaction from the payment service system; and

notifying, by the payment application executing on the mobile device, the mobile application of the completion of the purchase transaction.

2. The method of claim 1, wherein the email message is generated and sent by the payment application via a background process that is transparent to the user upon obtaining the confirmation from the user to proceed with the purchase transaction.

3. The method of claim 1, wherein the email message that is generated is displayed to the user to allow the user to send the email message to complete the purchase transaction.

4. The method of claim 1, wherein the confirmation message is generated by the payment application based on a preference setting established by the user.

5. The method of claim 4, wherein the preference setting established by the user specifies rules for processing purchase transactions between the user and any merchant.

6. The method of claim 4, wherein the preference setting established by the user specifies rules for processing purchase transactions between the user and a specific merchant.

7. The method of claim 1, wherein the information identifying the account includes at least one of an email address or a phone number associated with the user, an identifier associated with an instance of the payment application installed on the mobile device or an identifier associated with the mobile device.

8. The method of claim 1, wherein the payment request email comprises a HyperText Transfer Protocol (HTTP) request.

9. A computer-readable storage medium storing instructions that, when executed by a mobile device, cause the mobile device to perform operations for processing a purchase transaction initiated at a mobile application that invokes a payment application associated with a payment service system to complete the purchase transaction, the operations comprising:

receiving, by the payment application executing on the mobile device, a request from the mobile application to pay for the purchase transaction initiated at the mobile application,

wherein the purchase transaction is between a user and a merchant,

wherein the request is generated in response to the user selecting the mobile payment application as a payment method for the purchase transaction,

wherein the request includes at least a transaction amount and a merchant identifier associated with the merchant, and

wherein when the user selects the payment application as the payment method, the payment application is displayed on the foreground of the mobile device while the mobile application is executed in the background;

retrieving, by the payment application executing on the mobile device, a preference setting previously established by the user;

generating, by the payment application executing on the mobile device and using an email application installed on the mobile device and running in the background, a payment request email by generating an email using the email application installed on the mobile device,

wherein the payment request email comprises the transaction amount in a header portion, the payment request email is addressed to an email address associated with the merchant corresponding to the merchant identifier and addressed to a payment service email address corresponding to the payment service system, the payment request email containing information identifying an account for the payment service system that is associated with the user, and

wherein the payment request email is not displayed to the user;

sending the payment request email to the payment service system to prompt the payment service system to identify a user financial account associated with the user and a merchant financial account associated with the merchant and initiate a transfer of the transaction amount from the user financial account to the merchant financial account to complete the purchase transaction;

obtaining, by the mobile payment application executing on the mobile device, a confirmation of completion of the purchase transaction from the payment service system; and

notifying, by the payment application executing on the mobile device, the mobile application of the completion of the purchase transaction.

10. The computer-readable storage medium of claim 9, wherein the operations further comprise:

obtaining a confirmation from the user to send the payment request email to the payment service system.

11. The computer-readable storage medium of claim 9, wherein the email message is generated and sent by the payment application via a background process that is transparent to the user upon obtaining a confirmation from the user to proceed with the purchase transaction.

12. The computer-readable storage medium of claim 9, wherein the email message is displayed to the user to allow the user to send the email message to complete the purchase transaction.

13. The computer-readable storage medium of claim 9, wherein, based on the preference setting established by the user, the payment request email is generated and sent to the payment service system without obtaining a confirmation from the user.

14. The computer-readable storage medium of claim 9, wherein the preference setting established by the user specifies rules for processing purchase transactions between the user and any merchant.

15. The computer-readable storage medium of claim 9, wherein the preference setting established by the user specifies rules for processing purchase transactions between the user and a specific merchant.

16. The computer-readable storage medium of claim 9, wherein the information identifying the account includes at least one of an email address or a phone number associated with the user, an identifier associated with an instance of the payment application installed on the mobile device, or an identifier associated with the mobile device.

17. The computer-readable storage medium of claim 9, wherein the mobile application is a browser application used to access a website associated with the merchant to initiate the purchase transaction.

18. A payment system, executing on a mobile device, for processing a purchase transaction between a user and a merchant, the payment system comprising:

a memory;

one or more processors;

a payment application, executing on the foreground of the mobile device, configured to;

receive a request from a mobile application to pay for the purchase transaction initiated via the mobile application, wherein the request is generated in response to the user selecting the payment application as a payment method for the purchase transaction, and wherein the request includes at least a transaction amount and a merchant identifier associated with the merchant; and

generating a payment request by generating an email using an email application installed on the mobile device,

wherein the payment request email comprises the transaction amount in a header portion, the payment request email is addressed to an email address associated with the merchant corresponding to the merchant identifier and addressed to a payment service email address corresponding to the payment service system, the payment request email containing information identifying an account for the payment service system that is associated with the user, and wherein the payment request email is not displayed to the user;

an interface configured to send the payment request email to the payment service system to prompt the payment service system to identify a user financial account associated with the user and a merchant financial account associated with the merchant and initiate a transfer of the transaction amount from the user financial account to the merchant financial account to complete the purchase transaction;

wherein the payment application, executing on the mobile device, is further configured to notify the mobile application of the completion of the purchase transaction.

19. The payment system of claim 18 wherein the payment request email is sent in an email having a body or a subject line populated with the transaction amount so that the payment service system can analyze the email message to identify the transaction amount.

20. The payment system of claim 18 wherein the payment application generates the payment request email in the background and automatically sends the payment request email.

21. The payment system of claim 18, wherein the payment system further comprises a display screen configured to display a notification upon receiving the request from the mobile application, the notification being displayed to obtain a confirmation from the user to proceed with the purchase transaction.

22. The payment system of claim 21, wherein the notification includes an option to allow the user to configure a preference setting for processing subsequent purchase transactions with the merchant.