# US 2021/0241269 A1 · System and method for effecting a secure event

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

- Number: US 2021/0241269 A1
- Document ID: US20210241269A1
- Status: Published application
- Kind: A1
- Application number: 16/782,625
- Filed: 2020-02-05
- Published: 2021-08-05
- Earliest claimed: 2020-02-05
- Assignees: The Toronto-Dominion Bank
- Applicants: The Toronto-Dominion Bank
- Inventors: MILOS DUNJIC; Yubing LIU; Anthony Haituyen NGUYEN; Daniel David GRINBERG
- Web page: https://patentgrep.com/patent/US20210241269A1

## CPC

- G06Q 20/3829: {involving key management}
- G06K 19/06037: {multi-dimensional coding}
- G06Q 10/0838: {Historical data}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/108: {Remote banking, e.g. home banking}
- G06Q 20/22: Payment schemes or models
- G06Q 20/322: {Aspects of commerce using mobile devices [M-devices]}
- G06Q 20/3224: {Transactions dependent on location of M-devices}
- G06Q 20/3274: {using a pictured code, e.g. barcode or QR-code, being displayed on the M-device}
- G06Q 20/381: {Currency conversion}
- G06Q 20/3823: {combining multiple encryption tools for a transaction}
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/4015: {using location information}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 30/018: Certifying business or products
- H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]}
- H04L 9/085: {Secret sharing or secret splitting, e.g. threshold schemes}
- H04L 9/321: {involving a third party or a trusted authority}
- 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/3271: {using challenge-response}
- G06Q 2220/00: Business processing using cryptography
- 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
- G06K: GRAPHICAL DATA READING (image or video recognition or understanding G06V); PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for effecting secure transactions are described. A processing device, when executing computer-executable instructions: receives from a requesting entity computing system a transaction request for a payload. The transaction request is transmitted to delivery entity computing system associated with a delivery entity identifier and geographic location. An encryption key, random number and a unique request identifier are generated and transmitted to requesting and delivery entity computing systems. In response to receiving a delivery transaction confirmation from the delivery entity computing system, the processing device verifies the secure transaction. After receiving a requestor transaction confirmation from the requesting entity computing system (indicating a verified transfer of the payload), a payload reimbursement is transferred to a delivery transaction account from a requestor transaction account.

## Claims

### Claim 1

A computing system for effecting a secure transaction, the computing system comprising:
a memory storing computer-executable instructions, and
a processing device coupled to the memory, the computer-executable instructions when executed by the processing device causing the processing device to:
receive, over a network, a transaction request to receive at least one payload from a requesting entity computing system associated with a requestor entity, the transaction request comprising:
a requesting entity identifier, a requestor geographic location identifier, at least one transaction payload attribute and at least one transaction attribute;
transmit, over the network, the transaction request to a delivery entity computing system associated with a delivery entity, a delivery entity identifier and a delivery entity geographic location;
generate an encryption key, a random number and a unique request identifier;
receive, over the network, a delivery transaction confirmation from the delivery entity computing system;
in response to receiving the delivery transaction confirmation, verify the secure transaction;
receive, over the network, a requestor transaction confirmation from the requesting entity computing system, the requestor transaction confirmation indicating a verified transfer of the at least one payload from the delivery entity to the requestor entity; and
after receipt of the requestor transaction confirmation, transfer a payload reimbursement from a requestor transaction account associated with the requestor entity to a delivery transaction account associated with the delivery entity.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein the computer-executable instructions when executed by the processing device further cause the processing device to:
split the encryption key into a requestor entity key portion and a delivery entity key portion;
split the random number into a requestor entity number portion and a delivery entity number portion;
generate a requestor matrix code, the requestor matrix code comprising the requestor entity number portion, the unique request identifier, the requesting entity identifier and the requestor entity key portion;
generate a delivery matrix code, the delivery matrix code comprising the delivery entity number portion, the unique request identifier, the delivery entity identifier and the delivery entity key portion; and
transmit, over the network, the requestor matrix code to the requesting entity computing system and the delivery matrix code to the delivery entity computing system.

### Claim 3 (depends on 1)

The computing system of claim 1, wherein the at least one transaction attribute comprises one or more of a delivery time, a delivery date, receipt instructions and a preferred payment method for the payload reimbursement.

### Claim 4 (depends on 1)

The computing system of claim 1, wherein the computer-executable instructions when executed by the processing device further cause the processing device to:
prior to the receipt of the delivery transaction confirmation,
transfer a reimbursement amount from the requestor transaction account to a requestor escrow account, and
transmit an escrow confirmation to the delivery entity computing system;
wherein the transfer of the payload reimbursement comprises transferring the payload reimbursement from the requestor escrow account to the delivery transaction account.

### Claim 5 (depends on 1)

The computing system of claim 1, wherein the at least one transaction payload attribute comprises one or more of a payload type and a payload monetary valuation.

### Claim 6 (depends on 1)

The computing system of claim 1, wherein the computer-executable instructions when executed by the processing device further cause the processing device to:
prior to the receipt of the transaction request,
generate a requestor account profile in response to receiving a registration request from the requesting entity computing system, wherein the registration request comprises at least one payment method, and
verify the at least one payment method and program eligibility of the requestor entity.

### Claim 7 (depends on 2)

The computing system of claim 2 wherein:
the delivery entity computing system further comprises a memory storing computer-executable instructions and a processing device coupled to the memory, the computer-executable instructions when executed by the processing device to:
when the requesting entity computing system and the delivery entity computing system are geographically proximate, in accordance with the requestor geographic location identifier,
read the requestor matrix code to obtain the requestor entity key portion and the requestor entity number portion,
combine the obtained requesting entity key portion with the delivery entity key portion to obtain a complete delivery encryption key and combine the requestor entity number portion with the delivery entity number portion to obtain a complete delivery random number, and
generate a delivery cryptogram based on the complete delivery entity encryption key, the complete delivery random number, the unique request identifier, the requesting entity identifier, the at least one transaction payload attribute and the at least one transaction attribute, wherein the delivery transaction confirmation comprises the delivery cryptogram; and
transmit, over the network, the delivery cryptogram to the processing device of the computing system for effecting the secure transaction; and
wherein in verifying the transaction, the computer-executable instructions when executed by the processing device of the computing system for effecting the secure transaction further cause the processing device to:
generate a verification cryptogram based on the encryption key, the random number, the unique request identifier, the requesting entity identifier, the delivery entity identifier, the at least one transaction payload attribute and the at least one transaction attribute,
using the encryption key, decrypt both the received delivery cryptogram, thereby generating a delivery cryptogram result, and the verification cryptogram, thereby generating a verification cryptogram result,
compare the delivery cryptogram result with the verification cryptogram result, and
when the delivery cryptogram result matches the verification cryptogram result, transmit a transaction verification confirmation to the delivery entity computing system, and
when the delivery cryptogram result does not match the verification cryptogram result, transmit a decline transaction notification to the delivery entity computing system.

### Claim 8 (depends on 7)

The computing system of claim 7, wherein:
the requestor entity computing system further comprises a memory storing computer-executable instructions and a processing device coupled to the memory, the computer-executable instructions when executed by the processing device to:
when the requesting entity computing system and the delivery entity computing system are geographically proximate, in accordance with the requestor geographic location identifier,
read the delivery matrix code to obtain the delivery entity key portion, the delivery entity number portion and the delivery entity identifier,
combine the obtained delivery entity key portion with the requestor entity key portion to obtain a complete requestor encryption key and combine the obtained delivery entity number portion with the requestor number portion to obtain a complete requestor random number, and
generate a requestor cryptogram based on the complete requestor entity encryption key, the complete requestor random number, the unique request identifier, the delivery entity identifier, the requesting entity identifier, the at least one transaction payload attribute and the at least one transaction attribute, and
transmit, over the network, the requestor transaction confirmation to the processing device of the computing system for effecting the secure transaction, wherein the requestor transaction confirmation comprises the requestor cryptogram; and
the computer-executable instructions when executed by the processing device of the computing system for effecting the secure transaction further cause the processing device to:
using the encryption key, decrypt the requestor cryptogram, thereby generating a requestor cryptogram result;
compare the requestor cryptogram result with the verification cryptogram result; and
when the requestor cryptogram result matches the verification cryptogram result, transfer the payload reimbursement from the requestor transaction account to the delivery transaction account.

### Claim 9 (depends on 2)

The computing system of claim 2, wherein the requestor matrix code or the delivery matrix code is a QR code.

### Claim 10 (depends on 1)

The computing system of claim 1, wherein the at least one payload comprises one or more of cash and gold bullion.

### Claim 11 (depends on 1)

The computing system of claim 1, wherein the network is a secure network.

### Claim 12 (depends on 1)

The computing system of claim 1 further comprising:
a plurality of delivery entity computing systems associated with a plurality of delivery entities;
wherein the delivery entity computing system is a selected delivery entity computing system of the plurality of delivery entity computing systems.

### Claim 13

A non-transitory computer-readable medium for effecting a secure transaction, the computer-readable medium comprising computer-executable instructions for:
receiving, over a network, a transaction request to receive at least one payload from a requesting entity computing system associated with a requestor entity, the transaction request comprising:
a requesting entity identifier, a requestor geographic location identifier, at least one transaction payload attribute and at least one transaction attribute;
transmitting, over the network, the transaction request to a delivery entity computing system associated with a delivery entity, a delivery entity identifier and a delivery entity geographic location;
generating an encryption key, a random number and a unique request identifier;
receiving, over the network, a delivery transaction confirmation from the delivery entity computing system;
in response to receiving the delivery transaction confirmation, verifying the secure transaction;
receiving, over the network, a requestor transaction confirmation from the requesting entity computing system, the requestor transaction confirmation indicating a verified transfer of the at least one payload from the delivery entity to the requestor entity; and
after receipt of the requestor transaction confirmation, transferring a payload reimbursement from a requestor transaction account associated with the requestor entity to a delivery transaction account associated with the delivery entity.

### Claim 14 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the computer-readable medium further comprises computer-executable instructions for:
splitting the encryption key into a requestor entity key portion and a delivery entity key portion;
splitting the random number into a requestor entity number portion and a delivery entity number portion;
generating a requestor matrix code, the requestor matrix code comprising the requestor entity number portion, the unique request identifier, the requesting entity identifier and the requestor entity key portion;
generating a delivery matrix code, the delivery matrix code comprising the delivery entity number portion, the unique request identifier, the delivery entity identifier and the delivery entity key portion; and
transmitting, over the network, the requestor matrix code to the requesting entity computing system and the delivery matrix code to the delivery entity computing system.

### Claim 15 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the computer-readable medium further comprises computer-executable instructions for:
prior to the receipt of the transaction request,
generating a requestor account profile in response to receiving a registration request from the requesting entity computing system, wherein the registration request comprises at least one payment method, and
verifying the at least one payment method and program eligibility of the requestor entity.

### Claim 16 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the computer-readable medium further comprises computer-executable instructions for:
prior to the receipt of the transaction confirmation,
transferring a reimbursement amount from the requestor transaction account to a requestor escrow account, and
transmitting an escrow confirmation to the delivery entity computing system;
wherein transferring the payload reimbursement comprises transferring the payload reimbursement from the requestor escrow account to the delivery transaction account.

### Claim 17

A method of effecting a secure transaction, the method comprising:
via a processing device of an intermediary computing system,
receiving, over a network, a transaction request to receive at least one payload from a requesting entity computing system associated with a requestor entity, the transaction request comprising:
a requesting entity identifier, a requestor geographic location identifier, at least one transaction payload attribute and at least one transaction attribute;
transmitting, over the network, the transaction request to a delivery entity computing system associated with a delivery entity, a delivery entity identifier and a delivery entity geographic location;
generating an encryption key, a random number and a unique request identifier;
transmitting, over the network, at least a portion of the encryption key, the random number and the unique request identifier to each of the requesting entity computing system and the delivery entity computing system;
receiving, over the network, a delivery transaction confirmation from the delivery entity computing system;
in response to receiving the delivery transaction confirmation, verifying the secure transaction;
receiving, over the network, a requestor transaction confirmation from the requesting entity computing system, the requestor transaction confirmation indicating a verified transfer of the at least one payload from the delivery entity to the requestor entity; and
after receiving the requestor transaction confirmation, transferring a payload reimbursement from a requestor transaction account associated with the requestor entity to a delivery transaction account associated with the delivery entity.

### Claim 18 (depends on 17)

The method of claim 17 further comprising:
splitting the encryption key into a requestor entity key portion and a delivery entity key portion;
splitting the random number into a requestor entity number portion and a delivery entity number portion;
generating a requestor matrix code, the requestor matrix code comprising the requestor entity number portion, the unique request identifier, the requesting entity identifier and the requesting entity key portion;
generating a delivery matrix code, the delivery matrix code comprising the delivery entity number portion, the unique request identifier, the delivery entity identifier and the delivery entity key portion; and
transmitting, over the network, the requestor matrix code to the requesting entity computing system and the delivery matrix code to the delivery entity computing system.

### Claim 19 (depends on 18)

The method of claim 18 further comprising:
when the requesting entity computing system and the delivery entity computing system are geographically proximate, in accordance with the requestor geographic location identifier, via a processing device of the delivery entity computing system:
reading the requestor matrix code to obtain the requestor entity key portion and the requestor entity number portion,
combining the obtained requesting entity key portion with the delivery entity key portion to obtain a complete delivery encryption key and combine the requestor entity number portion with the delivery entity number portion to obtain a complete delivery random number,
generating a delivery cryptogram based on the complete delivery entity encryption key, the complete delivery random number, the unique request identifier, the requesting entity identifier, the at least one transaction payload attribute and the at least one transaction attribute, wherein the delivery transaction confirmation comprises the delivery cryptogram, and
transmitting, over the network, the delivery cryptogram to the processing device of the computing system for effecting the secure transaction; and
in verifying the transaction, via the processing device of the intermediary computing system:
generating a verification cryptogram based on the encryption key, the random number, the unique request identifier, the requesting entity identifier, the delivery entity identifier, the at least one transaction payload attribute and the at least one transaction attribute,
using the encryption key, decrypting both the received delivery cryptogram, thereby generating a delivery cryptogram result, and the verification cryptogram, thereby generating a verification cryptogram result,
comparing the delivery cryptogram result with the verification cryptogram result, and
when the delivery cryptogram result matches the verification cryptogram result, transmitting a transaction verification confirmation to the delivery entity computing system, and
when the delivery cryptogram result does not match the verification cryptogram result, transmitting a decline transaction notification to the delivery entity computing system.

### Claim 20 (depends on 19)

The method of claim 19 further comprising:
when the requesting entity computing system and the delivery entity computing system are geographically proximate, in accordance with the requestor geographic location identifier, via a processing device of the requestor entity computing system:
reading the delivery matrix code to obtain the delivery entity key portion, the delivery entity number portion and the delivery entity identifier,
combining the obtained delivery entity key portion with the requestor entity key portion to obtain a complete requestor encryption key and combine the obtained delivery entity number portion with the requestor number portion to obtain a complete requestor random number,
generating a requestor cryptogram based on the complete requestor entity encryption key, the complete requestor random number, the unique request identifier, the delivery entity identifier, the requesting entity identifier, the at least one transaction payload attribute and the at least one transaction attribute, and
transmitting, over the network, the requestor transaction confirmation to the processing device of the computing system for effecting the secure transaction, wherein the requestor transaction confirmation comprises the requestor cryptogram; and
via the processing device of the intermediary computing system:
using the encryption key, decrypting the requestor cryptogram, thereby generating a requestor cryptogram result;
comparing the requestor cryptogram result with the verification cryptogram result; and
when the requestor cryptogram result matches the verification cryptogram result, transferring the payload reimbursement from the requestor transaction account to the delivery transaction account.
