Integration of payment capability into secure elements of computers

• US 10,657,528 B2
• Filed: 08/31/2016
• Issued: 05/19/2020
• Est. Priority Date: 02/24/2010
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Hammad, Ayman
• Primary Examiner(s): Lee, Michael G
• Assistant Examiner(s): Tardif, David
• Application Number:
  US15/252,595
• Publication Number:
  US 20160371688A1
• Time in Patent Office: 1,357 Days
• Field of Search: 235375
• CPC Class Codes: G06F 16/2457 with adaptation to user needs
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 2221/2129 Authenticate client device independently of the user
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• 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/401 Transaction verification
• CPC Class Codes: G06Q 20/42 Confirmation, e.g. check or permission by the legal debtor of payment
• CPC Class Codes: G06Q 20/425 using two different networks, one for transaction and one for security confirmation
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 9/14 using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

Abstract

Methods, secure elements, validation entities, and computer program products for effecting secure communication of payment information to merchants for Internet-based purchases. Payment information for a user'"'"'s real payment information is installed in a secure element of a computer, the payment information may comprise a pseudo PAN number for the portable consumer device provided by a validation entity. The secure element is shielded from the computer'"'"'s operating system to thwart hacker attacks. The user accesses the secure element to make a purchase. In response, the secure element contacts the validation entity with the pseudo account number, and in response obtains dynamic payment information that the secure element can used to effect the payment. The dynamic payment information comprises an account number that is different from the pseudo PAN, and which has at least one difference which respect to the user'"'"'s real payment information.

Claims

1. A method performed by a server computer, the method comprising:

receiving, by the server computer, a pseudo account number from a user computer operated by a user, the pseudo account number being associated with and being different than a real account number;

in response to receiving the pseudo account number, transmitting, by the server computer to the user computer, dynamic payment information in response to receiving the pseudo account number, wherein the dynamic payment information comprises a dynamic account number, wherein the dynamic account number and the pseudo account number are different; and

receiving, by the server computer, the dynamic payment information via a merchant computer after the merchant computer receives the dynamic payment information from the user computer, and exchanging the dynamic payment information with the real account number during a transaction.

2. The method of claim 1, wherein the user computer is a mobile phone.

3. The method of claim 1, wherein the server computer is a validation entity computer.

4. The method of claim 1 further comprising:

transmitting, by the server computer, the pseudo account number to the user computer.

5. The method of claim 1, wherein the pseudo account number is 16 digits.

6. The method of claim 1, wherein the user computer comprises a secure element and the user computer stores the pseudo account number in the secure element.

7. The method of claim 1, wherein the dynamic account number and the pseudo account number are in the same format.

8. The method of claim 1, further comprising:

transmitting the real account number to a payment processing network.

9. The method of claim 1, wherein the user computer comprises a secure element and wherein the pseudo account number is stored in the secure element.

10. The method of claim 9, wherein the secure element comprises a data processor, an input/output controller, and a multiplexer.

11. The method of claim 9, wherein the dynamic account number, the pseudo account number, and the real account number, are each 15-19 digits in length.

12. A method comprising:

providing, by a user computer operated by a user, a pseudo account number to a server computer, wherein the pseudo account number is associated with and is different than a real account number;

receiving, by the user computer, dynamic payment information in response to providing the pseudo account number, wherein the dynamic payment information comprises a dynamic account number, wherein the dynamic account number and the pseudo account number are different; and

providing, by the user computer, the dynamic payment information in a transaction to the server computer via a merchant computer after the merchant computer receives the dynamic payment information from the user computer, wherein the server computer thereafter exchanges the dynamic payment information with the real account number during the transaction.

13. The method of claim 12 wherein the user computer is a mobile phone.

14. The method of claim 12, wherein the merchant computer operates a merchant Website.

15. The method of claim 12 wherein the user computer comprises a secure element and wherein the pseudo account number is stored in the secure element.

16. The method of claim 12 further comprising:

receiving, by the user computer, the pseudo account number from the server computer.

17. A server computer comprising:

a processor; and

a computer readable medium coupled to the processor, the computer readable medium comprising code, executable by the processor for implementing a method comprising

receiving, by the server computer, a pseudo account number from a user computer operated by a user, the pseudo account number being associated with and being different than a real account number,

in response to receiving the pseudo account number, transmitting, by the server computer to the user computer, dynamic payment information in response to receiving the pseudo account number, wherein the dynamic payment information comprises a dynamic account number, wherein the dynamic account number and the pseudo account number are different; and

receiving, by the server computer, the dynamic payment information from the user computer via a merchant computer after the merchant computer receives the dynamic payment information from the user computer, and exchanging the dynamic payment information with the real account number during a transaction.

18. The server computer of claim 17, wherein the user computer is a mobile phone.

19. The server computer of claim 17, wherein the server computer is a validation entity computer.

20. The server computer of claim 17, wherein the pseudo account number is 16 digits.