Collect device session (SEON)
Collects, in a hosted user experience, an encrypted SEON Device Intelligence session that can enrich a later fraud assessment.
Vue d’ensemble
This node opens a user action that loads SEON Device Intelligence in the browser and produces an encrypted session representing available device, network, and, depending on configuration, behavioral or geolocation signals.
- The session is intended to be sent to a fraud assessment; it is not itself a decision.
- Collection starts only after an explicit user action on the button shown in the journey.
- The journey may be configured to continue without a session when Device Intelligence is unavailable.
Typical scenario
During checkout, the buyer starts the device check. The resulting session is sent with the order, IP address, and buyer context to Assess fraud (SEON). SEON can then use device signals in its decision.
Quick start
The recommended configuration is to keep default collection settings, adapt displayed text, and bind the session to the assessment node.
Minimum configuration
- Select an active SEON configuration.
- Define a clear title and description in the journey language.
- Keep
allow_degraded = truewhen device data is not a mandatory signal.
Enhanced collection
- Enable geolocation only when its purpose is justified.
- Adapt
behavioral_targetsto fields actually present. - Provide consent or information text appropriate to your legal framework.
| Parameter | Binding | Role |
|---|---|---|
extension_config_id | seon_config_id | SEON configuration and region |
title | Security check | User-visible title |
description | We analyze this device to prevent fraud. | Collection purpose |
allow_degraded | true | Allows continuation without a session |
device_session to the node that actually consumes the signal. A collected session not sent to Assess fraud (SEON) does not improve the assessment.Process example
Collect device signals during checkout, then send the session to fraud assessment and handle the resulting decision.
Parameters 10
Presentation and configuration
SEON configuration and text shown to the user.
Secure device check.Collected signals
Choice of additional signals requested from the browser.
input, textarea, select, and button. Change only when your page structure requires it.Resilience
Adjust these settings only when network constraints or journey-blocking policy require it.
| Value | Behavior |
|---|---|
true | The journey may continue with collection_status = unavailable or failed, without a device_session. |
false | Failure is blocking and must be resolved before the user action can continue. |
Outputs 4
Collection result
Outputs to send to the rest of the process.
device_session input of Assess fraud (SEON).| Value | Signification |
|---|---|
collected | The device session was collected and device_session is available. |
unavailable | The Device Intelligence SDK could not be loaded or initialized. |
failed | The SDK was available, but session collection failed. |
Diagnostic
Available only when collection is unavailable or fails.
Behavior
Prepare the user action
The node reuses the region from SEON configuration and prepares text, timeouts, and collection options.
Charger Device Intelligence
The browser loads and initializes the SEON SDK. Unavailability produces collection_status = unavailable.
Trigger collection
The user explicitly starts the check. The button can also refresh an already-collected session.
Return the result
Successful collection produces device_session, collection_status = collected, and collected_at.
Apply the degraded-mode policy
With allow_degraded = true, the journey may continue without a session. Otherwise failure remains blocking.
Limits and responsibilities
- The node collects a device session; it calculates no score and makes no fraud decision.
- Collection requires a browser able to load the SEON SDK and a user interaction.
- Enabling geolocation may trigger a browser permission request.
- A degraded execution produces no
device_session: the following assessment has fewer signals. - You remain responsible for informing users, any required consent, and ensuring collection complies with your context.
Troubleshooting
`collection_status = unavailable`
The SDK could not be loaded or initialized. Check network access to the SEON domain, journey CSP policies, and provider configuration.
`collection_status = failed`
Collection started but produced no session. Inspect error_message, check timeouts, and optionally allow another attempt.
The journey remains blocked
Check allow_degraded. When false, any unavailability or failure must be resolved before continuing.