Adding card to mobile wallet using NFC

• US 10,262,320 B2
• Filed: 01/17/2017
• Issued: 04/16/2019
• Est. Priority Date: 02/03/2012
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Inventors: Moghadam, Ali Minaei
• Primary Examiner(s): Hess, Daniel A
• Application Number:
  US15/408,359
• Publication Number:
  US 20170124568A1
• Time in Patent Office: 819 Days
• Field of Search: 235379, 705 261, 705 272
• CPC Class Codes: G06K 7/10366 the interrogation device being adapted for miscellaneous applications
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/352 Contactless payments by cards
• CPC Class Codes: G06Q 20/3567 Software being in the reader
• CPC Class Codes: G06Q 20/3672 initialising or reloading thereof
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/4018 using the card verification value [CVV] associated with the card
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

A user enables a communication, such as through a tap, between an NFC-enabled payment or funding card and a mobile device. Card information, such as the card number, type, and expiration date, are read by the mobile device. The user is then authenticated through the user device, such as by entering a CVV code, a PIN for the card, a cardholder name, and/or a billing address for the card. If confirmed, the card is added to the user'"'"'s mobile/cloud wallet.

Claims

1. A method comprising:

retrieving, by a computing device, data from a payment instrument;

causing a user interface of the computing device to display at least a portion of the data retrieved from the payment instrument with at least one account information field of a plurality of account information fields, wherein the at least one account information field is configured to receive an input to change the at least the portion of the data received from the payment instrument;

receiving, by the computer device, an authentication input in the at least one account information field of the plurality of account information fields that indicates a user identifier associated with the payment instrument;

determining, by the computing device, an authentication of the user identifier; and

causing the user interface to display an option to add the at least the portion of the data retrieved from the payment instrument to a user account accessible by the computing device based at least on the authentication of the user identifier.

2. The method of claim 1, wherein the computing device is a mobile device, and wherein retrieving the data includes establishing near field communication between the mobile device and the payment instrument.

3. The method of claim 1, wherein the user identifier comprises an address associated with the computing device, and wherein the authentication input further comprises a personal identification number (PIN).

4. The method of claim 1, wherein the authentication input further comprises a card security code associated with the payment instrument.

5. The method of claim 1, further comprising, in response to determining that the user account includes the user identifier, causing the user interface to display a second input field, wherein the second input field is automatically populated with the authentication input.

6. The method of claim 1, wherein determining the authentication of the user identifier is based on information received from a payment provider server.

7. The method of claim 1, wherein determining the authentication of the user identifier comprises determining whether the user identifier is stored in a database.

8. A system comprising:

a non-transitory memory; and

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

retrieving data from a payment instrument;

displaying at least a portion of the data retrieved from the payment instrument with at least one account information field of a plurality of account information fields, wherein the at least one account information field is configured to receive an input to change the at least the portion of the data received from the payment instrument;

receiving an authentication input in at least one account information field of the plurality of account information fields that indicates a user identifier associated with the payment instrument;

determining an authentication of the user identifier; and

displaying an option to add the at least the portion of the data from the payment instrument to a user account associated with a payment provider server based at least on the authentication of the user identifier.

9. The system of claim 8, wherein retrieving the data includes establishing near field communication with the payment instrument.

10. The system of claim 8, wherein the authentication input further comprises a personal identification number (PIN).

11. The system of claim 8, wherein the authentication input further comprises a card security code (CSC).

12. The system of claim 8, wherein the operations further comprise, in response to determining that the user account includes the user identifier, displaying a second input field, wherein the second input field is automatically populated with the user identifier.

13. The system of claim 8, wherein determining the authentication of the user identifier is based on information received from a payment provider server.

14. The system of claim 8, wherein determining the authentication of the user identifier comprises determining whether the user identifier is stored in a database.

15. A non-transitory machine readable medium having stored thereon machine readable instructions executable to cause a machine to perform operations comprising:

retrieving data from a payment instrument;

displaying at least a portion of the data retrieved from the payment instrument with at least one account information field of a plurality of account information fields, wherein the at least one account information field is configured to receive an input to change the at least the portion of the data received from the payment instrument;

receiving an authentication input in at least one account information field of the plurality of account information fields that indicates a user identifier associated with the payment instrument;

authenticating a user of the payment instrument based on the user identifier; and

displaying an option to add the at least the portion of the data from the payment instrument to a user account in response to authenticating the user.

16. The non-transitory machine readable medium of claim 15, wherein retrieving the data includes establishing near field communication with the payment instrument.

17. The non-transitory machine readable medium of claim 15, wherein the user identifier further comprises a personal identification number (PIN).

18. The non-transitory machine readable medium of claim 15, wherein the user identifier further comprises a card verification value (CVV) code.

19. The non-transitory machine readable medium of claim 15, wherein the operations further comprise, when the user account includes the user identifier, displaying a second input field, wherein the second input field is automatically populated with the user identifier.

20. The non-transitory machine readable medium of claim 15, wherein the user is authenticated based on information received from a payment provider server.