# US 12,003,500 B2 · Token processing system and method

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

- Number: US 12,003,500 B2
- Document ID: US12003500B2
- Status: Granted
- Kind: B2
- Application number: 17/541,770
- Filed: 2021-12-03
- Published: 2023-06-08
- Granted: 2024-06-04
- Earliest claimed: 2021-12-03
- Assignees: Visa International Service Association
- Applicants: Visa International Service Association
- Inventors: Wilson Thampi; Tony Thomas Kollamparambil
- Web page: https://patentgrep.com/patent/US12003500B2

## CPC

- G06Q 20/405: {Establishing or using transaction specific rules}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- G06Q 20/0655: {e-cash managed centrally}
- G06Q 20/3223: {Realising banking transactions through M-devices}
- G06Q 20/3676: {Balancing accounts}
- G06Q 20/3829: {involving key management}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/4037: {Remote solvency checks}
- G06Q 20/40975: {using encryption therefor}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- 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
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method is disclosed and includes receiving, by a record server computer from a first processing network computer, a token, a device identifier associated with a user device, a session identifier associated with a registration request, and metadata about the token, and then receiving a metadata request from a second processing network computer in response to the second processing network computer receiving an authorization request message comprising the token, and the device identifier and/or the session identifier. The metadata request comprises at least the device identifier and/or the session identifier. The method also includes retrieving, by the record server computer, metadata associated with the metadata request, and providing the metadata to the second processing network computer. The second processing network computer processes the authorization request message using the token and the metadata.

## Claims

### Claim 1

A method comprising:
receiving, by a record server computer from a first processing network computer, a token, a device identifier associated with a user device, a session identifier associated with a registration request, and metadata about the token;
receiving, by the record server computer, a metadata request from a second processing network computer after the second processing network computer receives an authorization request message comprising the token, and the device identifier and/or the session identifier, the metadata request comprising at least the device identifier and/or the session identifier;
responsive to the metadata request, retrieving, by the record server computer, the metadata; and
providing, by the record server computer, the metadata to the second processing network computer, wherein the second processing network computer processes the authorization request message using the token and the metadata,
wherein the method further comprises:
receiving, by the first processing network computer, the registration request from the user device, the registration request comprising the device identifier;
determining, by the first processing network computer, the session identifier associated with the registration request; and
after receiving the registration request, providing, by the first processing network computer, the token to the user device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the metadata comprises transaction controls associated with the token.

### Claim 3 (depends on 1)

The method of claim 1, wherein the registration request comprises a public key, the user device storing a private key corresponding to the public key.

### Claim 4 (depends on 1)

The method of claim 1, wherein the session identifier is a random number.

### Claim 5 (depends on 4)

The method of claim 4, wherein the user device is a mobile phone.

### Claim 6 (depends on 1)

The method of claim 1, wherein the authorization request message is received from an access device.

### Claim 7 (depends on 1)

The method of claim 1, wherein the second processing network computer processes the authorization request message by using the metadata to validate the token and the user device that provided the token.

### Claim 8 (depends on 1)

The method of claim 1, wherein the metadata request was generated in response to the second processing network computer receiving the authorization request message comprising the token, and the device identifier and/or the session identifier.

### Claim 9 (depends on 8)

The method of claim 8, wherein an access device generated the authorization request message after the access device receives the token and the device identifier and/or the session identifier from the user device.

### Claim 10 (depends on 1)

The method of claim 1, wherein the authorization request message comprises the token, and the device identifier and the session identifier.

### Claim 11 (depends on 1)

The method of claim 1, wherein the record server computer comprises a plurality of data tables correlating a plurality of tokens and metadata for the tokens.

### Claim 12 (depends on 1)

The method of claim 1, wherein the record server computer manages a blockchain with data correlating a plurality of tokens and metadata for the tokens.

### Claim 13 (depends on 1)

The method of claim 1, wherein the record server computer communicates with the first processing network computer and the second processing network computer via APIs.

### Claim 14

A system comprising:
a record server computer comprising a processor, and a non-transitory computer readable medium comprising code, executable by the processor for performing operations comprising:
receiving, from a first processing network computer, a token, a device identifier associated with a user device, a session identifier associated with a registration request, and metadata about the token;
receiving a metadata request from a second processing network computer after the second processing network computer receives an authorization request message comprising the token, and the device identifier and/or the session identifier, the metadata request comprising at least the device identifier and/or the session identifier;
retrieving the metadata in response to the metadata request; and
providing the metadata to the second processing network computer, wherein the second processing network computer processes the authorization request message using the token and the metadata,
wherein the operations further comprise:
receiving, by the first processing network computer, the registration request from the user device, the registration request comprising the device identifier;
determining, by the first processing network computer, the session identifier associated with the registration request; and
after receiving the registration request, providing, by the first processing network computer, the token to the user device.

### Claim 15 (depends on 14)

The system of claim 14, further comprising:
the first processing network computer.