Multi-factor authentication (MFA) arrangements for dynamic virtual transaction token generation via browser extension

1. A non-transitory machine-readable medium storing program code of a browser extension executable by a processor to:

determine, by a browser extension executing on a processor, that a record indicating an authentication by a first multi-factor authentication does not exist for a user in a memory;

receives by the browser extension, a request for issuance of a transaction token for a financial transaction, wherein the request includes an indication of a value needed for the transaction token and a situational data type indicating a predetermined situation;

maintain a situation-specific predetermined value for each of a plurality of predetermined situations in a list of differing predetermined situations, wherein the list comprises multiple users with individualized limits on a per-user basis, wherein each user in the list is associated with a user-specific running period, a user-specific cumulative token value per running period, and a user-specific lifespan;

select, by the browser extension, the situation-specific predetermined value of the predetermined situation for the user in the request for the transaction token to be transacted in the financial transaction, wherein the situation-specific predetermined value is used as a predetermined value;

sum a number of requested transaction tokens including the transaction token requested in the request for the issuance of the transaction token;

in response to the predetermined situation and the sum of the requested transaction tokens being less than a threshold, retrieve, by the browser extension, the predetermined value and a predetermined number of transaction tokens from the memory, wherein the predetermined value is a monetary amount, and the predetermined number of tokens is a number of transaction tokens requested before another multi-factor authentication is requested;

issue the transaction token when the predetermined value needed does not exceed the predetermined value, the number of requested transaction tokens does not exceed the predetermined number of tokens, a cumulative token value does not exceed the user-specific cumulative token value per running period, and the user-specific lifespan has not expired; and

completes, by the browser extension, the financial transaction using the transaction token issued in response to an authenticated second multi-factor authentication.

2. The non-transitory machine-readable medium as claimed in claim 1 , wherein the transaction token is a virtual credit card, and the value needed for the transaction token is the monetary amount.

3. The non-transitory machine-readable medium as claimed in claim 1 , comprising:

maintaining a merchant-specific predetermined value for each merchant in a list of differing merchants; and

selecting the merchant-specific predetermined value of a merchant with which the transaction token is to be transacted, as the predetermined value.

4. The non-transitory machine-readable medium as claimed in claim 1 , wherein the transaction token includes identifier data mapping back to at least one of: identification of an individual; a prior session conducted previously; a financial service account; or a primary account number.

5. The non-transitory machine-readable medium of claim 1 , wherein when the processor is determining, by the browser extension, that the record indicating the authentication by the first multi-factor authentication, the non-transitory machine-readable medium causes the processor to:

determine whether a user-selected authorized span of time has passed since the first multi-factor authentication.

6. The non-transitory machine-readable medium of claim 1 , wherein when the program code of the browser extension is executed by the processor, the processor is further caused to:

in response to the determination that the authentication by a first multi-factor authentication does not exist for a user in the memory of a device, cause, by the browser extension, a prompt on a user interface on a display of the device to require a user input via a user input device to complete the authentication by the first multi-factor authentication;

receive, by the browser extension via the user input device, the first multi-factor authentication; and

present, by the browser extension, an option on the user interface for a second user input to request an issuance of a transaction token for a financial transaction.

7. The non-transitory machine-readable medium of claim 6 , wherein operation of the browser extension is device specific, requiring the first multi-factor authentication be performed after reinstalling the browser extension onto a same device or after installing the browser extension onto a new device.

8. A computing device comprising:

a user-interface device;

a processor;

a memory including browser extension program code, the browser extension program code, when executed by the processor, to cause the processor to:

determining, by a browser extension executing on the processor, that a record indicating an authentication by a first multi-factor authentication does not exist for a user in the memory;

receiving, by the browser extension, a request for issuance of a transaction token for a financial transaction, wherein the request includes an indication of a value needed for the transaction token and a situational data type indicating a predetermined situation;

maintaining a situation-specific predetermined value for each of a plurality of predetermined situations in a list of differing predetermined situations, wherein the list comprises multiple users with individualized limits on a per-user basis, wherein each user in the list is associated with a user-specific running period, a user-specific cumulative token value per running period, and a user-specific lifespan;

selecting, by the browser extension, the situation-specific predetermined value of the predetermined situation for the user in the request for the transaction token to be transacted in the financial transaction, wherein the situation-specific predetermined value is used as a predetermined value;

summing a number of requested transaction tokens including the transaction token requested in the request for the issuance of the transaction token;

in response to the predetermined situation and the sum of the requested transaction tokens being less than a threshold, retrieving, by the browser extension, the predetermined value and a predetermined number of transaction tokens from the memory, wherein the predetermined value is a monetary amount, and the predetermined number of tokens is a number of transaction tokens requested before another multi-factor authentication is requested;

issuing the transaction token when the predetermined value needed does not exceed the predetermined value, the number of requested transaction tokens does not exceed the predetermined number of tokens, a cumulative token value does not exceed the user-specific cumulative token value per running period, and the user-specific lifespan has not expired; and

completing, by the browser extension, the financial transaction using the transaction token issued in response to an authenticated second multi-factor authentication.

9. The computing device as claimed in claim 8 , wherein the transaction token is a virtual credit card, the value needed for the transaction token is a monetary value, and the predetermined value is a predetermined monetary amount.

10. The computing device as claimed in claim 8 , comprising:

a merchant-specific token selector configured to:

access a merchant-specific predetermined value for each merchant in a list of differing merchants; and

select the merchant-specific predetermined value of a merchant with which the transaction token is to be transacted, as the predetermined value.

11. The computing device as claimed in claim 8 , wherein the transaction token includes identifier data mapping back to at least one of: identification of an individual; a prior session conducted previously; a financial service account; or a primary account number.

12. The computing device of claim 8 , wherein when the processor is determining that the record indicating an authentication by the first multi-factor authentication does not exist for the user in the memory, the processor is operable to:

determine whether a user-selected authorized span of time has passed since the first multi-factor authentication.

13. The computing device of claim 8 , wherein when the program code of the browser extension is executed by the processor, the processor is further caused to:

in response to the determination that the authentication by a first multi-factor authentication does not exist for a user in the memory of a device, cause, by the browser extension, a prompt on a user interface on a display of the device to require a user input via a user input device to complete the authentication by the first multi-factor authentication;

receive, by the browser extension via the user input device, the first multi-factor authentication; and

present, by the browser extension, an option on the user interface for a second user input to request an issuance of a transaction token for a financial transaction.

14. The computing device of claim 13 , wherein operation of the browser extension is device specific, requiring the first multi-factor authentication be performed after reinstalling the browser extension onto a same device or after installing the browser extension onto a new device.

15. A computer-implemented method, comprising:

determining, by a browser extension executing on a processor, that a record indicating an authentication by a first multi-factor authentication does not exist for a user in a memory;

receiving, by the browser extension, a request for issuance of a transaction token for a financial transaction, wherein the request includes an indication of a value needed for the transaction token and a situational data type indicating a predetermined situation;

maintaining a situation-specific predetermined value for each of a plurality of predetermined situations in a list of differing predetermined situations, wherein each user in the list is associated with a user-specific running period, a user-specific cumulative token value per running period, and a user-specific lifespan;

selecting, by the browser extension, the situation-specific predetermined value of the predetermined situation for the user in the request for the transaction token to be transacted in the financial transaction, wherein the situation-specific predetermined value is used as a predetermined value;

summing a number of requested transaction tokens including the transaction token requested in the request for the issuance of the transaction token;

in response to the predetermined situation and the sum of the requested transaction tokens being less than a threshold, retrieving, by the browser extension, the predetermined value and a predetermined number of transaction tokens from the memory, wherein the predetermined value is a monetary amount, and the predetermined number of tokens is a number of transaction tokens requested before another multi-factor authentication is requested;

issuing the transaction token when the predetermined value needed does not exceed the predetermined value, the number of requested transaction tokens does not exceed the predetermined number of tokens, a cumulative token value does not exceed the user-specific cumulative token value per running period, and the user-specific lifespan has not expired; and

completing, by the browser extension, the financial transaction using the transaction token issued in response to an authenticated second multi-factor authentication.

16. The computer-implemented method as claimed in claim 15 , wherein the transaction token is a virtual credit card, and the predetermined value is a predetermined monetary amount.

17. The computer-implemented method as claimed in claim 15 , comprising:

maintaining a merchant-specific predetermined value for each merchant in a list of differing merchants; and

selecting the merchant-specific predetermined value of a merchant with which the transaction token is to be transacted, as the predetermined value.

18. The computer-implemented method as claimed in claim 15 , wherein the transaction token includes identifier data mapping back to at least one of: an identification of an individual; a prior session conducted previously; a financial service account; or a primary account number.

19. The computer-implemented method of claim 15 , wherein determining, by the browser extension executing on the processor, that the record indicating the authentication by the first multi-factor authentication does not exist for the user in the memory, further includes:

determining whether a user-selected authorized span of time has passed since the first multi-factor authentication.

20. The computer-implemented method of claim 15 , further comprising:

in response to the determination that the authentication by a first multi-factor authentication does not exist for a user in the memory of a device, causing, by the browser extension, a prompt on a user interface on a display of the device to require a user input via a user input device to complete the authentication by the first multi-factor authentication, wherein operation of the browser extension is device specific, requiring the first multi-factor authentication be performed after reinstalling the browser extension onto a same device or after installing the browser extension onto a new device;

receiving, by the browser extension via the user input device, the first multi-factor authentication; and

presenting, by the browser extension, an option on the user interface for a second user input to request an issuance of a transaction token for a financial transaction.