Systems and methods for binding unique tokens with transaction parameters to authorize transactions

Abstract

A system for binding unique tokens with transaction parameters to authorize transactions based on monitoring user interactions with one or more applications on a user device. Upon monitoring the system determines first payment transaction initiation by a user at a merchant payment gateway associated with the one or more applications based on the monitoring. The system generates and displays on the user device a unique token based at least on an input received from the user device. The system receives the unique token as part of an authorization request. Upon receiving the unique token, the system identifies first transaction parameters associated with the first payment transaction and automatically binds the generated unique token with the identified first transaction parameters.

1 . A system for binding unique tokens with merchant identifiers to authorize transactions, the system comprising:
 one or more memory devices storing instructions; and   one or more processors configured to execute the instructions to:
 monitor, with one or more applications on a user device, user interactions of a user of the user device; 
 detect, based on the monitoring, a first payment transaction initiation by the user at a merchant payment gateway of a webpage; 
 compare a webpage identifier of the webpage with a predetermined list of webpages stored in a database; 
 determine, based on the comparison, whether the webpage identifier is associated with at least one webpage from the list of webpages; 
 in response to a determination that the webpage identifier is not associated with at least one webpage from the list of webpages, generate and provide a unique token to the user device, the unique token being configured to be input by the user as a payment credential at the merchant payment gateway via the user device for completing a transaction; 
 receive the unique token as part of a first authorization request to authorize the first payment transaction; 
 upon successfully authorizing the first payment transaction in response to the first authorization request:
 identify one or more first transaction parameters identifying a merchant associated with the first payment transaction; and 
 automatically bind and store the generated unique token with the identified one or more first transaction parameters; 
 
 receive a second authorization request to authorize a second payment transaction using the unique token input at the merchant payment gateway; 
 identify, based on the received second authorization request, one or more second transaction parameters identifying a merchant associated with the second payment transaction; 
 compare the identified one or more second transaction parameters with the one or more first transaction parameters; and 
 authorize the second payment transaction based on a result of the comparison indicating a match between the merchant identified by the first transaction parameter and the merchant identified by the second transaction parameter. 
   
     
     
         2 . The system of  claim 1 , wherein the unique token is a unique virtual number utilized at the merchant payment gateway instead of a payment card number. 
     
     
         3 . The system of  claim 1 , wherein the one or more first transaction parameters comprise at least one of the webpage identifier of the webpage, a merchant category code associated with the first merchant, a name of the first merchant, a masked name of the first merchant, or a merchant identifier of the first merchant. 
     
     
         4 . The system of  claim 1 , the one or more processors being further configured to execute instructions to:
 identify an initiation of the second payment transaction at the merchant payment gateway based on the monitoring.   
     
     
         5 . (canceled) 
     
     
         6 . The system of  claim 1 , the one or more processors being further configured to execute instructions to:
 decline authorization of the second payment transaction based on the comparison indicating that at least one of the one or more second transaction parameters does not match with the one or more first transaction parameters.   
     
     
         7 . The system of  claim 1 , the one or more processors being further configured to execute instructions to:
 generate the unique token associated with the first merchant further based at least on a merchant identifier.   
     
     
         8 . A computer implemented method for binding unique tokens with merchant identifiers to authorize transactions, the method comprising:
 monitoring, with one or more applications on a user device, user interactions of a user of the user device;   detecting a first payment transaction initiation by the user at a merchant payment gateway of a webpage associated with the one or more applications based on the monitoring;   upon determining that an identifier associated with the webpage is not associated with a previously generated token, generating and providing a unique token to the user device, the unique token being configured to be input by the user as a payment credential at the merchant payment gateway via the user device for completing a transaction;   receiving the unique token as part of a first authorization request to authorize the first payment transaction;   upon successfully authorizing the first payment transaction in response to the first authorization request:
 identifying one or more first transaction parameters associated with the first payment transaction, the first transaction parameters identifying a merchant associated with the transaction; and 
 automatically binding and storing the generated unique token with the identified one or more first transaction parameters; 
   receiving a second authorization request to authorize a second payment transaction using the unique token input at the merchant payment gateway;   identifying, based on the received second authorization request, one or more second transaction parameters identifying a merchant associated with the second payment transaction;   comparing the identified one or more second transaction parameters with the one or more first transaction parameters; and   authorizing the second payment transaction based on a result of the comparison indicating a match between the merchant identified by the first transaction parameter and the merchant identified by the second transaction parameter.   
     
     
         9 . The method of  claim 8 , wherein the unique token is a unique virtual number utilized at the merchant payment gateway instead of a payment card number. 
     
     
         10 . The method of  claim 8 , wherein the one or more first transaction parameters comprise at least one of the identifier associated with the webpage, a merchant category code associated with the first merchant, a name of the first merchant, a masked name of the first merchant, or a merchant identifier of the first merchant. 
     
     
         11 . The method of  claim 8 , the method further comprising:
 identifying an initiation of the second payment transaction at the merchant payment gateway based on the monitoring.   
     
     
         12 . (canceled) 
     
     
         13 . The method of  claim 8 , the method further comprising:
 declining authorization of the second payment transaction based on the comparison indicating that at least one of the one or more second transaction parameters does not match with the one or more first transaction parameters.   
     
     
         14 . The method of  claim 8 , the method further comprising:
 generating the unique token associated with the first merchant further based at least on a merchant identifier.   
     
     
         15 . A non-transitory computer-readable medium storing instructions executable by one or more processors to perform operations for binding unique tokens with merchant identifiers to authorize transactions, the operations comprising:
 monitoring, with one or more applications on a user device, user interactions of a user of the user device;   determining, based on the monitoring, a first payment transaction initiation by the user at a merchant payment gateway of a webpage;   comparing a webpage identifier of the webpage with a predetermined list of webpages stored in a database;   determining, based on the comparison, whether the webpage identifier is associated with at least one webpage from the predetermined list;   in response to a determination that the webpage identifier is not associated with at least one webpage from the list of webpages, generating and providing a unique token to the user device, the unique token being configured to be input by the user as a payment credential at a payment interface of the webpage at the user device for completing a transaction;   receiving the unique token as part of a first authorization request to authorize the first payment transaction;   upon successfully authorizing the first payment transaction in response to the first authorization request:
 identifying one or more first transaction parameters identifying a merchant associated with the first payment transaction, the first transaction parameters comprising information identifying a merchant associated with the transaction; and 
 automatically binding and storing the generated unique token with the identified one or more first transaction parameters, the generated unique token being sufficient to complete a subsequent transaction only if one or more parameters of the subsequent transaction matches the identified one or more first transaction parameters; 
   receiving a second authorization request to authorize a second payment transaction using the unique token at the merchant payment gateway;   identify, based on the received second authorization request, one or more second transaction parameters identifying a merchant associated with the second payment transaction;   comparing the identified one or more second transaction parameters with the one or more first transaction parameters; and   authorizing the second payment transaction based on a result of the comparison indicating a match between the merchant identified by the first transaction parameter and the merchant identified by the second transaction parameter.   
     
     
         16 . The non-transitory computer-readable medium of  claim 15 , wherein the unique token is a unique virtual number utilized at the merchant payment gateway instead of a payment card number. 
     
     
         17 . The non-transitory computer-readable medium of  claim 15 , wherein the one or more first transaction parameters comprise at least one of the webpage identifier of the webpage, a merchant category code associated with the first merchant, a name of the first merchant, a masked name of the first merchant, or a merchant identifier of the first merchant. 
     
     
         18 . The non-transitory computer-readable medium of  claim 15 , the operations further comprising:
 identifying an initiation of the second payment transaction at the merchant payment gateway based on the monitoring.   
     
     
         19 . (canceled) 
     
     
         20 . The non-transitory computer-readable medium of  claim 15 , the operations further comprising:
 declining authorization of the second payment transaction based on the comparison indicating that at least one of the one or more second transaction parameters does not match with the one or more first transaction parameters.   
     
     
         21 . The system of  claim 4 , wherein the one or more processors are further configured to execute instructions to prompt the user to input the unique token at the merchant payment gateway to initiate the second transaction. 
     
     
         22 . The method of  claim 11 , wherein the method further comprises prompting the user to input the unique token at the merchant payment gateway to initiate the second transaction. 
     
     
         23 . The non-transitory computer-readable medium of  claim 18 , wherein the operations further comprise prompting the user to input the unique token at the merchant payment gateway to initiate the second transaction.