# US 10,311,433 B2 · Secure authorizations using independent communications and different one-time-use encryption keys for each party to a transaction

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

- Number: US 10,311,433 B2
- Document ID: US10311433B2
- Status: Granted
- Kind: B2
- Application number: 15/381,465
- Filed: 2016-12-16
- Published: 2017-05-25
- Granted: 2019-06-04
- Earliest claimed: 2014-11-12
- Assignees: BenedorTSE LLC
- Applicants: BenedorTSE LLC
- Inventors: Richard F. Carrott
- Web page: https://patentgrep.com/patent/US10311433B2

## CPC

- G06Q 20/3829: {involving key management}
- G06Q 20/202: {Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR}
- G06Q 20/3674: {involving authentication}
- G06Q 20/382: {insuring higher security of transaction}
- 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/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key}
- H04W 12/041: Key generation or derivation
- 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
- 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 registered provider device encrypts provider input related to a transaction between the provider device and one of many registered user devices to create an encrypted one-time-use provider code (the encryption is performed using an encryption key produced, in part, using a uniquely sequenced number generated by a sequencer maintained by the provider device). Similarly, the user device encrypts user input to create an encrypted one-time-use user code using an encryption key produced, in part, using a uniquely sequenced number generated by a user sequencer maintained by the user device. The provider and user devices independently transmit their different encrypted one-time-use codes to an intermediate entity, which decrypts the encrypted codes. This decryption is performed using one-time-use encryption keys produced using sequencers maintained by the intermediate entity, and this decryption generates an authorization request. The intermediate entity obtains an authorization decision regarding the authorization request from the authorization entity.

## Claims

### Claim 1

A system comprising:
an intermediate entity maintaining duplicate sequencers, a first app capable of being provided to registered user devices, and a second app capable of being provided to registered provider devices,
said second app, operating on a provider device, is capable of encrypting provider input related to a transaction between said provider device and a user device to create an encrypted one-time-use provider code using a one-time-use provider encryption key produced, in part, using a uniquely sequenced number generated by a provider sequencer maintained by said second app,
said first app, operating on said user device, is capable of encrypting user input related to said transaction to create an encrypted one-time-use user code using a one-time-use user encryption key produced, in part, using a uniquely sequenced number generated by a user sequencer maintained by said first app,
said provider sequencer is synchronized with a corresponding duplicate sequencer maintained by said intermediate entity and said user sequencer is synchronized with a different duplicate sequencer maintained by said intermediate entity, and
said provider sequencer and said user sequencer each produce a different encryption key for a given transaction,
said first app is capable of causing said user device to provide said encrypted one-time-use user code as an encrypted user half of said transaction to said intermediate entity, and said second app is capable of causing said provider device to provide said encrypted one-time-use provider code as an encrypted provider half of said transaction to said intermediate entity,
said intermediate entity is capable of decrypting said encrypted one-time-use provider code and is capable of decrypting said encrypted one-time-use user code using one-time-use encryption keys independently produced by said intermediate entity using corresponding ones of said duplicate sequencers maintained by said intermediate entity to produce a single authorization request for said transaction,
said intermediate entity is capable of obtaining an authorization decision regarding said single authorization request for said transaction from an authorization entity, and
said intermediate entity is capable of outputting said authorization decision.

### Claim 2 (depends on 1)

The system according to claim 1, said intermediate entity comprises: a financial institution; a financial clearing house; a resource controller; and/or a verification entity,
said provider device comprises a device operated by: a merchant, a resource storage entity, an access control agent, and/or a communications entity, and
said user device comprises a device operated by: a customer, a consumer, an organization, and/or an individual.

### Claim 3 (depends on 1)

The system according to claim 1, said user devices and said provider devices each only maintain a unique individual sequencer, and said user devices and said provider devices do not have access to sequencers of other user devices or other provider devices.

### Claim 4 (depends on 1)

The system according to claim 1, said intermediate entity securely maintains personal financial information of a user operating said user device, and said first app prevents said user device from maintaining said personal financial information.

### Claim 5 (depends on 1)

The system according to claim 1, said encrypted one-time-use provider code and said encrypted one-time-use user code are devoid of personal financial information of a user operating said user device.

### Claim 6

A system comprising:
an intermediate entity maintaining duplicate sequencers, a first app capable of being provided to registered user devices, and a second app capable of being provided to registered provider devices,
said second app, operating on a provider device, is capable of encrypting provider input related to a transaction between said provider device and a user device to create an encrypted one-time-use provider code using a one-time-use provider encryption key produced, in part, using a uniquely sequenced number generated by a provider sequencer maintained by said second app,
said provider input includes a unique transaction number,
said second app is capable of causing said provider device to supply said unique transaction number to said user device,
said first app, operating on said user device, is capable of encrypting said unique transaction number and user input related to said transaction to create an encrypted one-time-use user code using a one-time-use user encryption key produced, in part, using a uniquely sequenced number generated by a user sequencer maintained by said first app,
said provider sequencer is synchronized with a corresponding duplicate sequencer maintained by said intermediate entity and said user sequencer is synchronized with a different duplicate sequencer maintained by said intermediate entity, and
said provider sequencer and said user sequencer each produce a different encryption key for a given transaction,
said first app is capable of causing said user device to provide said encrypted one-time-use user code as an encrypted user half of said transaction to said intermediate entity, and said second app is capable of causing said provider device to provide said encrypted one-time-use provider code as an encrypted provider half of said transaction to said intermediate entity,
said intermediate entity is capable of decrypting said encrypted one-time-use provider code and is capable of decrypting said encrypted one-time-use user code using one-time-use encryption keys independently produced by said intermediate entity using corresponding ones of said duplicate sequencers maintained by said intermediate entity to produce a single authorization request for said transaction,
said intermediate entity is capable of obtaining an authorization decision regarding said single authorization request for said transaction from an authorization entity, and
said intermediate entity is capable of outputting said authorization decision.

### Claim 7 (depends on 6)

The system according to claim 6, said intermediate entity comprises: a financial institution; a financial clearing house; a resource controller; and/or a verification entity,
said provider device comprises a device operated by: a merchant, a resource storage entity, an access control agent, and/or a communications entity, and
said user device comprises a device operated by: a customer, a consumer, an organization, and/or an individual.

### Claim 8 (depends on 6)

The system according to claim 6, said user devices and said provider devices each only maintain a unique individual sequencer, and said user devices and said provider devices do not have access to sequencers of other user devices or other provider devices.

### Claim 9 (depends on 6)

The system according to claim 6, said intermediate entity securely maintains personal financial information of a user operating said user device, and said first app prevents said user device from maintaining said personal financial information.

### Claim 10 (depends on 6)

The system according to claim 6, said encrypted one-time-use provider code and said encrypted one-time-use user code are devoid of personal financial information of a user operating said user device.

### Claim 11

A method comprising:
maintaining, by an intermediate entity, duplicate sequencers, a first app, and a second app;
providing, by said intermediate entity, said first app to registered user devices, and said second app to registered provider devices;
encrypting, by said second app, provider input related to a transaction between a provider device and a user device to create an encrypted one-time-use provider code using a one-time-use provider encryption key produced, in part, using a uniquely sequenced number generated by a provider sequencer maintained by said second app;
encrypting, by said first app, user input related to said transaction to create an encrypted one-time-use user code using a one-time-use user encryption key produced, in part, using a uniquely sequenced number generated by a user sequencer maintained by said first app, said provider sequencer is synchronized with a corresponding duplicate sequencer maintained by said intermediate entity and said user sequencer is synchronized with a different duplicate sequencer maintained by said intermediate entity, and
said provider sequencer and said user sequencer each produce a different encryption key for a given transaction;
causing, by said first app, said user device to provide said encrypted one-time-use user code as an encrypted user half of said transaction to said intermediate entity;
causing, by said second app, said provider device to provide said encrypted one-time-use provider code as an encrypted provider half of said transaction to said intermediate entity;
decrypting, by said intermediate entity, said encrypted one-time-use provider code and said encrypted one-time-use user code using one-time-use encryption keys independently produced by said intermediate entity using corresponding ones of said duplicate sequencers maintained by said intermediate entity to produce a single authorization request for said transaction;
obtaining, by said intermediate entity, an authorization decision regarding said single authorization request for said transaction from an authorization entity; and
outputting, by said intermediate entity, said authorization decision.

### Claim 12 (depends on 11)

The method according to claim 11, said intermediate entity comprises: a financial institution; a financial clearing house; a resource controller; and/or a verification entity,
said provider device comprises a device operated by: a merchant, a resource storage entity, an access control agent, and/or a communications entity, and
said user device comprises a device operated by: a customer, a consumer, an organization, and/or an individual.

### Claim 13 (depends on 11)

The method according to claim 11, said user devices and said provider devices each only maintain a unique individual sequencer, and said user devices and said provider devices do not have access to sequencers of other user devices or other provider devices.

### Claim 14 (depends on 11)

The method according to claim 11, further comprising:
securely maintaining, by said intermediate entity, personal financial information of a user operating said user device; and
preventing, by said first app, said user device from maintaining said personal financial information.

### Claim 15 (depends on 11)

The method according to claim 11, said encrypted one-time-use provider code and said encrypted one-time-use user code are devoid of personal financial information of a user operating said user device.

### Claim 16

A method comprising:
maintaining, by an intermediate entity, duplicate sequencers, a first app, and a second app;
providing, by said intermediate entity, said first app to registered user devices, and said second app to registered provider devices;
encrypting, by said second app, provider input related to a transaction between a provider device and a user device to create an encrypted one-time-use provider code using a one-time-use provider encryption key produced, in part, using a uniquely sequenced number generated by a provider sequencer maintained by said second app, said provider input includes a unique transaction number;
causing, by said second app, said provider device to supply said unique transaction number to said user device;
encrypting, by said first app, said unique transaction number and user input related to said transaction to create an encrypted one-time-use user code using a one-time-use user encryption key produced, in part, using a uniquely sequenced number generated by a user sequencer maintained by said first app, said provider sequencer is synchronized with a corresponding duplicate sequencer maintained by said intermediate entity and said user sequencer is synchronized with a different duplicate sequencer maintained by said intermediate entity, and said provider sequencer and said user sequencer each produce a different encryption key for a given transaction;
causing, by said first app, said user device to provide said encrypted one-time-use user code as an encrypted user half of said transaction to said intermediate entity;
causing, by said second app, said provider device to provide said encrypted one-time-use provider code as an encrypted provider half of said transaction to said intermediate entity;
decrypting, by said intermediate entity, said encrypted one-time-use provider code and said encrypted one-time-use user code using one-time-use encryption keys independently produced by said intermediate entity using corresponding ones of said duplicate sequencers maintained by said intermediate entity to produce a single authorization request for said transaction;
obtaining, by said intermediate entity, an authorization decision regarding said single authorization request for said transaction from an authorization entity; and
outputting, by said intermediate entity, said authorization decision.

### Claim 17 (depends on 16)

The method according to claim 16, said causing said provider device to supply said unique transaction number to said user device comprising at least one of:
causing said provider device to display a computer-readable code on a display of said provider device readable by an optical device of said user device;
causing said provider device to display a human-readable code on said display of said provider device positioned to be readable by a user, said user entering said human-readable code into said user device;
causing said provider device to wirelessly transmit a code using a wireless device of said provider device capable of wirelessly communicating with a wireless device of said user device; and
causing said provider device to internally communicate said unique transaction number from a first application operating on said user device to a second application operating on said user device.

### Claim 18 (depends on 16)

The method according to claim 16, said user devices and said provider devices each only maintain a unique individual sequencer, and said user devices and said provider devices do not have access to sequencers of other user devices or other provider devices.

### Claim 19 (depends on 16)

The method according to claim 16, further comprising:
securely maintaining, by said intermediate entity, personal financial information of a user operating said user device; and
preventing, by said first app, said user device from maintaining said personal financial information.

### Claim 20 (depends on 16)

The method according to claim 16, said encrypted one-time-use provider code and said encrypted one-time-use user code are devoid of personal financial information of a user operating said user devise.