# US 2021/0342809 A1 · Tap to pay credit bill

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

- Number: US 2021/0342809 A1
- Document ID: US20210342809A1
- Status: Published application
- Kind: A1
- Application number: 16/863,658
- Filed: 2020-04-30
- Published: 2021-11-04
- Earliest claimed: 2020-04-30
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Jeffrey RULE; Clayton JOHNSON
- Web page: https://patentgrep.com/patent/US20210342809A1

## CPC

- G06Q 20/382: {insuring higher security of transaction}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06F 21/35: communicating wirelessly
- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 20/14: specially adapted for billing systems
- G06Q 20/24: Credit schemes, i.e. "pay after"
- G06Q 20/3223: {Realising banking transactions through M-devices}
- G06Q 20/3226: {Use of secure elements separate from M-devices}
- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06Q 20/341: {Active cards, i.e. cards including their own processing means, e.g. including an IC or chip}
- G06Q 20/352: {Contactless payments by cards}
- G06Q 20/353: {Payments by cards read by M-devices}
- G06Q 20/409: {Device specific authentication in transaction processing}
- 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)

## Abstract

Various embodiments are directed to enhancing a card payment experience by a single tap of a contactless card to a user computing device. In examples, the single tap of the card may be preconfigured to cause automatic payment of a predefined amount toward a card balance. If the single tap is not preconfigured to mean automatic card payment, the user may be presented with a notification and various payment amount options, which the user can select to pay toward the card balance.

## Claims

### Claim at position 1

1-7. (canceled)

### Claim 8

A system comprising:
device memory; and
at least one processor operable to execute stored instructions that, when executed, cause the at least one processor to:
receive, at an application programming interface (API) endpoint of one or more API endpoints, an authentication payload from a contactless card via a user device, wherein a uniform resource locator specifies the one or more endpoints for the user device to send the authentication payload;
determine an occurrence of a single tap event based on receiving the authentication payload; and
in response to the occurrence of the single tap event:
apply a first payment amount to a card balance and send a first notification to the user computing device of successful card payment, the first payment amount being a predefined amount preconfigured by a user, or
send a second notification to the user computing device of a payment amount input request, receive an indication of a second payment amount from the user computing device in response to the second notification, apply the second payment amount to the card balance, and send a third notification to the user computing device of the successful card payment.

### Claim at position 3

9-10. (canceled)

### Claim 11 (depends on 8)

The system of claim 8, wherein the at least one processor is further caused to:
decrypt the authentication payload and compare a customer identifier from the authentication payload against customer authentication information, and
if the customer identifier and the customer authentication information match, confirm the authentication of the user as being successful.

### Claim 12 (depends on 11)

The system of claim 11, wherein, in response to the successful authentication of the user, payment of the predefined amount is automatically processed via the one or more API endpoints.

### Claim 13 (depends on 8)

The system of claim 8, wherein the payment amount input request comprises a plurality of payment amount options and wherein the indication of the second payment amount is one of the plurality payment amount options selected by the user.

### Claim 14 (depends on 13)

The system of claim 13, wherein the plurality of payment amount options includes paying all of a card balance, paying half of the card balance, paying a percentage of the card balance, or paying a minimum payment on the card balance.

### Claim 15

A method comprising:
receiving, by a system including an application programming interface (API) endpoint of one or more API endpoints, an authentication payload from a contactless card via a user device, wherein a uniform resource locator (URL) specifies the one or more endpoints for the user device to send the authentication payload;
determining, by the system, an occurrence of a single tap event based on receiving the authentication protocol; and
in response to the occurrence of the single tap event:
applying, by the system, a first payment amount to a card balance and sending a first notification to the user computing device of successful card payment, the first payment amount being a predefined amount preconfigured by a user, or
sending, by the system, a second notification to the user computing device of a payment amount input request, receiving an indication of a second payment amount from the user computing device in response to the second notification, applying the second payment amount to the card balance, and sending a third notification to the user computing device of the successful card payment.

### Claim at position 9

16-17. (canceled)

### Claim 18 (depends on 15)

The method of claim 15, further comprising:
decrypting the authentication payload and comparing a customer identifier from the authentication payload against customer authentication information, and
if the customer identifier and the customer authentication information match, confirming the authentication of the user as being successful.

### Claim 19 (depends on 18)

The method of claim 18, wherein, in response to the successful authentication of the user, payment of the predefined amount is automatically processed via the one or more API endpoints.

### Claim 20 (depends on 15)

The method of claim 15, wherein the payment amount input request comprises a plurality of payment amount options and wherein the indication of the second payment amount is one of the plurality payment amount options selected by the user.

### Claim 21 (depends on 20)

The method of claim 20, wherein the plurality of payment amount options includes paying all of a card balance, paying half of the card balance, paying a percentage of the card balance, or paying a minimum payment on the card balance.
