# US 2021/0176067 A1 · System and method for authorizing secondary users to access a primary user's account using blockchain

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

- Number: US 2021/0176067 A1
- Document ID: US20210176067A1
- Status: Published application
- Kind: A1
- Application number: 16/707,772
- Filed: 2019-12-09
- Published: 2021-06-10
- Earliest claimed: 2019-12-09
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Saira ZAMAN; Salim MEMON
- Web page: https://patentgrep.com/patent/US20210176067A1

## CPC

- H04L 9/3236: {using cryptographic hash functions}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- G06F 21/604: {Tools and structures for managing or administering access control systems}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06F 21/645: {using a third party}
- G06Q 20/2295: {Parent-child type, e.g. where parent has control on child rights}
- G06Q 20/3827: {Use of message hashing}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/405: {Establishing or using transaction specific rules}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L 63/102: {Entity profiles}
- H04L 63/105: {Multiple levels of security}
- H04L 63/126: {the source of the received data}
- G06F 2221/2137: Time limited access, e.g. to a computer or data
- G06Q 20/401: {Transaction verification}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2463/062: applying encryption of the keys
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- 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

Described herein is a system for authorizing secondary users to access a primary user's account using blockchain. The primary user can transmit a request for providing access to a primary user's account to a secondary user. In response to receiving the request, the system may generate a new block in the blockchain ledger specifying the permissions of the secondary user. Furthermore, the new block may include the permission details. This way, when the secondary user attempts to access the primary user's account, the system may verify the secondary user based on the permission details in the last block in the sequence of blocks. Each new block may include the permission details.

## Claims

### Claim 1

A computer-implemented method for enabling access for different users using blockchain, the method comprising:
storing a copy of a cryptographically verifiable ledger represented by a sequence of blocks corresponding to a primary user, each block of the sequence of blocks containing transaction records of the primary user and a hash value associated with a previous block in the sequence of blocks, wherein the transaction records of the primary user include a hash identifier of the primary user, the hash identifier of the primary user is generated by encrypting a unique identifier of the primary user;
receiving a first request from the primary user to provide, to a secondary user, a permission to access the transaction records of the primary user contained in the sequence of blocks;
encrypting a unique identifier of the secondary user to generate a hash identifier of the secondary user;
generating a new block in the sequence of blocks, the new block containing the permission provided to the secondary user and the hash identifier of the secondary user, wherein both the hash identifier of the primary user and the hash identifier of the secondary user are contained in each subsequent block in the sequence of blocks;
receiving a second request from the secondary user to access the transaction records of the primary user contained in the sequence of blocks in response to the generating of the new block, wherein the second request includes the unique identifier of the secondary user;
retrieving the hash identifier of the primary user and the hash identifier of the secondary user from a last block of the sequence of blocks in response to the receiving of the second request;
decrypting the hash identifier of the primary user and the hash identifier of the secondary user retrieved from the last block;
verifying the primary user by comparing the decrypted hash identifier of the primary user with the unique identifier of the primary user;
authenticating the secondary user by comparing the unique identifier of the secondary user included in the second request to the decrypted hash identifier of the secondary user;
providing, to the secondary user, access to the transaction records of the primary user contained in the sequence of blocks, in response to the verifying of the primary user being successful and the authenticating of the secondary user being successful; and
generating a new last block in the sequence of blocks removing the hash identifier of the secondary user in the new last block, in response to the permission provided to the secondary user being revoked.

### Claim 2 (depends on 1)

The method of claim 1, wherein a network of computing nodes stores the copy of the cryptographically verifiable ledger.

### Claim 3 (depends on 2)

The method of claim 2, wherein authenticating the secondary user further comprises broadcasting to the network of computing nodes an attempt to authenticate the secondary user to verify that the last block including the hash identifier of the secondary user being used to authenticate the secondary user is in fact the unique identifier of the secondary user.

### Claim 4 (depends on 1)

The method of claim 1, wherein the first request includes a time frame in which the secondary user may access the transaction records of the primary user contained in the sequence of blocks.

### Claim 5 (depends on 4)

The method of claim 4, wherein a block in the sequence of blocks created after the time frame includes a hash value without authentication information associated with the secondary user.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
receiving a third request from the secondary user to access the transaction records of the primary user contained in the sequence of blocks after the time frame;
failing to retrieve the hash identifier of the secondary user from the new last block in the sequence of blocks; and
blocking an attempt of the secondary user to access the transaction records of the primary user contained in the sequence of blocks in response to failing to authenticate the secondary user.

### Claim 7 (depends on 6)

The method of claim 6, further comprising generating a second new block in the sequence of blocks containing information about an unauthorized access attempt by the secondary user and the hash identifier of the secondary user.

### Claim 8 (depends on 1)

The method of claim 1, wherein the permission includes: read only access or read and write access.

### Claim 9

A system for enabling access for different users using blockchain, the system comprising:
a memory;
a processor in communication with the memory, configured to:
store a copy of a cryptographically verifiable ledger represented by a sequence of blocks corresponding to a primary user, each block of the sequence of blocks containing transaction records of the primary user and a hash value associated with a previous block in the sequence of blocks, wherein the transaction records of the primary user include a hash identifier of the primary user, the hash identifier of the primary user is generated by encrypting a unique identifier of the primary user;
receive a first request from the primary user to provide, to a secondary user, a permission to access the transaction records of the primary user contained in the sequence of blocks;
encrypt a unique identifier of the secondary user to generate a hash identifier of the secondary user;
generate a new block in the sequence of blocks, the new block containing the permission provided to the secondary user and the hash identifier of the secondary user, wherein both the hash identifier of the primary user and the hash identifier of the secondary user are contained in each subsequent block in the sequence of blocks;
receive a second request from the secondary user to access the transaction records of the primary user contained in the sequence of blocks in response to the generation of the new block, wherein the second request includes the unique identifier of the secondary user;
retrieve the hash identifier of the primary user and the hash identifier of the secondary user from a last block of the sequence of blocks in response to the receipt of the second request;
decrypt the hash identifier of the primary user and the hash identifier of the secondary user retrieved from the last block;
verify the primary user by comparing the decrypted hash identifier of the primary user with the unique identifier of the primary user;
authenticate the secondary user by comparing the unique identifier of the secondary user included in the second request to the decrypted hash identifier of the secondary user;
provide, to the secondary user, access to the transaction records of the primary user contained in the sequence of blocks, in response to the verification of the primary user being successful and the authentication of the secondary user being successful; and
generate a new last block in the sequence of blocks removing the hash identifier of the secondary user in the new last block, in response to the permission provided to the secondary user being revoked.

### Claim 10 (depends on 9)

The system of claim 9, wherein a network of computing nodes stores the copy of the cryptographically verifiable ledger.

### Claim 11 (depends on 10)

The system of claim 10, wherein the processor is further configured to broadcast to the network of computing nodes an attempt to authenticate the secondary user to verify that the last block including the hash identifier of the secondary user being used to authenticate the secondary user is in fact the unique identifier of the secondary user.

### Claim 12 (depends on 9)

The system of claim 9, wherein the first request includes a time frame in which the secondary user may access the transaction records of the primary user contained in the sequence of blocks.

### Claim 13 (depends on 12)

The system of claim 12, wherein a block in the sequence of blocks created after the time frame includes a hash value without authentication information associated with the secondary user.

### Claim 14 (depends on 13)

The system of claim 13, wherein the processor is further configured to:
receive a third request from the secondary user to access the transaction records of the primary user contained in the sequence of blocks after the time frame;
fail to retrieve the hash identifier from the new last block in the sequence of blocks; and
block an attempt of the secondary user to access the transaction records of the primary user contained in the sequence of blocks in response to failing to authenticate the secondary user.

### Claim 15 (depends on 14)

The system of claim 14, wherein the processor is further configured to generate a second new block in the sequence of blocks containing information about an unauthorized access attempt by the secondary user and the hash identifier of the secondary user.

### Claim 16 (depends on 9)

The system of claim 9, wherein the permission includes: read only access or read and write access.

### Claim 17

A non-transitory computer-readable medium storing instructions that when executed by one or more processors of a device cause the one or more processors to:
store a copy of a cryptographically verifiable ledger represented by a sequence of blocks corresponding to a primary user, each block of the sequence of blocks containing transaction records of the primary user and a hash value associated with a previous block in the sequence of blocks, wherein the transaction records of the primary user include a hash identifier of the primary user, the hash identifier of the primary user is generated by encrypting a unique identifier of the primary user;
receive a first request from the primary user to provide, to a secondary user, a permission to access the transaction records of the primary user contained in the sequence of blocks;
encrypt a unique identifier of the secondary user to generate a hash identifier of the secondary user;
generate a new block in the sequence of blocks, the new block containing the permission provided to the secondary user and the hash identifier of the secondary user, wherein both the hash identifier of the primary user and the hash identifier of the secondary user are contained in each subsequent block in the sequence of blocks;
receive a second request from the secondary user to access the transaction records of the primary user contained in the sequence of blocks in response to the generation of the new block, wherein the second request includes the unique identifier of the secondary user;
retrieve the hash identifier of the primary user and the hash identifier of the secondary user from a last block of the sequence of blocks in response to the receipt of the second request;
decrypt the hash identifier of the primary user and the hash identifier of the secondary user retrieved from the last block;
verify the primary user by comparing the decrypted hash identifier of the primary user with the unique identifier of the primary user;
authenticate the secondary user by comparing the unique identifier of the secondary user included in the second request to the decrypted hash identifier of the secondary user;
provide, to the secondary user, access to the transaction records of the primary user contained in the sequence of blocks, in response to the verification of the primary user being successful and the authentication of the secondary user being successful; and
generate a new last block in the sequence of blocks removing the hash identifier of the secondary user in the new last block, in response to the permission provided to the secondary user being revoked.

### Claim 18 (depends on 17)

The medium of claim 17, wherein a network of computing nodes stores the copy of the cryptographically verifiable ledger.

### Claim 19 (depends on 18)

The medium of claim 18, wherein the instructions when executed cause the one or more processors to broadcast to the network of computing nodes an attempt to authenticate the secondary user to verify that the last block including the hash identifier of the secondary user being used to authenticate the secondary user is in fact the unique identifier of the secondary user.

### Claim 20 (depends on 19)

The medium of claim 19, wherein the instructions when executed cause the one or more processors to:
receive a third request from the secondary user to access the transaction records of the primary user contained in the sequence of blocks after a specified time frame included in the permission;
fail to retrieve the hash identifier from the new last block in the sequence of blocks; and
block an attempt of the secondary user to access the transaction records of the primary user contained in the sequence of blocks in response to failing to authenticate the secondary user.
