# US 2026/0030612 A1 · Transferring payments using scanned barcodes

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

- Number: US 2026/0030612 A1
- Document ID: US20260030612A1
- Status: Published application
- Kind: A1
- Application number: 19/349,691
- Filed: 2025-10-03
- Published: 2026-01-29
- Earliest claimed: 2023-01-03
- Assignees: American Express Travel Related Services Company, Inc.
- Applicants: American Express Travel Related Services Company, Inc.
- Inventors: Edson MANCILLA
- Web page: https://patentgrep.com/patent/US20260030612A1

## CPC

- G06Q 20/3276: {using a pictured code, e.g. barcode or QR-code, being read by the M-device}
- G06Q 20/065: {using e-cash}
- G06Q 20/102: {Bill distribution or payments}
- G06Q 20/3223: {Realising banking transactions through M-devices}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 20/42: Confirmation, e.g. check or permission by the legal debtor of payment
- 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

A system for making payments is disclosed. The system performs steps to at least receive a barcode with embedded information linking to a payee account capable of receiving a payment. Based on receiving the barcode a prompt for display on a browser of the user device can be generated, where the prompt requests identification of a financial institution connected to a user of the user device. The prompt can be transmitted to the user device. Identifying information identifying the financial institution can be received in response to the prompt. The financial institution can be accessed based on the response to the prompt. Based on accessing the user financial institution a request for the payment from the user financial institution to the payee account can be made.

## Claims

### Claim 1

A computer implemented method for establishing a connection between a first system implementing a first financial account and a second system implementing a second financial account via an intermediary server, the method comprising:
receiving, by the intermediary server and from a client device, embedded information from a scanned image of an optical label, wherein the embedded information comprises payee information and connection information for the second system implementing the second financial account, and wherein the client device is associated with a payer user and the payee information is associated with a payee user;
transmitting, responsive to receiving the embedded information, a first graphical user interface to the client device, wherein the first graphical user interface is configured to display a request for user confirmation to proceed with establishing the connection with the first system implementing the first financial account;
transmitting, responsive to receiving the user confirmation, a second graphical user interface to the client device, wherein the second graphical user interface is configured with an input field for receiving identifying information of the first system;
receiving the identifying information from the client device;
establishing, by the intermediary server based on the identifying information and without receiving from the client device additional information associated with the payer user and the payee user, the connection between the first system and the second system; and
facilitating, by the intermediary server via the connection, transfer of a payment amount from the first system to the second system.

### Claim 2 (depends on 1)

The method of claim 1, wherein establishing the connection comprises:
determining, by the intermediary server, whether a software application associated with the first system is installed on the client device; and
accessing the software application to obtain user credentials from the software application by authenticating the user via the software application and biometric information to access the first financial account via an application programing interface (API) integration with the first system upon determining that the software application is installed on the client device,
wherein facilitating the transfer of the payment amount from the first system to the second system is based upon obtaining the user credentials and via the API integration, and
wherein the transfer of the payment amount comprises a push payment via the connection.

### Claim 3 (depends on 1)

The method of claim 1, wherein the payee information comprises a minimum amount for the payment accepted by the payee, and wherein the payment amount comprises the minimum amount.

### Claim 4 (depends on 1)

The method of claim 1, wherein the transfer of the payment amount comprises a payment stream.

### Claim 5 (depends on 4)

The method of claim 4, wherein the connection comprises a real-time-payment (RTP) connection, wherein the payment stream comprises multiple payment transactions between the first system and the second system, and wherein a first payment transaction of the multiple payment transactions is received in real-time via the RTP connection.

### Claim 6 (depends on 5)

The method of claim 5, wherein subsequent payment transactions of the multiple payment transactions are transferred from the first financial account to the second financial account via the RTP connection.

### Claim 7 (depends on 1)

The method of claim 1, wherein establishing the connection comprises:
determining that the software application is not installed on the client device;
requesting user credentials from the client device; and
invoking a third-party API to interface with the financial institution responsive to receiving the user credentials, wherein the connection between the first system and the second system is establishing via the third-party API.

### Claim 8

A non-transitory computer readable medium having instructions stored thereon for establishing a connection between a first system implementing a first financial account and a second system implementing a second financial account via an intermediary server, causes the intermediary server to perform operations comprising:
receiving, by the intermediary server and from a client device, embedded information from a scanned image of an optical label, wherein the embedded information comprises payee information and connection information for the second system implementing the second financial account, and wherein the client device is associated with a payer user and the payee information is associated with a payee user;
transmitting, responsive to receiving the embedded information, a first graphical user interface to the client device, wherein the first graphical user interface is configured to display a request for user confirmation to proceed with establishing the connection with the first system implementing the first financial account;
transmitting, responsive to receiving the user confirmation, a second graphical user interface to the client device, wherein the second graphical user interface is configured with an input field for receiving identifying information of the first system;
receiving the identifying information from the client device;
establishing, by the intermediary server based on the identifying information and without receiving from the client device additional information associated with the payer user and the payee user, the connection between the first system and the second system; and
facilitating, by the intermediary server via the connection, transfer of a payment amount from the first system to the second system.

### Claim 9 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein in establishing the connection, the operations further comprise:
determining, by the intermediary server, whether a software application associated with the first system is installed on the client device; and
accessing the software application to obtain user credentials from the software application by authenticating the user via the software application and biometric information to access the first financial account via an application programing interface (API) integration with the first system upon determining that the software application is installed on the client device,
wherein facilitating the transfer of the payment amount from the first system to the second system is based upon obtaining the user credentials and via the API integration, and
wherein the transfer of the payment amount comprises a push payment via the connection.

### Claim 10 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein the payee information comprises a minimum amount for the payment accepted by the payee, and wherein the payment amount comprises the minimum amount.

### Claim 11 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein the transfer of the payment amount comprises a payment stream.

### Claim 12 (depends on 11)

The non-transitory computer readable medium of claim 11, wherein the connection comprises a real-time-payment (RTP) connection, wherein the payment stream comprises multiple payment transactions between the first system and the second system, and wherein a first payment transaction of the multiple payment transactions is received in real-time via the RTP connection.

### Claim 13 (depends on 12)

The non-transitory computer readable medium of claim 12, wherein subsequent payment transactions of the multiple payment transactions are transferred from the first financial account to the second financial account via the RTP connection.

### Claim 14 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein in establishing the connection, the operations further comprise:
determining that the software application is not installed on the client device;
requesting user credentials from the client device; and
invoking a third-party API to interface with the financial institution responsive to receiving the user credentials, wherein the connection between the first system and the second system is establishing via the third-party API.

### Claim 15

An intermediary computing system for establishing a connection between a first system implementing a first financial account and a second system implementing a second financial account comprising:
a memory configured to store instructions; and
one or more processors, coupled to the memory and configured to execute the instructions to perform operations comprising:
receiving, by the intermediary server and from a client device, embedded information from a scanned image of an optical label, wherein the embedded information comprises payee information and connection information for the second system implementing the second financial account, and wherein the client device is associated with a payer user and the payee information is associated with a payee user;
transmitting, responsive to receiving the embedded information, a first graphical user interface to the client device, wherein the first graphical user interface is configured to display a request for user confirmation to proceed with establishing the connection with the first system implementing the first financial account;
transmitting, responsive to receiving the user confirmation, a second graphical user interface to the client device, wherein the second graphical user interface is configured with an input field for receiving identifying information of the first system;
receiving the identifying information from the client device;
establishing, by the intermediary server based on the identifying information and without receiving from the client device additional information associated with the payer user and the payee user, the connection between the first system and the second system; and
facilitating, by the intermediary server via the connection, transfer of a payment amount from the first system to the second system.

### Claim 16 (depends on 15)

The computing system of claim 15, wherein in establishing the connection, the operations further comprise:
determining, by the intermediary server, whether a software application associated with the first system is installed on the client device; and
accessing the software application to obtain user credentials from the software application by authenticating the user via the software application and biometric information to access the first financial account via an application programing interface (API) integration with the first system upon determining that the software application is installed on the client device,
wherein facilitating the transfer of the payment amount from the first system to the second system is based upon obtaining the user credentials and via the API integration, and
wherein the transfer of the payment amount comprises a push payment via the connection.

### Claim 17 (depends on 15)

The computing system of claim 15, wherein the transfer of the payment amount comprises a payment stream.

### Claim 18 (depends on 15)

The computing system of claim 15, wherein the transfer of the payment amount comprises a payment stream.

### Claim 19 (depends on 18)

The computing system of claim 18, wherein the connection comprises a real-time-payment (RTP) connection, wherein the payment stream comprises multiple payment transactions between the first system and the second system, and wherein a first payment transaction of the multiple payment transactions is received in real-time via the RTP connection.

### Claim 20 (depends on 19)

The computing system of claim 19, wherein subsequent payment transactions of the multiple payment transactions are transferred from the first financial account to the second financial account via the RTP connection.
