User-Level Token for User Authentication via a User Device

1. A computer-implemented method comprising: generating a token associated with a user-level profile; receiving, via a computing system, a transaction message associated with a transaction, the transaction message comprising a first data portion and a second data portion, wherein a merchant identifier is part of at least one of the first data portion or the second data portion, and card information is part of the other of the at least one of the first data portion or the second data portion, and wherein the token is inserted into at least one of the first data portion or the second data portion; obtaining, via a network, the token from the received transaction message; validating the token responsive to receiving a validation confirmation from a service provider; and transmitting an identity verification to the computing system responsive to validating the token.

2. The computer-implemented method of claim 1, wherein: the transaction message further comprises a third data portion and a fourth data portion; the first data portion comprises an account number; the second data portion comprises at least one of a transaction type or a purchase type; the third data portion comprises one or more of a merchant identification number, a merchant type, or a merchant location; and the fourth data portion comprises at least one of a transaction amount or a transaction time.

3. The computer-implemented method of claim 1, wherein the user-level profile includes financial information and non-financial information of a user associated with the user-level profile.

4. The computer-implemented method of claim 3, wherein the non-financial information comprises at least one of an age, an address, a name, a height, a weight, biometric data, or travel rewards data of the user associated with the user-level profile.

5. The computer-implemented method of claim 3, further comprising requesting permission of the user associated with the user-level profile to share the non-financial information with a merchant associated with the transaction.

6. The computer-implemented method of claim 1, further comprising analyzing contextual data of the received transaction message, wherein the contextual data comprises a location of a user associated with the user-level profile.

7. The computer-implemented method of claim 1, wherein: the user-level profile is a first user-level profile of a plurality of user-level profiles stored in a database; and the token is unique to a user associated with the first user-level profile.

8. The computer-implemented method of claim 1, wherein the transaction message further comprises: a message type indicator classifying the transaction message; and wherein a classification of the transaction message comprises one or more of an authorization message, a financial message, a reconciliation message, or an administrative message.

9. The computer-implemented method of claim 1, wherein validating the token further comprises determining that the token is not expired.

10. The computer-implemented method of claim 1, wherein the token is formatted as at least one of a tokenized account number or a personal account number.

11. The computer-implemented method of claim 1, wherein the transaction message is structured as an International Organization for Standardization (ISO) 8583-compliant financial transaction card-originated message.

12. A system comprising: a first computing system comprising one or more processors and instructions stored in non-transitory machine-readable media, the instructions configured to cause the first computing system to: generate a token associated with a user-level profile; receive, via a second computing system, a transaction message associated with a transaction, the transaction message comprising a first data portion and a second data portion, wherein a merchant identifier is part of at least one of the first data portion or the second data portion, and card information is part of the other of the at least one of the first data portion or the second data portion, and wherein the token is inserted into at least one of the first data portion or the second data portion; obtain, via a network, the token from the received transaction message; validate the token responsive to receiving a validation confirmation from a service provider; and transmit an identity verification to the second computing system responsive to validating the token.

13. The system of claim 12, wherein: the transaction message further comprises a third data portion and a fourth data portion; the first data portion comprises an account number; the second data portion comprises at least one of a transaction type or a purchase type; the third data portion comprises one or more of a merchant identification number, a merchant type, or a merchant location; and the fourth data portion comprises at least one of a transaction amount or a transaction time.

14. The system of claim 12, wherein the user-level profile includes financial information and non-financial information of a user associated with the user-level profile.

15. The system of claim 14, wherein the non-financial information comprises at least one of an age, an address, a name, a height, a weight, biometric data, or travel rewards data of the user associated with the user-level profile.

16. The system of claim 14, wherein the instructions are further configured to cause the first computing system to request permission of the user associated with the user-level profile to share the non-financial information with a merchant associated with the transaction.

17. The system of claim 12, wherein the instructions are further configured to cause the first computing system to analyze contextual data of the received transaction message, wherein the contextual data comprises a location of a user associated with the user-level profile.

18. The system of claim 12, wherein the transaction message further comprises: a message type indicator classifying the transaction message; and wherein a classification of the transaction message comprises one or more of an authorization message, a financial message, a reconciliation message, or an administrative message.

19. The system of claim 12, wherein the token is formatted as at least one of a tokenized account number or a personal account number.

20. A computing system comprising: a network interface configured to communicate with a second computing system; a database configured to store a plurality of user-level profiles; and a processing circuit comprising one or more processors and a memory storing instructions that, when executed by the one or more processors, causes the processing circuit to: generate a token associated with a user-level profile; receive, via the second computing system, a transaction message associated with a transaction, the transaction message comprising a first data portion and a second data portion, wherein a merchant identifier is part of at least one of the first data portion or the second data portion, and card information is part of the other of the at least one of the first data portion or the second data portion, and wherein the token is inserted into at least one of the first data portion or the second data portion; obtain, via a network, the token from the received transaction message; validate the token responsive to receiving a validation confirmation from a service provider; and transmit an identity verification to the second computing system responsive to validating the token.