# US 2025/0061445 A1 · Show to pay payment mode of a digital asset payment network

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

- Number: US 2025/0061445 A1
- Document ID: US20250061445A1
- Status: Published application
- Kind: A1
- Application number: 18/936,427
- Filed: 2024-11-04
- Published: 2025-02-20
- Earliest claimed: 2021-01-29
- Assignees: Flexa Inc.
- Applicants: Flexa Inc.
- Inventors: Trevor Filter; Zachary Kilgore; Tyler Robert Spalding
- Web page: https://patentgrep.com/patent/US20250061445A1

## CPC

- G06Q 20/065: {using e-cash}
- G06Q 20/3674: {involving authentication}
- G06K 7/1095: {the scanner comprising adaptations for scanning a record carrier that is displayed on a display-screen or the like}
- G06K 7/1413: {1D bar codes}
- G06K 7/1417: {2D bar codes}
- G06K 19/06028: {using bar codes}
- G06K 19/06037: {multi-dimensional coding}
- G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit}
- G06Q 20/208: {Input by product or record sensing, e.g. weighing or scanner processing}
- G06Q 20/3274: {using a pictured code, e.g. barcode or QR-code, being displayed on the M-device}
- G06Q 20/36: using electronic wallets or electronic money safes
- G06Q 20/3678: {e-cash details, e.g. blinded, divisible or detecting double spending}
- G06Q 20/381: {Currency conversion}
- G06Q 20/387: {Payment using discounts or coupons (relating to marketing G06Q30/02)}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 20/0655: {e-cash managed centrally}
- G06Q 20/326: {Payment applications installed on the mobile devices}
- 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
- G06K: GRAPHICAL DATA READING (image or video recognition or understanding G06V); PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS

## Abstract

A method includes initiating, by a user computing device, a digital asset-based payment to a merchant computing entity and sending, by the user computing device, user computing device real-time payment information to a digital asset payment computing entity. The method further includes locking, by the digital asset payment computing entity, an amount of network digital assets, generating a user authorization scannable code, and sending the user authorization scannable code to the user computing device. The method further includes providing, by the user computing device, the user authorization scannable code to the merchant computing entity. When the merchant computing entity scans the user authorization scannable code, the method further includes sending, by the merchant computing entity, merchant computing entity real-time payment information to the digital asset payment computing entity, and providing, by the digital asset payment computing entity, a confirmation to the merchant computing entity.

## Claims

### Claim 1

A method comprises:
receiving, by a digital asset payment computing entity of a digital asset payment network, a merchant selection regarding a merchant computing entity from a user computing device of the digital asset payment network via a digital asset payment interface;
receiving, by the digital asset payment computing entity, a digital asset type selection for a digital asset-based payment with the merchant computing entity, wherein the merchant computing entity accepts a desired asset;
locking, by the digital asset payment computing entity, an amount of network digital assets based on an authorized payment amount for the digital asset-based payment;
providing, by the digital asset payment computing entity, a user authorization scannable code to the user computing device, wherein the user authorization scannable code authorizes the authorized payment amount for a time period;
obtaining, by the digital asset payment computing entity, digital asset-based payment information from the merchant computing entity via a merchant digital asset payment interface;
executing, by the digital asset payment computing entity, a real-time digital asset-based payment process to provide a payment amount of the desired asset to the merchant computing; and
executing, by the digital asset payment computing entity, a nonreal-time digital asset-based payment process to verify a payment amount of digital assets obtained from the user computing device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the real-time digital asset-based payment process comprises:
providing, by the digital asset payment computing entity, a confirmation to the merchant that the digital asset-based payment is approved;
obtaining, by the digital asset payment computing entity, the payment amount of the digital assets from the user computing device;
exchanging, by the digital asset payment computing entity, the payment amount of the digital assets for a substantially equivalent payment amount of the desired asset; and
sending, by the digital asset payment computing entity, the substantially equivalent payment amount of the desired asset to the merchant computing entity.

### Claim 3 (depends on 2)

The method of claim 2, wherein the real-time digital asset-based payment process further comprises:
adjusting, by the digital asset payment computing entity, the locked amount of the network digital assets based on the digital asset payment information.

### Claim 4 (depends on 2)

The method of claim 2, wherein the nonreal-time digital asset-based payment process comprises:
implementing, by the digital asset payment computing entity, a nonreal-time verification process associated with the type of digital asset to verify the payment amount of the digital assets obtained from the user computing device; and
when the payment amount of the digital assets is verified by the nonreal-time verification process:
unlocking the amount of the network digital assets; and
when the payment amount of the digital assets is not verified by the nonreal-time verification process:
consuming the amount of the network digital assets.

### Claim 5 (depends on 1)

The method of claim 1 further comprises:
locking, by the digital asset payment computing entity, a rate quote for the payment amount of digital assets.

### Claim 6 (depends on 1)

The method of claim 1, wherein the digital asset-based payment information includes:
a merchant computing entity identifier (ID) associated with the merchant computing entity;
a type of asset of the desired asset; and
a payment amount of the digital asset-based payment.

### Claim 7 (depends on 1)

The method of claim 1 further comprises:
obtaining, by the digital asset payment computing entity, the digital asset-based payment information from the merchant computing entity after the time period;
providing, by the digital asset payment computing entity, a new user authorization scannable code to the user computing device, wherein the new user authorization scannable code authorizes the authorized payment amount for a new time period; and
requesting, by the digital asset payment computing entity, new digital asset-based payment information from the merchant computing entity.

### Claim 8 (depends on 1)

The method of claim 1 further comprises:
when the digital asset-based payment information from the merchant computing entity is not obtained within the time period, providing, by the digital asset payment computing entity, a new user authorization scannable code to the user computing device, wherein the new user authorization scannable code authorizes the authorized payment amount for a new time period.

### Claim 9

A non-transitory computer readable memory comprises:
a first memory element that stores operational instructions that, when executed by a digital asset payment computing entity of a digital asset payment network, causes the digital asset payment computing entity to:
receive a merchant selection regarding a merchant computing entity from a user computing device of the digital asset payment network via a digital asset payment interface;
receive a digital asset type selection for a digital asset-based payment with the merchant computing entity, wherein the merchant computing entity accepts a desired asset;
a second memory element that stores operational instructions that, when executed by the digital asset payment computing entity, causes the digital asset payment computing entity to:
lock an amount of network digital assets based on an authorized payment amount for the digital asset-based payment;
a third memory element that stores operational instructions that, when executed by the digital asset payment computing entity, causes the digital asset payment computing entity to:
provide a user authorization scannable code to the user computing device, wherein the user authorization scannable code authorizes the authorized payment amount for a time period;
a fourth memory element that stores operational instructions that, when executed by the digital asset payment computing entity, causes the digital asset payment computing entity to:
obtaining digital asset-based payment information from the merchant computing entity via a merchant digital asset payment interface; and
a fifth memory element that stores operational instructions that, when executed by the digital asset payment computing entity, causes the digital asset payment computing entity to:
executing a real-time digital asset-based payment process to provide a payment amount of the desired asset to the merchant computing; and
execute a nonreal-time digital asset-based payment process to verify a payment amount of digital assets obtained from the user computing device.

### Claim 10 (depends on 9)

The non-transitory computer readable memory claim 9, wherein the fifth memory element further stores operational instructions that, when executed by the digital asset payment computing entity, causes the digital asset payment computing entity to execute the real-time digital asset-based payment process by:
providing a confirmation to the merchant that the digital asset-based payment is approved;
obtaining the payment amount of the digital assets from the user computing device;
exchanging the payment amount of the digital assets for a substantially equivalent payment amount of the desired asset; and
sending the substantially equivalent payment amount of the desired asset to the merchant computing entity.

### Claim 11 (depends on 10)

The non-transitory computer readable memory claim 10, wherein the fifth memory element further stores operational instructions that, when executed by the digital asset payment computing entity, causes the digital asset payment computing entity to execute the real-time digital asset-based payment process by:
adjusting the locked amount of the network digital assets based on the digital asset payment information.

### Claim 12 (depends on 10)

The non-transitory computer readable memory claim 10, wherein the fifth memory element further stores operational instructions that, when executed by the digital asset payment computing entity, causes the digital asset payment computing entity to execute the nonreal-time digital asset-based payment process by:
implementing a nonreal-time verification process associated with the type of digital asset to verify the payment amount of the digital assets obtained from the user computing device; and
when the payment amount of the digital assets is verified by the nonreal-time verification process:
unlocking the amount of the network digital assets; and
when the payment amount of the digital assets is not verified by the nonreal-time verification process:
consuming the amount of the network digital assets.

### Claim 13 (depends on 9)

The non-transitory computer readable memory of claim 9, wherein the second memory element further stores operational instructions that, when executed by the digital asset payment computing entity, causes the digital asset payment computing entity to:
lock a rate quote for the payment amount of digital assets.

### Claim 14 (depends on 9)

The non-transitory computer readable memory of claim 9, wherein the digital asset-based payment information includes:
a merchant computing entity identifier (ID) associated with the merchant computing entity;
a type of asset of the desired asset; and
a payment amount of the digital asset-based payment.

### Claim 15 (depends on 9)

The non-transitory computer readable memory of claim 9, wherein the third memory element further stores operational instructions that, when executed by the digital asset payment computing entity, causes the digital asset payment computing entity to:
obtain the digital asset-based payment information from the merchant computing entity after the time period;
provide a new user authorization scannable code to the user computing device, wherein the new user authorization scannable code authorizes the authorized payment amount for a new time period; and
request new digital asset-based payment information from the merchant computing entity.

### Claim 16 (depends on 9)

The non-transitory computer readable memory of claim 9, wherein the third memory element further stores operational instructions that, when executed by the digital asset payment computing entity, causes the digital asset payment computing entity to:
when the digital asset-based payment information from the merchant computing entity is not obtained within the time period, provide a new user authorization scannable code to the user computing device, wherein the new user authorization scannable code authorizes the authorized payment amount for a new time period.
