# US 2022/0027873 A1 · Peer-to-peer (p2p) payment with security protection for payee

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

- Number: US 2022/0027873 A1
- Document ID: US20220027873A1
- Status: Published application
- Kind: A1
- Application number: 16/938,434
- Filed: 2020-07-24
- Published: 2022-01-27
- Earliest claimed: 2020-07-24
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Sai PATHURI; Harrison FESEL; Sreenivasa Chandrasekhar NARASINGOLU; Justin PINSKY; Rajeev KRISHNAN; Fnu Sushil KUMAR
- Web page: https://patentgrep.com/patent/US20220027873A1

## CPC

- G06Q 20/108: {Remote banking, e.g. home banking}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06K 7/1417: {2D bar codes}
- G06K 19/06037: {multi-dimensional coding}
- G06Q 20/023: {the neutral party being a clearing house}
- G06Q 20/0855: {involving a third party}
- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 20/223: {based on the use of peer-to-peer networks}
- G06Q 20/3274: {using a pictured code, e.g. barcode or QR-code, being displayed on the M-device}
- G06Q 20/3276: {using a pictured code, e.g. barcode or QR-code, being read by the M-device}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/407: {Cancellation of a transaction}
- G06Q 20/42: Confirmation, e.g. check or permission by the legal debtor of payment
- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- H04L 67/104: Peer-to-peer [P2P] networks
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06K: GRAPHICAL DATA READING (image or video recognition or understanding G06V); PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

System, apparatus, device, method and/or computer program product are disclosed for making a payment by a customer to a merchant using a peer-to-peer (P2P) payment identification of the customer for a commercial transaction between the merchant and the customer. Embodiments herein provide security protection to the merchant by not revealing a P2P payment identification of the merchant to the customer. A payment request including a customer-facing merchant identification to identify the merchant to the customer is sent to the customer, where the customer-facing merchant identification is different from the P2P payment identification of the merchant. The system is further integrated with a merchant server and the P2P payment system to fulfill the payment to the merchant, to track a status of the payment request, and to determine a status of the commercial transaction between the merchant and the customer.

## Claims

### Claim 1

A system, comprising:
a storage device; and
a processor coupled to the storage device and configured to:
receive a peer-to-peer (P2P) payment identification of a customer, wherein the P2P payment identification of the customer identifies the customer in a P2P payment system;
generate a payment request to initiate a payment over the P2P payment system from the customer to a merchant for a commercial transaction between the merchant and the customer, wherein the payment request includes a customer-facing merchant identification to identify the merchant to the customer;
send the payment request to the customer through a communication channel associated with the P2P payment identification of the customer;
receive, from the customer, a response to the payment request, wherein the received response from the customer indicates an approval of the payment request; and
send, to the P2P payment system, an instruction to fulfill the payment to the merchant from the customer, wherein the instruction includes the approval of the payment request, a P2P payment identification of the merchant, and the P2P payment identification of the customer, wherein the P2P payment identification of the merchant identifies the merchant in the P2P payment system.

### Claim 2 (depends on 1)

The system of claim 1, wherein the customer-facing merchant identification is different from the P2P payment identification of the merchant.

### Claim 3 (depends on 1)

The system of claim 1, wherein the processor is further configured to:
track a status of the payment request; and
determine, based on the status of the payment request, a status of the commercial transaction between the merchant and the customer.

### Claim 4 (depends on 1)

The system of claim 1, wherein the processor is further configured to receive an amount to be paid from the customer to the merchant associated with the commercial transaction, and wherein the payment request indicates the amount to be paid from the customer to the merchant associated with the commercial transaction.

### Claim 5 (depends on 1)

The system of claim 1, wherein the P2P payment identification of the customer is received from a merchant server associated with the merchant and coupled to the system.

### Claim 6 (depends on 1)

The system of claim 1, wherein the instruction to fulfill the payment comprises an instruction to transfer funds from a monetary account of the customer to a monetary account of the merchant.

### Claim 7 (depends on 1)

The system of claim 1, wherein the system is located on a third-party system in communication with the P2P payment system, a merchant server associated with the merchant, and a customer device associated with the customer.

### Claim 8 (depends on 1)

The system of claim 1, wherein the P2P payment identification of the customer includes an email address or a telephone number of the customer.

### Claim 9 (depends on 1)

The system of claim 1, wherein the P2P payment identification of the customer is associated with a bank account of the customer, the P2P payment identification of the merchant is associated with a bank account of the merchant, and the P2P payment system communicates with an Automated Clearing House (ACH) payment system to transfer funds from the bank account of the customer to the bank account of the merchant.

### Claim 10 (depends on 1)

The system of claim 1, wherein the received response is a first response, and the processor is further configured to:
receive, from the customer, a second response to the payment request, wherein the second response indicates a cancellation of the payment request; and
send, to a merchant server associated with the merchant, an instruction to stop fulfilling the commercial transaction between the merchant and the customer.

### Claim 11

A computer-implemented method for making a payment, comprising:
receiving, by an application program interface (API) operated by a processor, a peer-to-peer (P2P) payment identification of a customer, wherein the P2P payment identification of the customer identifies the customer in a P2P payment system;
determining a customer-facing merchant identification to identify a merchant to the customer, wherein the customer-facing merchant identification is different from a P2P payment identification of the merchant that identifies the merchant in the P2P payment system;
generating a payment request to initiate a payment over the P2P payment system from the customer to the merchant for a commercial transaction between the merchant and the customer, wherein the payment request includes the customer-facing merchant identification, and an amount to be paid from the customer to the merchant;
sending the payment request to a customer device associated with the P2P payment identification of the customer;
receiving, from the customer device, a response to the payment request, wherein the response indicates an approval of the payment request by the customer; and
sending to the P2P payment system, an instruction to fulfill the payment to the merchant from the customer, wherein the instruction includes the approval of the payment request, the P2P payment identification of the merchant, and the P2P payment identification of the customer.

### Claim 12 (depends on 11)

The computer-implemented method of claim 11, wherein the P2P payment identification of the customer is associated with a bank account of the customer, the P2P payment identification of the merchant is associated with a bank account of the merchant, and the P2P payment system, upon receiving the instruction to fulfill the payment, communicates with an Automated Clearing House (ACH) payment system to transfer funds from the bank account of the customer to the bank account of the merchant.

### Claim 13 (depends on 11)

The computer-implemented method of claim 11, further comprising:
tracking a status of the payment request; and
determining, based on the status of the payment request, a status of the commercial transaction between the merchant and the customer.

### Claim 14 (depends on 11)

The computer-implemented method of claim 11, wherein the P2P payment identification of the customer is received in response to a request made by a merchant server during a shopping flow by the customer.

### Claim 15 (depends on 14)

The computer-implemented method of claim 14, wherein the P2P payment identification of the customer is submitted at a checkout time of an online shopping activity by the customer.

### Claim 16 (depends on 11)

The computer-implemented method of claim 11, wherein the P2P payment identification of the customer is received from a QR code.

### Claim 17 (depends on 11)

The computer-implemented method of claim 11, wherein the P2P payment identification of the customer includes an email address or a telephone number of the customer.

### Claim 18 (depends on 11)

The computer-implemented method of claim 11, wherein the customer-facing merchant identification includes a name of the merchant or a logo of the merchant to identify the merchant to the customer.

### Claim 19

A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:
receiving a peer-to-peer (P2P) payment identification of a customer, wherein the P2P payment identification of the customer identifies the customer in a P2P payment system;
generating a payment request to initiate a payment over the P2P payment system from the customer to a merchant for a commercial transaction between the merchant and the customer, wherein the payment request includes a customer-facing merchant identification to identify the merchant to the customer, and an amount to be paid from the customer to the merchant;
sending the payment request to the customer through a communication channel associated with the P2P payment identification of the customer;
receiving, from the customer, a response to the payment request, wherein the response indicates an approval of the payment request; and
sending, to the P2P payment system, an instruction to fulfill the payment to the merchant from the customer, wherein the instruction includes the approval of the payment request, a P2P payment identification of the merchant, and the P2P payment identification of the customer, wherein the P2P payment identification of the merchant identifies the merchant in the P2P payment system.

### Claim 20 (depends on 19)

The non-transitory computer-readable device of claim 19, wherein the P2P payment identification of the customer includes an email address or a telephone number of the customer, and wherein the customer-facing merchant identification includes a name of the merchant or a logo of the merchant to identify the merchant to the customer.
