SYSTEMS AND METHODS FOR INTEROPERABLE NETWORK TOKEN PROCESSING

• US 20150032626A1
• Filed: 07/24/2014
• Published: 01/29/2015
• Est. Priority Date: 07/24/2013
• Status: Abandoned Application

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Prasanna Laxminarayanan
• Inventors: Dill, Matthew, Laxminarayanan, Prasanna, Powell, Glenn, Sheets, John, Carpenter, Andrew
• Application Number:
  US14/340,444
• Publication Number:
  US 20150032626A1
• 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. A method comprising:

receiving, by a server computer, an authorization request message comprising a payment token, wherein the payment token comprises a payment token issuer identifier, wherein the payment token issuer identifier is a substitute for a real issuer identifier for an issuer and is static for the issuer;

determining, by the server computer, a real account identifier associated with the payment token;

generating, by the server computer, a modified authorization request message comprising the real account identifier; and

transmitting, by the server computer, the modified authorization request message to the issuer for approval.

2. The method of claim 1, wherein the authorization request message is received by the server computer from a merchant computer.

3. The method of claim 1, wherein determining the real account identifier comprises searching a database for the real account identifier using the payment token.

4. The method of claim 1, further comprising:

receiving, by the server computer, an authorization response message from the issuer;

generating, by the server computer, a modified authorization response message comprising the payment token; and

transmitting the modified authorization response message to a merchant computer.

5. The method of claim 1, wherein the authorization request message further comprises a token requestor identifier and wherein the method further comprises:

validating, by the server computer, that the token requestor identifier is associated with the payment token.

6. The method of claim 1, wherein the authorization request message further comprises a token presentment mode and wherein the method further comprises:

validating, by the server computer, that the payment token is associated with the token presentment mode.

7. The method of claim 1, wherein the modified authorization request message further comprises a token assurance level code and wherein the issuer uses the token assurance level code to determine whether to authorize the transaction.

8. The method of claim 1, wherein before receiving the authorization request message, the payment token is generated and provided to the server computer by an account issuer.

9. The method of claim 7, wherein the token assurance level code indicates a level of confidence that the payment token was requested by an account holder of the underlying payment account associated with the real account identifier.

10. The method of claim 1, further comprising:

updating a routing table file to include a plurality of payment token issuer identifiers, wherein each of the payment token issuer identifiers is associated with a plurality of real issuer identifiers for a plurality of issuers, wherein the routing table file identifies a server computer for processing each of the plurality of payment token issuer identifiers; and

sending the routing table file to at least one of a merchant computer, an acquirer computer, and a payment service provider computer.

11. A server computer comprising a processor and a computer readable medium comprising code, executable by the processor, for implementing a method comprising:

receiving an authorization request message comprising a payment token, wherein the payment token comprises a payment token issuer identifier, wherein the payment token issuer identifier is a substitute for a real issuer identifier for an issuer and is static for the issuer;

determining a real account identifier associated with the payment token;

generating a modified authorization request message comprising the real account identifier; and

transmitting the modified authorization request message to the issuer for approval.

12. The server computer of claim 11, wherein the authorization request message is received by the server computer from a merchant computer.

13. The server computer of claim 11, wherein determining the real account identifier comprises searching a database for the real account identifier using the payment token.

14. The server computer of claim 11, the method further comprising:

receiving an authorization response message from the issuer;

generating a modified authorization response message comprising the payment token; and

transmitting the modified authorization response message to a merchant computer.

15. The server computer of claim 11, wherein the authorization request message further comprises a token requestor identifier and wherein the method further comprises:

validating that the token requestor identifier is associated with the payment token.

16. The server computer of claim 11, wherein the authorization request message further comprises a token presentment mode and wherein the method further comprises:

validating, by the server computer, that the payment token is associated with the token presentment mode.

17. The server computer of claim 11, wherein the modified authorization request message further comprises a token assurance level code and wherein the issuer uses the token assurance level code to determine whether to authorize the transaction.

18. The server computer of claim 11, wherein before receiving the authorization request message, the payment token is generated and provided to the server computer by an account issuer.

19. The server computer of claim 17, wherein the token assurance level code indicates a level of confidence that the payment token was requested by an account holder of the underlying payment account associated with the real account identifier.

20. The server computer of claim 11, wherein the method further comprises:

updating a routing table file to include a plurality of payment token issuer identifiers, wherein each of the payment token issuer identifiers is associated with a plurality of real issuer identifiers for a plurality of issuers, wherein the routing table file identifies a server computer for processing each of the plurality of payment token issuer identifiers; and

sending the routing table file to at least one of a merchant computer, an acquirer computer, and a payment service provider computer.

21-40. -40. (canceled)