Adding card to mobile wallet using NFC
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.
1. A method, comprising:
retrieving, by a computing device, data from a payment instrument detected proximate to the computing device;
determining an account number associated with the payment instrument based at least on the data;
causing a user interface of the computing device to display account information with a plurality of fields, wherein the account information comprises at least a portion of the account number, and wherein at least one field from the plurality of fields is configured to receive an input to change the account information displayed;
receiving an authentication input in the plurality of fields that indicates a user identifier;
determining the user identifier is stored in one or more databases;
determining an authentication of the user identifier based at least on the user identifier stored in the one or more databases and the account information; and
causing the user interface to display an option to add the account number 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 the data is retrieved based at least on a near field communication established between the mobile device and a communication chip embedded in the payment instrument detected.
3. The method of claim 1 , wherein the user identifier comprises an address associated with the computing device, and wherein the method further comprises:
receiving an authentication input in the plurality of fields that indicates a personal identification number (PIN); and
determining the PIN is stored in the one or more databases, wherein the authentication of the user identifier is determined based further on the PIN stored in the one or more databases.
4. The method of claim 1 , further comprising:
receiving an input in the plurality of fields that indicates a request to change the account information displayed; and
causing the user interface to display second information based at least on the request, and wherein the authentication of the user identifier is determined based further on the second information displayed.
5. The method of claim 4 , wherein the request to change the account information comprises a request to add an expiration date to the account information, and wherein the second information is displayed to include the expiration date.
6. The method of claim 4 , wherein the request to change the card information comprises a request to add an account verification code to the account information, and wherein the second information is displayed to include the account verification code.
7. The method of claim 1 , wherein the data is retrieved from a communication chip associated with the payment instrument based at least on user input received via an application executing on the computing device.
8. A system, comprising:
non-transitory memory; and
one or more hardware processors couples to the non-transitory memory and configured to execute instructions to cause the system to perform operations comprising:
retrieving, by a computing device, data from a payment instrument detected proximate to the computing device;
determining an account number associated with the payment instrument based at least on the data;
causing a user interface of the computing device to display account information with a plurality of fields, wherein the account information comprises at least a portion of the account number, and wherein at least one field from the plurality of fields is configured to receive an input to change the account information displayed;
receiving an authentication input in the plurality of fields that indicates a user identifier;
determining the user identifier is stored in one or more databases;
determining an authentication of the user identifier based at least on the user identifier stored in the one or more databases and the account information; and
causing the user interface to display an option to add the account number to a user account accessible by the computing device based at least on the authentication of the user identifier.
9. The system of claim 8 , wherein the computing device is a mobile device, and wherein the data is retrieved based at least on a near field communication established between the mobile device and a communication chip embedded in the payment instrument detected.
10. The system of claim 8 , wherein the user identifier comprises an address associated with the computing device, and wherein the operations further comprise:
receiving an authentication input in the plurality of fields that indicates a personal identification number (PIN); and
determining the PIN is stored in the one or more databases, wherein the authentication of the user identifier is determined based further on the PIN stored in the one or more databases.
11. The system of claim 8 , wherein the operations further comprise:
receiving an input in the plurality of fields that indicates a request to change the account information displayed; and
causing the user interface to display second information based at least on the request, and wherein the authentication of the user identifier is determined based further on the second information displayed.
12. The system of claim 11 , wherein the request to change the account information comprises a request to add an expiration date to the account information, and wherein the second information is displayed to include the expiration date.
13. The system of claim 11 , wherein the request to change the card information comprises a request to add an account verification code to the account information, and wherein the second information is displayed to include the account verification code.
14. The system of claim 8 , wherein the data is retrieved from a communication chip associated with the payment instrument based at least on user input received via an application executing on the computing device.
15. A non-transitory machine readable medium having stored thereon machine readable instructions executable to cause a machine to perform operations comprising:
retrieving, by a computing device, data from a payment instrument detected proximate to the computing device;
determining an account number associated with the payment instrument based at least on the data;
causing a user interface of the computing device to display account information with a plurality of fields, wherein the account information comprises at least a portion of the account number, and wherein at least one field from the plurality of fields is configured to receive an input to change the account information displayed;
receiving an authentication input in the plurality of fields that indicates a user identifier;
determining the user identifier is stored in one or more databases;
determining an authentication of the user identifier based at least on the user identifier stored in the one or more databases and the account information; and
causing the user interface to display an option to add the account number to a user account accessible by the computing device based at least on the authentication of the user identifier.
16. The non-transitory machine readable medium of claim 15 , wherein the computing device is a mobile device, and wherein the data is retrieved based at least on a near field communication established between the mobile device and a communication chip embedded in the payment instrument detected.
17. The non-transitory machine readable medium of claim 15 , wherein the user identifier comprises an address associated with the computing device, and wherein the operations further comprise:
receiving an authentication input in the plurality of fields that indicates a personal identification number (PIN); and
determining the PIN is stored in the one or more databases, wherein the authentication of the user identifier is determined based further on the PIN stored in the one or more databases.
18. The non-transitory machine readable medium of claim 15 , wherein the processes further comprise:
receiving an input in the plurality of fields that indicates a request to change the account information displayed; and
causing the user interface to display second information based at least on the request, and wherein the authentication of the user identifier is determined based further on the second information displayed.
19. The non-transitory machine readable medium of claim 18 , wherein the request to change the account information comprises a request to add an expiration date to the account information, and wherein the second information is displayed to include the expiration date.
20. The non-transitory machine readable medium of claim 18 , wherein the request to change the card information comprises a request to add an account verification code to the account information, and wherein the second information is displayed to include the account verification code.