# US 2026/0065276 A1 · System and method for sharing know your customer (kyc) data using a blockchain

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

- Number: US 2026/0065276 A1
- Document ID: US20260065276A1
- Status: Published application
- Kind: A1
- Application number: 18/920,165
- Filed: 2024-10-18
- Published: 2026-03-05
- Earliest claimed: 2024-09-05
- Assignees: JPMorgan Chase Bank, N.A.
- Applicants: JPMorgan Chase Bank, N.A.
- Inventors: Sandeep KESWANI; Mitul MEHTA; Srinivasan KRISHNAN; Rohit RAJ; Ankur SAMBHAR; Suresh SHETTY
- Web page: https://patentgrep.com/patent/US20260065276A1

## CPC

- G06Q 20/383: {Anonymous user system}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/3829: {involving key management}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/40145: {Biometric identity checks}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 2220/00: Business processing using cryptography
- 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

A system and method for sharing know your customer (KYC) data using a blockchain are disclosed. The method includes receiving a first request from a user to access at least one service and obtaining user identity details. Next, the method includes registering at least one KYC data for the user. Next, the method includes storing the at least one KYC data into at least one database associated with the first institution. Next, the method includes loading the KYC data onto a distributed ledger through a smart contract, the KYC data is accessible with a private key associated with the KYC data. Next, the method includes receiving a second request to access the KYC data, from a second institution. Next, the method includes providing access to the KYC data to the second institution based on an execution of the smart contract using a successful verification of the private key.

## Claims

### Claim 1

A method for sharing a know your customer (KYC) data using a blockchain, the method being implemented by at least one processor, the method comprising:
receiving, by the at least one processor, a first request from a user to access at least one service of a first institution;
obtaining, by the at least one processor, user identity details from the user in response to the first request;
registering, by the at least one processor, at least one KYC data for the user upon a successful verification of the user identity details;
storing, by the at least one processor, the at least one KYC data into at least one database associated with the first institution;
loading, by the at least one processor, the at least one KYC data onto a distributed ledger through a smart contract, wherein the at least one KYC data is accessible with a private key associated with the at least one KYC data;
receiving, by the at least one processor, a second request to access the at least one KYC data of the user on the distributed ledger, from a second institution; and
providing, by the at least one processor, access to the at least one KYC data to the second institution based on an execution of the smart contract using a successful verification of the private key.

### Claim 2 (depends on 1)

The method as claimed in claim 1, wherein the user identity details comprise personal identity details, contact details, income details, and transaction details.

### Claim 3 (depends on 1)

The method as claimed in claim 1, wherein the at least one KYC data comprises verified documents corresponding to the user identity details.

### Claim 4 (depends on 1)

The method as claimed in claim 1, wherein the smart contract comprises at least one from among a block identifier, a transaction identifier, a chain identifier, a contract address and business logic parameters.

### Claim 5 (depends on 1)

The method as claimed in claim 1, wherein the smart contract is encrypted using encryption techniques to avoid an unauthorized access to the at least one KYC data.

### Claim 6 (depends on 1)

The method as claimed in claim 1, wherein upon a successful completion of a blockchain consensus process, the at least one KYC data is loaded onto the distributed ledger.

### Claim 7 (depends on 6)

The method as claimed in claim 6, wherein the successful completion of the blockchain consensus process further comprises:
validating, by the at least one processor, the smart contract by executing the blockchain consensus process involving a plurality of trusted parties associated with a blockchain network.

### Claim 8 (depends on 1)

The method as claimed in claim 1, wherein the method further comprises:
updating, by the at least one processor, the at least one KYC data upon receipt of a data updating request from the second institution.

### Claim 9

A computing device configured to implement an execution of a method for sharing a know your customer (KYC) data using a blockchain, the computing device comprising:
a processor;
a memory; and
a communication interface coupled to each of the processor and the memory, wherein the processor is configured to:
receive a first request from a user to access at least one service of a first institution;
obtain user identity details from the user in response to the first request;
register at least one KYC data for the user upon a successful verification of the user identity details;
store the at least one KYC data into at least one database associated with the first institution;
load the at least one KYC data onto a distributed ledger through a smart contract, wherein the at least one KYC data is accessible with a private key associated with the at least one KYC data;
receive a second request to access the at least one KYC data of the user on the distributed ledger, from a second institution; and
provide access to the at least one KYC data to the second institution based on an execution of the smart contract using a successful verification of the private key.

### Claim 10 (depends on 9)

The computing device as claimed in claim 9, wherein the user identity details comprise personal identity details, contact details, income details, and transaction details.

### Claim 11 (depends on 9)

The computing device as claimed in claim 9, wherein the at least one KYC data comprises verified documents corresponding to the user identity details.

### Claim 12 (depends on 9)

The computing device as claimed in claim 9, wherein the smart contract comprises at least one from among a block identifier, a transaction identifier, a chain identifier, a contract address and business logic parameters.

### Claim 13 (depends on 9)

The computing device as claimed in claim 9, wherein the smart contract is encrypted using encryption techniques to avoid an unauthorized access to the at least one KYC data.

### Claim 14 (depends on 9)

The computing device as claimed in claim 9, wherein upon a successful completion of a blockchain consensus process, the at least one KYC data is loaded onto the distributed ledger.

### Claim 15 (depends on 14)

The computing device as claimed in claim 14, wherein for the successful completion of the blockchain consensus process, the processor is further configured to:
validate the smart contract through execution of the blockchain consensus process involving a plurality of trusted parties associated with a blockchain network.

### Claim 16 (depends on 9)

The computing device as claimed in claim 9, wherein the processor is further configured to:
update the at least one KYC data upon reception of a data updating request from the second institution.

### Claim 17

A non-transitory computer readable storage medium storing instructions for sharing a know your customer (KYC) data using a blockchain, the storage medium comprising executable code which, when executed by a processor, causes the processor to:
receive a first request from a user to access at least one service of a first institution;
obtain user identity details from the user in response to the first request;
register at least one KYC data for the user upon a successful verification of the user identity details;
store the at least one KYC data into at least one database associated with the first institution;
load the at least one KYC data onto a distributed ledger through a smart contract, wherein the at least one KYC data is accessible with a private key associated with the at least one KYC data;
receive a second request to access the at least one KYC data of the user on the distributed ledger, from a second institution; and
provide access to the at least one KYC data to the second institution based on an execution of the smart contract using a successful verification of the private key.

### Claim 18 (depends on 17)

The storage medium as claimed in claim 17, wherein the smart contract is encrypted using encryption techniques to avoid an unauthorized access to the at least one KYC data.

### Claim 19 (depends on 17)

The storage medium as claimed in claim 17, wherein upon a successful completion of a blockchain consensus process, the at least one KYC data is loaded onto the distributed ledger.

### Claim 20 (depends on 19)

The storage medium as claimed in claim 19, wherein for the successful completion of the blockchain consensus process, when executed by the processor, the executable code further causes the processor to: validate the smart contract through execution of the blockchain consensus process involving a plurality of trusted parties associated with a blockchain network.
