Systems and methods for reducing fraud risk for a primary transaction account

1. A computer-implemented method comprising:

creating, by an authorization system, a single-use account token for a valid primary account identifier;

sending, by the authorization system, the single-use account token as an email attachment to an email address of an associate account holder, wherein a user device is configured to physically isolate the email attachment in a quarantine memory sector of the user device and to load the single-use account token from the email attachment into a wallet application of the user device;

preventing the valid primary account identifier from being used by the authorization system to authorize a transaction in response to the single-use account token being created;

receiving, by the authorization system and from a merchant system, an authorization request including a payment account first identifier;

determining, by the authorization system, that the payment account first identifier is the valid primary account identifier and not the single-use account token;

declining, by the authorization system, the authorization request in response to determining that the payment account first identifier is the valid primary account identifier and not the single-use account token; and

sending, by the authorization system and to the merchant system, a decline response.

2. The method of claim 1 , wherein the authorization request is a settlement request or a payment authorization request.

3. The method of claim 1 , further comprising:

constructing, by the authorization system, a query having a search condition, wherein the search condition is the payment account first identifier;

running, by the authorization system, the query against a database, wherein the database comprises at least one of a relational database management system or a data file; and

retrieving, by the authorization system, payment account information including the valid primary account identifier from the database in response to the payment account information including the search condition.

4. The method of claim 1 , further comprising parsing, by the authorization system, the authorization request to identify the payment account first identifier.

5. The method of claim 1 , further comprising associating, by the authorization system, a transaction block indicator with the valid primary account identifier.

6. The method of claim 1 , further comprising basing, by the authorization system, the decline response on additional factors.

7. The method of claim 1 , wherein the decline response is not sent in response to the valid primary account identifier lacking a transaction block indicator.

8. A system comprising:

a processor; and

a tangible, non-transitory memory configured to communicate with the processor, the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the processor to perform operations comprising:

creating, by the processor, a single-use account token for a valid primary account identifier;

sending, by the processor, the single-use account token as an email attachment to an email address of an associate account holder, wherein a user device is configured to physically isolate the email attachment in a quarantine memory sector of the user device and to load the single-use account token from the email attachment into a wallet application of the user device;

preventing, by the processor, the valid primary account identifier from being used to authorize a transaction in response to the single-use account token being created;

receiving, by the processor and from a merchant system, an authorization request including a payment account first identifier;

determining, by the processor, that the payment account first identifier is the valid primary account identifier and not the single-use account token;

declining, by the processor, the authorization request in response to determining that the payment account first identifier is the valid primary account identifier and not the single-use account token; and

sending, by the processor and to the merchant system, a decline response.

9. The method of claim 1 , further comprising determining, by the authorization system, that transaction information associated with the authorization request satisfies use parameters.

10. The method of claim 1 , wherein the payment account first identifier is associated with an associate account holder.

11. The system of claim 8 , further comprising:

constructing, by the processor, a query having a search condition, wherein the search condition is the payment account first identifier;

running, by the processor, the query against a database, wherein the database comprises at least one of a relational database management system or a data file; and

retrieving, by the processor, payment account information including the valid primary account identifier from the database in response to the payment account information including the search condition.

12. The system of claim 8 , further comprising parsing, by the processor, the authorization request to identify the payment account first identifier.

13. The system of claim 8 , further comprising associating, by the processor, a transaction block indicator with the valid primary account identifier.

14. The system of claim 8 , further comprising basing, by the processor, the decline response on additional factors.

15. The system of claim 8 , wherein the decline response is not sent in response to the valid primary account identifier lacking a transaction block indicator.

16. A computer-implemented method comprising:

receiving, by a merchant system, a payment account first identifier,

wherein an authorization system is configured, in response to a single-use account token being created for a valid primary account identifier, to send the single-use account token as an email attachment to an email address of an associate account holder and to prevent the valid primary account identifier from being authorized in an authorization request from the merchant system,

wherein a user device is configured to physically isolate the email attachment in a quarantine memory sector of the user device and to load the single-use account token from the email attachment into a wallet application of the user device;

transmitting, by the merchant system and to the authorization system, the authorization request including the payment account first identifier; and

receiving, at the merchant system, a decline response in response to the authorization system determining that the authorization request is declined because the payment account first identifier is the valid primary account identifier and not the single-use account token.

17. The method of claim 16 , wherein the authorization system constructs and runs a query having a search condition comprising the payment account first identifier, and wherein payment account information including the valid primary account identifier is retrieved from a database in response to the payment account information including the search condition.

18. The system of claim 8 , wherein the user device is further configured to at least:

transfer the email attachment to the quarantine a first memory sector of the user device;

perform an analysis on the email attachment; and

transfer the email attachment to a second memory sector of the user device based at least in part on the analysis.

19. The system of claim 18 , wherein the analysis comprises comparing the email attachment to one or more malicious code-indicative patterns stored within a signature database.

20. The method of claim 1 , wherein the user device is further configured to at least:

transfer the email attachment to the quarantine memory sector of the user device;

perform an analysis on the email attachment; and

transfer the email attachment to a second memory sector of the user device based at least in part on the analysis.