Use case 08
Merchant abuse
Merchant-side collusion and abuse.
Planned — not built
Merchant risk · plannednot built
Todaymerchant tokens accepted · graph node type
Proximityapplies via TrustGraph
Baselinenot built
Endpointnot built
The problem
Colluding merchants, refund abuse and merchant accounts used as collectors are a distinct pattern from customer fraud.
How Cenvoriq approaches it
Merchant tokens are accepted on events and become graph nodes, so proximity to confirmed cases already applies. A merchant baseline and endpoint are on the roadmap.
Status in the current release
Not built. Listed so the boundary is clear.
Signals the engine uses
- Not yet defined for scoring
Relevant components
Deployment
Measured in SHADOW before it touches a payment
A design partner replays its own tokenised history first, then mirrors a live stream. The engine scores this pattern and records the recommendation; the applied action is always allow and the institution’s own systems keep every control.
SHADOW MODE observing
Payment authorityNONE
Transaction impactNONE
IntelligenceACTIVE
Evidence recordRECORDING
Recommended · appliedn/a · n/a