Systems and methods for blocking credit card charges

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.

What is claimed is: 
     
         1 . A system for blocking subsequent merchant charges, the system comprising:
 one or more memory devices storing instructions; and   one or more processors configured to execute the instructions to perform operations comprising:
 providing a first alert to a user device of a user, wherein the first alert comprises a first set of instructions to display an application interface for the user to accept or decline blocking merchant charges and first alert information comprising data related to blocking the merchant charges; 
 receiving, via the user device, a first user input to accept blocking the merchant charges; 
 determining whether a merchant will initiate an authorization request for a subsequent charge, wherein the subsequent charge is associated with an initial charge from the merchant; 
 responsive to determining that the merchant will initiate the authorization request, providing a second alert to the user device, wherein the second alert comprises a second set of instructions to the user device to display the application interface for the user to accept or decline blocking subsequent charges by the merchant and second alert information for displaying information related to the merchant; 
 receiving, via the user device, a second user input to accept blocking the subsequent charges by the merchant; 
 based on receiving the second user input to accept blocking the subsequent charges by the merchant, adding the merchant to a block-charge list; and 
 in response to receiving the second user input, providing a third alert to the user device, wherein the third alert comprises an identifier of the merchant and an indication that the subsequent charges from the merchant are blocked. 
   
     
     
         2 . The system of  claim 1 , wherein the one or more processors are further configured to execute the instructions to perform operations comprising:
 receiving, from the user device, a first authorization request associated with a payment account associated with the user; and   identifying the merchant associated with the first authorization request.   
     
     
         3 . The system of  claim 2 , wherein the one or more processors are further configured to perform operations comprising:
 determining a merchant identification code based on the first authorization request;   determining whether the merchant identification code matches a merchant identifier in the block-charge list; and   responsive to a 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 first authorization request.   
     
     
         4 . The system of  claim 2 , wherein the first alert to the user device of the user is provided in response to receiving the first authorization request. 
     
     
         5 . The system of  claim 1 , wherein the one or more processors are further configured to execute the instructions to perform operations comprising:
 responsive to receiving a second authorization request, determining that the merchant has been added to the block-charge list; and   responsive to determining that the merchant has been added to the block-charge list, declining the second authorization request.   
     
     
         6 . The system of  claim 5 , wherein the instructions further cause the one or more processors to perform operations comprising:
 updating a reputation score of the merchant based on the second authorization request; or   removing the merchant from the block-charge list after a period of time.   
     
     
         7 . The system of  claim 1 , wherein the instructions for adding the merchant to the block-charge list cause the one or more processors to perform operations comprising:
 determining a merchant identifier for the merchant; and   adding the merchant identifier to the block-charge list.   
     
     
         8 . A method comprising:
 providing a first alert to a user device of a user, wherein the first alert comprises a first set of instructions to display an application interface for the user to accept or decline blocking merchant charges and first alert information comprising data related to blocking the merchant charges;   receiving, via the user device, a first user input to accept blocking the merchant charges;   determining whether a merchant will initiate an authorization request for a subsequent charge, wherein the subsequent charge is associated with an initial charge from the merchant;   responsive to determining that the merchant will initiate the authorization request, providing a second alert to the user device, wherein the second alert comprises a second set of instructions to the user device to display the application interface for the user to accept or decline blocking subsequent charges by the merchant and second alert information for displaying information related to the merchant;   receiving, via the user device, a second user input to accept blocking the subsequent charges by the merchant;   based on receiving the second user input to accept blocking the subsequent charges by the merchant, adding the merchant to a block-charge list; and   in response to receiving the second user input, providing a third alert to the user device, wherein the third alert comprises an identifier of the merchant and an indication that the subsequent charges from the merchant are blocked.   
     
     
         9 . The method of  claim 8 , further comprising:
 receiving, from the user device, a first authorization request associated with a payment account of the user; and   identifying the merchant associated with the first authorization request.   
     
     
         10 . The method of  claim 9 , further comprising:
 determining a merchant identification code based on the first authorization request;   determining whether the merchant identification code matches a merchant identifier in the block-charge list; and   responsive to a 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 first authorization request.   
     
     
         11 . The method of  claim 9 , wherein the first alert to the user device of the user is provided in response to receiving the first authorization request. 
     
     
         12 . The method of  claim 8 , further comprising:
 responsive to receiving a second authorization request, determining that the merchant has been added to the block-charge list; and   responsive to determining that the merchant has been added to the block-charge list, declining the second authorization request.   
     
     
         13 . The method of  claim 12 , further comprising:
 updating a reputation score of the merchant based on the second authorization request; or   removing the merchant from the block-charge list after a period of time.   
     
     
         14 . The method of  claim 8 , wherein adding the merchant to the block-charge list comprises:
 determining a merchant identifier for the merchant; and   adding the merchant identifier to the block-charge list.   
     
     
         15 . A non-transitory, computer-readable medium storing instructions that when executed by one or more processors cause the one or more processors to perform operations comprising:
 providing a first alert to a user device of a user, wherein the first alert comprises a first set of instructions to display an application interface for the user to accept or decline blocking merchant charges and first alert information comprising data related to blocking the merchant charges;   receiving, via the user device, a first user input to accept blocking the merchant charges;   determining whether a merchant will initiate an authorization request for a sub sequent charge, wherein the subsequent charge is associated with an initial charge from the merchant;   responsive to determining that the merchant will initiate the authorization request, providing a second alert to the user device, wherein the second alert comprises a second set of instructions to the user device to display the application interface for the user to accept or decline blocking subsequent charges by the merchant and second alert information for displaying information related to the merchant;   receiving, via the user device, a second user input to accept blocking the subsequent charges by the merchant;   based on receiving the second user input to accept blocking the subsequent charges by the merchant, adding the merchant to a block-charge list; and   in response to receiving the second user input, providing a third alert to the user device, wherein the third alert comprises an identifier of the merchant and an indication that the subsequent charges from the merchant are blocked.   
     
     
         16 . The non-transitory, computer-readable medium of  claim 15 , wherein the instructions further cause the one or more processors to perform operations comprising:
 receiving, from the user device, a first authorization request associated with a payment account of the user; and   identifying the merchant associated with the first authorization request.   
     
     
         17 . The non-transitory, computer-readable medium of  claim 16 , wherein the instructions further cause the one or more processors to perform operations comprising:
 determining a merchant identification code based on the first authorization request;   determining whether the merchant identification code matches a merchant identifier in the block-charge list; and   responsive to a 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 first authorization request.   
     
     
         18 . The non-transitory, computer-readable medium of  claim 16 , wherein the first alert to the user device of the user is provided in response to receiving the first authorization request. 
     
     
         19 . The non-transitory, computer-readable medium of  claim 15 , wherein the instructions further cause the one or more processors to perform operations comprising:
 responsive to receiving a second authorization request, determining that the merchant has been added to the block-charge list; and   responsive to determining that the merchant has been added to the block-charge list, declining the second authorization request.   
     
     
         20 . The non-transitory, computer-readable medium of  claim 19 , wherein the instructions further cause the one or more processors to perform operations comprising:
 updating a reputation score of the merchant based on the second authorization request; or   removing the merchant from the block-charge list after a period of time.