Use case 04

Account takeover

Signals that the account is no longer in its owner's hands.

Partial
Account takeover · signal-levelpartial
Window72 h after SIM, device, factor or recovery change
Inputsaccount events · failed-login burst
Feedsato_risk · scam_risk (recent recovery)
Demo scenarionone yet

The problem

After a SIM swap or credential compromise, the first payments to new recipients are the moment of loss. The takeover signals live in account events, the loss lives in the payment.

How Cenvoriq approaches it

Account Takeover Risk is a separate dimension fed by account events. Recent recovery also contributes to Scam Risk.

Status in the current release

Signal-level implementation. A fuller account-takeover engine is planned and is not part of the current release. Not one of the seven demo scenarios.

Signals the engine uses
  • SIM, device, authentication-factor or recovery change within 72 hours
  • Failed-login burst
  • Payment to a first-time recipient soon after a change
  • Recipient with collector characteristics
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 · appliedMANUAL_REVIEW · ALLOW