# US 12,598,176 B2 · Token validation for event processing approval > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,598,176 B2 - Document ID: US12598176B2 - Status: Granted - Kind: B2 - Application number: 18/242,765 - Filed: 2023-09-06 - Published: 2025-03-06 - Granted: 2026-04-07 - Earliest claimed: 2023-09-06 - Assignees: Bank of America Corporation - Applicants: Bank of America Corporation - Inventors: Jeetendra Hukmichand Jain; Bradley Holland - Web page: https://patentgrep.com/patent/US12598176B2 ## CPC - H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Aspects of the disclosure relate to virtual tokens. A computing platform may generate, based on approval of a first authentication token, a second authentication token corresponding to an individual. The computing platform may receive an event processing request corresponding to the individual and the second authentication token. The computing platform may analyze the second authentication token to identify whether or not the second authentication token satisfies one or more predetermined conditions. Based on identifying that at least one of the one or more predetermined conditions is satisfied, the computing platform may execute further authentication measures for the event processing request. Based on identifying that the further authentication measures are satisfied, the computing platform may process the event processing request. ## Claims ### Claim 1 A computing platform comprising: at least one processor; a communication interface communicatively coupled to the at least one processor; and memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to: send, to a payment device, the generated authentication token; generate, based on approval of a first authentication token, a second authentication token, wherein the second authentication token corresponds to a payment device of an individual, wherein the first authentication token is a received token and the second authentication token is a generated authentication token; receive an event processing request corresponding to the payment device, wherein the generated authentication token is received along with the event processing request; analyze the generated authentication token to identify whether or not the generated authentication token satisfies one or more predetermined conditions, wherein analyzing the generated authentication token to identify whether or not the generated authentication token satisfies the one or more predetermined conditions is based on identifying that a funding primary account number (FPAN) status indicates that a payment card, corresponding to the event processing request, is inactive or locked, wherein the one or more predetermined conditions comprise: the generated authentication token was generated based on another approved authentication token, the generated authentication token was generated by the computing platform, or the generated authentication token is associated with an enterprise of the computing platform; based on identifying that at least one of the one or more predetermined conditions is satisfied, execute further authentication processes for the event processing request; based on identifying that the further authentication processes are satisfied, process the event processing request, wherein processing the event processing request comprises processing, despite the FPAN status indicating that the payment card is inactive or locked, the event processing request; and based on identifying that none of the one or more predetermined conditions are satisfied: decline the event processing request, wherein the event processing request is declined based on an FPAN status of the payment card corresponding to the event processing request, and send, to a merchant computing device, an indication that the event processing request is declined and one or more commands directing the merchant computing device to display the indication, wherein sending the one or more commands directing the merchant computing device to display the indication causes the merchant computing device to display the indication. ### Claim 2 (depends on 1) The computing platform of claim 1, wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to: receive, from the merchant computing device, the received authentication token and a tokenization request; and identify, prior to generating the generated authentication token, that the received authentication token is approved. ### Claim 3 (depends on 2) The computing platform of claim 2, wherein the tokenization request comprises a primary account number (PAN) for the payment device associated with the individual. ### Claim 4 (depends on 1) The computing platform of claim 1, wherein analyzing the generated authentication token to identify whether or not the generated authentication token satisfies the one or more predetermined conditions is based on identifying that the FPAN status indicates that the payment card is inactive or locked. ### Claim 5 (depends on 1) The computing platform of claim 1, wherein the further authentication measures comprise one or more of: verify that an account of the individual comprises sufficient funds to satisfy the event processing request, or perform a fraud analysis on the event processing request. ### Claim 6 (depends on 1) The computing platform of claim 1, wherein processing the event processing request comprises causing an amount of funds corresponding to the event processing request to be transferred from an account of the individual to an account of an enterprise corresponding to the event processing request. ### Claim 7 A method comprising: at a computing platform comprising at least one processor, a communication interface, and memory: generating, based on approval of a first authentication token, a second authentication token, wherein the second authentication token corresponds to a payment device of an individual, wherein the first authentication token is a received token and the second authentication token is a generated authentication token; send, to the payment device, the generated authentication token; receiving an event processing request corresponding to the payment device, wherein the generated authentication token is received along with the event processing request; analyzing the generated authentication token to identify whether or not the generated authentication token satisfies one or more predetermined conditions, wherein analyzing the generated authentication token to identify whether or not the generated authentication token satisfies the one or more predetermined conditions is based on identifying that a funding primary account number (FPAN) status indicates that a payment card, corresponding to the event processing request, is inactive or locked, wherein the one or more predetermined conditions comprise: the generated authentication token was generated based on another approved authentication token, the generated authentication token was generated by the computing platform, or the generated authentication token is associated with an enterprise of the computing platform; based on identifying that at least one of the one or more predetermined conditions is satisfied, executing further authentication processes for the event processing request; and based on identifying that the further authentication processes are satisfied, processing the event processing request, wherein processing the event processing request comprises processing, despite the FPAN status indicating that the payment card is inactive or locked, the event processing request; and based on identifying that none of the one or more predetermined conditions are satisfied: decline the event processing request, wherein the event processing request is declined based on the FPAN status of the payment card corresponding to the event processing request, and send, to a merchant computing device, an indication that the event processing request is declined and one or more commands directing the merchant computing device to display the indication, wherein sending the one or more commands directing the merchant computing device to display the indication causes the merchant computing device to display the indication. ### Claim 8 (depends on 7) The method of claim 7, further comprising: receiving, from the merchant computing device, the received authentication token and a tokenization request; and identifying, prior to generating the generated authentication token, that the received authentication is approved. ### Claim 9 (depends on 8) The method of claim 8, wherein the tokenization request comprises a primary account number (PAN) for the payment device associated with the individual. ### Claim 10 (depends on 7) The method of claim 7, wherein analyzing the generated authentication token to identify whether or not the generated authentication token satisfies the one or more predetermined conditions is based on identifying that the FPAN status indicates that the payment card is inactive or locked. ### Claim 11 (depends on 7) The method of claim 7, wherein the further authentication measures comprise one or more of: verify that an account of the individual comprises sufficient funds to satisfy the event processing request, or perform a fraud analysis on the event processing request. ### Claim 12 One or more non-transitory computer-readable media storing instructions that, when executed by a computing platform comprising at least one processor, a communication interface, and memory, cause the computing platform to: generate, based on approval of a first authentication token, a second authentication token, wherein the second authentication token corresponds to a payment device of an individual, wherein the first authentication token is a received token and the second authentication token is a generated authentication token; send, to the payment device, the generated authentication token; receive an event processing request corresponding to the payment device, wherein the generated authentication token is received along with the event processing request; analyze the generated authentication token to identify whether or not the generated authentication token satisfies one or more predetermined conditions, wherein analyzing the generated authentication token to identify whether or not the generated authentication token satisfies the one or more predetermined conditions is based on identifying that a funding primary account number (FPAN) status indicates that a payment card, corresponding to the event processing request, is inactive or locked, wherein the one or more predetermined conditions comprise: the generated authentication token was generated based on another approved authentication token, the generated authentication token was generated by the computing platform, or the generated authentication token is associated with an enterprise of the computing platform; based on identifying that at least one of the one or more predetermined conditions is satisfied, execute further authentication processes for the event processing request; based on identifying that the further authentication processes are satisfied, process the event processing request, wherein processing the event processing request comprises processing, despite an FPAN status indicating that the payment card is inactive or locked, the event processing request; and based on identifying that none of the one or more predetermined conditions are satisfied: decline the event processing request, wherein the event processing request is declined based on the FPAN status of the payment card corresponding to the event processing request, and send, to a merchant computing device, an indication that the event processing request is declined and one or more commands directing the merchant computing device to display the indication, wherein sending the one or more commands directing the merchant computing device to display the indication causes the merchant computing device to display the indication. ### Claim 13 (depends on 12) The one or more non-transitory computer-readable media of claim 12, wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to: receive, from the merchant computing device, the received authentication token and a tokenization request; and identify, prior to generating the generated authentication token, that the received authentication token is approved. ### Claim 14 (depends on 13) The one or more non-transitory computer-readable media of claim 13, wherein the tokenization request comprises a primary account number (PAN) for the payment device associated with the individual. ### Claim 15 (depends on 12) The one or more non-transitory computer-readable media of claim 12, wherein analyzing the generated authentication token to identify whether or not the generated authentication token satisfies the one or more predetermined conditions is based on identifying that the FPAN status indicates that the payment card is inactive or locked.