# US 10,482,467 B1 · Systems and methods for blocking credit card charges > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,482,467 B1 - Document ID: US10482467B1 - Status: Granted - Kind: B1 - Application number: 16/008,469 - Filed: 2018-06-14 - Granted: 2019-11-19 - Earliest claimed: 2018-06-14 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Jeffrey Samitt; Zeel Maharshi Jha; Colleen Kerr; Henry Feer Joyce; Joshua M. Wilbur; John William Schmidt; Krystle Voss; Riken Shah - Web page: https://patentgrep.com/patent/US10482467B1 ## CPC - G06Q 20/407: {Cancellation of a transaction} - G06Q 20/401: {Transaction verification} - G06Q 20/4093: {Monitoring of device authentication} - 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 Systems and methods are provided for blocking charges from a merchant to a payment account of a user. An exemplary system may include one or more memory devices storing instructions and one or more processors configured to execute the instructions to perform various operations. The operations may include receiving, from the user, a dispute request to dispute a charge to the payment account applied by the merchant. In response to the dispute request, the operations may include determining whether to block subsequent charges applied by the merchant to the payment account, based on a history of charging activities of the merchant. Responsive to a determination to block subsequent charges, the operations may include adding the merchant to a block-charge list associated with the payment account. ## Claims ### Claim 1 A system for blocking merchant charges to a payment account of a user, the system comprising: one or more memory devices storing instructions; and one or more processors configured to execute the instructions to perform operations comprising: receiving, from a user device, a dispute request of a charge by a merchant to the payment account; identifying the merchant associated with the dispute request; in response to receiving the dispute request, determining whether to block subsequent charges applied by the merchant to the payment account based on a history of charging activities of the merchant; providing instructions to the user device to display an application interface for the user to accept or decline blocking subsequent charges by the merchant; receiving, via the user device, the user's input to accept blocking subsequent charges by the merchant; responsive to the receipt of the user's input to block subsequent charges, adding the merchant to a block-charge list associated with the payment account; receiving a transaction authorization request to charge the payment account; determining whether the merchant on the block-charge list initiated the transaction authorization request; and responsive to the determination that the merchant on the block-charge list initiated the transaction authorization request, declining the transaction authorization request. ### Claim 2 (depends on 1) The system of claim 1, wherein: the history of charging activities comprises a number of dispute requests received against the merchant; and the operations comprise determining to block subsequent charges applied by the merchant to the payment account when the number of dispute requests received against the merchant exceeds a predetermined threshold. ### Claim 3 (depends on 1) The system of claim 1, wherein: the history of charging activities comprises a number of dispute requests received from the user against the merchant; and the operations comprise determining to block subsequent charges applied by the merchant to the payment account when the number of dispute requests received from the user against the merchant exceeds a predetermined threshold. ### Claim 4 (depends on 1) The system of claim 1, wherein: the history of charging activities of the merchant comprises a number of repeated charges applied by the merchant to the payment account; and the operations comprise determining to block subsequent charges applied by the merchant to the payment account when the number of the repeated charges exceeds a predetermined threshold. ### Claim 5 (depends on 1) The system of claim 1, wherein adding the merchant to the block-charge list comprises: determining a merchant identifier identifying the merchant; and adding the merchant identifier to the block-charge list. ### Claim 6 (depends on 5) The system of claim 5, wherein the operations comprise: determining a merchant identification code based on the transaction authorization request; determining whether the merchant identification code matches the merchant identifier in the block-charge list; and responsive to the determination that the merchant identification code matches the merchant identifier in the block-charge list, determining that the merchant on the block-charge list initiated the transaction authorization request. ### Claim 7 (depends on 1) The system of claim 1, wherein the operations comprise: determining a reputation score for the merchant based on the history of charging activities of the merchant; and adding the merchant to the block-charge list when the reputation score is below a predetermined threshold. ### Claim 8 (depends on 7) The system of claim 7, wherein the reputation score is based on at least one of: a number of dispute requests received against the merchant; a number of repeated charges applied by the merchant to the payment account; or a number of dispute requests received from the user against the merchant. ### Claim 9 (depends on 7) The system of claim 7, wherein the operations comprise: updating the reputation score of the merchant based on the dispute request received from the user. ### Claim 10 (depends on 1) The system of claim 1, wherein the operations comprise: removing the merchant from the block-charge list after a predetermined period of time. ### Claim 11 A computer-implemented method for blocking merchant charges to a payment account of a user, the method comprising: receiving, from a user device, a dispute request of a charge by a merchant to the payment account; identifying the merchant associated with the dispute request; in response to the dispute request, determining whether to block subsequent charges applied by the merchant to the payment account based on a history of charging activities of the merchant; providing instructions to the user device to display an application interface for the user to accept or decline blocking subsequent charges by the merchant; receiving, via the user device, the user's input to accept blocking subsequent charges by the merchant; responsive to the receipt of the user's input to block subsequent charges, adding the merchant to a block-charge list associated with the payment account; receiving a transaction authorization request to charge the payment account; determining whether the merchant on the block-charge list initiated the transaction authorization request; and responsive to the determination that the merchant on the block-charge list initiated the transaction authorization request, declining the transaction authorization request. ### Claim 12 (depends on 11) The computer-implemented method of claim 11, wherein: the history of charging activities of the merchant comprises a number of dispute requests received against the merchant; and the method comprises determining to block subsequent charges applied by the merchant to the payment account when the number of dispute requests received against the merchant exceeds a predetermined threshold. ### Claim 13 (depends on 11) The computer-implemented method of claim 11, wherein: the history of charging activities of the merchant comprises a number of dispute requests received from the user against the merchant; and the method comprises determining to block subsequent charges applied by the merchant to the payment account when the number of dispute requests received from the user against the merchant exceeds a predetermined threshold. ### Claim 14 (depends on 11) The computer-implemented method of claim 11, wherein: the history of charging activities of the merchant comprises a number of repeated charges applied by the merchant to the payment account; and the method comprises determining to block subsequent charges applied by the merchant to the payment account when the number of the repeated charges exceeds a predetermined threshold. ### Claim 15 (depends on 11) The computer-implemented method of claim 11, wherein adding the merchant to the block-charge list comprises: determining a merchant identifier identifying the merchant; and adding the merchant identifier to the block-charge list. ### Claim 16 (depends on 15) The computer-implemented method of claim 15, further comprising: determining a merchant identification code based on the transaction authorization request; determining whether the merchant identification code matches the merchant identifier in the block-charge list; and responsive to the determination that the merchant identification code matches the merchant identifier in the block-charge list, determining that the merchant on the block-charge list initiated the transaction authorization request. ### Claim 17 (depends on 11) The computer-implemented method of claim 11, further comprising: determining a reputation score for the merchant based on the history of charging activities of the merchant; and adding the merchant to the block-charge list when the reputation score is below a predetermined threshold. ### Claim 18 (depends on 17) The computer-implemented method of claim 17, wherein the reputation score is based on at least one of: a number of dispute requests received against the merchant; a number of repeated charges applied by the merchant to the payment account; or a number of dispute requests received from the user against the merchant. ### Claim 19 (depends on 17) The computer-implemented method of claim 17, further comprising: updating the reputation score of the merchant based on the dispute request received from the user. ### Claim 20 A non-transitory computer-readable medium storing instructions executable by a processor to cause the processor to perform operations for blocking merchant charges to a payment account of a user, the operations comprising: receiving, from a user device, a dispute request of a charge by a merchant to the payment account; identifying the merchant associated with the dispute request; in response to the dispute request, determining whether to block subsequent charges applied by the merchant to the payment account based on a history of charging activities of the merchant; providing instructions to the user device to display an application interface for the user to accept or decline blocking subsequent charges by the merchant; receiving, via the user device, the user's input to accept blocking subsequent charges by the merchant; responsive to the determination to block subsequent charges, adding the merchant to a block-charge list associated with the payment account; receiving a transaction authorization request to charge the payment account; determining whether the merchant on the block-charge list initiated the transaction authorization request; and responsive to the receipt of the user's input that the merchant on the block-charge list initiated the transaction authorization request, declining the transaction authorization request.