Recommended payment options

• US 10,318,946 B2
• Filed: 04/22/2015
• Issued: 06/11/2019
• Est. Priority Date: 04/22/2014
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Inventors: Mills, Benjamin Eroe, Benitez, II, Juan Antonio
• Primary Examiner(s): Ojiaku, Chikaodinaka
• Application Number:
  US14/693,671
• Publication Number:
  US 20150302383A1
• Time in Patent Office: 1,511 Days
• Field of Search: 705 39
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer

Abstract

Methods and systems for providing the most suitable payment methods to a user in a specific transaction are described. A service provider uses information obtained from a merchant about the transaction and information the service provider knows about a user to generate a list of possible payment methods. The service provider determines which payment methods the user may want to use for the transaction by looking at, for example, user preferences, merchant preferences, and past purchases made by the user, and the payment methods are displayed on a user device.

Claims

1. A system of a payment service provider, comprising:

a non-transitory memory; and

one or more hardware processors coupled with the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising;

receiving a request for a client token from a merchant server, the request received subsequent to a purchase request associated with a purchase transmitted to the merchant server from a user device of a user and prior to the user providing payment information to the merchant server for the purchase, wherein the purchase request comprises information related to the purchase;

receiving merchant acquired information of the user that corresponds to the purchase request;

in response to receiving the request and the merchant acquired information of the user, identifying, from a plurality of user accounts with the payment service provider, a user account associated with the user based on the merchant acquired information of the user, wherein the user account includes information related to a plurality of payment methods available to the user and user behavior information derived from past interactions with the user, wherein each payment method in the plurality of payment methods is associated with a set of hardware component requirements and a set of software component requirements;

generating a client token for the purchase based on the merchant acquired information of the user and the user behavior information of the user;

transmitting the client token to the merchant server, the transmitting, causing the merchant server to forward the client token to an application associated with the merchant server and executed on the user device;

based on the client token being forwarded to the application executed on the user device, receiving, from the application executed on the user device, device information corresponding to the user device, wherein the device information comprises location information obtained from a location component of the user device, information associated with a hardware component of the user device, and information associated with a software component of the user device;

in response to receiving the device information from the application executed on the user device, selecting, based on the merchant acquired information, the user behavior information, and the device information, a subset of payment methods for the purchase from the plurality of payment methods available to the user, wherein the subset of payment methods is selected based at least in part on the hardware component and the software component of the user device satisfying the set of hardware component requirements and the set of software component requirements associated with each payment method in the subset of payment methods;

generating a set of single-use payment tokens, each single-use payment token of the set of single-use payment tokens corresponding to using a respective payment method included in the subset of payment methods for the purchase;

transmitting the set of single-use payment tokens to the application executed on the user device, the transmitting causing the application to display the subset of payment methods in a checkout page of the application displayed on the user device;

receiving, from the application executed on the user device, a first single-use payment token of the set of single-use payment tokens, the first single-use payment token corresponding to a first payment method included in the subset of payment methods for the user; and

in response to receiving the first single-use payment token from the application executed on the user device, processing an electronic payment transaction between the user and a merchant associated with the merchant server for the purchase using the first payment method based on the first single-use payment token.

2. The system of claim 1, wherein the information related to the purchase comprises at least one of a transaction amount, an item description, an item price, a total price, a shipping cost, or a tax amount.

3. The system of claim 1, wherein the user behavior information comprises at least one of a user identity, a type of payment methods used by the user, past purchase transactions information of the user, or a payment frequency associated with a payment method.

4. The system of claim 1, wherein the operations further comprise:

receiving, from the application, time and calendar information stored on the user device, wherein the selecting the subset of payment methods for the purchase is further based on the time and calendar information.

5. The system of claim 1, wherein the information associated with the hardware component of the user device comprises a model number of the user device.

6. The system of claim 1, wherein the information associated with the software component of the user device comprises a version of an operating system running on the user device, and wherein the operations further comprise determining that the first payment method is supported by the user device based on the version of the operation system running on the user device.

7. The system of claim 1, wherein the request comprises an identifier of the merchant, and wherein the subset of payment methods is selected further based on the identifier of the merchant.

8. A method for providing payment methods, comprising:

receiving, by a service provider server comprising one or more hardware processors, a request for a client token from a merchant server, the request received subsequent to a purchase request associated with a purchase transmitted to the merchant server from a user device of a user and prior to the user providing payment information to the merchant server for the purchase, wherein the purchase request comprises information related to the purchase;

receiving, by the service provider server, merchant acquired information of the user that corresponds to the purchase request;

in response to receiving the request and the merchant acquired information of the user, identifying, by the service provider server from a plurality of user accounts with the service provider server, a user account associated with the user based on the merchant acquired information of the user, wherein the user account includes information related to a plurality of payment methods available to the user and user behavior information derived from past interactions between the service provider server and the user, wherein each payment method in the plurality of payment methods is associated with a set of hardware component requirements and a set of software component requirements;

generating, by the service provider server, a client token for the purchase based on the merchant acquired information and the user behavior information of the user;

transmitting, by the service provider server, the client token to the merchant server, the transmitting causing the merchant server to forward the client token to an application associated with the merchant server and executed on the user device;

based on the client token being forwarded to the application executed on the user device, receiving, by the service provider server from the application executed on the user device, device information corresponding to the user device, wherein the device information comprises location information obtained from a location component of the user device, information associated with a hardware component of the user device, and information associated with a software component of the user device;

in response to receiving the device information from the application executed on the user device, selecting, by the service provider server based on the merchant acquired information, the user behavior information, and the device information, a subset of payment methods for the purchase from the plurality of payment methods available to the user, wherein the subset of payment methods is selected based at least in part on the hardware component and the software component of the user device satisfying the set of hardware component requirements and the set of software component requirements associated with each payment method in the subset of payment methods;

generating, by the service provider server, a set of single-use payment tokens, each single-use payment token of the set of single-use payment tokens corresponding to using a respective payment method included in the subset of payment methods for the purchase;

transmitting, by the service provider server, the set of single-use payment tokens to the application executed on the user device, the transmitting causing the application to display the subset of payment methods on the user device;

receiving, by the service provider server from the application the user device, a first single-use payment token of the set of single-use payment tokens, the first single-use payment token corresponding to a first payment method included in the subset of payment methods for the user; and

in response to receiving the first single-use payment token from the application of executed on the user device, processing, by the service provider server, a payment transaction between the user and a merchant associated with the merchant server for the purchase using the first payment method based on the first single-use payment token.

9. The method of claim 8, wherein the information related to the purchase comprises at least one of a transaction amount, an item description, an item price, a total price, a shipping cost, or a tax amount.

10. The method of claim 8, wherein the user behavior information comprises at least one of a user identity, a type of payment methods used by the user, past purchase transactions information of the user, or a payment frequency associated with a payment method.

11. The method of claim 8, further comprising receiving, by the service provider server from the application, time and calendar information stored on the user device, wherein the selecting the subset of payment methods for the purchase is further based on the time and calendar information.

12. The method of claim 8, wherein the information associated with the hardware component of the user device comprises a model number of the user device, and wherein the method further comprises determining that a second payment method of the plurality of payment method not included in the subset of payment method is unsupported by the user device based on the model number.

13. The method of claim 8, wherein the information associated with the software component of the user device comprises a version of an operating system running on the user device, and wherein the method further comprises determining that the first payment method is supported by the user device based on the version of the operation system running on the user device.

14. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine associated with a payment service provider to perform operations comprising:

receiving a request for a client token from a merchant server, the request received subsequent to a purchase request associated with a purchase transmitted to the merchant server from a user device of a user and prior to the user providing payment information to the merchant server for the purchase, wherein the purchase request comprises information related to the purchase;

receiving merchant acquired information of the user that corresponds to the purchase request;

in response to receiving the request and the merchant acquired information of the user, identifying, from a plurality of user accounts with the payment service provider, a user account associated with the user based on the merchant acquired information of the user, wherein the user account includes information related to a plurality of payment methods available to the user and user behavior information derived from past interactions with the user, wherein each payment method in the plurality of payment methods is associated with a set of hardware component requirements and a set of software component requirements;

generating a client token for the purchase based on the merchant acquired information of the user and the user behavior information of the user;

transmitting the client token to the merchant server, the transmitting causing the merchant server to forward the client token to an application of associated with the merchant server and executed on the user device;

based on the client token being forwarded to the application executed on the user device, receiving, from the application executed on the user device, device information corresponding to the user device, wherein the device information comprises location information obtained from a location component of the user device, information associated with a hardware component of the user device, and information associated with a software component of the user device;

in response to receiving the device information from the application executed on the user device, selecting, based on the merchant acquired information, the user behavior information, and the device information, a subset of payment methods for the purchase from the plurality of payment methods available to the user, wherein the subset of payment methods is selected based at least in part on the hardware component and the software component of the user device satisfying the set of hardware component requirements and the set of software component requirements associated with each payment method in the subset of payment methods;

generating a set of single-use payment tokens, each single-use payment token of the set of single-use payment tokens corresponding to a respective payment method included in the subset of payment methods for the purchase;

transmitting the set of single-use payment tokens to the application executed on the user device, the transmitting causing the application to display the subset of payment methods on the user device;

receiving, from the application executed on the user device, a first single-use payment token of the set of single-use payment tokens, the first single-use payment token corresponding to a first payment method included in the subset of payment methods for the user; and

in response to receiving the first single-use payment token from the application executed on the user device, processing a payment transaction between the user and a merchant associated with the merchant server for the purchase using the first payment method based on the first single-use payment token.

15. The non-transitory machine-readable medium of claim 14, wherein the device information comprises at least one of a transaction amount, an item description, an item price, a total price, a shipping cost, or a tax amount.

16. The non-transitory machine-readable medium of claim 14, wherein the user behavior information comprises at least one of a user identity, a type of payment methods used by the user, past purchase transactions information of the user, or a payment frequency associated with a payment method.

17. The non-transitory machine-readable medium of claim 14, wherein the operations further comprise:

receiving, from the application, time and calendar information stored on the user device, wherein the selecting the subset of payment methods for the purchase is further based on the time and calendar information.

18. The non-transitory machine-readable medium of claim 14, wherein the information associated with the hardware component of the user device comprises a model number of the user device.

19. The non-transitory machine-readable medium of claim 14, wherein the merchant acquired information of the user comprises user identity information associated with the user.

20. The non-transitory machine-readable medium of claim 14, wherein the information associated with the software component of the user device comprises a version of an operating system running on the user device, and wherein the operations further comprise determining that the first payment method is supported by the user device based on the version of the operation system running on the user device.