SEONRouteurStable

Get transaction (SEON)

Rereads an existing SEON transaction, normalizes its current state, and routes the process to approval, manual review, or decline.

Transaction SEON

Business object

Récupérer une transaction (SEON)

Approuvé

Revue requise

Refusé

Transaction SEON

Fraud assessment SEON

Vue d’ensemble

This node does not create a new assessment. It rereads a transaction already known to SEON to obtain its current state and reapply Ormuz decision normalization.

Use it after a wait, process resume, or when provider state may have changed.
The transaction may be supplied directly or resolved from the assessed business object.
The same three routes as Assess fraud (SEON) are produced from the reread state.

Typical scenario

An order had been sent to manual review. After a wait step, the process rereads the SEON transaction from the same order. The decision is now approved and the process resumes order confirmation.

Quick start

Prefer the SEON transaction returned by the previous node. Use the subject only when the process resumes later without retaining that output.

Direct chaining

Bind seon_transaction to the output of the previous Assess fraud or Get transaction. This is recommended within one process.

Resume by business object

Bind subject to the same object and use the same SEON configuration as the initial assessment.

Explicit reference

Set transaction_reference only when your integration directly knows the value expected by the SEON read.

Configuration example

Parameter	Binding	Role
`extension_config_id`	`seon_config_id`	Same configuration as the assessment
`seon_transaction`	`assess_fraud.seon_transaction`	Recommended mode

Key point Only one of the three resolution methods is required. When several are supplied, seon_transaction.id takes precedence, then transaction_reference, then the subject association.

Decision routes

approved

Acceptable risk

The reread state is normalized as approval.

Recommended actionResume or continue the operation when your business policy permits it.

review_required

Review still required

The state remains intermediate, unknown, or directed to an additional verification.

Recommended actionKeep the suspension, wait for another event, or continue manual review.

declined

High risk

The reread state is normalized as decline.

Recommended actionBlock the operation or apply your decline procedure.

Attention A transaction that cannot be found or resolved causes a node error. It is not converted to review_required.

Process example

Resume after waiting

Récupérer une transaction (SEON)

Approuvé

Revue requise

Refusé

Reprendre

Continue review

Refuser

After a wait or resume, reread the SEON transaction and continue the process according to its current decision.

Data resolution

The node resolves the transaction in the following order. The first available value is used.

Priority	Source	Quand l’utiliser
1	`seon_transaction.id`	Direct chaining from a SEON output.
2	`transaction_reference`	Direct reference or identifier known by your integration.
3	`subject`	Association created during the initial assessment.

Attention Lookup by subject is tied to the SEON configuration. An association created with another configuration is not used.

Parameters 4

Configuration

Provider context used for the read.

extension_config_idRequisref(extension_config:seon)

Active SEON configuration used to reread the transaction. Normally use the same configuration as for the initial assessment.

Transaction to reread

Three alternative ways to find the transaction.

seon_transactionOptionnelSeon transaction

Transaction returned by Assess fraud (SEON) or a previous reread. Its identifier is the most direct and safest way to target the transaction.

subjectOptionnelobject

Business object originally assessed. When Assess fraud (SEON) created the corresponding association with the same configuration, Ormuz can resolve the transaction from this object.

transaction_referenceOptionnelstring

Direct identifier or reference usable by the SEON read endpoint. Use only when you have neither seon_transaction nor an already-associated subject.

Outputs 9

Decision and transaction

Main outputs to use in the process.

fraud_assessmentSeon fraud assessment

Normalized decision from the reread state: score, risk level, applied rules, and assessment date.

selected_routeenum

Route selected from the normalized decision: approved, review_required, or declined.

seon_transactionSeon transaction

Updated SEON transaction with identifier, reference, state, score, and normalized provider response.

Updated enrichments

Detailed signals available in the reread response.

email_intelligenceOptionnelSeon email intelligence

Email signals present in the updated SEON transaction when that module had been used.

phone_intelligenceOptionnelSeon phone intelligence

Phone signals present in the updated SEON transaction when that module had been used.

ip_intelligenceOptionnelSeon ip intelligence

Network and IP signals present in the updated SEON transaction.

device_intelligenceOptionnelSeon device intelligence

Device Intelligence signals present in the updated SEON transaction.

bin_intelligenceOptionnelSeon bin intelligence

BIN information present in the updated SEON transaction.

Binding compatibility

selected_value contains the same decision as selected_route.

selected_valueenum

Decision value identical to selected_route, available for bindings and process outputs.

Behavior

Resolve the transaction

The node uses the SEON object first, then the explicit reference, then the subject association.

Relire SEON

The transaction is requested in the region and with the identifiers of the selected configuration.

Normalize the result

State, score, rules, and available enrichments are transformed into typed SEON objects.

Select the route

Approval states become approved, declines declined, and every other state review_required.

Limits and responsibilities

The node rereads an existing transaction; it does not resend signals to SEON or start a new scoring.
It does not modify the associated business object or change the provider decision.
A subject association exists only when a previous assessment used a persisted object with the same configuration.
A reread approved decision remains a risk recommendation, not a guarantee of no fraud.

Troubleshooting

No transaction resolved

Provide seon_transaction, check the direct reference, or use exactly the same subject and configuration as the assessment.

No association for the subject

The initial assessment may not have received an object with an identifier, or may have used another SEON configuration.

Route `review_required` inattendue

This route intentionally covers intermediate or unknown states. Inspect fraud_assessment.provider_state and applied rules before deciding what to do next.