CONTEXTUAL TRANSACTION TOKEN METHODS AND SYSTEMS

• US 20150112870A1
• Filed: 10/20/2014
• Published: 04/23/2015
• Est. Priority Date: 10/18/2013
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Nagasundaram, Sekhar, Gaddam, Ajit, Aissi, Selim
• Granted Patent: US 10,515,358 B2
• Time in Patent Office: Days
• US Class Current: 705/67
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 9/3213 using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807

Abstract

Embodiments of the present invention are directed to methods, systems, apparatuses, and computer-readable mediums for generating and providing a transaction token that may provide contextual information associated with the token. Accordingly, the transaction token may provide any entities within a transaction processing system immediate information about the context in which the token was generated, how the token may be used, and any other information that may be pertinent to processing the token.

Claims

1. A method comprising:

receiving, by a server computer, a request for a transaction token from a requestor;

determining, by the server computer, a consumer account and contextual information associated with the request for the transaction token;

determining, by the server computer, a substitute identifier for the consumer account;

generating, by the server computer, the transaction token associated with the request, wherein the transaction token includes the determined contextual information and the substitute identifier;

storing, by the server computer, the transaction token in a transaction token database; and

sending, by the server computer, the transaction token to the requestor.

2. The method of claim 1, wherein the determined contextual information includes transaction entity information and transaction parameter information.

3. The method of claim 2, wherein the transaction entity information includes at least one of a token issuer identifier, an account issuer identifier, a token requestor identifier, and a token verifier identifier.

4. The method of claim 2, wherein the transaction parameter information includes at least one of a token type identifier, a channel identifier, channel properties, expiration information, and transaction restriction information.

5. The method of claim 1, wherein the transaction token is configured to be processed in a transaction initiated by an access device of a merchant.

6. The method of claim 5, wherein the merchant receives the transaction token and generates a derived token based on the contextual information of the transaction token.

7. The method of claim 6, wherein the derived token is generated by updating the determined contextual information of the transaction token with merchant-specific information.

8. The method of claim 5, wherein the merchant interprets the contextual information included in the payment token, verifies the transaction token is valid for the transaction based on the interpreted contextual information, and sends the transaction information including the transaction token to a payment processing network for processing.

9. The method of claim 1, wherein the transaction token comprises a format identifier and wherein the format identifier is associated with a predefined token legend for interpreting the contextual information included in the transaction token.

10. The method of claim 1, further comprising:

receiving, by the server computer, a token verification request including the transaction token from a token subscriber computer;

interpreting, by the server computer, the contextual information included in the transaction token;

verifying, by the server computer, the transaction token is valid based on the interpreted contextual information; and

sending, by the server computer, a token verification response message including a status of the payment token to the token subscriber computer.

11. The method of claim 1, wherein the token subscriber computer includes one of a merchant computer, an acquirer computer, a payment processing network computer, an issuer computer, or a fraud analysis computer.

12. A computer comprising:

a processor; and

a computer-readable medium coupled to the processor, the computer-readable medium comprising code, executable by the processor, for performing a method, the method comprising;

receiving a request for a transaction token from a requestor;

determining a consumer account associated with the requestor and contextual information associated with the request for the payment token;

generating the payment token, wherein the transaction token includes the determined contextual information and a token payload;

storing the token payload and the determined contextual information in a token database, the token payload being associated with the consumer account; and

sending the payment token to the requestor.

13. The computer of claim 12, wherein the determined contextual information includes contextual data fields, the contextual data fields including transaction entity information and transaction parameter information.

14. The computer of claim 13, wherein the transaction entity information includes at least one of a token issuer identifier, an account issuer identifier, and a token verifier identifier.

15. The computer of claim 13, wherein the transaction parameter information includes at least one of a token type identifier, a channel identifier, channel properties, expiration information, and transaction restriction information.

16. The computer of claim 12, wherein the payment token is configured to be processed in a transaction initiated by an access device at a merchant.

17. The computer of claim 16, wherein the merchant receives the payment token, and wherein the merchant generates a derived token based on the contextual data fields of the transaction token.

18. The computer of claim 17, wherein the derived token is generated by updating the determined contextual information of the transaction token with merchant-specific information.

19. The computer of claim 12, wherein the payment token comprises a format identifier associated with a token legend for determining a format of the contextual information included in the transaction token.

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

receiving a token verification request including the transaction token from a token subscriber computer;

interpreting the contextual information included in the payment token;

verifying the payment token is valid based on the interpreted contextual information; and

sending a token verification response message including a status of the payment token to the token subscriber computer.