# US 2023/0267455 A1 · Multi-network tokenization processing

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0267455 A1
- Document ID: US20230267455A1
- Status: Published application
- Kind: A1
- Application number: 18/310,374
- Filed: 2023-05-01
- Published: 2023-08-24
- Earliest claimed: 2013-08-08
- Assignees: Visa International Service Association
- Applicants: Visa International Service Association
- Inventors: Prasanna L. Narayan; Glenn Powell; John Sheets; Paul Tait; Andrew Carpenter
- Web page: https://patentgrep.com/patent/US20230267455A1

## CPC

- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/20: Point-of-sale [POS] network systems
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## 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

### Claim 1

A token requestor computer comprising:
a processor; and
a non-transitory computer-readable storage medium comprising code executable by the processor for implementing a method comprising:
receiving a token and transaction data for a transaction associated with an account;
generating an authorization request message for the transaction including the token and the transaction data;
transmitting the authorization request message to a first payment network server computer associated with a first payment network, thereby causing the first payment network server computer to:
identify 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,
send 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,
receive a token verification response message including the primary account identifier and a validation result, and
send a modified authorization request message including the primary account identifier, the validation result, and the transaction data to an issuer of the account; and
receiving an authorization response message including an authorization decision for the transaction, wherein the authorization decision is based on the modified authorization request message.

### Claim 2 (depends on 1)

The token requestor computer of claim 1, wherein the authorization request message 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.

### Claim 3 (depends on 1)

The token requestor computer of claim 1, wherein the authorization request message further includes an encrypted PIN block comprising a PIN associated with the account, and wherein the first payment network server computer further:
determines an issuer PIN key using the primary account identifier; and
validates the PIN using the determined issuer PIN key.

### Claim 4 (depends on 1)

The token requestor computer of claim 1, wherein the authorization request message 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 first payment network server computer further:
translates the PIN block to be based on the primary account identifier; and
sends the converted PIN block to the issuer, wherein the issuer validates the PIN.

### Claim 5 (depends on 1)

The token requestor computer of claim 1, wherein the authorization request message 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.

### Claim 6 (depends on 1)

The token requestor computer of claim 1, wherein the authorization request message 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 the token presentment mode.

### Claim 7 (depends on 1)

The token requestor computer of claim 1, wherein the authorization request message 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.

### Claim 8 (depends on 1)

The token requestor 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.

### Claim 9 (depends on 1)

The token requestor computer of claim 1, the method further comprising:
determining the first payment network, of a plurality of payment processing networks, to use for the transaction.

### Claim 10 (depends on 1)

The token requestor computer of claim 1, wherein the authorization response message further comprises 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.

### Claim 11 (depends on 1)

The token requestor computer of claim 1, wherein the token requestor computer is a merchant computer.

### Claim 12

A computer-implemented method comprising:
receiving, by a token requestor computer, a token and transaction data for a transaction associated with an account;
generating, by the token requestor computer, an authorization request message for the transaction including the token and the transaction data;
transmitting, by the token requestor computer, the authorization request message to a first payment network server computer associated with a first payment network, thereby causing the first payment network server computer to:
identify 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,
send 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, and
send a modified authorization request message including the primary account identifier, a validation result, and the transaction data to an issuer of the account; and
receiving, by the token requestor computer, an authorization response message including an authorization decision for the transaction, wherein the authorization decision is based on the modified authorization request message.

### Claim 13 (depends on 12)

The method of claim 12, wherein the authorization request message 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.

### Claim 14 (depends on 12)

The method of claim 12, wherein the authorization request message further includes an encrypted PIN block comprising a PIN associated with the account, and wherein the first payment network server computer further:
validates the PIN using a determined issuer PIN key.

### Claim 15 (depends on 12)

The method of claim 12, wherein the authorization request message 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 first payment network server computer further:
translates the PIN block to be based on the primary account identifier; and
sends the converted PIN block to the issuer, wherein the issuer validates the PIN.

### Claim 16 (depends on 12)

The method of claim 12, wherein the authorization request message 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.

### Claim 17 (depends on 12)

The method of claim 12, wherein the authorization request message 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 the token presentment mode.

### Claim 18 (depends on 12)

The method of claim 12, wherein the authorization request message 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 network token system of the second payment network validates the use of the token for the transaction using the token assurance level code.

### Claim 19 (depends on 12)

The method of claim 12, 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.

### Claim 20 (depends on 12)

The method of claim 12, further comprising:
determining, by the token requestor computer, the first payment network, of a plurality of payment processing networks, to use for the transaction.