# US 12,192,195 B2 · Systems utilizing secure offline limited-use tokens for temporary electronic activity authentication and methods of use thereof > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,192,195 B2 - Document ID: US12192195B2 - Status: Granted - Kind: B2 - Application number: 17/090,733 - Filed: 2020-11-05 - Published: 2022-05-05 - Granted: 2025-01-07 - Earliest claimed: 2020-11-05 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Jennifer Kwok; Viraj Chaudhary; Abdelkader M'hamed Benkreira - Web page: https://patentgrep.com/patent/US12192195B2 ## CPC - H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)} - H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)} - G06F 21/33: using certificates - H04L 63/107: {wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals} - H04L 63/108: {when the policy decisions are valid for a limited amount of time} - H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Systems and methods of the present disclosure enable the generation and use of secure offline tokens for account activity authentication. A processor receives an activity record including activity details including an entity identifier. The processor determines a flight booking associated with the activity record when the entity identifier includes an airline, and determines flight data associated with the flight booking. The processor automatically generates an offline token associated with the user account, including account access restrictions. The account access restrictions include a token activation period that binds the offline token to a duration of the flight, and a token entity binding that binds the offline token to use with the airline for performing in-flight account activity requests. The processor automatically causes a computing device to download the offline token to enabling performing the in-flight account activity requests with the entity during the offline token activation period. ## Claims ### Claim 1 A method comprising: receiving, by at least one hardware processor, a transaction record comprising transaction details associated with a transaction in a user account of a user; wherein the transaction details comprise an entity identifier associated with an entity; wherein the user account is associated with a computing device, configured to facilitate executing transactions with at least one point-of-sale device; determining, by the at least one hardware processor, a scheduled transaction-related activity between the user and the entity based at least in part on the entity identifier of the transaction details of the transaction record; wherein the scheduled transaction-related activity is indicative of at least one potential subsequent offline transaction between the user account and the entity; determining, by the at least one hardware processor, transaction-related activity data associated with the scheduled transaction-related activity utilizing a data enrichment engine, the transaction-related activity data comprising a transaction-related activity start time; automatically generating, by the at least one hardware processor, in response to the transaction-related activity data, a temporary, entity-specific, offline limited-use token associated with the user account for the at least one potential subsequent offline transaction associated with the scheduled transaction-related activity; wherein the temporary, entity-specific, offline limited-use token comprises at least one account access restriction that restricts the use of the temporary, entity-specific, offline limited-use token to the scheduled transaction-related activity; wherein the at least one account access restriction identifies: a temporary, entity-specific, offline token activation period, identifying an active offline time period of the temporary, entity-specific, offline limited-use token based on the transaction-related activity start time, and a token entity binding, identifying the entity to which the temporary, entity-specific, offline limited-use token being bound to during the token activation period; and automatically causing, by the at least one hardware processor, to download the temporary, entity-specific, offline limited-use token to the computing device; wherein the computing device is configured to communicate the temporary, entity-specific, offline limited-use token to the at least one point-of-sale device that executes at least one subsequent offline transaction request while the computing device is offline during the temporary offline token activation period and restricted to the entity. ### Claim 2 (depends on 1) The method of claim 1, further comprising: receiving, by the at least one hardware processor, enhanced transaction details associated with the transaction record; wherein the enhanced transaction details comprise additional transaction-related activity data comprising transaction-related activity start time data associated with a beginning of the transaction-related activity; and determining, by the at least one hardware processor, the temporary offline limited-use token activation period to be a duration of transaction-related activity. ### Claim 3 (depends on 1) The method of claim 1, further comprising: receiving, by the at least one hardware processor, enhanced transaction-related activity details associated with the transaction record; wherein the enhanced transaction-related activity details comprise additional transaction-related activity data comprising transaction-related activity location data associated with a transaction-related activity location; receiving, by the at least one hardware processor, a geolocation associated with the computing device; and determining, by the at least one hardware processor, the temporary offline limited-use token activation period to begin upon the geolocation matching the transaction-related activity location. ### Claim 4 (depends on 1) The method of claim 1, further comprising: receiving, by the at least one hardware processor, enhanced transaction details associated with the transaction record; wherein the enhanced transaction details comprise additional transaction-related activity data comprising transaction-related activity end location data associated with a transaction-related activity end location; receiving, by the at least one hardware processor, a geolocation associated with the computing device; and determining, by the at least one hardware processor, the temporary offline limited-use token activation period to end upon the geolocation matching the transaction-related activity end location. ### Claim 5 (depends on 1) The method of claim 1, wherein the transaction-related activity comprises a flight and the transaction-related activity data comprises flight data. ### Claim 6 (depends on 5) The method of claim 5, further comprising: receiving, by the at least one hardware processor, enhanced transaction details associated with the transaction record; wherein the enhanced transaction details comprise additional flight data comprising layover data associated with one or more layover airports; and generating, by the at least one hardware processor, an update to the temporary offline limited-use token to comprise a new temporary offline limited-use token entity binding associated with one or more entities or entity categories of the one or more layover airports. ### Claim 7 (depends on 1) The method of claim 1, further comprising determining, by the at least one hardware processor, an activation state of the temporary offline limited-use token based at least in part on an online access setting of the computing device. ### Claim 8 (depends on 7) The method of claim 7, wherein the temporary offline limited-use token is in an inactive state when the computing device has the online access setting set to an online state associated with the computing device having access to the Internet. ### Claim 9 (depends on 7) The method of claim 7, wherein the temporary offline limited-use token is in an active state when the computing device has the online access setting set to an offline state associated with the computing device having no access to the Internet. ### Claim 10 (depends on 7) The method of claim 7, further comprising: sending, by the at least one hardware processor, a ping to the computing device; and determining, by the at least one hardware processor, the online access setting of the computing device based on whether a response to the ping is received. ### Claim 11 (depends on 1) The method of claim 1, wherein the temporary offline limited-use token comprises a virtual credit card number representing a temporary virtual credit card associated with the user account. ### Claim 12 A method comprising: receiving, by at least one hardware processor, a transaction record comprising transaction details associated with a transaction activity in a user account of a user; wherein the transaction details comprise an activity reference number; wherein the user account is associated with a computing device, configured to facilitate executing transactions with at least one point-of-sale device; determining, by the at least one hardware processor, scheduled transaction-related activity data associated with the activity reference number, the scheduled transaction-related activity data comprising: i) a transaction-related activity start time indicator associated with a transaction-related activity start time, ii) a transaction-related activity end time indicator associated a transaction-related activity end time, and iii) an entity identifier identifying an entity associated with the activity reference number; wherein the transaction-related activity is indicative of at least one potential subsequent offline transaction between the user account and the entity; automatically generating, by the at least one hardware processor, in response to the transaction-related activity data, a temporary, entity-specific, offline limited-use token associated with the user account for the at least one potential subsequent offline transaction associated with the scheduled transaction-related activity; wherein the temporary, entity-specific, offline limited-use token comprises at least one account access restriction that restricts the use of the temporary, entity-specific, offline limited-use token to the scheduled transaction-related activity; wherein the account access restrictions comprise: a temporary, entity-specific, offline limited-use token activation period associated with the temporary, entity-specific, offline limited-use token being active during the scheduled transaction-related activity based on the transaction-related activity data; and automatically causing, by the at least one hardware processor, to download the temporary, entity-specific, offline limited-use token to the computing device; wherein the computing device is configured to communicate the temporary, entity-specific, offline limited-use token to the at least one point-of-sale device of that executes at least one subsequent offline transaction request while the computing device is offline during the temporary offline token activation period and restricted to the entity. ### Claim 13 (depends on 12) The method of claim 12, further comprising: wherein the transaction details are associated with a flight number; wherein the transaction-related activity start time indicator is associated with a flight departure time; and determining, by the at least one hardware processor, the temporary offline limited-use token activation period to be a duration of a flight associated with the flight number starting at the flight departure time. ### Claim 14 (depends on 12) The method of claim 12, further comprising: wherein the transaction details are associated with a flight number; receiving, by the at least one hardware processor, additional flight data comprising flight departure data associated with a flight departure airport; receiving, by the at least one hardware processor, a geolocation associated with the computing device; and determining, by the at least one hardware processor, the temporary offline limited-use token activation period to begin upon the geolocation matching the flight departure airport. ### Claim 15 (depends on 12) The method of claim 12, further comprising: wherein the transaction details are associated with a flight number; receiving, by the at least one hardware processor, additional flight data comprising flight destination data associated with a flight destination airport; receiving, by the at least one hardware processor, a geolocation associated with the computing device; and determining, by the at least one hardware processor, the temporary offline limited-use token activation period to end upon the geolocation matching the flight destination airport. ### Claim 16 (depends on 12) The method of claim 12, further comprising: wherein the transaction details are associated with a flight number; receiving, by the at least one hardware processor, additional flight data comprising layover data associated with one or more layover airports; and generating, by the at least one hardware processor, an update to the temporary offline limited-use token to comprise a new temporary offline limited-use token entity binding associated with one or more entities or entity categories of the one or more layover airports. ### Claim 17 (depends on 12) The method of claim 12, further comprising determining, by the at least one hardware processor, an activation state of the temporary offline limited-use token based at least in part on an online access setting of the computing device. ### Claim 18 (depends on 17) The method of claim 17, wherein the temporary offline limited-use token is in an inactive state when the computing device has the online access setting set to an online state associated with the computing device having access to the Internet. ### Claim 19 (depends on 17) The method of claim 17, further comprising: sending, by the at least one hardware processor, a ping to the computing device; and determining, by the at least one hardware processor, the online access setting of the computing device based on whether a response to the ping is received. ### Claim 20 A system comprising: at least one processor in communication with a user account, wherein the at least one processor is configured to implement software instructions causing the at least one processor to perform steps to: receive a transaction record comprising transaction details associated with a transaction in a user account of a user; wherein the transaction details comprise an entity identifier associated with an entity; wherein the user account is associated with a computing device, configured to facilitate executing transactions with at least one point-of-sale device; determine scheduled transaction-related activity between the user and the entity based at least in part on the entity identifier of the transaction details of the transaction record; wherein the scheduled transaction-related activity is indicative of at least one potential subsequent offline transaction between the user account and the entity; determine transaction-related activity data associated with the scheduled transaction-related activity utilizing a data enrichment engine, the transaction-related activity data comprising a transaction-related activity start time; automatically generate, in response to the transaction-related activity data, a temporary, entity-specific, offline limited-use token associated with the user account for the at least one potential subsequent offline transaction associated with the scheduled transaction-related activity; wherein the temporary, entity-specific, offline limited-use token comprises at least one account access restriction that restricts the use of the temporary, entity-specific, offline limited-use token to the scheduled transaction-related activity: wherein the at least one account access restriction identifies: a temporary, entity-specific, offline token activation period, identifying an active offline time period of the temporary, entity-specific, offline limited-use token based on the transaction-related activity start time, and a token entity binding, identifying the entity to which the temporary, entity-specific, offline limited-use token being bound to during the token activation period; and automatically cause to download the temporary, entity-specific, offline limited-use token to the computing device; wherein the computing device is configured to communicate the temporary, entity-specific, offline limited-use token to the at least one point-of-sale device that executes at least one subsequent offline transaction request while the computing device is offline during the temporary offline token activation period and restricted to the entity.