Contextual tapping engine
US-10636241-B1 · Apr 28, 2020 · US
US11455606B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11455606-B2 |
| Application number | US-202016863658-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 30, 2020 |
| Priority date | Apr 30, 2020 |
| Publication date | Sep 27, 2022 |
| Grant date | Sep 27, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1. 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 computing device, wherein a uniform resource locator specifies the one or more endpoints for the user computing device to send the authentication payload; decrypt the authentication payload and compare a customer identifier from the authentication payload against customer authentication information; if the customer identifier and the customer authentication information match, confirm the authentication of the user as being successful; 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. 2. The system of claim 1 , 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. 3. The system of claim 1 , 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. 4. The system of claim 3 , 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. 5. 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 computing device, wherein a uniform resource locator (URL) specifies the one or more endpoints for the user computing device to send the authentication payload; decrypting the authentication payload and compare a customer identifier from the authentication payload against customer authentication information; if the customer identifier and the customer authentication information match, confirming the authentication of the user as being successful; 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. 6. The method of claim 5 , 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. 7. The method of claim 5 , 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. 8. The method of claim 7 , 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. 9. A non-transitory computer-readable medium, comprising instructions executable by processing circuitry, that when executed cause the processing circuitry 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 computing device, wherein a uniform resource locator specifies the one or more endpoints for the user computing device to send the authentication payload; decrypt the authentication payload and compare a customer identifier from the authentication payload against customer authentication information; if the customer identifier and the customer authentication information match, confirm the authentication of the user as being successful; 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. 10. The non-transitory computer readable of claim 9 , 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. 11. The non-transitory computer readable of claim 9 , 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. 12. The non-transitory computer readable of claim 9 , 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.
Use of secure elements separate from M-devices · CPC title
specially adapted for electronic shopping systems · CPC title
RFID or NFC payments by means of M-devices · CPC title
insuring higher security of transaction · CPC title
specially adapted for billing systems · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.