G2 Risk Solutions

Real time listing classification and reading of relationships between web addresses to surface returning bad actors are inference throughout. Without the models, only manual merchant review remains, which cannot run at marketplace volume.

Listings are blocked, flagged or routed for review under rules, automation levels and thresholds the customer sets, with flagged items reviewable in the interface or through the API. Default thresholds and sampling of blocked listings are left to each customer.

Every listing decision carries a reason for why it was flagged, blocked or approved, so a reviewer can interrogate a specific outcome. Precision, recall and false positive rates are unpublished, and validation against shifting evasion tactics is not described.

Customers such as Trust Payments, Finix and Emirates NBD are named, and the 2025 combination announcement claims nearly every major payment provider as a client. Figures tied to named customers, listing volumes and precision are all unpublished.

Repeat offender detection works because observations accumulate across the whole customer base, so a payment provider both feeds and draws on a shared view. What each customer contributes, whether a merchant flagged at one acquirer is visible to another and how long associations persist are unstated.

A privacy policy, consumer center and EverC Data Privacy Framework notice are linked, yet none describes retention of merchant, owner and onboarding data or the subprocessors handling it. Onboarding touches identifiable owners, and the risk graph keeps entity associations over time.

Legal links in the footer are the only security reference, with no SOC 2 report, ISO certification or PCI attestation named. Banks and payment providers gate merchant onboarding tools through supplier assessment.

Mastercard's Merchant Monitoring Program and its 2026 requirements are named, and the products target transaction laundering, the misuse of merchant category codes. No supervisor or money laundering statute is named, and card network registration goes unmentioned.

Payment acceptance can be lost by a merchant classified as high risk, decided by a third party it has no relationship with, and the graph can catch it by connection rather than conduct. Nothing published covers false positive rates, error by seller type or reinstatement, and the identity and biometric line has no published performance data either.

An audit trail of enforcement decisions and review before action give the customer a way to challenge an outcome. A delisted seller deals with the platform, may never learn a third party classification drove it and has no route to contest a graph association, and no accuracy guarantee or indemnity is published.

Two decades of proprietary merchant data underpin the risk graph. Model providers, hosting and external data suppliers are unnamed, and the way listing content is obtained is left out.

Results flow through an API, a no code option or file exchange, and Smart Scan maps a catalog with no integration at all. Payment, acquiring and marketplace platforms are not named as integrations, and no public API documentation is linked.

Supervisory regimes differ across the bank and acquirer customer base, and each expects to know where merchant data is processed, yet no host, region or residency commitment is named.

MarketView and Smart Scan carry no published price, nor do the onboarding and monitoring products. Whether charges fall per merchant, per listing or as a platform fee is unstated.

Banks, acquirers and marketplaces, the chain liable for merchant conduct, are all served. The portfolio now runs from merchant onboarding and monitoring through transaction laundering detection to identity verification and bankruptcy services, though material per institution type is thin.