SEON
Score transactions and onboarding events with SEON, consume normalized decisions, and submit observed fraud outcomes.
4Nodes
2Events
8Provider objects
0Workflows
Definition
Nature and scope
| Integration type | Service extension |
|---|---|
| Business capabilities | |
| Integration mechanisms | rest_apiwebhook |
Use cases
What this extension lets you build
- Assess purchase, payment, refund, and payout events before execution.
- Detect suspicious contact, network, and device signals during onboarding.
- Report confirmed fraud, chargebacks, legitimate activity, and false positives.
Journey examples
Assess fraud before execution and learn from the outcome
SEON combines session signals and transactional data, then receives feedback when the real outcome becomes known.
1. Score a transaction
The process collects device signals and then submits the transaction with buyer and payment context.
The normalized decision can be used to accept, reject, or trigger enhanced verification.
2. Send the observed outcome
After a chargeback, confirmed fraud, or false positive, Ormuz reconciles the actual outcome with the SEON transaction.
This feedback loop improves future decision quality on the provider side.
Documentation
Browse the documentation
Review the configuration, nodes, events, objects, and access declared by this extension.
ConfigurationReview installation mode and Ormuz connector settings.NodesExplore actions, routers, and interactions available in processes.EventsReview Ormuz events, their originating provider event, and inputs exposed to processes.Objects and mappingsIdentify exposed provider objects and their reference schemas.Access and dataUnderstand the channels used and platform-object access requested by nodes.Resources and extensionsAccess associated documentation, support, plugins, and external marketplaces.