Systems and methods for use in evaluating vulnerability risks associated with payment applications

A system for evaluating applications based on associated vulnerabilities, the system comprising:

• a processor;
• and
• a memory in communication with the processor, the memory including processor-executable instructions that, when executed by the processor, cause the processor to:
• solicit application data, for an application to be evaluated, from a developer of the application via a questionnaire interface;
• validate the application data against an infrastructure database;
• validate the application data against a compliance database;
• assign a first plurality of impact point values to the application data based on the validation of the application data against the infrastructure database and the compliance database;
• validate the application data against a vulnerability database;
• assign a second plurality of impact point values to the application data based on the validation of the application data against the vulnerability database;
• combine the first plurality of impact point values and the second plurality of impact point values into a vulnerability risk score;
• and
• deny the application when the vulnerability risk score satisfies a denial threshold.

A non-transitory computer readable media including processor-executable instructions for evaluating a payment application based on associated vulnerabilities, which when executed by a processor, cause the processor to:

• validate application data for a payment application against an infrastructure database;
• validate the application data for the payment application against a compliance database;
• validate the application data for the payment application against a vulnerability database;
• assign first impact points to the application data based on the validation of the application data of the payment application against one of the infrastructure database, the compliance database, and the vulnerability database;
• generate a first score for the payment application based on the assigned first impact points;
• assign second impact points to the application data based on the validation of the application data of the payment application against the other two of the infrastructure database, the compliance database, and the vulnerability database;
• generate a second score for the payment application based on the assigned second impact points;
• compile the first score and the second score, to thereby provide a vulnerability risk score for the payment application indicative of trustworthiness of the payment application regarding use of payment account information;
• and
• activate the payment application when the vulnerability risk score satisfies a threshold.