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

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.

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.