# US 2022/0284428 A1 · Stable digital token processing and encryption on blockchain

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

- Number: US 2022/0284428 A1
- Document ID: US20220284428A1
- Status: Published application
- Kind: A1
- Application number: 17/680,072
- Filed: 2022-02-24
- Published: 2022-09-08
- Earliest claimed: 2019-08-27
- Assignees: MShift, Inc.
- Applicants: MShift, Inc.
- Inventors: Xiaomeng ZHOU; Scott MOELLER; Jacqueline SNELL; Andrew YEE; David TCHEAU; Denny TRAN; David DENG
- Web page: https://patentgrep.com/patent/US20220284428A1

## CPC

- 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}
- G06F 21/6254: {by anonymising data, e.g. decorrelating personal data from the owner's identification}
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06Q 20/32: using wireless devices
- G06Q 20/382: {insuring higher security of transaction}
- G06Q 20/3823: {combining multiple encryption tools for a transaction}
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/3827: {Use of message hashing}
- G06Q 20/3829: {involving key management}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- 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/085: {Secret sharing or secret splitting, e.g. threshold schemes}
- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- 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)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Disclosed herein are methods and systems for facilitating payment comprising the exchange of digital tokens from consumer accounts to merchant accounts in exchange for goods and/or services wherein the merchant may request the issuance of reward tokens, backed up by a central entity, to the consumer accounts. The reward tokens can then be used to facilitate payment for goods or services from the requesting merchant.

## Claims

### Claim 1

A method for masking a transaction, comprising:
i. providing a first database accessible by a certifier entity, comprising protected data, wherein the protected data is assigned an identifier; and
ii. providing a second database, comprising transactional records associated with the identifier, wherein the transactional records are encrypted by (1) a first key corresponding to a private key of the certifier entity and (2) a second key corresponding to a private key of a master avatar associated with the identifier, wherein the second key is managed by the central entity or a user associated with the master avatar, wherein in order to search for the transactional records associated with the identifier, two keys must be provided to the second database.

### Claim 2 (depends on 1)

The method of claim 1, wherein the certifier entity does not have access to the second key.

### Claim 3 (depends on 1)

The method of claim 1, wherein the identifier is hashed data.

### Claim 4 (depends on 1)

The method of claim 1, wherein the identifier has been verified by both a user assigned to the identifier and the certifier entity.

### Claim 5 (depends on 1)

The method of claim 1, wherein the identifier is first verified by a user assigned to the identifier and second by a certifier entity.

### Claim 6 (depends on 6)

A system for masking a transaction, comprising:
a first database accessible by a certifier entity, comprising protected data, wherein the protected data is assigned an identifier; and
a second database, comprising transactional records associated with the identity identifier, wherein the transactional records are encrypted by (1) a first key corresponding to a private key of the certifier entity and (2) a second key corresponding to a private key of a master avatar associated with the identifier,
wherein the second key is managed by the central entity or a user associated with the master avatar,
wherein in order to search for the transactional records associated with the identifier, two keys are provided to the second database. (Original) The system of claim 6, wherein the certifier entity does not have access to the second key.

### Claim 8 (depends on 6)

The system of claim 6, wherein the identifier is hashed data.

### Claim 9 (depends on 6)

The system of claim 6, wherein the identifier has been verified by both a user assigned to the identifier and the certifier entity.

### Claim 10

A method for facilitating payment, comprising:
i. receiving, at a server in communication with a central entity, from a user device of a first user, a selection of a digital token transfer method to a second user;
ii. processing said digital token transfer method, by said server, by initiating a transfer of digital tokens from a digital account of said first user to a digital account of said central entity and substantially simultaneously initiating a transfer of a same amount of said digital tokens from said central entity to an account of said second user; and
iii. receiving, at a server in communication with said central entity, from a second device of said second user a request to issue an incentive amount of digital tokens to said first user and substantially simultaneously initiate a transfer of said digital tokens of the same incentive amount from said account of said second user to said first user.

### Claim 11 (depends on 10)

The method of claim 10, wherein the central entity has received verification of an identity of the first user and an identity of the second user.

### Claim 12 (depends on 10)

The method of claim 10, further comprising, prior to (a), initiating a transfer of fiat currency from a financial institution account of said first user to a financial institution of said central entity, and substantially simultaneously initiating a transfer of digital tokens from said central entity to an account of said first user.

### Claim 13 (depends on 12)

The method of claim 12, wherein the initiating is performed on a web-based interface.

### Claim 14 (depends on 12)

The method of claim 12, wherein the initiating is performed on a mobile-web interface.

### Claim 15 (depends on 10)

The method of claim 10, further comprising receiving a selection of a digital token transfer to the second user and a third user simultaneously.

### Claim 16

A system for facilitating payment, comprising:
a server in communication with a blockchain network and a central entity, wherein the server comprises one or more processors, individually or collectively, configured to:
i. receive from a first user device of a first user, a selection of a digital token transfer method to a second user;
ii. process said digital token transfer method, by said server, by initiating a transfer of digital tokens from a digital account of said first user to a digital account of said central entity on said blockchain and substantially simultaneously initiating a transfer of a same amount of said digital tokens from said central entity to an account of said second user; and
iii. receive, at a server in communication with said central entity, from a second device of said second user a request to issue a reward amount of digital tokens to said first user and substantially simultaneously initiating a transfer of said digital tokens of a same reward amount from said account of said second user to said first user.

### Claim 17 (depends on 16)

The system of claim 16, wherein the central entity has received verification of an identify of the first user and an identity of the second user.

### Claim 18 (depends on 16)

The system of claim 16, wherein the one or more processors are, individually or collectively, further configured to, receive fund transfer initiation from the first user to the second user.

### Claim 19 (depends on 16)

The system of claim 16, wherein the one or more processors are, individually or collectively, further configured to, provide a mobile-based interface for the fund transfer initiation to the user device.
