WatchTower + Identity
How Remllo WatchTower and Remllo Identity work together without reducing either product to a narrow single-purpose feature.
WatchTower only
Run transaction monitoring, alerting, and investigations without enabling Identity.
Identity only
Run KYC, KYB, and onboarding workflows without transaction monitoring.
Together
Feed identity-safe customer context into WatchTower so analysts do not investigate transactions in a vacuum.
Correct product relationship
WatchTower is not just a stream processor for transaction decisions. Identity is not just a feeder for WatchTower. Each product stands on its own and some customers will use only one of them.
When the same tenant enables both, Identity enriches WatchTower with investigation-safe customer context so fraud, AML, and transaction-monitoring teams can understand who the customer is, how they were onboarded, and what identity activity may explain the current transaction risk.
What WatchTower receives
- customer trust posture and verification status
- KYC and KYB posture
- onboarding evidence summaries
- linked identifiers such as accounts, wallets, devices, sessions, and beneficiaries
- recent identity activity and access context
Customer onboarding or verification flow
|
v
Remllo Identity
- documents
- provider checks
- trust posture
- linked identifiers
|
| investigation-safe summaries only
v
Remllo WatchTower
- transaction decisions
- alerts and cases
- analyst investigation workspaceWhat stays inside Identity
- raw documents and biometric evidence
- sensitive provider-level responses
- manual review artifacts that are not needed for transaction investigations
WatchTower should only expose investigation-safe context. Identity remains the system of record for sensitive onboarding evidence and detailed verification artifacts.