# US 2024/0257085 A1 · Token Account Payment Computing System

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

- Number: US 2024/0257085 A1
- Document ID: US20240257085A1
- Status: Published application
- Kind: A1
- Application number: 18/161,667
- Filed: 2023-01-30
- Published: 2024-08-01
- Earliest claimed: 2023-01-30
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: Jesika Gandhi; Jeetendra Hukmichand Jain
- Web page: https://patentgrep.com/patent/US20240257085A1

## CPC

- G06Q 20/108: {Remote banking, e.g. home banking}
- G06Q 20/385: {using an alias or single-use codes}
- G06Q 20/102: {Bill distribution or payments}
- G06Q 20/227: {characterised in that multiple accounts are available, e.g. to the payer}
- G06Q 20/351: {Virtual cards}
- G06Q 20/405: {Establishing or using transaction specific rules}
- 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

Various aspects of the disclosure relate to creation, management, and use of electronic payment tokens to facilitate coordination of payments for products and/or services. A payment token account system may facilitate creation of a payment token account and an associated payment token to electronically receive deposit from one or more sources and to complete an electronic payment transaction. Each payment token may be separately enabled and disabled and may be associated as a backup to another payment account to ensure a payment transaction may be completed when a payment network associated with the payment account is down or otherwise unavailable.

## Claims

### Claim 1

A system comprising:
a payment computing system initiating an electronic payment transaction;
a payment token account platform, comprising:
at least one processor; and
non-transitory memory storing computer-readable instructions that, when executed by the at least one processor, cause the payment token account platform to:
generate, based on a user request, a payment token;
configure, based on user input received from a user device, the payment token, wherein a payment token configuration defines use cases for the payment token;
receive, via a network and from a deposit computing system, an electronic funds deposit request;
accept, based on the configuration, the electronic funds deposit;
receive, via a network and from the payment computing system, a payment request associated with the electronic payment transaction;
initiate payment, via the payment token, to a deposit account associated with the electronic payment transaction, based on a payment token configuration; and
send, via the network and to the payment computing system, confirmation of completion of the electronic payment transaction.

### Claim 2 (depends on 1)

The system of claim 1, wherein the instructions further cause the payment token account platform to:
present, at a user device, a payment token configuration screen; and
solicit, via the payment token configuration screen, a configuration of the payment token.

### Claim 3 (depends on 1)

The system of claim 1, wherein the instructions further cause the payment token account platform to associate a virtual card number to the payment token.

### Claim 4 (depends on 3)

The system of claim 3, wherein the instructions further cause the payment token account platform to:
identify, based on the virtual card number, from the electronic payment transaction.

### Claim 5 (depends on 1)

The system of claim 1, wherein the instructions further cause the payment token account platform to:
associate a group of users with permissions to deposit funds to the token account; and
solicit, via messages sent via the network to each user of the group of users, deposit of funds via one or more electronic transactions.

### Claim 6 (depends on 1)

The system of claim 1, wherein the instructions further cause the payment token account platform to associate a second group of users with permissions to initiate a payment transaction using the token account.

### Claim 7 (depends on 1)

The system of claim 1, wherein the payment token configuration comprises one or both of an enablement flag and an association with a payment account.

### Claim 8 (depends on 7)

The system of claim 7, wherein the payment account is a credit card, where configuration specifies that the payment token is used for payments when a credit card network is unavailable.

### Claim 9 (depends on 1)

The system of claim 1, wherein the payment token is associated with a payment token account.

### Claim 10 (depends on 1)

The system of claim 1, wherein the payment token is associated with a payment token account and wherein the payment token account is associated with a plurality of payment tokens, each payment token of the plurality of payment tokens having a different configuration.

### Claim 11

A method comprising:
generating, based on a user request, a payment token;
configuring, based on user input received from a user device, the payment token, wherein a payment token configuration defines use cases for the payment token;
receiving, via a network and from a deposit computing system, an electronic funds deposit request;
accepting, based on the configuration, the electronic funds deposit;
receiving, via a network and from the payment computing system, a payment request associated with an electronic payment transaction received from a vendor transaction computing system;
initiating payment, via the payment token, to a deposit account associated with the electronic payment transaction, based on the payment token configuration; and
sending, via the network and to the payment computing system, confirmation of completion of the electronic payment transaction.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
presenting, at a user device, a payment token configuration screen; and
soliciting, via the payment token configuration screen, a configuration of the payment token.

### Claim 13 (depends on 11)

The method of claim 11, further comprising associating a virtual card number to the payment token.

### Claim 14 (depends on 13)

The method of claim 13, further comprising identifying, based on the virtual card number, from the electronic payment transaction.

### Claim 15 (depends on 11)

The method of claim 11, further comprising:
associating a group of users with permissions to deposit funds to the token account; and
soliciting, via messages sent via the network to each user of the group of users, deposit of funds via one or more electronic transactions.

### Claim 16 (depends on 11)

The method of claim 11, further comprising associating a second group of users with permissions to initiate a payment transaction using the token account.

### Claim 17 (depends on 11)

The method of claim 11, wherein the payment token configuration comprises one or both of an enablement flag and an association with a payment account.

### Claim 18 (depends on 11)

The method of claim 11, wherein the payment account is a credit card, where configuration specifies that the payment token is used for payments when a credit card network is unavailable.

### Claim 19 (depends on 11)

The method of claim 11, wherein the payment token is associated with a payment token account.

### Claim 20 (depends on 11)

The method of claim 11, wherein the payment token is associated with a payment token account and wherein the payment token account is associated with a plurality of payment tokens, each payment token of the plurality of payment tokens having a different configuration.
