Systems and methods for generating a merchant trust score

A non-transitory computer readable storage medium, including instructions stored thereon, which when read and executed by one or more computer processors, cause the one or more computer processors to perform steps comprising:

• receiving, from a score service application executed by one or more processors and by a predicate module of a backend server, a request for a merchant lifetime trust score for a merchant via an application programming interface (“API”) call in response to an event;
• triggering, by the predicate module, a model of a model registry of the backend server, the model being selected by the predicate module based on the event and a merchant risk profile of the merchant;
• deploying, by a framework module, a Merchant Lifetime Trust Score (“MLT”) microservice module that coordinates a number of machine learning (“ML”) models based on the triggered mode, the MLT microservice module using outputs of underlying models which are deployed separately;
• determining, by the MLT microservice module, one or more calibration models based on one or more merchant features of the merchant risk profile, the one or more calibration models matching a merchant segment of the merchant risk profile, the one or more calibration models being trained on more than one merchant risk profiles including one or more risky merchant risk profiles and one or more non-risky profiles;
• generating, by an onboarding risk score machine learning model and a payment behavior score machine learning model, a raw score for the merchant lifetime trust score request;
• calibrating, by a calibrator model, the raw score from each of the onboarding risk score machine learning model and the payment behavior score machine learning model, based on the model and the merchant segment;
• aggregating, by an aggregator model, the calibrated scores using weighted average for each model, the weighted average depending on the event and the merchant segment to form aggregated scores;
• generating, by the score service application, a final score based on a business rule to the aggregated scores;
• and
• controlling, by the score service application in communication with a payment processing application executed by a frontend server, a transaction based on the final score for the merchant, wherein controlling comprises an approval decision, a hold decision, a block decision, or a request for more information related to the transaction.