# US 12,008,549 B2 · Federated custodian

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

- Number: US 12,008,549 B2
- Document ID: US12008549B2
- Status: Granted
- Kind: B2
- Application number: 16/518,764
- Filed: 2019-07-22
- Published: 2021-01-28
- Granted: 2024-06-11
- Earliest claimed: 2019-07-22
- Assignees: Visa International Service Association
- Applicants: Visa International Service Association
- Inventors: Sivanarayana Gaddam; Atul Luykx; Cuy Sheffield
- Web page: https://patentgrep.com/patent/US12008549B2

## CPC

- G06Q 20/3674: {involving authentication}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/027: {involving a payment switch or gateway}
- G06Q 20/401: {Transaction verification}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/0897: {involving additional devices, e.g. trusted platform module [TPM], smartcard or USB}
- G06Q 2220/00: Business processing using cryptography
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- 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

An enhanced federated custodian system is described. One embodiment is directed to a computer system executing instructions to: receive, from one or more members of a federated blockchain on a network of computing devices, an approval for a transaction associated with an authentication capsule; generate, via a first trusted execution environment, a first machine readable code in response to receiving the approval for the transaction; transmit to a cold interaction system, the first machine readable code; and the cold interaction system comprising one or more processors and one or more memories, the one or more memories comprising instructions executable by the one or more processors to: receive the first machine readable code comprising the encrypted information and the approval; decrypt the encrypted information for the transaction and the approval; and generate a private key that corresponds to a public key for the transaction.

## Claims

### Claim 1

A computer system, comprising:
a gateway comprising a first processor, and a first memory including instructions that, when executed by the first processor causes the gateway to:
receive, from a plurality of members of a federated blockchain on a network of computing devices, approvals for a transaction associated with an authentication capsule, wherein each of the plurality of members receives the authentication capsule and approves of the transaction based upon data in the authentication capsule, the authentication capsule including one or more authentication policies, encrypted credentials, and device and application metadata, the device and application metadata identifying a currency amount associated with the transaction or a frequency of previous transactions associated with a member of the plurality of members conducting the transaction, the one or more authentication policies identifying at least the plurality of members required to authenticate the transaction for the approvals and conditions for approving the transaction via the plurality of members of the federated blockchain on the network of computing devices based at least in part on the device and application metadata, a number of the plurality of members required to authenticate the transaction determined based on device data of a device conducting the transaction and a geographic location of the transaction, the device data including an IP address of the device and application data of the device;
generate, via a first trusted execution environment implemented by the computer system, a first machine readable code in response to receiving the approvals for the transaction, the first machine readable code including encrypted information for the transaction and the approvals; and
transmit, to a cold interaction system, the first machine readable code generated in response to receiving approvals for the transaction; and the cold interaction system comprising one or more processors and one or more memories, the one or more memories comprising instructions executable by the one or more processors to:
receive the first machine readable code comprising the encrypted information and the approvals;
decrypt the encrypted information for the transaction and the approvals from the first machine readable code;
generate a first private key that corresponds to a public key for the transaction, the public key maintained by the plurality of members of the federated blockchain on the network of computing devices;
encrypt the transaction using the first private key; and
transmit, to the gateway, a second machine readable code, the second machine readable code verifying completion of the transaction.

### Claim 2 (depends on 1)

The computer system of claim 1, wherein the computer system is further configured to transmit to the plurality of members of the federated blockchain on the network of computing devices information verifying completion of the transaction.

### Claim 3 (depends on 2)

The computer system of claim 2, wherein the plurality of members of the federated blockchain on the network of computing devices maintain an audit log of transactions conducted by the plurality of members that is updated with the information verifying completion of the transaction.

### Claim 4 (depends on 1)

The computer system of claim 1, wherein the first machine readable code and the second machine readable code include an audio machine readable code that utilizes audible or inaudible sound frequencies.

### Claim 5 (depends on 4)

The computer system of claim 4, wherein the cold interaction system further comprises an offline server, and wherein the gateway and the offline server are configured to utilize speakers and microphones for capturing and transmitting audio corresponding to the audio machine readable code.

### Claim 6 (depends on 1)

The computer system of claim 1, wherein a member of the plurality of members signs the transaction as part of authenticating the transaction for approval.

### Claim 7 (depends on 1)

The computer system of claim 1 wherein a member of the plurality of members generates the public key for the transaction.

### Claim 8 (depends on 1)

The computer system of claim 1, wherein the gateway and the cold interaction system are physically separated and not in electrical communication with each other.

### Claim 9 (depends on 1)

The computer system of claim 1, wherein the device data further includes SIM card data of the device.

### Claim 10 (depends on 1)

The computer system of claim 1, wherein each hot wallet is utilized in an entity network domain of a respective associated entity.

### Claim 11 (depends on 1)

The computer system according to claim 1, wherein the first trusted execution environment comprises a hot wallet.

### Claim 12

A computer implemented method comprising:
receiving, by a computer system and from a plurality of members of a federated blockchain on a network of computing devices, approvals for a transaction associated with an authentication capsule, wherein each of the plurality of members receives the authentication capsule and approves of the transaction based upon data in the authentication capsule, the authentication capsule including one or more authentication policies, encrypted credentials, and device and application metadata, the device and application metadata identifying a currency amount associated with the transaction or a frequency of previous transactions associated with a member of the plurality of members conducting the transaction, the one or more authentication policies identifying at least the plurality of members required to authenticate the transaction for the approvals and conditions for approving the transaction via the plurality of members of the federated blockchain on the network of computing devices based at least in part on the device and application metadata, a number of the plurality of members required to authenticate the transaction determined based on device data of a device conducting the transaction and a geographic location of the transaction, the device data including an IP address of the device and application data of the device;
generating, via a first trusted execution environment implemented by the computer system, a first machine readable code in response to receiving the approvals for the transaction, the first machine readable code including encrypted information for the transaction and the approvals;
transmitting, to an offline server, the first machine readable code generated in response to receiving approvals for the transaction; by presenting the first machine readable code to the offline server; and
receiving, from the offline server, a second machine readable code generated by the offline server in a second trusted execution environment, the second machine readable code verifying completion of the transaction, wherein the offline server is configured for:
receiving the first machine readable code;
verifying proximity of the computer system to the offline server in response to receiving the first machine readable code;
decrypting, via the second trusted execution environment implemented by the offline server, the encrypted information for the transaction and the approvals from the first machine readable code in response to verifying proximity of the computer system;
requesting, via an associated hardware security module, for generation of a private key that corresponds to a public key for the transaction, the public key maintained by the plurality of members of the federated blockchain on the network of computing devices;
encrypting, via the second trusted execution environment, the transaction using the private key from the hardware security module; and
transmitting, to the computer system, the second machine readable code.

### Claim 13 (depends on 12)

The computer-implemented method of claim 12, further comprising transmitting to the plurality of members of the federated blockchain on the network of computing devices information verifying completion of the transaction.

### Claim 14 (depends on 13)

The computer-implemented method of claim 13, wherein the plurality of members of the federated blockchain of computing devices are configured to maintain an audit log of transactions conducted by the plurality of members that is updated with the information verifying completion of the transaction.

### Claim 15

A computer-implemented method comprising:
generating, by a computer system, a first audio machine readable code in response to receiving approvals for a transaction from a plurality of members of a federated blockchain on a network of computing devices, the first audio machine readable code including encrypted information for the transaction and the approval, the approvals associated with an authentication capsule, the authentication capsule including one or more authentication policies, encrypted credentials, and device and application metadata, the device and application metadata identifying a currency amount associated with the transaction or a frequency of previous transactions associated with a member of the plurality of members conducting the transaction, the one or more authentication policies identifying the plurality of members required to authenticate the transaction for the approvals and conditions for approving the transaction via the plurality of members of the federated blockchain on the network of computing devices based at least in part on the device and application metadata, a number of the plurality of members determined based on device data of a device conducting the transaction and a geographic location of the transaction, the device data including an IP address of the device and application data of the device, wherein each of the plurality of members receives the authentication capsule and approves of the transaction based upon data in the authentication capsule; and
transmitting, to an offline server, the first audio machine readable code generated in response to receiving approvals for the transaction by presenting the first audio machine readable code to the offline server, wherein the offline server is configured for:
receiving the first audio machine readable code;
verifying proximity of the computer system to the offline server in response to receiving the first audio machine readable code;
decrypting, via a trusted execution environment implemented by the offline server, the encrypted information for the transaction and the approvals from the first audio machine readable code in response to verifying proximity of the computer system;
requesting, via an associated hardware security module, for generation of a private key that corresponds to a public key for the transaction, the public key maintained by the plurality of members of the federated blockchain on the network of computing devices;
encrypting, via the trusted execution environment, the approvals of the transaction using the private key from the hardware security module;
generating a second audio machine readable code that includes the approvals of the transaction; and
transmitting, to the computer system, the second audio machine readable code.