Cloud service-based secured data workflow integration and methods thereof

The present disclosure includes systems and methods enabling secure workflows by receiving an electronic event authentication message from an initiator device, where the electronic event authentication message comprises a user profile identifier, and an entity identifier. A first device-specific actions-sequence token is generated for an actions-sequence session to execute a device-specific instance of at least one automated processing actions-sequence. A workflow request message is received from the initiator device that includes the user profile identifier and the entity identifier, and a second device-specific actions-sequence token is generated. Where the first and second device-specific actions-sequence tokens match, the actions-sequence session is executed and a criterion update in response to the actions-sequence session is produced. The criterion update may then be transmitted to the initiator device.

TECHNICAL FIELD

The present disclosure generally relates to computer-based methods and systems for cloud service-based secured data workflow integration, including entity-agnostic user communication services with improved user data security.

BACKGROUND

Electronic accounts can sometimes be used by a user to engage in an electronic activity with a third-party. Often, the third-party may need user data to effectuate processes related to the electronic activity, such as sending a communication to the user regarding the electronic activity. Typically, the user would then provide personal contact information or other sensitive user data to the third-party, so the processes may be performed.

SUMMARY

In some aspects, the techniques described herein relate to a method including: receiving, by the at least one processor, a workflow request message from the initiator device, wherein the workflow request message is associated with a workflow request; wherein the workflow request message includes: at least one user profile identifier identifying the user profile associated with the user, at least one entity identifier identifying the entity and a actions-sequence identifier identifying the at least one automated processing actions-sequence, including a plurality of instructions corresponding to a plurality of actions; determining, by the at least one processor, the at least one automated processing actions-sequence based at least in part on: the actions-sequence identifier and at least one registered actions-sequence; generating, by the at least one processor, a first device-specific actions-sequence token for the actions-sequence session; wherein the first device-specific actions-sequence token is based on the workflow request message; generating, by the at least one processor, a workflow authorization request including the second device-specific actions-sequence token; receiving, by the at least one processor, a workflow execution authorization in response to the workflow authorization request; wherein the workflow execution authorization includes: a verification that the first device-specific actions-sequence token matches a second device-specific actions-sequence token, and user data of the user; wherein the second device-specific actions-sequence token is based on an electronic event authentication message from an initiator device associated with an entity; wherein the electronic event authentication message includes: the at least one user profile identifier identifying the user profile associated with the user, and the at least one entity identifier identifying the entity; executing, by the at least one processor, within the actions-sequence session, the instance of the at least one automated processing actions-sequence based at least in part on: the workflow execution authorization; the actions-sequence identifier, and user data of the user; wherein the user data of the user confidentially stored separate from the entity; generating, by the at least one processor, at least one criterion update in response to the executing the instance of the automated processing actions-sequence; and transmitting, by the at least one processor, a criterion notification to the initiator device, a computing device associated with the user, or both; wherein the criterion notification includes an indication of the at least one criterion update.

In some aspects, the techniques described herein relate to a method, further including electronically communicating, by the at least one processor, the criterion notification to contact information identified in the user data, wherein the contact information identifies a communication address of the computing device.

In some aspects, the techniques described herein relate to a method, wherein the contact information includes a telephone number specified in a user account at a financial institution and the criterion notification includes a text message to the telephone number.

In some aspects, the techniques described herein relate to a method, wherein the first device-specific actions-sequence token is a one-time token that expires upon generating the at least one criterion update.

In some aspects, the techniques described herein relate to a method, further including receiving, by the at least one processor, the electronic event authentication message via a payment advice and authorization message standard.

In some aspects, the techniques described herein relate to a method, further including receiving, by the at least one processor, the workflow request message via an application programming interface (API) over an Internet.

In some aspects, the techniques described herein relate to a method, wherein the initiator device includes a point-of-sale device.

In some aspects, the techniques described herein relate to a method, wherein the point-of-sale device includes a payment system associated with a merchant.

In some aspects, the techniques described herein relate to a method, further including receiving, by the at least one processor, a transaction fulfillment message as the at least one electronic message from a merchant associated with the initiator device, wherein the transaction fulfillment message indicates a fulfillment of a condition of a transaction associated with the workflow request message.

In some aspects, the techniques described herein relate to a method, wherein the criterion notification includes a purchased item shipping confirmation.

In some aspects, the techniques described herein relate to a system including: at least one processor configured to execute software instruction causing the at least one processor to perform steps to: receive a workflow request message from the initiator device, wherein the workflow request message is associated with a workflow request; wherein the workflow request message includes: at least one user profile identifier identifying the user profile associated with the user, at least one entity identifier identifying the entity and a actions-sequence identifier identifying the at least one automated processing actions-sequence, including a plurality of instructions corresponding to a plurality of actions; determine the at least one automated processing actions-sequence based at least in part on: the actions-sequence identifier and at least one registered actions-sequence; generate a first device-specific actions-sequence token for the actions-sequence session; wherein the first device-specific actions-sequence token is based on the workflow request message; generate at least one workflow authorization request including the first device-specific actions-sequence token; receive a workflow execution authorization in response to the workflow authorization request; wherein the workflow execution authorization includes: a verification that the first device-specific actions-sequence token matches a second device-specific actions-sequence token, and user data of the user; wherein the second device-specific actions-sequence token is based on an electronic event authentication message from an initiator device associated with an entity; wherein the electronic event authentication message includes: the at least one user profile identifier identifying the user profile associated with the user, and the at least one entity identifier identifying the entity; execute within the actions-sequence session, the instance of the at least one automated processing actions-sequence based at least in part on: the workflow execution authorization; the actions-sequence identifier, and user data of the user; wherein the user data of the user confidentially stored separate from the entity; generate at least one criterion update in response to the executing the instance of the automated processing actions-sequence; and transmit a criterion notification to the initiator device, a computing device associated with the user, or both; wherein the criterion notification includes an indication of the at least one criterion update.

In some aspects, the techniques described herein relate to a system, wherein the software instruction further cause the at least one processor to perform steps to electronically communicate the criterion notification to contact information identified in the user data, wherein the contact information identifies a communication address of the computing device.

In some aspects, the techniques described herein relate to a system, wherein the contact information includes a telephone number specified in a user account at a financial institution and the criterion notification includes a text message to the telephone number.

In some aspects, the techniques described herein relate to a system, wherein the first device-specific actions-sequence token is a one-time token that expires upon generating the at least one criterion update.

In some aspects, the techniques described herein relate to a system, wherein the software instruction further cause the at least one processor to perform steps to receive the electronic event authentication message via a payment advice and authorization message standard.

In some aspects, the techniques described herein relate to a system, wherein the software instruction further cause the at least one processor to perform steps to receive the workflow request message via an application programming interface (API) over an Internet.

In some aspects, the techniques described herein relate to a system, wherein the initiator device includes a point-of-sale device.

In some aspects, the techniques described herein relate to a system, wherein the point-of-sale device includes a payment system associated with a merchant.

In some aspects, the techniques described herein relate to a system, wherein the software instruction further cause the at least one processor to perform steps to receive a transaction fulfillment message as the at least one electronic message from a merchant associated with the initiator device, wherein the transaction fulfillment message indicates a fulfillment of a condition of a transaction associated with the workflow request message.

In some aspects, the techniques described herein relate to a system, wherein the criterion notification includes a purchased item shipping confirmation.

In some aspects, the techniques described herein relate to a method including: receiving, by the at least one processor, a workflow request message from an initiator device; where the workflow request message includes: at least one user profile identifier identifying a user profile of a user associated with the workflow request message, at least one entity identifier identifying an entity associated with the initiator device, and an actions-sequence identifier identifying a workflow including at least one automated processing actions-sequence; generating, by the at least one processor, a first device-specific actions-sequence token based on the workflow request message; receiving, by the at least one processor from at least one separate computer platform, a second device-specific actions-sequence token associated with electronic event authentication message; executing, by the at least one processor, an instance of the at least one automated processing actions-sequence based at least in part on: the first device-specific actions-sequence token matching the second device-specific actions-sequence token, the actions-sequence identifier, and user data of the user; generating, by the at least one processor, at least one message in response to the executing the instance of the automated processing actions-sequence; and transmitting, by the at least one processor, the at least one message to the initiator device, a computing device associated with the user, or both.

DETAILED DESCRIPTION

As used herein, the terms “and” and “or” may be used interchangeably to refer to a set of items in both the conjunctive and disjunctive in order to encompass the full description of combinations and alternatives of the items. By way of example, a set of items may be listed with the disjunctive “or”, or with the conjunction “and.” In either case, the set is to be interpreted as meaning each of the items singularly as alternatives, as well as any combination of the listed items.

FIGS.1through7illustrate systems and methods of computer-based interaction (e.g., communication) with one or more users. The following embodiments provide technical solutions and technical improvements that overcome technical problems, drawbacks and/or deficiencies in the technical fields involving efficiency of electronic interaction, including, without limitation, computer-based communication, and user data privacy and/or security. As explained in more detail, below, technical solutions and technical improvements herein include aspects of improved user authentication and/or activity authentication requests to enable computer-based interaction (e.g., direct contact) with the user without accessing user contact data. The following embodiments provide further technical solutions and technical improvements that overcome technical problems, drawbacks and/or deficiencies in the technical fields involving multi-entity integration into a workflow service by separating the workflow service from entity-specific systems.

There may be scenarios where a user may utilize an electronic account to engage in an electronic activity with a third-party. In some instances, additional workflows based on the electronic activity may be performed, such as a third-party sending the user a communication regarding the electronic activity. For example, a user may typically provide user information, such as contact information in order to receive the communication regarding the electronic activity.

A user sharing contact information with the third-party erodes the user's control of personal information and sensitive data, not to mention requires cumbersome and repetitive processes to provide the data to the third-party. Indeed, each entity that has access to the user's data is another opportunity for that data to be comprised or mishandled. Accordingly, a solution for secure and efficient direct contact to a user is needed. Thus, such workflows may face, for example, technical problems, such as account security, data privacy, and information control. For example, when a user shares contact information or provides access to his or her account, the user's control of personal information and/or sensitive data erodes. As another example of a technical problem, in some workflows, each entity may be given access to the user's data. Such access may present an opportunity for that data to be comprised or mishandled.

Accordingly, disclosed embodiments may provide technological improvements that address these challenges, such as by enabling the entity to have direct interaction (e.g., direct contact) with the user without necessarily relying on (or even having access to) a user's contact information or details of the user's electronic activity. Using these and other advancements discussed in this disclosure, disclosed embodiments may improve the security and/or confidentiality of the user's data, along with other technical advancements that may not be explicitly enumerated.

For example, at least some embodiments described herein may provide various technological improvements to various password services that are employed for one-click logins at websites and internet-based services. Such one-click logins may enable a user to login to their account with the password service and leverage a plug-in with individual websites and services authenticate access via the password service, rather than creating or logging in to an account specific to each individual website and service. At least some embodiments of the present disclosure may leverage the relationship of the password service with each individual website and service to provide additional workflows (e.g., providing notifications to the user, other functionalities requiring user data) without necessarily permitting the individual websites and services with access to the user data required for the workflow.

As another example, disclosed embodiments may include multi-factor authentication for user accounts that may improve security of the user accounts. In some embodiments, an illustrative computer system of the present disclosure may be configured to leverage the relationship with a password service, financial entity (e.g., account) and/or other trusted entity (e.g., account) to provide additional workflows to generate and/or communicate multi-factor authentication tokens to the user, without a need for third-party systems to access to the user contact information.

As another example problem, in user service contexts where a user pays a service provider or merchant using a financial account (e.g., using a credit card, debit card, contactless payment, or other suitable payment technology), the user may wait for fulfillment of her/his order to complete the service. Typically, the user may provide the service provider or merchant with contact information so that the user may be provided with a notification of fulfillment, e.g., via telephone, email, social media, internet messaging or other communication media, thus compromising the privacy and security of the user's data.

To mitigate this example issue, service providers and merchants may typically use a variety of computer-based tools such as queue management system, notification devices, and the like. However, at least some tools may require a user to carry around a device, repeatedly look for their order number on a screen, and/or provide personal contact information. A technological solution to the problem of the user giving access to user data or carrying a notification device may include leveraging the financial institution holding the financial account of the user to enable an electronic payment-based order fulfillment system that allows any user paying via an electronic payment method to receive notifications on their mobile devices without having to register themselves with the service provider or merchant. In particular, in some embodiments, contact with the user can be effectuated using a workflow that does not require the user to provide contact information to the service provider or merchant, such as through a service (“Agnostic Notification”) that is agnostic and allows for integration with any suitable bank on fulfillment of an electronic payment request and the associated service. Because the financial intuition has an existing relationship with the user, and has user contact information, the financial institution may utilize specially customized tokens and/or authentication messages to an agnostic workflow platform to trigger the workflow. Thus, the user data is protected from third-parties while enabling direct contact between the service provider or merchant and the user.

Further technical benefits become available to users and operators of these systems and methods. Moreover, various practical applications of the disclosed technology are also described, which provide further practical benefits to users and operators that are also new and useful improvements in the art.

FIG.1is a block diagram of an exemplary computer-based system for an agnostic secure workflow service in accordance with one or more embodiments of the present disclosure.

In some embodiments, technical solutions, such as those described above, may be provided by an agnostic workflow platform120and activity verification system160in communication with an initiator component110. The initiator component110may include an authorization request generator111to generate and send an authorization request103for an electronic activity to the activity verification system160, and a workflow request generator112to generate and send a workflow request105to the agnostic workflow platform. The initiator component110may include one or more suitable computing devices and/or computing systems having hardware and/or software components for initiating electronic activities.

In some embodiments, the initiator component110may include or be incorporated, partially or entirely into at least one point-of-sale device, personal computer (PC), laptop computer, ultra-laptop computer, tablet, touch pad, portable computer, handheld computer, palmtop computer, personal digital assistant (PDA), cellular telephone, combination cellular telephone/PDA, television, smart device (e.g., smart phone, smart tablet or smart television), mobile internet device (MID), messaging device, data communication device, and so forth.

In some embodiments, the activity verification system160may include one or more suitable computing devices and/or computing systems having hardware and/or software components for authorizing electronic activities. Thus, the activity verification system160may include hardware and software components including, e.g., the user computing device101hardware and software, cloud or server hardware and software, or a combination thereof.

In some embodiments, the activity verification system160may include hardware components such as a processor, which may include local or remote processing components. In some embodiments, the processor may include any type of data processing capacity, such as a hardware logic circuit, for example an application specific integrated circuit (ASIC) and a programmable logic, or such as a computing device, for example, a microcomputer or microcontroller that include a programmable microprocessor. Similarly, the activity verification system160may include storage, such as local hard-drive, solid-state drive, flash drive, database or other local storage, or remote storage such as a server, mainframe, database, or cloud provided storage solution. In some embodiments, the storage may maintain data for the activity verification system160. For example, profiles managed by the profile service170may be stored in the storage (e.g., in a profile management database). Other data and software of the activity verification system160may be stored for on-demand access in the storage.

The activity verification system160may include hardware and/or software components for a profile service170to access a user profile associated with the authorization request103and generate an authorization for the authorization request103. The activity verification system160may include hardware and/or software components for a tokenization service180to generate a workflow token for the electronic activity.

In some embodiments, the agnostic workflow platform120may include one or more suitable computing devices and/or computing systems having hardware and/or software components for implementing a workflow for the electronic activity associated with the initiator component110. The agnostic workflow platform120may include one or more centralized and/or distributed processing resources and/or storage resources. The agnostic workflow platform120may include a user computing device, a server, a cloud platform, or any suitable combination thereof. In some embodiments, a server may include a service point which provides processing, database, and communication facilities. By way of example, and not limitation, the term “server” can refer to a single, physical processor with associated communications and data storage and database facilities, or it can refer to a networked or clustered complex of processors and associated network and storage devices, as well as operating software and one or more database systems and application software that support the services provided by the server. Cloud servers are examples.

The agnostic workflow platform120may include a processor122and a storage121. In some embodiments, the processor122may include any type of data processing capacity, such as a hardware logic circuit, for example an application specific integrated circuit (ASIC) and a programmable logic, or such as a computing device, for example, a microcomputer or microcontroller that include a programmable microprocessor. In some embodiments, the storage121may include, e.g., a suitable memory or storage solutions for maintaining electronic data representing the activity histories for each account. For example, the data storage solution may include database technology such as, e.g., a centralized or distributed database, cloud storage platform, decentralized system, server, or server system, among other storage systems. In some embodiments, the data storage solution may, additionally or alternatively, include one or more data storage devices such as, e.g., a hard drive, solid-state drive, flash drive, or other suitable storage device. In some embodiments, the data storage solution may, additionally or alternatively, include one or more temporary storage devices such as, e.g., a random-access memory, cache, buffer, or other suitable memory device, or any other data storage solution and combinations thereof.

The storage121may include a workflow library123that catalogs workflows and a workflow queue124to maintain an order of the execution of workflows. The agnostic workflow platform120may include a tokenization service130instantiated with the processor122and the storage121to facilitate generating a second workflow token for the electronic activity to be validated against the workflow token of the activity verification system160. The agnostic workflow platform120may include a workflow management service140instantiated with the processor122and the storage121to facilitate orchestration and ordering of workflows for execution.

In some embodiments, a user computing device101may receive an output107of a workflow from the agnostic workflow platform120. Thus, the user computing device101may be provided with software services associated with an electronic activity without providing personal data to the initiator component110or to an entity associated therewith. In some embodiments, the user computing device101may include or be incorporated, partially or entirely into at least one personal computer (PC), laptop computer, ultra-laptop computer, tablet, touch pad, portable computer, handheld computer, palmtop computer, personal digital assistant (PDA), cellular telephone, combination cellular telephone/PDA, television, smart device (e.g., smart phone, smart tablet or smart television), mobile internet device (MID), messaging device, data communication device, and so forth.

In some embodiments, the terms “service”, “computer engine” and “engine,” including the profile service170, the tokenization service180, the tokenization service130and the workflow management service140, identify at least one software component and/or a combination of at least one software component and at least one hardware component which are designed/programmed/configured to manage/control other software and/or hardware components (such as the libraries, software development kits (SDKs), objects, etc.).

In some embodiments, a user's account in an agnostic workflow platform120may be leveraged to provide user data-based workflows to third-party entities while maintaining confidentiality of the user's data. The user data-based workflows can be performed contemporaneously with verification of an electronic activity relative to the user's account such that the entity can provide additional activity-related services to the user without accessing the user's data. As a result, the user's data is kept secure. Moreover, parallel processing and resource use related to the electronic activity and addition activity-related service are made more efficient due to reduced duplication of processing and hardware components.

In some embodiments, to enable the user data-based workflows, a computer component including an initiator component110, the agnostic workflow platform120and an activity verification system160utilize a specialized activity verification request103to leverage the existing user profile associated with the user. Using the specialized activity verification request103, the initiator component110can interface with the activity verification system160and the agnostic workflow platform120to trigger data and token exchanges that enable the user data-based workflow to be provided as a service to the initiator component110without compromising (e.g., opening to cyber-attack, etc.) the user data.

In some embodiments, a user data-based workflow may include any suitable actions-sequence formed of a sequence of computational and/or network actions to provide a service to the user. In some embodiments, the actions sequence may include actions for identifying a criterion associated with a particular device and/or particular user and/or particular electronic activity and performing a set of actions based on the criterion to provide a notification, display, service, data, or other service to the particular device and/or particular user. Thus, the actions sequence may be device-specific, user-specific, and/or customized based any suitable parameter or any combination thereof. For example, actions sequence may include generating and sending a notification based on the criterion, where the notification and/or criterion may be customized and/or configured specifically for the device and/or for the user.

In some embodiments, the initiator component110may be a third-party computing device or system with which a user may use to initiate an electronic activity with the third-party. For example, the initiator component110may be, e.g., a social network server, cloud storage system, online payment system, point-of-sale device, website account server, or other system and/or device for electronic activities.

In some embodiments, the initiator component110may rely on an external activity verification system160, such as, e.g., a password service, a password management service, a social network, an identity management system, a financial institution system, or other suitable computer-based system that may manage and/or verifies user identity and user-related electronic activities. Accordingly, in some embodiments, upon the user entering into an electronic activity with the initiator component110, an authorization request generator111of the initiator component110may be configured to receive electronic activity data, user data, entity data, and/or other activity-related data. In some embodiments, the data may be provided, e.g., by user input via a user interface, by third-party input via the user interface, and/or being automatically generated based, at least in part, on electronic activity attribute(s), or a combination thereof.

In some embodiments, the user may input user identity data, such as, e.g., a user identifier (e.g., name), a user account identifier, a user credential (e.g., password, personal identification number (PIN), biometric login, among others and combinations thereof), and other user identity data. In some embodiments, one or more of the user identity data items may be automatically determined or received. For example, the user may present an authentication device for executing electronic activities, such as, e.g., a hardware authentication device, two-factor authentication device, identity, or account card (e.g., credit card, debit card, personnel badge, etc.), or other device. Such a device may interact with the initiator component110to automatically provide user identity data and, in at least some embodiments, user credential data (e.g., cryptographic signatures, cryptographic keys, etc.).

In some embodiments, the user and/or the entity may provide electronic activity details, such as, e.g., a third-party identifier, an initiator device identifier, an activity type, an activity operation, an activity value, an activity quantity, among other electronic activity details. In some embodiments, one or more of the electronic activity details may be automatically generated based on data input by the user or entity or both. The authorization request generator111may be pre-programmed to generate one or more of the electronic activity details based on certain inputs by the user, entity, or both. For example, the entity may input a physical object effected by or otherwise associated with the electronic activity, and the authorization request generator111may automatically generate user-related, activity-related data such as the activity type, activity operation, activity value, and/or any other activity-related parameter (e.g., frequency, quantity, etc.) based on the physical object associated with the electronic activity.

In some embodiments, based on the electronic activity, certain workflows may be advantageous for providing data and information to the user, the entity or both. For example, a status of a transaction for food or for an online purchase may be better communicated to the user through direct contact. In another example, a user profile creation at a website or social network may be made more efficient and secure by data sharing via an account or identity management system. Accordingly, based on, e.g., the activity type or activity operation or other suitable activity-related data item, the authorization request generator111may be configured to automatically generate a workflow identifier identifying a requested workflow service, workflow type identifier identifying a workflow type, or both.

In some embodiments, the authorization request generator111may be configured to generate the activity verification request103based on the activity-related data. Accordingly, the authorization request generator111may append the activity-related data and the workflow identifier or workflow type or both to an electronic message to form the activity verification request103. The activity verification request103may have a format configured to provide the activity-related data to the activity verification system160for verification of the electronic activity.

In some embodiments, the activity verification request103may be a structured data message having predetermined data fields for specifying corresponding data items, e.g., according to a messaging or message standard. For example, the activity verification request103may have one or more data fields for one or more of, e.g., the user identifier, the user account identifier, the user credential, the third-party identifier, the initiator device identifier, the activity type, the activity operation, the activity value, the activity quantity, the workflow identifier, the workflow type, or other data item or combinations thereof. As a result, the activity verification system160may receive the activity verification request103and identify the authorization request to verify the electronic activity. In some embodiments, the data fields may conform to a standard, such as, e.g., an application programming interface (API) specification, standardized messaging structure (e.g., according to an International Organization for Standardization (ISO) standard), or other format for electronic messages.

In some embodiments, the initiator component110may include a data field in the activity verification request103specifying the device identifier and/or the third-party identifier. In some embodiments, the initiator component110may be registered with the activity verification system160, e.g., via the device identifier and/or the third-party identifier, as participating in providing workflows to users. For example, the device identifier and/or the third-party identifier may have an initiator profile in a profile service170of the activity verification system160. The initiator profile may include an attribute, flag, parameters, or other data item signifying the eligibility of initiator component110for providing workflows for the users. The initiator profile may enable a tokenization service180to interface with the agnostic workflow platform120to verify workflow requests. In some embodiments, the initiator profile may be omitted, and workflow requests can be verified against electronic activities without screening by the initiator profile.

In some embodiments, the initiator component110may communicate the activity verification request103to the activity verification system160to verify the electronic activity so that it may be executed or otherwise completed. In some embodiments, the activity verification request103may be communicated as an electronic message via any suitable messaging protocol or API, such as, e.g., a request-response or request-reply protocol, a publish-subscribe protocol, or any suitable communication protocol.

In some embodiments, the initiator component110and the activity verification system160may communicate via wired or wireless interfaces. For example, the connection may be a wireless network connection, such as a cellular network, WiFi, Bluetooth, Zigbee, Z-Wave, or other wireless network. In another example, the connection be a wired connection, such as, e.g., fiber optic, ethernet, coaxial, or other wired connection in a wired network such as, e.g., broadband, local area network, wide area network, or other suitable wired network. In some embodiments, the initiator component110and activity verification system160may be in communication with each other via a combination of wired networks, wired connections, wireless networks and wireless connections.

In some embodiments, the activity verification system160may receive the activity verification request103and verify the electronic activity. In some embodiments, the activity verification system160may be a part of the user computing device101.

In some embodiments, the activity verification system160may implement computer engines for the profile service170to manage profiles, the workflow management service140to authorize and manage the provision of a workflow service to the initiator component110, and the tokenization service130to secure access to the workflow service via token-based credentials.

In some embodiments, the profile service170may utilize the activity verification request103to identify the profile associated with the user and verify that the electronic activity is authentic as being associated with the user. In order to implement the profile service170, the profile service170may be include one or more computer engines that may include software components, hardware components, or a combination thereof. For example, each computer engine may include a dedicated processor and storage. In some embodiments, the computer engines share hardware resources, including the processor and storage of the activity verification system160via, e.g., a bus. Thus, the profile service170may include a memory including software and software instructions, such as, e.g., profile management and electronic activity verification, among other profile-related functionalities.

In some embodiments, as described above, the activity verification request103may include a structured data format for recording the data related to the electronic activity for which verification is requested. In some embodiments the profile service170may parse the data of the activity verification request103to extract, e.g., the user identifier, the profile identifier, or other identifier. In some embodiments, the activity verification request103may be an unstructured electronic message. Accordingly, the profile service170may utilize, e.g., natural language processing, or other technique for parsing unstructured data and automatically identifying the user identifier or profile identifier.

In some embodiments, using the user identifier, profile identifier, or other identifier, the profile service170may search the storage, e.g., using a suitable database query, text search, index look-up, or other search technique to identify and access the profile associated with the user participating in the electronic activity. As a result, the profile service170may associated the activity verification request103with the profile of the user.

Accordingly, in some embodiments, the profile service170may parse the data of the activity verification request103to extract the activity-related data. The activity-related data may be compared to data in the profile to determine whether the electronic activity is in fact associated with the user as opposed to a fraudulent or otherwise incorrect request, such as, e.g., a fraudulent transaction, an unverifiable login request, an impersonation in social media or fraudulent communication, among other unverifiable activities. Accordingly, data items such as, e.g., the activity type, the activity operation, the activity value or activity quantity, the activity date, the activity location, the entity, among other data can be analyzed in view of user behaviors to determine whether the electronic activity is being performed by the user and not someone else.

In some embodiments, in order to verify the activity, the profile service170may use the activity-related data from the activity verification request103with, e.g., software logic or rules for similarity to data in, e.g., the user profile, verified history, activity history, among other data and combinations thereof. For example, in some embodiments, the profile service170may, e.g., use past user behaviors using data mining, machine learning, statistical analysis and other techniques. Alternatively, or additionally, the profile service170may use other verification techniques to ensure that the electronic activity is verified only when it is authentic and correct, including, e.g., using external authentication services and cryptographic authentication.

In some embodiments, based on the verification of the electronic activity associated with the activity verification request103, the profile service170may append the activity verification to a response message104. In some embodiments, the activity verification system160may return the response message104to authorize the initiator component110to execute the electronic activity. Moreover, in some embodiments, the profile service170may log the activity verification request103and the response message104in the profile associated with the user. The log may specify the activity-related data and the authorization of the electronic activity, and the registration of the initiator component110for workflow services.

In some embodiments, upon receiving the response message104indicating authorization of the electronic activity, the initiator component110may implement a workflow request generator112to request instantiation of a workflow by the agnostic workflow platform120. In some embodiments, the workflow request generator112may track a status of the electronic activity and generate a workflow request105based on the status. The workflow request generator112may issue the workflow request105, e.g., periodically, upon at least one trigger condition that triggers the workflow request105, or by any other trigger or any combination thereof. For example, one or more trigger conditions may include, e.g., without limitation, order status changes based on an electronic activity including an order of a product or service (e.g., food delivery status, reservation status, vehicle maintenance/repair status, product maintenance/repair status, etc.), file download/transfer/upload status changes (e.g., download/transfer/upload start, in progress, complete, etc.), ride share status changes (e.g., en-route to pick-up, nearby to pick-up, waiting for pick-up, en-route to destination, nearby to destination, drop-off complete, etc.), among other trigger conditions in one or more electronic activities, or any combination thereof. In some embodiments, the trigger may be periodic updates according to, e.g., one minute, two-minute, three-minute, four-minute, five-minute, ten-minute, fifteen-minute, twenty-minute, twenty-five-minute, thirty-minute, forty-five-minute, one hour, two-hour, three-hour, four-hour, five-hour, six-hour, eight-hour, ten-hour, twelve-hour, one day or any other suitable period based on the electronic activity or any combination thereof.

In some embodiments, the workflow request generator112may formulate the workflow request105based on the trigger conditions. In some embodiments, depending on the electronic activity being executed, the workflow being request may be responsive to certain conditions. For example, in a food service transaction, the trigger conditions may be the food being ready to serve or ready for pickup or other status and combinations thereof. Similarly, for an online ordering transaction, the trigger condition may include a shipment of the online order or other status and combinations thereof. In some embodiments, where the trigger conditions are satisfied, the workflow request generator112may generate the workflow request105and append one or more trigger conditions, as well as, e.g., a workflow identifier, the user identifier, the initiator device identifier, the third-party identifier, the activity type, the activity operation, or other activity-related data and combinations thereof.

In some embodiments, the workflow identifier may specify a particular type of workflow for effectuating a particular functionality. For example, the workflow identifier may specify workflows including, e.g., a notification service, a social media posting service, an automated payment service, an automated scheduling service, or other suitable workflow or any combination thereof.

In some embodiments, the workflow request105may be sent to the agnostic workflow platform120to request the workflow to be performed. In some embodiments, the workflow request generator112may interface with the agnostic workflow platform120to provide the workflow request105via a suitable interface, such as, e.g., an API, a messaging adapter, or other software processor or system to cause the workflow to be executed. For example, the workflow request generator112may provide the workflow request105to the agnostic workflow platform120via a suitable API call.

In some embodiments, the agnostic workflow platform120may implement computer engines for a tokenization service130to generate and verify actions-sequence tokens to authenticate the workflow request105via token-based credentials, and a workflow management service140to authorize and manage the provision of a workflow service to the initiator component110.

In some embodiments, at least one workflow request105may include a structured data format for recording the data related to the electronic activity for which verification is requested. In some embodiments the tokenization service130may parse the data of the workflow request105to extract, e.g., the user identifier, the user profile identifier, the entity identifier, the initiator device identifier, the workflow identifier, an electronic activity identifier, an activity verification system identifier associated with the activity verification system160, and/or other identifier and/or other attributes or any combination thereof. In some embodiments, the tokenization service130may be an unstructured electronic message. Accordingly, the tokenization service130may utilize, e.g., natural language processing or other technique(s) for parsing unstructured data and automatically identifying the user identifier or account identifier.

Accordingly, in some embodiments, the tokenization service130may parse the data of the workflow request105to extract workflow-related data. The workflow-related data may be used to determine whether the electronic activity is in fact associated with the user, a registered initiator component/entity, and/or a valid workflow, as opposed to a fraudulent or otherwise incorrect request (e.g., a fraudulent transaction, an unverifiable login request, an impersonation in social media, fraudulent communication, other unverifiable activities).

In some embodiments, the tokenization service130may generate a secure and identifiable actions-sequence token enabling the workflow management service140to perform the request for the workflow. In some embodiments, the tokenization service130may utilize the identified workflow and the electronic activity as specified in the workflow request105to generate the secure token. In order to implement the tokenization service130, the tokenization service130may include one or more computer engines that may include software components, hardware components, or a combination thereof. For example, each computer engine may include a dedicated processor and storage. In some embodiments, the computer engines share hardware resources, including the processor122and storage121of the agnostic workflow platform120via, e.g., a bus. Thus, the tokenization service130may include a memory including software and software instructions, such as, e.g., account management and electronic activity verification, among other account-related functionalities.

In some embodiments, the tokenization service130may extract the indicator of the workflow verification as well as the workflow type or workflow identifier from the workflow request105. In some embodiments, based on the indicator, the tokenization service130may generate a digital actions-sequence token that represents permission to request a workflow and access the workflow functionality. Thus, in some embodiments, the tokenization service130may generate, e.g., a one-time use token, such as, e.g., a one-time password, a cryptographic hash, a message authentication code (MAC), or other limited use token. For example, the tokenization service130may tokenize some or all the data of the workflow request105using, e.g., a randomly generated value, a cryptographic hash of the indicator, or a combination of a cryptographic hash with the indicator and the randomly generated value. In an example, the tokenization may also include the third-party identifier, or a device identifier associated with the initiator component110in the cryptographic hash to, e.g., ensure the requester requesting a workflow is an authorized requester according to an identifier associated with the requester. Accordingly, the tokenization service130may produce tokens of varying security levels that are specific to the initiator device (device specific), to the user (user specific), to the third-party (entity specific), to the activity verification system (activity verification system specific), or to any other suitable device and/or entity or any combination thereof.

In some embodiments, the tokenization service130may generate and record the token and the associated electronic activity and/or workflow using, e.g., a distributed ledger such as a blockchain, including, e.g., Bitcoin, Ethereum, or other blockchain technologies. In some embodiments, the exemplary computer-based systems/platforms, the exemplary computer-based devices, and/or the exemplary computer-based components of the present disclosure may be configured interact and/or to store data in one or more private and/or private-permissioned cryptographically-protected, distributed databased such as, without limitation, a blockchain (distributed ledger technology), Ethereum (Ethereum Foundation, Zug, Switzerland), and/or other similar distributed data management technologies. For example, as utilized herein, the distributed database(s), such as distributed ledgers ensure the integrity of data by generating a chain of data blocks linked together by cryptographic hashes of the data records in the data blocks. For example, a cryptographic hash of at least a portion of data records within a first block, and, in some cases, combined with a portion of data records in previous blocks is used to generate the block address for a new digital identity block succeeding the first block. As an update to the data records stored in the one or more data blocks, a new data block is generated containing respective updated data records and linked to a preceding block with an address based upon a cryptographic hash of at least a portion of the data records in the preceding block. In other words, the linked blocks form a blockchain that inherently includes a traceable sequence of addresses that can be used to track the updates to the data records contained therein. The linked blocks (or blockchain) may be distributed among multiple network nodes within a computer network such that each node may maintain a copy of the blockchain. Malicious network nodes attempting to compromise the integrity of the database must recreate and redistribute the blockchain faster than the honest network nodes, which, in most cases, is computationally infeasible. In other words, data integrity is guaranteed by the virtue of multiple network nodes in a network having a copy of the same blockchain. In some embodiments, as utilized herein, a central trust authority for sensor data management may not be needed to vouch for the integrity of the distributed database hosted by multiple nodes in the network.

In some embodiments, the exemplary distributed blockchain-type ledger implementations of the present disclosure with associated devices may be configured to affect transactions involving Bitcoins and other cryptocurrencies into one another and into (or between) so-called FIAT money or FIAT currency and vice versa.

In some embodiments, the exemplary distributed blockchain-type ledger implementations of the present disclosure with associated devices are configured to utilize smart contracts that are computer processes that facilitate, verify and/or enforce negotiation and/or performance of one or more particular activities among users/parties. For example, an exemplary smart contract may be configured to be partially or fully self-executing and/or self-enforcing. In some embodiments, the exemplary inventive asset-tokenized distributed blockchain-type ledger implementations of the present disclosure may utilize smart contract architecture that can be implemented by replicated asset registries and contract execution using cryptographic hash chains and Byzantine fault tolerant replication. For example, each node in a peer-to-peer network or blockchain distributed network may act as a title registry and escrow, thereby executing changes of ownership and implementing sets of predetermined rules that govern transactions on the network. For example, each node may also check the work of other nodes and in some cases, as noted above, function as miners or validators.

In some embodiments, in order to ensure the initiator component110accesses only the workflow for which it is authorized, the tokenization service130may verify the token with the activity verification system160.

Additionally, in some embodiments, the agnostic workflow platform120may provide a secure and confidential workflow platform that would enable workflows without maintaining user data. Rather, the agnostic workflow platform120may use the token for the workflow request105to request a temporary or one-time use access to user data for effectuating the requested workflow. Accordingly, in some embodiments, the agnostic workflow platform120may include an interface150for interfacing with the activity verification system160. In some embodiments, the interface150may enable third-party integration with the agnostic workflow platform120for providing secured and confidential workflows to users across any one or more activity verification systems.

In some embodiments, the interface150may extract from the workflow request105the activity verification system identifier that identifies the activity verification system160. In some embodiments, when the workflow request105does not specify the activity verification system identifier, the interface150may determine the activity verification system160based on, e.g., electronic activity identifier, the user identifier, the initiator device identifier, the entity identifier, among other data from the workflow request105or any combination thereof. For example, the interface150may include an address index or mapping that correlates the activity verification system160to one or more of the data from the workflow request105. As a result, the interface150may issue a workflow authorization request to the activity verification system160, e.g., via a suitable API pull request, a message according to a suitable message adapter, or by any other suitable interfacing technology. In response, the activity verification system160may verify and provide user data for executing the workflow.

In some embodiments, rather than identifying the activity verification system160, the interface150may publish the workflow authorization request via a publish-subscribe modality. Accordingly, the associated activity verification system160may inspect the workflow authorization request and respond with a verification and user data for workflow execution.

In some embodiments, the interface150may instead receive a push request and/or published message (via the publish-subscribe modality) from the activity verification system160. The activity verification system160may generate a separate token independently and in parallel to the agnostic workflow platform120and may provide the separate token and/or user data for the workflow via the interface150without a request from the interface150.

In some embodiments, to enable the agnostic workflow platform120to execute the requested workflow, the activity verification system160may verify the actions-sequence token. To do so, the activity verification system160may utilize a tokenization service180to generate an actions-sequence token for each activity verification request, including the activity verification request103. Similar to the tokenization service130, the tokenization service180may generate a digital token that represents permission to execute a workflow for a user. Thus, in some embodiments, the tokenization service180may generate, e.g., a one-time use token, such as, e.g., a one-time password, a cryptographic hash, a message authentication code (MAC), or other limited use token. For example, the tokenization service180may tokenize electronic activity-related data from the activity verification request103using, e.g., a randomly generated value, a cryptographic hash of the indicator, or a combination of a cryptographic hash with the indicator and the randomly generated value. In an example, the tokenization may also include the third-party identifier, or a device identifier associated with the initiator component110in the cryptographic hash to, e.g., ensure the requester requesting a workflow is an authorized requester according to an identifier associated with the requester. Accordingly, the tokenization service130may produce tokens of varying security levels.

In some embodiments, to ensure compatibility, the tokenization service180and the tokenization service130may use the same data items to generate the actions-sequence tokens. For example, e.g., of the tokenization service180and the tokenization service130may identify, e.g., the user identifier, the user profile identifier, the entity identifier, the initiator device identifier, the electronic activity identifier, a time, a date, among other data items or any combination thereof. The actions-sequence tokens may each then be generated using the same algorithm, such as the same cryptographic hashing or other suitable algorithm. As a result, one actions-sequence token may be used to verify the other such that the workflow request105can be matched to the activity verification request103. In some embodiments, if the tokens are matched and the workflow request105is associated with a particular activity verification request, the tokenization service180may nevertheless invalidate the actions-sequence token if the response message104did not authorize the electronic activity. Thus, where the electronic activity is invalidated, the activity verification system160may also invalidate the workflow request105.

In some embodiments, the actions-sequence token produced by the activity verification system160may be linked to the electronic activity logged in the profile service170for which the token is generated. Thus, in some embodiments, the tokenization service180compare the token from the tokenization service130to match the workflow request105to the activity verification request103based on the logged data in the profile service170and identify the electronic activity including attributes thereof, such as the user identifier associated therewith.

In some embodiments, upon matching the actions-sequence token(s), thus validating the workflow request105and identifying the user via the user identifier, the tokenization service180may generate a workflow execution authorization. In some embodiments, the workflow execution authorization may include, e.g., a verification confirmation indicating that the workflow request105matches the activity verification request103and workflow-related user data. For example, in some embodiments, the workflow authorization request may specify a workflow type and/or workflow data requirements. Thus, the tokenization service180may determine the data requirements for workflow-related data based on the workflow type and/or the workflow data requirements. Accordingly, the workflow execution authorization may include the workflow-related data, such as, e.g., user contact information, a user computing device identifier, a user social media account, a user blog, a user address, or other user information necessary for executing the workflow or any combination thereof.

In some embodiments, rather than providing the workflow-related data to the agnostic workflow platform120with the workflow execution authorization, the agnostic workflow platform120may maintain, e.g., in the storage121, a copy of the user profile associated with each activity verification system that interfaces with the agnostic workflow platform120. Thus, activity verification system160may verify the actions-sequence token and return the workflow execution authorization indicating the verification of the token without communicating any user data. In some embodiments, each activity verification system that interfaces with the agnostic workflow platform120may update the user profiles storing user data in the agnostic workflow platform120via periodic uploads. For example, the user profiles may be updated upon each period including, e.g., six hours, eight hours, twelve hours, twenty-four hours, two days, three days, four days, five days, six days, seven days, two weeks, three weeks, four weeks, one month, two months, three months, four months, six months, one year, etc.

In some embodiments, upon verifying the workflow request105, the tokenization service130may add the workflow request105and/or the workflow data associated with the workflow request105to a workflow queue124, e.g., in the storage121. In some embodiments, the workflow queue124may establish an order of execution of each workflow request received by the agnostic workflow platform120. In some embodiments, the order may be a first-in-first-out (FIFO) queue or may be ordered based time of receiving the workflow request105, time of receiving a workflow execution authorization, priority value and/or flag, location, a due data, or any other suitable ordering methodology or any combination thereof.

In some embodiments, the workflow management service140may access the verification and the workflow request105in the workflow queue124based on the ordering and may identify an associated workflow and execute the workflow for the initiator component110. In some embodiments, the workflow may include a preconfigured sequence of actions constructed of one or more modules or functions of instructions. In some embodiments, the instructions may include customized instructions, customized combinations of instructions, template instructions, or other suitable software construct to define the set of actions in the actions sequence. In some embodiments, the workflow library123may store a library of registered instructions, sets of instruction combinations of instructions, templates of instructions, functions defined by instructions, modules defined by instructions, actions formed by one or more instructions, sequences of actions, or other suitable library of the preconfigured sequences of actions that form each workflow in the workflow library123.

In order to implement the workflow management service140, the workflow management service140may include one or more computer engines that may include software components, hardware components, or a combination thereof. For example, each computer engine may include a dedicated processor and storage. In some embodiments, the computer engines share hardware resources, including the processor122and storage121of the agnostic workflow platform120via, e.g., a bus. Thus, the workflow management service140may include a memory including software and software instructions, such as, e.g., workflow management, workflow authentication and workflow execution, among other workflow management-related functionalities.

In some embodiments, the workflow management service140may parse the data of the workflow request105to extract, e.g., the workflow type, the workflow identifier, or other identifier. In some embodiments, the workflow request105may be an unstructured electronic message. Accordingly, the workflow management service140may utilize, e.g., natural language processing, or other technique for parsing unstructured data and automatically identifying the workflow type, the workflow identifier, or other identifier.

In some embodiments, using the workflow type and/or the workflow identifier, the workflow management service140may reference the workflow library123, e.g., using a suitable database query, text search, index look-up, or other search technique to identify and access a registered workflow corresponding to the workflow associated with the workflow request105.

In some embodiments, the workflow management service140authorizes the initiator component110to access the identified workflow associated with the workflow request105. For example, in some embodiments, the workflow library123may include permissioned and/or participating third-party entities. Such permissioned or participating third-party entities may be specified in workflow records that define each workflow. For example, a workflow record can include attributes defining a particular workflow, such as, e.g., a workflow type, a workflow identifier, a workflow function, third-party identifiers identifying permissioned or participating third-party entities, as well as any other suitable characteristics and attributes of each workflow. Based on the listed third-party identifiers in the record of the identified workflow of the workflow request105, the workflow management service140may authorize the entity for access to the workflow functions via the agnostic workflow platform120.

In some embodiments, upon validation, the workflow management service140may manage the workflow service to execute the appropriate workflow using user data received form the activity verification system160via the interface150in the workflow execution authorization, such as, e.g., contact information or other user information. In some embodiments, the workflow management service140may trigger the execution of the workflow and output the workflow output107to the user computing device101. In some embodiments, the workflow output107may include workflow functionality such as, e.g., issuing a workflow output107to the user computing device101. For example, the workflow may generate a status update notification that notifies the user of the status of the electronic activity. The status update notification may then be sent to the user computing device101according to the user's contact information while protecting the contact information from third-party access and improving convenience for the user.

FIG.2is a block diagram of another exemplary computer-based system for an agnostic secure workflow service using the tokenization service130in accordance with one or more embodiments of the present disclosure. In some embodiments, the tokenization service130may communicate with the tokenization service180and profile service170of the activity verification system160through the interface150as described above.

In some embodiments, the workflow request105may be provided to the agnostic workflow platform110. In some embodiments, the workflow request105may include workflow attributes that may be used to define or otherwise determine a specific sequence of actions to be performed based on the attributes of the workflow request105and/or private user data. In some embodiments, the attributes of the workflow request105may include, e.g., a user identifier, a user profile identifier, an initiator device identifier, an entity identifier of an entity associated with an electronic activity, one or more electronic activity data (e.g., type, data, quantity, event indicator(s) indicating the occurrence of one or more events associated with the electronic activity, etc.), one or more workflow parameters (e.g., workflow type, actions to be performed, output type, scheduled execution data and/or time, one or more criteria for triggering and/or executing the workflow among other workflow parameters or any combination thereof), among other attributes or any combination thereof. For example, the workflow request105may include a fulfillment notification request for an electronic activity including a purchase transaction at an entity including a merchant of goods and/or services. In such an example, the workflow request105may include attributes including, e.g., an entity identifier including a merchant identifier, an electronic activity identifier including a transaction ID, electronic activity data including transaction details such as item or service purchase, quantity purchased, location of transaction, time of transaction, fulfillment status of the purchase, value of the purchase, among other transaction details or any combination thereof, and/or workflow parameters including fulfillment notification details (e.g., the fulfillment status), among other attributes or any combination thereof.

In some embodiments, upon ingesting the workflow request105and generating the associated action-sequence token, the tokenization service130may verify the token with the tokenization service180of the activity verification system160. Thus, the tokenization service130may ensure the initiator component110accesses only the workflow for which it is authorized in a secure and confidential manner.

Additionally, in some embodiments, the agnostic workflow platform120provides a secure and confidential workflow platform that enables workflows without maintaining user data. Rather, the agnostic workflow platform120may use the token for the workflow request105to request a temporary or one-time use access to user data for effectuating the requested workflow. Accordingly, in some embodiments, the agnostic workflow platform120may include an interface150for interfacing with the activity verification system160. In some embodiments, the interface150may enable third-party integration with the agnostic workflow platform120for providing secured and confidential workflows to users across any one or more activity verification systems.

In some embodiments, the interface150may extract from the workflow request105the activity verification system identifier that identifies the activity verification system160. In some embodiments, where the workflow request105does not specify the activity verification system identifier, the interface150may determine the activity verification system160based on, e.g., electronic activity identifier, the user identifier, the initiator device identifier, the entity identifier, among other data from the workflow request105or any combination thereof. For example, the interface150may include an address index or mapping that correlates the activity verification system160to one or more of the data from the workflow request105. As a result, the interface150may issue a workflow authorization request108to the activity verification system160, e.g., via a suitable API pull request, a message according to a suitable message adapter, or by any other suitable interfacing technology. In response, the activity verification system160may verify and provide user data for executing the workflow.

In some embodiments, rather than identifying the activity verification system160, the interface150may publish the workflow authorization request108via a publish-subscribe modality. Accordingly, the associated activity verification system160may inspect the workflow authorization request108and respond with a verification and user data for workflow execution.

In some embodiments, the interface150may instead receive a push request and/or published message (via the publish-subscribe modality) from the activity verification system160. The activity verification system160may generate a separate action-sequence token independently and in parallel to the agnostic workflow platform120and may provide the separate action-sequence token and/or user data for the workflow via the interface150without a request from the interface150.

In some embodiments, to enable the agnostic workflow platform120to execute the requested workflow, the activity verification system160may verify the action-sequence token. To do so, the activity verification system160may utilize a tokenization service180to generate an action-sequence token for each activity verification request, including the activity verification request103. Similar to the tokenization service130, the tokenization service180may generate a digital action-sequence token that represents permission to execute a workflow for a user. Thus, in some embodiments, the tokenization service180may generate, e.g., a one-time use token, such as, e.g., a one-time password, a cryptographic hash, a message authentication code (MAC), or other limited use token. For example, the tokenization service180may tokenize electronic activity-related data from the activity verification request103using, e.g., a randomly generated value, a cryptographic hash of the indicator, or a combination of a cryptographic hash with the indicator and the randomly generated value. In an example, the tokenization may also include the third-party identifier, or a device identifier associated with the initiator component110in the cryptographic hash to, e.g., ensure the requester requesting a workflow is an authorized requester according to an identifier associated with the requester. Accordingly, the tokenization service130may produce tokens of varying security levels.

In some embodiments, to ensure compatibility, the tokenization service180and the tokenization service130may use the same data items to generate the tokens. For example, e.g., of the tokenization service180and the tokenization service130may identify, e.g., the user identifier, the third-party identifier, the initiator device identifier, the electronic activity identifier, a time, a date, among other data items or any combination thereof. The action-sequence tokens may each then be generated using the same algorithm, such as the same cryptographic hashing or other suitable algorithm. As a result, one action-sequence token may be used to verify the other action-sequence token such that the workflow request105can be matched to the activity verification request103. In some embodiments, if the action-sequence tokens are matched and the workflow request105is associated with a particular activity verification request, the tokenization service180may nevertheless invalidate the action-sequence token if the response message104did not authorize the electronic activity. Thus, where the electronic activity is invalidated, the activity verification system160may also invalidate the workflow request105.

In some embodiments, the action-sequence token produced by the activity verification system160may be linked to the electronic activity logged in the profile service170for which the token is generated. Thus, in some embodiments, the tokenization service180compare the token from the tokenization service130to match the workflow request105to the activity verification request103based on the logged data in the profile service170and identify the electronic activity including attributes thereof, such as the user identifier associated therewith.

In some embodiments, upon matching the action-sequence tokens, thus validating the workflow request105and identifying the user via the user identifier, the tokenization service180may generate a workflow execution authorization109. In some embodiments, the workflow execution authorization109may include, e.g., a verification confirmation indicating that the workflow request105matches the activity verification request103and workflow-related user data. For example, in some embodiments, the workflow authorization request108may specify a workflow type and/or workflow data requirements. Thus, the tokenization service180may determine the data requirements for workflow-related data based on the workflow type and/or the workflow data requirements. Accordingly, the workflow execution authorization109may include the workflow-related data, such as, e.g., user contact information, a user computing device identifier, a user social media account, a user blog, a user address, or other user information necessary for executing the workflow or any combination thereof. The workflow request105and the workflow-related data of the workflow execution authorization109may then be provided to the workflow management service140for identification, orchestration, and execution of the associated workflow on behalf of the initiator component110.

FIG.3is a block diagram of another exemplary computer-based system for an agnostic secure workflow service using a workflow management service in accordance with one or more embodiments of the present disclosure. In some embodiments, the workflow management service140may communicate with the tokenization service130as described above. The workflow management service140may include a workflow identifier141, a workflow loader142and a workflow engine143to identify, load and execute a workflow from the workflow library123. Each of the workflow identifier141, the workflow loader142and the workflow engine143may be each include components such as at least one software component and/or a combination of at least one software component and at least one hardware component which are designed/programmed/configured to manage/control other software and/or hardware components (such as the libraries, software development kits (SDKs), objects, etc.).

In some embodiments, the workflow management service140may receive the workflow request105and the workflow-related data of the workflow execution authorization109, e.g., from the tokenization service130. In some embodiments, the initiator component110is associated with an entity with which a user is engaging in an electronic activity.

In some embodiments, the workflow request105includes data fields based on a message standard. For example, some request messages include standard data structures with standard data fields depending on the service provider (e.g., an operator of the systems and services associated with the workflow management service140). In some embodiments, the message standard may include one or more data fields for requesting secure workflows for providing functionality to the entity and the user.

In some embodiments, the data field(s) of the workflow request105may indicate a secure workflow for providing a service to the user in a secure manner that maintains user data confidentiality. In some embodiments, a workflow identifier141of the workflow management service140may utilize the auxiliary data field to extract a workflow identifier of the workflow request. Using the data in the auxiliary data field, the workflow identifier141may consult a workflow library123to identify an associated workflow file. The workflow file may include, e.g., a secure workflow, workflow type data, workflow permissions data, among other workflow data and information for each registered workflow registered with the workflow management service140and stored in the workflow library123. Thus, the workflow identifier141can identify and access the particular secure workflow associated with the workflow request105.

In some embodiments, in order to ensure the initiating device accesses only the workflow for which it is authorized and that only the initiating device accesses the workflow, the tokenization service130may link the token to the workflow. Thus, the workflow execution authorization109validating the token to authorize the workflow is associated with a device-specific actions-sequence token. For example, in some embodiments, the activity verification system160and/or the workflow management service140may include, e.g., an index, library, look-up-table, a blockchain or other data structure to catalog the token and the associated workflow, as well as any other suitable data, such as, e.g., the third-party identifier, the initiator device identifier, the activity identifier or activity type, the user identifier, among any other suitable data.

In some embodiments, the validation of the token via the workflow execution authorization109authorizations the workflow identifier141to provide the workflow request105, the associated workflow identifier and the workflow-related data to a workflow loader142to identify and load the secure workflow from the workflow library123. In some embodiments, the workflow loader142may utilize the workflow identifier to reference the workflow library123, e.g., according to a look-up-table, index, database query, search, or other suitable technique. In some embodiments, the entry in the workflow library123associated with the secure workflow may store or otherwise link to the secure workflow. For example, the secure workflow may be a locally stored or cloud service stored software program that is loaded by the workflow library123. In other examples, the secure workflow may be an external service that is called using, e.g., a suitable API request by the entry in the workflow library123. Other techniques for loading the software functionality associated with the secure workflow are also contemplated.

In some embodiments, upon loading the secure workflow for providing functionality on behalf of the initiating device, a workflow engine143may execute the secure workflow. Accordingly, an instance of the secure workflow is created and executed on behalf of the initiating device to provide a device-specific secure workflow.

In some embodiments, the secure workflow, when executed, may perform user data related actions on behalf of the initiating device. Thus, user data related actions may be triggered by the initiating device without the initiating device handling or accessing the user data, maintaining security of the user data. Because the activity verification system validates the workflow request105and has an existing relationship with the user, including an existing user profile with, e.g., contact information as well as other user information, the agnostic workflow platform may leverage that relationship to enable the entity to provide services to the user without the entity having the infrastructure or user data to do so, thus improving functionality of the initiating device by operating on its behalf upon receipt of a valid workflow request105. Moreover, the agnostic workflow platform may interface with any number of additional activity verification systems to enable access to user data in a secure manner for users associated with any one or more of the activity verification systems without control of the user data leaving the activity verification systems.

In some embodiments, to further improve the security of the user data, the workflow engine143may be permissioned to access confidentially stored user data, such as, e.g., an encrypted user profile or other encrypted user data. Such encrypted data may be inaccessible to outside devices, ensuring security and confidentiality.

In some embodiments, the workflow engine143may execute the secure workflow according to the workflow request105, which may specify, e.g., an electronic activity status related to a status of the electronic activity. In some embodiments, the workflow request105may include workflow attributes that may be used to define or otherwise determine a specific sequence of actions to be performed based on the attributes of the workflow request105and/or private user data. In some embodiments, the attributes of the workflow request105may include, e.g., a user identifier, a user profile identifier, an initiator device identifier, an entity identifier of an entity associated with an electronic activity, one or more electronic activity data (e.g., type, data, quantity, event indicator(s) indicating the occurrence of one or more events associated with the electronic activity, etc.), one or more workflow parameters (e.g., workflow type, actions to be performed, output type, scheduled execution data and/or time, one or more criteria for triggering and/or executing the workflow among other workflow parameters or any combination thereof), among other attributes or any combination thereof. For example, the workflow request105may include a fulfillment notification request for an electronic activity including a purchase transaction at an entity including a merchant of goods and/or services. In such an example, the workflow request105may include attributes including, e.g., an entity identifier including a merchant identifier, an electronic activity identifier including a transaction ID, electronic activity data including transaction details such as item or service purchase, quantity purchased, location of transaction, time of transaction, fulfillment status of the purchase, value of the purchase, among other transaction details or any combination thereof, and/or workflow parameters including fulfillment notification details (e.g., the fulfillment status), among other attributes or any combination thereof.

Thus, for example, the workflow may include one or more action sequences associated with performing transaction or service fulfillment status notifications, order fulfillment status notifications, multi-factor authentication token provision, among other statuses associated with performance and fulfillment of the electronic activity. Accordingly, the workflow engine143may use the electronic activity status to test a criterion associated with the workflow of the workflow request105. Where the status satisfies the criterion, the workflow engine143may proceed to execute the sequence of actions of the workflow.

In some embodiments, the workflow engine143may utilize one or more of the attributes of the workflow request105as inputs to the associated action sequence. The sequence of action in the sequence may then process the attribute(s) to generate a workflow output107including, e.g., a status notification to notify a user of the activity status. For example, where the activity status includes a transaction fulfillment status, the secure workflow may generate a status notification including, e.g., an indication of the fulfillment status such as, e.g., processing, shipped, delivered, ready to serve, served, or other status. In another example, where the activity status includes a multifactor authentication token status, the secure workflow may generate a status notification including, e.g., a multifactor authentication token, an amount of time left for token validity, among other multifactor authentication token status information. In some embodiments, the secure workflow may also generate the multifactor authentication token in addition to the notification regarding the token. In some embodiments, the secure workflow may look up or reference an externally generated multifactor authentication token.

In some embodiments, the workflow engine143using the secure workflow may generate the status notification and determine user contact information. In some embodiments, the user contact information may include, e.g., an email address, a social media account, a device ID for push notifications, a telephone number (e.g., for an automated voice call or an automated text message), an internet messaging account, or other contact information. In some embodiments, the contact information may also include, e.g., user contact preferences. For example, the contact information in the user profile may be selectable by the user to include modes of communication (e.g., email, text message, phone call, internet message, social media, push notification, etc.). The selected modes of communication may be a global preference (e.g., for all communications and notifications), or may be specified for types of communications or sources of the communications. For example, the user profile may include a user specified contact preference for the entity associated with the initiating device. Accordingly, the workflow engine143may use the device identifier and/or entity identifier to determine the matching user preference to the entity.

In some embodiments, based on the contact information from the user profile of the activity verification system160and/or locally stored by the agnostic workflow platform120, the workflow engine may transmit the status notification to the user computing device, e.g., using an associated API request or by another suitable mechanism.

In some embodiments, the workflow engine143may alternatively or additionally provide the workflow output107to the initiating device. For example, in some scenarios the user may be located at the initiating device. As a result, the workflow output107may be advantageously delivered to the initiating device to alert the user while at the initiating device's location, increasing the likelihood that the user receives the workflow output107.

In some embodiments, because the token is tied to the workflow validated for the initiating device and the electronic activity, the token may expire upon transmission of the workflow output107. In some embodiments, the expiration may be a result of a time limit elapsing, by the workflow engine143deleting the token, by the token including a hash as a function of a date of authorization, electronic activity identifier, or other data unique to the electronic activity for which the workflow output107is issued.

Accordingly, the workflow management service140may securely and efficiently provide functionality using user data on behalf of an initiating device to enhance initiating device functionality while maintaining security and confidentiality of user data.

FIG.4illustrates a flowchart of an exemplary computer-based method for an agnostic secure workflow service in accordance with one or more embodiments of the present disclosure. In some embodiments, the method includes computer implemented steps401through408to enable the provision of services to a user based on user data while maintaining the confidentiality and security of the user data by preventing disclosure to a device with which the user is executing an electronic event and/or activity.

In some embodiments, at step401, a system, such as the agnostic workflow platform120described above, may receive a workflow request message from the initiator device, where the workflow request message is associated with a workflow request. The workflow request message may include at least one user profile identifier identifying the user profile associated with the user, at least one entity identifier identifying the entity and an actions-sequence identifier identifying the at least one automated processing actions-sequence, including a plurality of instructions corresponding to a plurality of actions.

In some embodiments, at step402, the system may determine the at least one automated processing actions-sequence based at least in part on the actions-sequence identifier and at least one registered actions-sequence. For example, the at least one automated processing actions-sequence may include a set of processing instructions that cause, e.g., the workflow management service140or other suitable instance of an actions-sequence session to perform the workflow and provide a specified service to the user.

In some embodiments, at step403, the system may generate a first device-specific actions-sequence token for the actions-sequence session. In some embodiments, the first device-specific actions-sequence token may be based on the workflow request message. For example, the system may produce a hash of the workflow request message and/or the data carried by the workflow request message using, e.g., a suitable hash function and/or cryptographic cipher for any other suitable tokenization.

In some embodiments, at step404, the system may generate a workflow authorization request including the first device-specific actions-sequence token. For example, the system may create the workflow authorization request to provide the first device-specific actions-sequence token to an authentication service, such as the activity verification system160described above. The authentication service may verify the first device-specific actions-sequence token based on data held at the authentication service, such as, e.g., an electronic event authentication message for an electronic event executed by a user from an initiator device associated with an entity.

In some embodiments, at step405, the system may receive a workflow execution authorization in response to the workflow authorization request. In some embodiments, the workflow execution authorization may include a verification that the first device-specific actions-sequence token matches a second device-specific actions-sequence token, and user data of the user.

In some embodiments, the second device-specific actions-sequence token is based on the electronic event authentication message and the hash or other suitable tokenization used to create the first device-specific actions-sequence token. In some embodiments, the electronic event authentication message may include the at least one user profile identifier identifying the user profile associated with the user, and the at least one entity identifier identifying the entity, e.g., as specified to execute the electronic event at the initiator device.

In some embodiments, at step406, the system may execute, within the actions-sequence session, the instance of the at least one automated processing actions-sequence based at least in part on the workflow execution authorization, the actions-sequence identifier, and the user data of the user. In some embodiments, the user data of the user confidentially stored separate from the entity, e.g., at the authentication service.

In some embodiments, at step407, the system may generate at least one criterion update in response to the executing of the instance of the automated processing actions-sequence.

In some embodiments, at step408, the system may transmit a criterion notification to the initiator device, a computing device associated with the user (e.g., the user computing device101), or both. In some embodiments, the criterion notification includes an indication of the at least one criterion update.

FIG.5depicts a block diagram of an exemplary computer-based system and network500for utilizing the agnostic workflow platform120to provide secure workflow functionality to third-party devices while maintaining the confidentiality and security of user data in accordance with one or more embodiments of the present disclosure. However, not all of these components may be required to practice one or more embodiments, and variations in the arrangement and type of the components may be made without departing from the spirit or scope of various embodiments of the present disclosure. In some embodiments, the illustrative computing devices and the illustrative computing components of the exemplary computer-based system and network500may be configured to manage a large number of devices and concurrent operations, as detailed herein. In some embodiments, the exemplary computer-based system and network500may be based on a scalable computer and network architecture that incorporates varies strategies for assessing the data, caching, searching, and/or database connection pooling. An example of the scalable architecture is an architecture that is capable of operating multiple servers.

In some embodiments, referring toFIG.5, member computing device502, member computing device503and member computing device504(e.g., clients) of the exemplary computer-based system and network500may include one or more user computing devices101and/or initiator components110, including virtually any computing devices capable of receiving and sending a message over a network (e.g., cloud network), such as network505, to and from another computing device, such as servers506and507, each other, and the like.

In some embodiments, the member computing devices502through504may be personal computers, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, and the like. In some embodiments, one or more member computing devices within member computing devices502through504may include computing devices that typically connect using a wireless communications medium such as cell phones, smart phones, pagers, walkie talkies, radio frequency (RF) devices, infrared (IR) devices, CBs, integrated devices combining one or more of the preceding devices, or virtually any mobile computing device, and the like. In some embodiments, one or more member computing devices within member computing devices502-504may be devices that are capable of connecting using a wired or wireless communication medium such as a PDA, POCKET PC, wearable computer, a laptop, tablet, desktop computer, a netbook, a video game device, a pager, a smart phone, an ultra-mobile personal computer (UMPC), and/or any other device that is equipped to communicate over a wired and/or wireless communication medium (e.g., NFC, RFID, NBIOT, 3G, 4G, 5G, GSM, GPRS, WiFi, WiMax, CDMA, satellite, ZigBee, etc.). In some embodiments, one or more member computing devices within member computing devices502through504may include may run one or more applications, such as Internet browsers, mobile applications, voice calls, video games, videoconferencing, and email, among others. In some embodiments, one or more member computing devices within member computing devices502through504may be configured to receive and to send web pages, and the like. In some embodiments, an exemplary specifically programmed browser application of the present disclosure may be configured to receive and display graphics, text, multimedia, and the like, employing virtually any web based language, including, but not limited to Standard Generalized Markup Language (SMGL), such as HyperText Markup Language (HTML), a wireless application protocol (WAP), a Handheld Device Markup Language (HDML), such as Wireless Markup Language (WML), WMLScript, XML, JavaScript, and the like. In some embodiments, a member computing device within member computing devices502-504may be specifically programmed by either Java, .Net, QT, C, C++ and/or other suitable programming language. In some embodiments, one or more member computing devices within member computing devices502-504may be specifically programmed include or execute an application to perform a variety of possible tasks, such as, without limitation, messaging functionality, browsing, searching, playing, streaming, or displaying various forms of content, including locally stored or uploaded messages, images and/or video, and/or games.

In some embodiments, the exemplary server506and/or the exemplary server507may be a web server (or a series of servers) running a network operating system, examples of which may include but are not limited to Microsoft Windows Server, Novell NetWare, or Linux. In some embodiments, the exemplary server506or the exemplary server507may be used for and/or provide cloud and/or network computing. Although not shown inFIG.5, in some embodiments, the exemplary server506or the exemplary server507may have connections to external systems like email, SMS messaging, text messaging, ad content providers, etc. Any of the features of the exemplary server506may be also implemented in the exemplary server507and vice versa.

In some embodiments, one or more of the exemplary servers506and507may be specifically programmed to host the agnostic workflow platform120and/or the activity verification system160described above, including provisioning memory and/or compute resources such as the processor122and/or storage121. In some embodiments, one or more of the exemplary servers506and507may be specifically programmed to perform, in non-limiting example, as authentication servers, search servers, email servers, social networking services servers, SMS servers, IM servers, MMS servers, exchange servers, photo-sharing services servers, advertisement providing servers, financial/banking-related services servers, travel services servers, or any similarly suitable service-base servers for users of the member computing device502, member computing device503through member computing device504.

In some embodiments and, optionally, in combination of any embodiment described above or below, for example, one or more exemplary computing member computing devices502through504, the exemplary server506, and/or the exemplary server507may include a specifically programmed software module that may be configured to send, process, and receive information using a scripting language, a remote procedure call, an email, a tweet, Short Message Service (SMS), Multimedia Message Service (MMS), instant messaging (IM), internet relay chat (IRC), mIRC, Jabber, an application programming interface, Simple Object Access Protocol (SOAP) methods, Common Object Request Broker Architecture (CORBA), HTTP (Hypertext Transfer Protocol), REST (Representational State Transfer), or any combination thereof.

FIG.6depicts a block diagram of another exemplary computer-based system and network600for utilizing the agnostic workflow platform120to provide secure workflow functionality to third-party devices while maintaining the confidentiality and security of user data in accordance with one or more embodiments of the present disclosure. However, not all of these components may be required to practice one or more embodiments, and variations in the arrangement and type of the components may be made without departing from the spirit or scope of various embodiments of the present disclosure.

In some embodiments, the member computing devices602a,602bthrough602nshown each may include a user computing device101and/or an initiator component110for receiving outputs from the agnostic workflow platform120and executing electronic events and/or operations. Thus, the member computing device602athrough602nmay include a computer-readable medium, such as a random-access memory (RAM)608coupled to a processor610or FLASH memory. In some embodiments, the processor610may execute computer-executable program instructions stored in memory608. In some embodiments, the processor610may include a microprocessor, an ASIC, and/or a state machine. In some embodiments, the processor610may include, or may be in communication with, media, for example computer-readable media, which stores instructions that, when executed by the processor610, may cause the processor610to perform one or more steps described herein. In some embodiments, examples of computer-readable media may include, but are not limited to, an electronic, optical, magnetic, or other storage or transmission device capable of providing a processor, such as the processor610of member computing device602a, with computer-readable instructions. In some embodiments, other examples of suitable media may include, but are not limited to, a floppy disk, CD-ROM, DVD, magnetic disk, memory chip, ROM, RAM, an ASIC, a configured processor, all optical media, all magnetic tape, or other magnetic media, or any other medium from which a computer processor can read instructions. Also, various other forms of computer-readable media may transmit or carry instructions to a computer, including a router, private or public network, or other transmission device or channel, both wired and wireless. In some embodiments, the instructions may comprise code from any computer-programming language, including, for example, C, C++, Visual Basic, Java, Python, Perl, JavaScript, etc.

In some embodiments, member computing devices602athrough602nmay also comprise a number of external or internal devices such as a mouse, a CD-ROM, DVD, a physical or virtual keyboard, a display, or other input or output devices. In some embodiments, examples of member computing devices602athrough602n(e.g., clients) may be any type of processor-based platforms that are connected to a network606such as, without limitation, personal computers, digital assistants, personal digital assistants, smart phones, pagers, digital tablets, laptop computers, Internet appliances, and other processor-based devices. In some embodiments, member computing device602a, member computing device602bthrough member computing device602nmay be specifically programmed with one or more application programs in accordance with one or more principles/methodologies detailed herein. In some embodiments, member computing devices602athrough602nmay operate on any operating system capable of supporting a browser or browser-enabled application, such as Microsoft™, Windows™, and/or Linux. In some embodiments, member computing devices602athrough602nshown may include, for example, personal computers executing a browser application program such as Microsoft Corporation's Internet Explorer™, Apple Computer, Inc.'s Safari™, Mozilla Firefox, and/or Opera.

In some embodiments, through the member computing devices602athrough602n, user612a, user612bthrough user612n, may communicate over the exemplary network606with each other and/or with other systems and/or devices coupled to the network606. As shown inFIG.6, exemplary server device604and server device613may be also coupled to the network606. Server device604may include processor605and memory617, and server613may include processor614and memory616. In some embodiments, one or more member computing devices602athrough602nmay be mobile clients. In some embodiments, the server device604and server device613may host the agnostic workflow platform120and/or the activity verification system160described above, including provisioning memory and/or compute resources such as the processor122and/or storage121. Thus, the processors605and/or614may provide the processor122for the agnostic workflow platform120. Similarly, the memory616and memory617may provide the storage121for the agnostic workflow platform120.

In some embodiments, at least one database of exemplary databases607and615may be any type of database, including a database managed by a database management system (DBMS). In some embodiments, the databases607and615may be the storage121for storing the workflow library123of the agnostic workflow platform120and/or the workflow queue124of the agnostic workflow platform. In some embodiments, an exemplary DBMS-managed database may be specifically programmed as an engine that controls organization, storage, management, and/or retrieval of data in the respective database. In some embodiments, the exemplary DBMS-managed database may be specifically programmed to provide the ability to query, backup and replicate, enforce rules, provide security, compute, perform change and access logging, and/or automate optimization. In some embodiments, the exemplary DBMS-managed database may be chosen from Oracle database, IBM DB2, Adaptive Server Enterprise, FileMaker, Microsoft Access, Microsoft SQL Server, MySQL, PostgreSQL, and a NoSQL implementation. In some embodiments, the exemplary DBMS-managed database may be specifically programmed to define each respective schema of each database in the exemplary DBMS, according to a particular database model of the present disclosure which may include a hierarchical model, network model, relational model, object model, or some other suitable organization that may result in one or more applicable data structures that may include fields, records, files, and/or objects. In some embodiments, the exemplary DBMS-managed database may be specifically programmed to include metadata about the data that is stored.

In some embodiments, the exemplary computer-based systems/platforms, the exemplary computer-based devices, and/or the exemplary computer-based components of the present disclosure may be specifically configured to operate in a cloud computing/architecture625such as, but not limiting to: infrastructure a service (IaaS)810, platform as a service (PaaS)808, and/or software as a service (SaaS)806using a web browser, mobile app, thin client, terminal emulator, or other endpoint804.FIGS.7and8illustrate schematics of exemplary implementations of the cloud computing/architecture(s) in which the exemplary computer-based systems/platforms, the exemplary computer-based devices, and/or the exemplary computer-based components of the present disclosure may be specifically configured to operate.

It is understood that at least one aspect/functionality of the agnostic workflow platform120described herein can be performed in real-time and/or dynamically. As used herein, the term “real-time”is directed to an event/action that can occur instantaneously or almost instantaneously in time when another event/action has occurred. For example, the “real-time processing,” “real-time computation,” and “real-time execution” all pertain to the performance of a computation during the actual time that the related physical process (e.g., a user interacting with an application on a mobile device) occurs, in order that results of the computation can be used in guiding the physical process.

In some embodiments, exemplary specially programmed computing systems and platforms with the agnostic workflow platform120, the initiator component110, the user computing device101and/or the activity verification system160may be configured to operate in the distributed network environment, communicating with one another over one or more suitable data communication networks (e.g., the Internet, satellite, etc.) and utilizing one or more suitable data communication protocols/modes such as, without limitation, IPX/SPX, X.25, AX.25, AppleTalk™, TCP/IP (e.g., HTTP), near-field wireless communication (NFC), RFID, Narrow Band Internet of Things (NBIOT), 3G, 4G, 5G, GSM, GPRS, WiFi, WiMax, CDMA, satellite, ZigBee, and other suitable communication modes.

Computer-related systems, computer systems, and systems, such as the agnostic workflow platform120, the initiator component110, the user computing device101and/or the activity verification system160, include any combination of hardware and software. Examples of software may include software components, programs, applications, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computer code, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.

In some embodiments, one or more of the agnostic workflow platform120, the initiator component110, the user computing device101and/or the activity verification system160may include or be incorporated, partially or entirely into at least one personal computer (PC), laptop computer, ultra-laptop computer, tablet, touch pad, portable computer, handheld computer, palmtop computer, personal digital assistant (PDA), cellular telephone, combination cellular telephone/PDA, television, smart device (e.g., smart phone, smart tablet or smart television), mobile internet device (MID), messaging device, data communication device, and so forth.

In some embodiments, as detailed herein, one or more of the agnostic workflow platform120, the initiator component110, the user computing device101and/or the activity verification system160of the present disclosure may obtain, manipulate, transfer, store, transform, generate, and/or output any digital object and/or data unit (e.g., from inside and/or outside of a particular application) that can be in any suitable form such as, without limitation, a file, a contact, a task, an email, a message, a map, an entire application (e.g., a calculator), data points, and other suitable data.

In some embodiments, as detailed herein, one or more of the agnostic workflow platform120, the initiator component110, the user computing device101and/or the activity verification system160may be implemented across one or more of various computer platforms such as, but not limited to: (1) Linux, (2) Microsoft Windows, (3) OS X (Mac OS), (4) Solaris, (5) UNIX (6) VMWare, (7) Android, (8) Java Platforms, (9) Open Web Platform, (10) Kubernetes or other suitable computer platforms. In some embodiments, illustrative computer-based systems or platforms of the present disclosure may be configured to utilize hardwired circuitry that may be used in place of or in combination with software instructions to implement features consistent with principles of the disclosure. Thus, implementations consistent with principles of the disclosure are not limited to any specific combination of hardware circuitry and software. For example, various embodiments may be embodied in many different ways as a software component such as, without limitation, a stand-alone software package, a combination of software packages, or it may be a software package incorporated as a “tool” in a larger software product.

In some embodiments, the agnostic workflow platform120, the initiator component110, the user computing device101and/or the activity verification system160of the present disclosure may be configured to handle numerous concurrent users that may be, but is not limited to, at least 200 (e.g., but not limited to, 200-999), at least 2,000 (e.g., but not limited to, 2,000-9,999), at least 20,000 (e.g., but not limited to, 20,000-99,999), at least 200,000 (e.g., but not limited to, 200,000-999,999), at least 2,000,000 (e.g., but not limited to, 2,000,000-9,999,999), at least 20,000,000 (e.g., but not limited to, 20,000,000-99,999,999), at least 200,000,000 (e.g., but not limited to, 200,000,000-999,999,999), at least 2,000,000,000 (e.g., but not limited to, 2,000,000,000-999,999,999,999), and so on.

In some embodiments, the agnostic workflow platform120, the initiator component110, the user computing device101and/or the activity verification system160may be configured to output to distinct, specifically programmed graphical user interface implementations of the present disclosure (e.g., a desktop, a web app., etc.). In various implementations of the present disclosure, a final output may be displayed on a displaying screen which may be, without limitation, a screen of a computer, a screen of a mobile device, or the like. In various implementations, the display may be a holographic display. In various implementations, the display may be a transparent surface that may receive a visual projection. Such projections may convey various forms of information, images, or objects. For example, such projections may be a visual overlay for a mobile augmented reality (MAR) application.

In some embodiments, the illustrative computer-based systems or platforms of the present disclosure may be configured to securely store and/or transmit data by utilizing one or more of encryption techniques (e.g., private/public key pair, Triple Data Encryption Standard (3DES), block cipher algorithms (e.g., IDEA, RC2, RC5, CAST and Skipjack), cryptographic hash algorithms (e.g., MD5, RIPEMD-160, RTRO, SHA-1, SHA-2, Tiger (TTH), WHIRLPOOL, RNGs).

The examples are, of course, illustrative, and not restrictive.

At least some aspects of the present disclosure will now be described with reference to the following numbered clauses.

Clause 1. A method including:

receiving, by the at least one processor, a workflow request message from the initiator device, where the workflow request message is associated with a workflow request;where the workflow request message includes:at least one user profile identifier identifying the user profile associated with the user,at least one entity identifier identifying the entity andan actions-sequence identifier identifying the at least one automated processing actions-sequence, including a plurality of instructions corresponding to a plurality of actions;determining, by the at least one processor, the at least one automated processing actions-sequence based at least in part on:the actions-sequence identifier andat least one registered actions-sequence;generating, by the at least one processor, a first device-specific actions-sequence token for the actions-sequence session;where the first device-specific actions-sequence token is based on the workflow request message;generating, by the at least one processor, a workflow authorization request including the second device-specific actions-sequence token;receiving, by the at least one processor, a workflow execution authorization in response to the workflow authorization request;where the workflow execution authorization includes:a verification that the first device-specific actions-sequence token matches a second device-specific actions-sequence token, anduser data of the user;where the second device-specific actions-sequence token is based on an electronic event authentication message from an initiator device associated with an entity;where the electronic event authentication message includes:the at least one user profile identifier identifying the user profile associated with the user, andthe at least one entity identifier identifying the entity;executing, by the at least one processor, within the actions-sequence session, the instance of the at least one automated processing actions-sequence based at least in part on:the workflow execution authorization;the actions-sequence identifier, andthe user data of the user;where the user data of the user confidentially stored separate from the entity;generating, by the at least one processor, at least one criterion update in response to the executing the instance of the automated processing actions-sequence; andtransmitting, by the at least one processor, a criterion notification to the initiator device, a computing device associated with the user, or both;where the criterion notification includes an indication of the at least one criterion update.
Clause 2. A system including:at least one processor configured to execute software instruction causing the at least one processor to perform steps to:receive a workflow request message from the initiator device, where the workflow request message is associated with a workflow request;where the workflow request message includes:at least one user profile identifier identifying the user profile associated with the user,at least one entity identifier identifying the entity andan actions-sequence identifier identifying the at least one automated processing actions-sequence, including a plurality of instructions corresponding to a plurality of actions;determine the at least one automated processing actions-sequence based at least in part on:the actions-sequence identifier andat least one registered actions-sequence;generate a first device-specific actions-sequence token for the actions-sequence session;where the first device-specific actions-sequence token is based on the workflow request message;generate a workflow authorization request including the second device-specific actions-sequence token;receive a workflow execution authorization in response to the workflow authorization request;where the workflow execution authorization includes:a verification that the first device-specific actions-sequence token matches a second device-specific actions-sequence token, anduser data of the user;where the second device-specific actions-sequence token is based on an electronic event authentication message from an initiator device associated with an entity;where the electronic event authentication message includes:the at least one user profile identifier identifying the user profile associated with the user, andthe at least one entity identifier identifying the entity;execute within the actions-sequence session, the instance of the at least one automated processing actions-sequence based at least in part on:the workflow execution authorization;the actions-sequence identifier, andthe user data of the user;where the user data of the user confidentially stored separate from the entity;generate at least one criterion update in response to the executing the instance of the automated processing actions-sequence; andtransmit a criterion notification to the initiator device, a computing device associated with the user, or both;where the criterion notification includes an indication of the at least one criterion update.
Clause 3. A method including:receiving, by the at least one processor, a workflow request message from an initiator device;where the workflow request message includes:at least one user profile identifier identifying a user profile of a user associated with the workflow request message,at least one entity identifier identifying an entity associated with the initiator device, andan actions-sequence identifier identifying a workflow including at least one automated processing actions-sequence;generating, by the at least one processor, a first device-specific actions-sequence token based on the workflow request message;receiving, by the at least one processor from at least one separate computer platform, a second device-specific actions-sequence token associated with electronic event authentication message;executing, by the at least one processor, an instance of the at least one automated processing actions-sequence based at least in part on:the first device-specific actions-sequence token matching the second device-specific actions-sequence token,the actions-sequence identifier, anduser data of the user;generating, by the at least one processor, at least one message in response to the executing the instance of the automated processing actions-sequence; andtransmitting, by the at least one processor, the at least one message to the initiator device, a computing device associated with the user, or both.
Clause 4. The system and/or method of any one or more of clauses 1 through 3, further including electronically communicating, by the at least one processor, the criterion notification to contact information identified in the user data, where the contact information identifies a communication address of the computing device.
Clause 5. The system and/or method of any of any one or more of clauses 1 through 4, where the contact information includes a telephone number specified in a user account at a financial institution and the criterion notification includes a text message to the telephone number.
Clause 6. The system and/or method of any one or more of clauses 1 through 3, where the first device-specific actions-sequence token is a one-time token that expires upon generating the at least one criterion update.

Clause 7. The system and/or method of any one or more of clauses 1 through 3, further including receiving, by the at least one processor, the electronic event authentication message via a payment advice and authorization message standard.

Clause 8. The system and/or method of any one or more of clauses 1 through 3 and/or 6, further including receiving, by the at least one processor, the workflow request message via an application programming interface (API) over the Internet.

Clause 9. The system and/or method of any one or more of clauses 1 through 3, where the initiator device includes a point-of-sale device.

Clause 10. The system and/or method of any one or more of clauses 1 through 3 and/or 7, where the point-of-sale device includes a payment system associated with a merchant.

Clause 11. The system and/or method of any one or more of clauses 1 through 3, further including receiving, by the at least one processor, a transaction fulfillment message as the at least one electronic message from a merchant associated with the initiator device, where the transaction fulfillment message indicates a fulfillment of a condition of a transaction associated with the workflow request message.

Clause 12. The system and/or method of any one or more of clauses 1 through 3, where the criterion notification includes a purchased item shipping confirmation.