Detect risky keywords
Risky keyword detection scans a business’s web presence for terms tied to prohibited or high-risk activity. Industry classification verifies what a business does, but a business in an acceptable category can still sell prohibited products, and that activity often shows up in its own marketing or in customer reviews before anywhere else. Payment processors and platforms use risky keyword results to catch this conduct early, including the brand-damaging and illegal activity that card network enforcement programs like Mastercard BRAM (Business Risk Assessment and Mitigation) penalize.
How Middesk detects risky keywords
Risky keyword scanning runs as part of web presence analysis. Middesk scans the business’s website along with third-party profile content, including posts and reviews on platforms such as Google, Facebook, LinkedIn, Instagram, and Yelp.
Middesk groups matches into results by category. Each result includes:
- The
categoryof risky keyword and anexplanationof why the category appears in the results. - A
severityofprohibited,needs_review, orignore, set by the rules configured for your account. Middesk provides a default rule set, and you can tailor the categories, keywords, and severities to match your policy. - One or more
sources[], each with theurlwhere the match was found, thematched_keywords, and atext_snippetof the surrounding content. Thesource_typefield identifies where the content came from, and post and review sources also include aposted_attimestamp. See the Website reference for the full list of source types.
The following example shows one entry in risky_keywords_results[]:
How to use risky keyword results
Read the results
Risky keyword results appear under risky_keywords_results[] on the business’s website object. On Risk orders, results also appear at the top level of the business. A summary outcome appears in the risky_keywords review task.
Act on severity
Severity maps each result to an action:
prohibitedfindings indicate activity your program does not allow. Decline the business or escalate to your compliance team.needs_reviewfindings warrant a closer look. Route them to manual review along with the evidence insources[].ignorefindings are informational and need no action.