Solutions · Custom
Protect the event that matters to your business. SENTR’s modular engine supports custom event types, mapped signals and configurable rules—so we can explore fraud workflows beyond the industries featured here.
Custom events
Some fraud problems sit between categories. A loyalty programme, a hybrid marketplace or an internal transfer may need different signals and a different response from a card payment.
SENTR’s configurable event model gives a practical starting point: the action, the context and the decision your team needs to make.
Define the pattern
Name the loss or abuse pattern you want to address.
Connect the journey
Link activity before and after the event, using the data you can supply.
Agree the response
Decide who acts on the decision and how the outcome returns to the operation.
Work through six practical questions with us. The answers shape the integration, controls and evaluation.
Protected event → context → action → evidence → owner → Architecture
Use the session to clarify ownership, evidence requirements and the boundaries of a workable evaluation.
Define your event types and map the context they need. The shared SENTR decisioning and investigation foundation connects the work.
Custom operation anatomy
A multi-brand group needs risk on inventory reallocation between sister companies — not card checkout.
Architecture Session scopes ingestion from the ERP feed and whether SENTR.Citadel ownership exists.
This is an illustrative custom workflow, not a packaged ERP integration. Discovery must validate the data, signals and decision handling before it can be offered.
Custom events are supported; suitability for a new domain depends on its data and workflow. We confirm that scope with you. Automated dispute filing and AML screening are not available today. Qualified Shadow Mode can test an agreed SENTR.Citadel use case read-only.
Inside the workflow · illustrative configurations
Custom event types extend the platform’s decision framework. Suitability still depends on the required signals, history and an application that can act on the result.
An illustrative authentication event includes account, device, session, IP and payment-method identifiers, plus an amount field. They are example mapped fields, not a required schema: include only fields applicable to that event. A custom event still needs usable signals, detection logic and an application that can act on the result.
Identify the event, its source, the relevant entities and the outcome you can observe. Map fields and import usable history rather than assuming a ready-made industry connector.
Compose event-scoped rules, list influence and review/block policies around those mapped signals. A custom event name alone does not create detection logic.
Specify what the reviewer must inspect, how cases move and which reasons distinguish confirmed abuse from legitimate activity. Agree success criteria before judging a result.
Use an agreed feed, baseline and historical context. Establish which business actions must remain under the incumbent’s control.
Test rules and use Monitor for non-impacting evaluation. For qualified SENTR.Citadel comparisons, Shadow Mode is the separate read-only deployment route.
Investigate differences and label outcomes. Use the evidence to proceed, refine the scope or stop—without presenting disagreement with the incumbent as automatically better detection.
See the controls behind these workflows: SENTR.Citadel product deep dive → Compare guided SENTR.Tower →
Tell us where fraud enters your operation. We will explore the data, controls and workflow needed to respond.