SYSTEMS AND METHODS FOR COMMUNICATING TOKEN ATTRIBUTES ASSOCIATED WITH A TOKEN VAULT

• US 20150032627A1
• Filed: 07/24/2014
• Published: 01/29/2015
• Est. Priority Date: 07/24/2013
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Prasanna Laxminarayanan
• Inventors: Laxminarayanan, Prasanna, Powell, Glenn, Sheets, John, Carpenter, Andrew, Dill, Matthew
• Granted Patent: US 9,996,835 B2
• Time in Patent Office: Days
• US Class Current: 705/44
• 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/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: H04L 2209/42 Anonymization, e.g. involving pseudonyms
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 9/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Abstract

Systems and methods for interoperable network token processing are provided. A network token system provides a platform that can be leveraged by external entities (e.g., third party wallets, e-commerce merchants, payment enablers/payment service providers, etc.) or internal payment processing network systems that have the need to use the tokens to facilitate payment transactions. A token registry vault can provide interfaces for various token requestors (e.g., mobile device, issuers, merchants, mobile wallet providers, etc.), merchants, acquirers, issuers, and payment processing network systems to request generation, use and management of tokens. The network token system further provides services such as card registration, token generation, token issuance, token authentication and activation, token exchange, and token life-cycle management.

Claims

1-20. -20. (canceled)

21. A server computer for use in a payment processing system, the payment processing system comprising at least two entities operating at least two entity computers, where the at least two entities are capable of processing different parts of a single payment transaction, the server computer comprising:

a) a processor;

b) a computer readable medium comprising code, executable by the processor for implementing a method comprising;

receiving a first token request message from a first entity;

analyzing the first token request message;

determining that the first token request message includes a request for a token;

determining a first token;

transmitting the first token to the first entity;

receiving a second token request message from a second entity;

analyzing the second token request message;

determining that the second token request message includes a token request associated with the first token;

determining token attributes associated with the first token; and

transmitting the determined token attributes to the second entity.

22. The server computer of claim 21, wherein the first entity and the second entity are different, and wherein the first entity and the second entity are selected from a group comprising:

a mobile device, a mobile wallet, a merchant, an acquirer, an issuer, and a payment processing network.

23. The server computer of claim 21, wherein the token request associated with the first token includes at least one of a token validation request, a token management request, a token inquiry request, and a token exchange request.

24. The server computer of claim 21, wherein the first token request message comprises an account identifier, authentication data, and a token requestor identifier and the first token response message comprises a token and a token assurance level code.

25. The server computer of claim 23, wherein the token request includes the token validation request, wherein the second entity is a merchant, wherein the token validation request includes transaction data and the first token, and wherein determining the token attributes further comprises searching a token database for transaction restrictions associated with the first token, wherein the token attributes include the transaction restrictions.

26. The server computer of claim 23, wherein the second entity is a mobile device or a mobile wallet provider, wherein the token request includes the token exchange request, the token exchange request including the first token and a token requestor identifier, and wherein determining the token attributes further comprises searching a token database for an account identifier associated with the first token, validating the token requestor identifier is associated with the first token, and, wherein the token attributes include the transaction restrictions.

27. The server computer of claim 23, wherein the second entity is an issuer and wherein the token request includes the token management request, the token management request including the first token and including instructions to activate, de-activate, or update the first token, wherein the token attributes include a status of the first token.

28. The server computer of claim 27, wherein the token management request includes instructions to update the first token, wherein the instructions to update the first token includes an updated real account identifier associated with the first token, and wherein the server computer updates a token record to include the real updated account identifier associated with the first token.

29. The server computer of claim 23, wherein the token request includes the token inquiry request, wherein the token inquiry request includes an account identifier or the first token, and wherein determining the token attributes further comprises searching a token database for a token record associated with the received account identifier or the received first token, determining authorized information from the token record for the second entity, and wherein the token attributes include the authorized information from the token record.

30. A system comprising:

the server computer of claim 21; and

a database coupled to the server computer, the database comprising a plurality of payment tokens.

31. The system of claim 30, further comprising an issuer computer, an acquirer computer, and a merchant computer coupled to the server computer.

32. A method comprising:

receiving, by a server computer, a first token request message from a first entity;

analyzing, by the server computer, the first token request message;

determining, by the server computer, that the first token request message includes a request for a token;

determining, by the server computer, a first token;

transmitting, by the server computer, the first token to the first entity;

receiving, by the server computer, a second token request message from a second entity;

analyzing, by the server computer, the second token request message;

determining, by the server computer, that the second token request message includes a token request associated with the first token;

determining, by the server computer, token attributes associated with the first token; and

transmitting, by the server computer, the determined token attributes to the second entity.

33. The method claim 32, wherein the first entity and the second entity are different, and wherein the first entity and the second entity are selected from a group comprising:

a mobile device, a mobile wallet, a merchant, an acquirer, an issuer, and a payment processing network.

34. The method of claim 32, wherein the token request associated with the first token includes at least one of a token validation request, a token inquiry request, a token exchange request, and a token management request.

35. The method of claim 32, wherein the first token request message comprises an account identifier, authentication data, and a token requestor identifier and the first token response message comprises a token and a token assurance level code.

36. The method of claim 34, wherein the token request includes the token validation request, wherein the second entity is a merchant, wherein the token validation request includes transaction data and the first token, and wherein determining the token attributes further comprises searching a token database for transaction restrictions associated with the first token, wherein the token attributes include the transaction restrictions.

37. The method of claim 34, wherein the second entity is a mobile device or a mobile wallet provider, wherein the token request includes the token exchange request, the token exchange request including the first token and a token requestor identifier, and wherein determining the token attributes further comprises searching a token database for an account identifier associated with the first token, validating the token requestor identifier is associated with the first token, and, wherein the token attributes include the transaction restrictions.

38. The method of claim 34, wherein the second entity is an issuer and wherein the token request includes the token management request, the token management request including the first token and including instructions to activate, de-activate, or update the first token, wherein the token attributes include a status of the first token.

39. The method of claim 38, wherein the token management request includes instructions to update the first token, wherein the instructions to update the first token includes an updated real account identifier associated with the first token, and wherein the server computer updates a token record to include the real updated account identifier associated with the first token.

40. The method of claim 34, wherein the token request includes the token inquiry request, wherein the token inquiry request includes an account identifier or the first token, and wherein determining the token attributes further comprises searching a token database for a token record associated with the received account identifier or the received first token, determining authorized information from the token record for the second entity, and wherein the token attributes include the authorized information from the token record.