SEONConnecteurStable

Submit fraud feedback (SEON)

Sends SEON the actually observed transaction outcome to feed its learning loop and improve future fraud decisions.

Type de retour

Transmettre un retour d’information fraude (SEON)

Label SEON

Feedback status

Vue d’ensemble

A fraud decision is only a prediction at action time. This node closes the loop when the real outcome becomes known: confirmed fraud, legitimate activity, chargeback, or false positive.

Submit feedback when you have a sufficiently reliable outcome, not immediately after scoring.
Use a stable source reference to link feedback to evidence or a business event.
Feedback improves data available to SEON but does not retroactively modify Ormuz objects or decisions.

Typical scenario

Several days after an approved payment, a chargeback is received. The process resolves the SEON transaction from the payment or retained output, submits feedback_type = chargeback, sets the chargeback identifier as source_reference, and keeps the returned label for audit.

Quick start

The recommended mode is to pass the SEON transaction directly with a clearly qualified observed outcome.

Cible

Bind seon_transaction to the assessed transaction. Otherwise use the same subject and SEON configuration.

Result

Choose feedback_type from the actually confirmed outcome, then specify fraud_category when your taxonomy supports it.

Traceability

Set occurred_at to the date of the observed fact and source_reference to a stable evidence reference.

Configuration example

Parameter	Binding	Role
`extension_config_id`	`seon_config_id`	Configuration from the initial assessment
`seon_transaction`	`assess_fraud.seon_transaction`	Transaction to label
`feedback_type`	`chargeback`	Actually observed outcome
`source_reference`	`chargeback.id`	Evidence and traceability
`occurred_at`	`chargeback.created_at`	Observed-outcome date

Attention Design the process to send feedback once per business outcome. source_reference is sent to SEON, but the node does not itself perform local deduplication.

Process example

Confirmed chargeback

Transmettre un retour d’information fraude (SEON)

Retain the feedback

When a real outcome is confirmed, resolve the assessed transaction, submit feedback to SEON, then retain the returned status.

Data resolution

The target transaction is resolved using the same priority as Get transaction (SEON).

Priority	Source	Recommended use
1	`seon_transaction.id`	Transaction retained from assessment or reread.
2	`transaction_reference`	Direct reference known by the integration.
3	`subject`	Association created during the initial assessment with the same configuration.

Parameters 9

Target transaction

Configuration and alternative ways to resolve the transaction.

extension_config_idRequisref(extension_config:seon)

Active SEON configuration used to submit feedback. Use the same configuration that assessed the transaction.

seon_transactionOptionnelSeon transaction

Transaction returned by Assess fraud (SEON) or Get transaction (SEON). Its identifier takes priority when targeting feedback.

subjectOptionnelobject

Business object originally assessed. It can resolve the transaction when its association was created with the same SEON configuration.

transaction_referenceOptionnelstring

Direct identifier or reference usable to target the SEON transaction when the previous objects are unavailable.

Observed outcome

Business qualification of the result sent to SEON.

feedback_typeRequisenum

Observed outcome to send to SEON.

Value	Quand l’utiliser
`fraud`	The transaction or activity was confirmed as fraudulent.
`legitimate`	The activity was confirmed as legitimate.
`chargeback`	A chargeback related to the transaction was observed.
`false_positive`	A negative decision or alert proved unjustified.
`other`	Known outcome not covered by the previous categories.

fraud_categoryOptionnelstring

More precise business category, for example payment fraud, account takeover, or promotion abuse. Set it when your taxonomy and SEON can use it.

occurred_atOptionneldatetime

Date and time when the outcome was actually observed. When absent, submission time is used.

Traceability

Additional context useful for audit and reconciliation with your business events.

commentOptionnelstring

Context comment for feedback tracking. Avoid unnecessary personal or sensitive data.

source_referenceOptionnelstring

Stable reference of the evidence or event that triggered feedback, for example a chargeback, review, or internal-case identifier.

Outputs 3

Feedback confirmation

Result to retain for tracking and audit.

seon_labelSeon label

Normalized SEON label with returned identifier, targeted transaction, feedback type, and provider response.

feedback_statusstring

Normalized status returned by SEON. When the provider returns no explicit status, the value is submitted.

submitted_atdatetime

Date and time when Ormuz submitted the feedback to SEON.

Behavior

Resolve the transaction

The node uses the SEON transaction, explicit reference, or business-object association.

Build the feedback

The observed outcome, category, comment, date, and source reference are prepared for SEON.

Apply the default date

When occurred_at is not supplied, submission time is used as the outcome date.

Submit and confirm

SEON receives the label and Ormuz exposes the seon_label, normalized status, and submitted_at.

Limits and responsibilities

The node does not automatically determine whether a transaction is fraudulent or legitimate: this qualification must come from a reliable business outcome.
It does not modify the initial decision, order, payment, customer, or any other Ormuz business object.
It does not guarantee deduplication of multiple submissions about the same outcome.
A stable source_reference makes reconciliation easier, but the process remains responsible for sending only relevant feedback.
Comments and categories must follow your data-minimization policy.

Troubleshooting

Transaction introuvable

Pass seon_transaction directly or verify that subject and configuration match the initial assessment.

Feedback sent several times

Add a business guard in the process and use a stable source_reference tied to the observed event.

Incorrect outcome date

Set occurred_at to the date of fraud, chargeback, or review. Without a value, submission date is used.

Uncertain feedback type

Use false_positive for an unjustified alert, legitimate for activity confirmed as normal, and other only when no standard category fits.