# US 2023/0066397 A1 · Remotely sharing a payment instrument to a client device

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

- Number: US 2023/0066397 A1
- Document ID: US20230066397A1
- Status: Published application
- Kind: A1
- Application number: 17/412,182
- Filed: 2021-08-25
- Published: 2023-03-02
- Earliest claimed: 2021-08-25
- Assignees: American Express Travel Related Services Company, Inc.
- Applicants: American Express Travel Related Services Company, Inc.
- Inventors: Pankaj Mehla; Anuj Goyal; Anthony Jaleel Wooten; Yogesh Edekar; Moses Godinez; Sridevi Majeti; Sharad Kumar; Nicholas Martinez
- Web page: https://patentgrep.com/patent/US20230066397A1

## CPC

- G06Q 20/2295: {Parent-child type, e.g. where parent has control on child rights}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/065: {using e-cash}
- G06Q 20/227: {characterised in that multiple accounts are available, e.g. to the payer}
- G06Q 20/3274: {using a pictured code, e.g. barcode or QR-code, being displayed on the M-device}
- G06Q 20/351: {Virtual cards}
- G06Q 20/363: {with the personal data of a user}
- 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 embodiments for remotely sharing a payment instrument of a first user to a client device of a second user are provided. In some embodiments, a system is configured to receive a first request from a first client device to generate a beneficiary user for a payment instrument account. The system is configured to receive a second request from the first client device in order to generate a virtual payment instrument, and the second request comprises a spending policy. The system is configured to generate the virtual payment instrument for the beneficiary identifier based at least in part on the spending policy and configured to transmit a reference notification for accessing the virtual payment instrument to a second client device. The virtual payment instrument is configured to be restricted for a purchase based at least in part on the spending policy.

## 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:
receive a first request from a first client device to generate a beneficiary user for a payment instrument account, the first request comprising beneficiary user data;
generate a beneficiary identifier for the beneficiary user based at least in part on the beneficiary user data, wherein the beneficiary identifier is associated with the payment instrument account;
receive a second request from the first client device to generate a virtual payment instrument for the beneficiary identifier, the second request comprising a spending policy;
generate the virtual payment instrument for the beneficiary identifier based at least in part on the spending policy; and
transmit a notification for accessing the virtual payment instrument to a second client device based at least in part on the beneficiary user data, wherein the virtual payment instrument is configured to be restricted for a purchase based at least in part on the spending policy.

### Claim 2 (depends on 1)

The system of claim 1, wherein the spending policy comprises at least one of an amount that can be paid using the payment instrument account, a start date for the virtual payment instrument, an ending date for the virtual payment instrument, or a spend frequency for the virtual payment instrument.

### Claim 3 (depends on 1)

The system of claim 1, wherein the machine-readable instructions, when executed by the processor, cause the computing device to at least:
receive an indication that the second client device has activated a hyperlink from the notification;
transmit data for displaying an authentication user interface on the second client device; and
authenticate the beneficiary identifier based at least in part on receiving a user credential from the second client device.

### Claim 4 (depends on 1)

The system of claim 1, wherein the machine-readable instructions, when executed by the processor, cause the computing device to at least:
receive an indication that the second client device has activated a hyperlink from the notification;
transmit data for displaying a user interface on the second client device;
receive beneficiary profile data from the user interface, wherein the beneficiary profile data comprises a device identifier associated with the second client device; and
configure the beneficiary identifier for the beneficiary user based at least in part on the beneficiary profile data from the user interface.

### Claim 5 (depends on 4)

The system of claim 4, wherein the machine-readable instructions, when executed by the processor, cause the computing device to at least:
store the device identifier of the second client device in association with the beneficiary identifier.

### Claim 6 (depends on 4)

The system of claim 4, wherein the machine-readable instructions, when executed by the processor, cause the computing device to at least:
transmit to the second client device a second hyperlink for a beneficiary wallet application, wherein upon activation, the second hyperlink directs the second client device to download the beneficiary wallet application.

### Claim 7 (depends on 1)

The system of claim 1, wherein the machine-readable instructions, when executed by the processor, cause the computing device to at least:
transmit to the second client device a digital token associated with the beneficiary identifier in response to configuring the beneficiary identifier for the second client device.

### Claim 8

A computer-implemented method comprising:
displaying, by a client device, a beneficiary user interface for creating a beneficiary user;
obtaining, by the client device, beneficiary user data using the beneficiary user interface;
transmitting, by the client device, to a computing device the beneficiary user data for generating the beneficiary user, wherein the beneficiary user is associated with a payment instrument account of the client device;
displaying, by the client device, a virtual payment user interface for creating a virtual payment instrument associated with the beneficiary user;
receiving, by the client device, a spending policy from the virtual payment user interface;
transmitting, by the client device, to the computing device the spending policy for generating the virtual payment instrument, wherein the virtual payment instrument is associated with the beneficiary user; and
receiving, by the client device, from the computing device a reference notification for accessing the virtual payment instrument associated with the beneficiary user, wherein the virtual payment instrument is configured to be restricted for a purchase based at least in part on the spending policy.

### Claim 9 (depends on 8)

The method of claim 8, wherein the spending policy comprises at least one of an amount that can be paid using the payment instrument account, a start date for the virtual payment instrument, an ending date for the virtual payment instrument, or a spend frequency for the virtual payment instrument.

### Claim 10 (depends on 8)

The method of claim 8, wherein the spending policy comprises a first spending policy, and further comprising:
displaying, by the client device, a dashboard user interface which includes a status for the virtual payment instrument associated with the beneficiary user; and
transmitting, by the client device, a second spending policy to the computing device based at least in part on obtaining the second spending policy using the virtual payment user interface.

### Claim 11 (depends on 10)

The method of claim 10, wherein the status comprises a spending history for the virtual payment instrument associated with the beneficiary user.

### Claim 12 (depends on 8)

The method of claim 8, further comprising:
displaying, by the client device, a dashboard user interface that includes an indication that the beneficiary user has been generated and associated with the payment instrument account.

### Claim 13 (depends on 12)

The method of claim 12, wherein the dashboard user interface includes a virtual card user interface component that is configured to display the virtual payment user interface for generating a second virtual payment instrument in association with the payment instrument account.

### Claim 14 (depends on 12)

The method of claim 12, wherein the beneficiary user comprises a first beneficiary user, and the dashboard user interface includes a beneficiary user component that is configured to display the beneficiary user interface for adding a second beneficiary user in association with the payment instrument account.

### Claim 15

A non-transitory, computer-readable medium, comprising machine-readable instructions that, when executed by a processor of a client device, cause the client device to at least:
display a beneficiary user interface for creating a beneficiary user;
obtain beneficiary user data using the beneficiary user interface;
transmit to a computing device the beneficiary user data to generate a beneficiary user, wherein the beneficiary user is associated with a payment instrument account;
display a virtual payment user interface for creating a virtual payment instrument associated with the beneficiary user;
obtain a spending policy through the virtual payment user interface;
transmit to the computing device the spending policy for generating the virtual payment instrument, wherein the virtual payment instrument is associated with the beneficiary user; and
receive from the computing device a reference notification for accessing the virtual payment instrument associated with the beneficiary user, wherein the virtual payment instrument is configured to be restricted for a purchase based at least in part on the spending policy.

### Claim 16 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the spending policy comprises at least one of an amount that can be paid using the payment instrument account, a start date for the virtual payment instrument, an ending date for the virtual payment instrument, or a spend frequency for the virtual payment instrument.

### Claim 17 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the virtual payment user interface comprises an amount entry and a frequency entry.

### Claim 18 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the machine-readable instructions that, when executed by the processor, cause the client device to at least:
display a dashboard user interface that includes the hyperlink for the virtual payment instrument.

### Claim 19 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the spending policy comprises a first spending policy, and the machine-readable instructions that, when executed by the processor, cause the client device to at least:
display a dashboard user interface which includes a status for the virtual payment instrument associated with the beneficiary user; and
transmit a second spending policy to the computing device based at least in part on obtaining the second spending policy through the dashboard user interface.

### Claim 20 (depends on 19)

The non-transitory, computer-readable medium of claim 19, wherein the status comprises a spending history for the virtual payment instrument associated with the beneficiary user.
