MULTI-NETWORK TOKENIZATION PROCESSING

• US 20150046338A1
• Filed: 08/08/2014
• Published: 02/12/2015
• Est. Priority Date: 08/08/2013
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: LAXMINARAYANAN, PRASANNA, Powell, Glenn, Sheets, John, Tait, Paul, Carpenter, Andrew
• Granted Patent: US 10,496,986 B2
• Time in Patent Office: Days
• US Class Current: 705/67
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights

Abstract

Systems, apparatuses, and methods are provided for enabling a transaction using a token associated with a first payment network to be conducted using a second payment network. When a transaction using a token is submitted to a payment network, the payment network can determine the payment network associated with the token. If the token is associated with a second payment network, a token verification request including the token can be sent to the second payment network. The second payment network can then return a token verification response including a primary account identifier such as a primary account number (PAN) corresponding to the token and a validation result. The transaction may then be processed using the primary account identifier.

Claims

1. A server computer associated with a first payment network comprising:

a processor; and

a non-transitory computer-readable storage medium comprising code executable by the processor for implementing a method comprising;

receiving an authorization request message for a transaction including a token and transaction data;

identifying a network token system associated with the token based on a predetermined issuer identifier of the token, the network token system being operated by a second payment network;

sending a token verification request message to the network token system of the second payment network, the token verification request message including the token and the transaction data, wherein the network token system of the second payment network determines a primary account identifier associated with the token and validates the use of the token for the transaction;

receiving a token verification response message including a primary account identifier and a validation result; and

sending a modified authorization request message including the primary account identifier, the validation result, and the transaction data to an issuer of the account.

2. The server computer of claim 1, wherein the authorization request message received by the server computer further includes restrictions associated with the token, and wherein the network token system of the second payment network validates the use of the token for the transaction using a determination of whether the restrictions associated with the token preclude the transaction.

3. The server computer of claim 1, wherein the authorization request message received by the server computer further includes an encrypted PIN block comprising a PIN associated with the account, and wherein the method further comprises:

determining an issuer PIN key using the primary account identifier; and

validating the PIN using the determined issuer PIN key.

4. The server computer of claim 1, wherein the authorization request message received by the server computer further includes an encrypted PIN block comprising a PIN associated with the account, wherein the PIN block is generated based on the token, and wherein the method further comprises:

translating the PIN block to be based on the primary account identifier; and

sending the converted PIN block to the issuer, wherein the issuer validates the PIN.

5. The server computer of claim 1, wherein the authorization request message received by the server computer further includes a token requestor identifier, wherein the network token system of the second payment network validates the use of the token for the transaction using token requestor identifier.

6. The server computer of claim 1, wherein the authorization request message received by the server computer further includes a token presentment mode, wherein the network token system of the second payment network validates the use of the token for the transaction using token presentment mode.

7. The server computer of claim 1, wherein the authorization request message received by the server computer further includes a token assurance level code, wherein the token assurance level code indicates a level of confidence that the token was requested by an authorized entity, and wherein the validation result is determined using the token assurance level code.

8. The server computer of claim 1, wherein the second payment network is determined using a routing table, wherein the routing table associates each of a plurality of token issuer identifiers with a payment processing network.

9. A system comprising:

the server computer of claim 1; and

the second payment network.

10. A computer-implemented method comprising:

receiving, by a server computer associated with a first payment network, an authorization request message for a transaction including a token and transaction data;

identifying, by the server computer, a network token system associated with the token based on a predetermined issuer identifier of the token, the network token system being operated by a second payment network;

sending, by the server computer, a token verification request message to the network token system of the second payment network, the token verification request message including the token and the transaction data, wherein the network token system of the second payment network determines a primary account identifier associated with the token and validates the use of the token for the transaction;

receiving, by the server computer, a token verification response message including a primary account identifier and a validation result; and

sending, by the server computer, a modified authorization request message including the primary account identifier, the validation result, and the transaction data to an issuer of the account.

11. The method of claim 10, wherein the authorization request message received by the server computer further includes restrictions associated with the token, and wherein validating the use of the token for the transaction comprises determining whether the restrictions associated with the token preclude the transaction.

12. The method of claim 10, wherein the authorization request message received by the server computer further includes an encrypted PIN block comprising a PIN associated with the account, and wherein the method further comprises:

determining, by the server computer, an issuer PIN key using the primary account identifier; and

validating, by the server computer, the PIN using the determined issuer PIN key.

13. The method of claim 10, wherein the authorization request message received by the server computer further includes an encrypted PIN block comprising a PIN associated with the account, wherein the PIN block is generated based on the token, and wherein the method further comprises:

translating, by the server computer, the PIN block to be based on the primary account identifier; and

sending, by the server computer, the converted PIN block to the issuer, wherein the issuer validates the PIN.

14. The method of claim 10, wherein the authorization request message received by the server computer further includes a token requestor identifier, wherein the network token system of the second payment network validates the use of the token for the transaction using token requestor identifier.

15. The method of claim 10, wherein the authorization request message received by the server computer further includes a token presentment mode, wherein the network token system of the second payment network validates the use of the token for the transaction using token presentment mode.

16. The method of claim 10, wherein the authorization request message received by the server computer further includes a token assurance level code, wherein the token assurance level code indicates a level of confidence that the token was requested by an authorized entity, and wherein network token system of the second payment network validates the use of the token for the transaction using the token assurance level code.

17. The method of claim 10, wherein the issuer identifier comprises a predetermined number of digits of the token.

18. The method of claim 10, wherein the second payment network is determined using a routing table, wherein the routing table associates each of a plurality of token issuer identifiers with a payment processing network.

19. The method of claim 10, wherein prior to the transaction, the network token system operated by the second payment network receives the primary account identifier and generates the token.

20. A computer-implemented method comprising:

receiving, by a server computer associated with a second payment network, a token verification request message from a first payment network, the token verification request including a token and transaction data, wherein the second payment network is associated with a predetermined issuer identifier of the token;

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

validating, by the server computer, whether the use of the token for the transaction is authorized to determine a validation result; and

sending, by the server computer, a token verification response message including the primary account identifier and the validation result, wherein the primary account identifier, the validation result, and the transaction data are provided to an issuer of the account.