Systems and methods for detecting security risks in network pages

1. A computer implemented method, executed by one or more hardware processors, for detecting security risks in network pages, comprising:

providing, by the one or more hardware processors, at least one secure transaction page to a secure transaction provider, the secure transaction page enabling the secure transaction provider to request secure transactions;

determining an expected request rate for the secure transaction page by the secure transaction provider based on a history of request rate for the secure transaction page and at least one of a time, an entity size, an event data, or a network outage data;

determining an actual request rate for the secure transaction page by the secure transaction provider;

determining a first predetermined threshold for a change in request rate for the secure transaction page by the secure transaction provider, the change in request rate representing a difference between the expected request rate and the actual request rate;

receiving, by the one or more hardware processors, secure transaction data from the secure transaction provider;

determining a second predetermined threshold different from the first predetermined threshold based on the secure transaction data;

in response to determining that the second predetermined threshold has been exceeded:

declining at least one of a new token request and/or a card-not-present (CNP) token request from the secure transaction provider; and

providing a notification to the secure transaction provider based on the determination that the second predetermined threshold has been exceeded.

2. The method of claim 1 , wherein the actual request rate is indicative of a number of calls for the secure transaction page over a predetermined time period.

3. The method of claim 1 , wherein determining the first predetermined threshold for the change in request rate comprises:

comparing the actual request rate with the expected request rate to determine the first predetermined threshold for the change in request rate.

4. The method of claim 1 , further comprising:

determining whether the secure transaction page is functioning;

receiving an electronic transaction request associated with the secure transaction provider; and

in response to determining that the secure transaction page is not functioning, declining the electronic transaction request.

5. The method of claim 1 , wherein the secure transaction provider is an online merchant.

6. The method of claim 1 , wherein the secure transaction page is an iFrame hosted by a third party, such that sensitive data received via the secure transaction page is isolated from the secure transaction page.

7. A system for detecting security risks in network pages, the system comprising:

a data storage device storing instructions for detecting security risks in secure transaction pages; and

a hardware processor configured to execute the instructions to perform a method comprising:

providing at least one secure transaction page to a secure transaction provider, the secure transaction page enabling the secure transaction provider to request secure transactions;

determining an expected request rate for the secure transaction page by the secure transaction provider based on a history of request rate for the secure transaction page and at least one of a time, an entity size, an event data, or a network outage data;

determining an actual request rate for the secure transaction page by the secure transaction provider;

determining a first predetermined threshold for a change in request rate for the secure transaction page by the secure transaction provider, the change in request rate representing a difference between the expected request rate and the actual request rate;

receiving secure transaction data from the secure transaction provider;

determining a second predetermined threshold being smaller or larger than the first predetermined threshold based on the secure transaction data;

in response to determining that the second predetermined threshold has been exceeded:

declining at least one of a new token request and/or a card-not-present (CNP) token request from the secure transaction provider; and

providing a notification to the secure transaction provider based on the determination that the second predetermined threshold has been exceeded.

8. The system of claim 7 , wherein the actual request rate is indicative of a number of calls for the secure transaction page over a predetermined time period.

9. The system of claim 7 , wherein determining the first predetermined threshold for the change in request rate comprises:

comparing the actual request rate with the expected request rate to determine the first predetermined threshold for the change in request rate.

10. The system of claim 7 , wherein the method further comprises:

determining whether the secure transaction page is functioning;

receiving an electronic transaction request associated with the secure transaction provider; and

in response to determining that the secure transaction page is not functioning, declining the electronic transaction request.

11. The system of claim 7 , wherein the secure transaction provider is an online merchant.

12. The system of claim 7 , wherein the secure transaction page is an iFrame hosted by a third party, such that sensitive data received via the secure transaction page is isolated from the secure transaction page.

13. A non-transitory computer-readable medium storing instructions that, when executed by a transaction processor, cause the transaction processor to perform a method for detecting security risks in network pages, the method comprising:

providing at least one secure transaction page to a secure transaction provider, the secure transaction page enabling the secure transaction provider to request secure transactions;

determining an expected request rate for the secure transaction page by the secure transaction provider based on a history of request rate for the secure transaction page and at least one of a time, an entity size, an event data, or a network outage data;

determining an actual request rate for the secure transaction page by the secure transaction provider;

determining a first predetermined threshold for a change in request rate for the secure transaction page by the secure transaction provider, the change in request rate representing a difference between the expected request rate and the actual request rate;

receiving secure transaction data from the secure transaction provider;

determining a second predetermined threshold being less or greater than the first predetermined threshold based on the secure transaction data;

in response to determining that the second predetermined threshold has been exceeded:

declining at least one of a new token request and/or a card-not-present (CNP) token request from the secure transaction provider; and

providing a notification to the secure transaction provider based on the determination that the second predetermined threshold has been exceeded.

14. The computer-readable medium of claim 13 , wherein the actual request rate is indicative of a number of calls for the secure transaction page over a predetermined time period.

15. The computer-readable medium of claim 13 , wherein determining the first predetermined threshold for the change in request rate comprises:

comparing the actual request rate with the expected request rate to determine the first predetermined threshold for the change in request rate.

16. The computer-readable medium of claim 13 , wherein the method further comprises:

determining whether the secure transaction page is functioning;

receiving an electronic transaction request associated with the secure transaction provider; and

in response to determining that the secure transaction page is not functioning, declining the electronic transaction request.

17. The computer-readable medium of claim 13 , wherein the secure transaction provider is an online merchant.