Abstract: There may be situations in which it is desirable to dynamically implement a rule on the firewall in response to detecting a particular pattern of user activity. However, the software code required for tracking user activity, identifying patterns of user activity, and deciding what action to take may be relatively complex. Deploying such software code on a firewall increases the complexity of the firewall. For example, the firewall can no longer be “stateless”. In some embodiments, the destination server works in combination with the firewall. The destination server monitors traffic to determine particular patterns of user activity. In response to a particular pattern of user activity being detected, an appropriate rule is established and the firewall is sent a command to implement the rule.

Abstract: Methods and systems for using a distributed ledger to record bot mitigation test results and enable servers to determine a bot mitigation score for a remote device based on previously recorded test results associated with the remote device. The server may detect a trigger for bot mitigation in association with a remote device, obtain identifying data regarding the remote device and search a distributed ledger using the identifying data to locate one or more test results stored in records on the distributed ledger containing the identifying data. It may then determine a bot likelihood score based on the one or more test results, compare the bot likelihood score to a threshold and, in response to the comparison, execute a mitigation action.

Abstract: There may be situations in which it is desirable to dynamically implement a rule on the firewall in response to detecting a particular pattern of user activity. However, the software code required for tracking user activity, identifying patterns of user activity, and deciding what action to take may be relatively complex. Deploying such software code on a firewall increases the complexity of the firewall. For example, the firewall can no longer be “stateless”. In some embodiments, the destination server works in combination with the firewall. The destination server monitors traffic to determine particular patterns of user activity. In response to a particular pattern of user activity being detected, an appropriate rule is established and the firewall is sent a command to implement the rule.

Abstract: A computer-implemented method may comprise receiving a first request to initiate a workflow, the first request being associated with a first session; receiving a second request to initiate the workflow, the second request being associated with a second session; instructing a server to execute a challenge protocol for the first session and the second session, the execution of the challenge protocol causing presentation of one or more responsive elements on respective electronic devices associated with the first session and the second session; receiving one or more indications corresponding to responses to the one or more responsive elements provided by the electronic devices; and responsive to the one or more indications, releasing the second session to proceed with the workflow prior to the first session.

Abstract: A computer-implemented system and method of dynamically switching between a full checkout process and a partial checkout process based on a payment processor load condition. An e-commerce platform may receive checkout requests in connection with a merchant account and may complete, for each of at least one of the checkout requests, an authorization operation and a capture operation via a payment processor. If the platform detects a first payment throughput limit event with regard to the payment processor then it completes a respective authorization operation for each new checkout request, and delays a respective capture operation for the new checkout request until after a second payment throughput limit event is detected.

Abstract: A computer-implemented system and method of dynamically switching between a full checkout process and a partial checkout process based on a payment processor load condition. An e-commerce platform may receive checkout requests in connection with a merchant account and may complete, for each of at least one of the checkout requests, an authorization operation and a capture operation via a payment processor. If the platform detects a first payment throughput limit event with regard to the payment processor then it completes a respective authorization operation for each new checkout request, and delays a respective capture operation for the new checkout request until after a second payment throughput limit event is detected.

Abstract: Methods and systems for using a distributed ledger to record bot mitigation test results and enable servers to determine a bot mitigation score for a remote device based on previously recorded test results associated with the remote device. The server may detect a trigger for bot mitigation in association with a remote device, obtain identifying data regarding the remote device and search a distributed ledger using the identifying data to locate one or more test results stored in records on the distributed ledger containing the identifying data. It may then determine a bot likelihood score based on the one or more test results, compare the bot likelihood score to a threshold and, in response to the comparison, execute a mitigation action.