# US 2026/0179074 A1 · Methods and systems of central bank digital currency facilitated micropayments

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

- Number: US 2026/0179074 A1
- Document ID: US20260179074A1
- Status: Published application
- Kind: A1
- Application number: 19/538,816
- Filed: 2026-02-12
- Published: 2026-06-25
- Earliest claimed: 2023-01-27
- Assignees: American Express Travel Related Services Company, Inc.
- Applicants: American Express Travel Related Services Company, Inc.
- Inventors: Lucky Bimolaksono; Matthew Stephen Bodell; Jaime A. Cruz-Herrera; Dean Ernest Arthur Nicolson
- Web page: https://patentgrep.com/patent/US20260179074A1

## CPC

- G06Q 20/29: {characterised by micropayments}
- G06Q 20/065: {using e-cash}
- G06Q 20/20: Point-of-sale [POS] network systems
- G06Q 20/227: {characterised in that multiple accounts are available, e.g. to the payer}
- G06Q 20/36: using electronic wallets or electronic money safes
- G06Q 20/3674: {involving authentication}
- G06Q 20/381: {Currency conversion}
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/401: {Transaction verification}
- G06Q 20/403: {Solvency checks}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 40/123: {Tax preparation or submission}
- 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

## Abstract

Disclosed are various embodiments of methods and systems for central bank digital currency (CBDC) facilitated micropayments. In at least some embodiments, a system can establish an event stream between a computing device and a client device in response to receiving a start session request, wherein the event stream includes at least a payment event. Then, the system can identify the payment event within the event stream, the payment event comprising a purchase amount. Finally, the system can transmit, in response to identifying the payment event, a digital currency transfer corresponding to the purchase amount to a digital currency network.

## Claims

### Claim 1

A system, comprising:
a computing device comprising a processor and a memory; and
machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least:
establish an event stream between the computing device and a client device in response to receiving a start session request, wherein the event stream includes at least a payment event;
identify the payment event within the event stream, the payment event comprising a purchase amount; and
transmit, in response to identifying the payment event, a digital currency transfer corresponding to the purchase amount to a digital currency network.

### Claim 2 (depends on 1)

The system of claim 1, wherein the machine-readable instructions that transmit the digital currency transfer, when executed by the processor, further cause the computing device to at least:
debit the purchase amount from a payor funding source;
credit a payor wallet capable of holding a central bank digital currency (CBDC) with a first CBDC amount, wherein the first CBDC amount is equivalent to the purchase amount and the payor wallet being identifiable by a payor wallet address; and
generate a first CBDC transfer from the payor wallet address to a payee wallet address for the first CBDC amount.

### Claim 3 (depends on 2)

The system of claim 2, wherein the payor wallet is unique to an account holder that controls the payor funding source.

### Claim 4 (depends on 1)

The system of claim 1, wherein the payment event is a first payment event, and wherein the purchase amount is a first purchase amount, and wherein the machine-readable instructions that identify the first payment event, when executed by the processor, further cause the computing device to at least:
identify a second payment event, the second payment event comprising a second purchase amount, wherein the second purchase amount is representative of a non-digital currency.

### Claim 5 (depends on 4)

The system of claim 4, wherein the machine-readable instructions that identify the second payment event, when executed by the processor, further cause the computing device to at least:
debit the second purchase amount from a payor funding source;
credit a payor wallet with a CBDC amount, wherein the CBDC amount is equivalent to the second purchase amount;
generate a second transfer from a payor wallet address to a payee wallet address for the CBDC amount; and
transmit the second transfer to the digital currency network.

### Claim 6 (depends on 1)

The system of claim 1, wherein the payment event is placed on the event stream by an internet-of-things (IoT) device.

### Claim 7 (depends on 1)

The system of claim 1, wherein the machine-readable instructions that identify the payment event, when executed by the processor, further cause the computing device to at least iterate through each event on the event stream to identify the payment event.

### Claim 8

A method, comprising:
establishing an event stream between a computing device and a client device in response to receiving a start session request, wherein the event stream includes at least a payment event;
identifying the payment event within the event stream, the payment event comprising a purchase amount; and
transmitting, in response to identifying the payment event, a digital currency transfer corresponding to the purchase amount to a digital currency network.

### Claim 9 (depends on 8)

The method of claim 8, wherein transmitting the digital currency transfer further comprises:
debiting the purchase amount from a payor funding source;
crediting a payor wallet capable of holding a central bank digital currency (CBDC) with a first CBDC amount, wherein the first CBDC amount is equivalent to the purchase amount and the payor wallet being identifiable by a payor wallet address; and
generating a first CBDC transfer from the payor wallet address to a payee wallet address for the first CBDC amount.

### Claim 10 (depends on 9)

The method of claim 9, wherein the payor wallet is unique to an account holder that controls the payor funding source.

### Claim 11 (depends on 8)

The method of claim 8, wherein the payment event is a first payment event, and wherein the purchase amount is a first purchase amount, and wherein identifying the first payment event further comprises:
identifying a second payment event, the second payment event comprising a second purchase amount, wherein the second purchase amount is representative of a non-digital currency.

### Claim 12 (depends on 11)

The method of claim 11, wherein identifying the second payment event further comprises:
debiting the second purchase amount from a payor funding source;
crediting a payor wallet with a CBDC amount, wherein the CBDC amount is equivalent to the second purchase amount;
generating a second transfer from a payor wallet address to a payee wallet address for the CBDC amount; and
transmitting the second transfer to the digital currency network.

### Claim 13 (depends on 8)

The method of claim 8, wherein the payment event is placed on the event stream by an internet-of-things (IoT) device.

### Claim 14 (depends on 8)

The method of claim 8, wherein initiating the event stream further comprises iterating through each event on the event stream for at least the payment event.

### Claim 15

A non-transitory, computer-readable medium, comprising machine-readable instructions that, when executed by a processor of a computing device, cause the computing device to at least:
establish an event stream between the computing device and a client device in response to receiving a start session request, and wherein the event stream includes at least a payment event;
identify the payment event within the event stream, the payment event comprising a purchase amount; and
transmit, in response to identifying the payment event, a digital currency transfer corresponding to the purchase amount to a digital currency network.

### Claim 16 (depends on 15)

The non-transitory, computer readable medium of claim 15, wherein the machine-readable instructions that transmit the digital currency transfer, when executed by the processor, further cause the computing device to at least:
debit the purchase amount from a payor funding source;
credit a payor wallet capable of holding a central bank digital currency (CBDC) with a first CBDC amount, wherein the first CBDC amount is equivalent to the purchase amount and the payor wallet being identifiable by a payor wallet address; and
generate a first CBDC transfer from the payor wallet address to a payee wallet address for the first CBDC amount.

### Claim 17 (depends on 16)

The non-transitory, computer-readable medium of claim 16, wherein the payor wallet is unique to an account holder that controls the payor funding source.

### Claim 18 (depends on 15)

The non-transitory, computer readable medium of claim 15, wherein the payment event is a first payment event, and wherein the purchase amount is a first purchase amount, and wherein the machine-readable instructions that identifies the first payment event, when executed by the processor, further cause the computing device to at least:
identify a second payment event, the second payment event comprising a second purchase amount, wherein the second purchase amount is representative of a non-digital currency.

### Claim 19 (depends on 18)

The non-transitory, computer readable medium of claim 18, wherein the machine-readable instructions that identify the second payment event, when executed by the processor, further cause the computing device to at least:
debit the second purchase amount from a payor funding source;
credit a payor wallet with a CBDC amount, wherein the CBDC amount is equivalent to the second purchase amount;
generate a second transfer from a payor wallet address to a payee wallet address for the CBDC amount; and
transmit the second transfer to the digital currency network.

### Claim 20 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the payment event is placed on the event stream by an internet-of-things (IoT) device.
