# US 2017/0255932 A1 · Systems and methods for domain restriction with remote authentication

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

- Number: US 2017/0255932 A1
- Document ID: US20170255932A1
- Status: Published application
- Kind: A1
- Application number: 15/060,212
- Filed: 2016-03-03
- Published: 2017-09-07
- Earliest claimed: 2016-03-03
- Assignees: Visa International Service Association
- Inventors: Christian Aabye; Christopher Jones
- Web page: https://patentgrep.com/patent/US20170255932A1

## CPC

- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 20/385: {using an alias or single-use 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
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)}
- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04W 12/12: Detection or prevention of fraud
- G06Q 2220/00: Business processing using cryptography
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- 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)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A process for combining domain restriction and remote authentication may include receiving a token from a plug-in application to conduct a transaction associated with a user of a communicating device. The process may include sending an authentication request to a remote access control sever to authenticate the user, and receiving, from the remote access control server, an authentication tracking value that the remote access control server used in generation of an authentication cryptogram. The process may also include generating, using the authentication tracking value, a domain restriction cryptogram that is used for domain restriction of the token, and sending, to the plug-in application, the domain restriction cryptogram.

## Claims

### Claim 1

A computing system comprising:
at least one processor and at least one memory coupled to the at least one processor, the at least one memory storing instructions, which when executed by the at least one processor cause the at least one processor to:
receive a token from a plug-in application to conduct a transaction associated with a user of a communicating device;
send, to a remote access control sever, an authentication request to authenticate the user;
receive, from the remote access control server, an authentication tracking value that the remote access control server used in generation of an authentication cryptogram;
generate, using the authentication tracking value, a domain restriction cryptogram that is used for domain restriction of the token; and
send, to the plug-in application, the domain restriction cryptogram, wherein the transaction is authorized by verifying both the authentication cryptogram and the domain restriction cryptogram.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein the domain restriction cryptogram is generated by encrypting a domain restriction data set including at least a token requestor identifier associated with the token and at least a portion of the authentication transaction value using a derived encryption key.

### Claim 3 (depends on 2)

The computing system of claim 2, wherein the derived encryption key is derived from the token.

### Claim 4 (depends on 2)

The computing system of claim 2, wherein the domain restriction data set further includes an application transaction counter.

### Claim 5 (depends on 4)

The computing system of claim 4, wherein the application transaction counter is incremented for each transaction conducted using the token.

### Claim 6 (depends on 5)

The computing system of claim 5, wherein the application transaction counter is incremented by the computing system.

### Claim 7 (depends on 5)

The computing system of claim 5, wherein the application transaction counter is incremented by the communication device.

### Claim 8 (depends on 1)

The computing system of claim 1, wherein the authentication cryptogram is generated by encrypting an authentication data set including an account identifier associated with the token and at least a portion of the authentication transaction value using an access control encryption key.

### Claim 9 (depends on 1)

The computing system of claim 1, wherein the authentication tracking value is generated by the remote access control server to identify the transaction.

### Claim 10 (depends on 1)

The computing system of claim 1, wherein the instructions, which when executed by the at least one processor further cause the at least one processor to:
determine an account identifier associated with the token; and
determine that the account identifier qualifies for remote authentication by the remote access control server.

### Claim 11

A method comprising:
receiving, by a computing system, a token from a plug-in application to conduct a transaction associated with a user of a communicating device;
sending, by the computing system to a remote access control sever, an authentication request to authenticate the user;
receiving, by the computing system from the remote access control server, an authentication tracking value that the remote access control server used in generation of an authentication cryptogram;
generating, by the computing system using the authentication tracking value, a domain restriction cryptogram that is used for domain restriction of the token; and
sending, by the computing system to the plug-in application, the domain restriction cryptogram, wherein the transaction is authorized by verifying both the authentication cryptogram and the domain restriction cryptogram.

### Claim 12 (depends on 11)

The method of claim 11, wherein the domain restriction cryptogram is generated by encrypting a domain restriction data set including at least a token requestor identifier associated with the token and at least a portion of the authentication transaction value using a derived encryption key.

### Claim 13 (depends on 12)

The method of claim 12, wherein the derived encryption key is derived from the token.

### Claim 14 (depends on 12)

The method of claim 12, wherein the domain restriction data set further includes an application transaction counter.

### Claim 15 (depends on 14)

The method of claim 14, wherein the application transaction counter is incremented for each transaction conducted using the token.

### Claim 16 (depends on 15)

The method of claim 15, wherein the application transaction counter is incremented by the computing system.

### Claim 17 (depends on 15)

The method of claim 15, wherein the application transaction counter is incremented by the communication device.

### Claim 18 (depends on 11)

The method of claim 11, wherein the authentication cryptogram is generated by encrypting an authentication data set including an account identifier associated with the token and at least a portion of the authentication transaction value using an access control encryption key.

### Claim 19 (depends on 11)

The method of claim 11, wherein the authentication tracking value is generated by the remote access control server to identify the transaction.

### Claim 20 (depends on 11)

The method of claim 11, further comprising:
determining an account identifier associated with the token; and
determining that the account identifier qualifies for remote authentication by the access control server.
