Understand device sessions and provider values for PSP device fingerprint data in card payments
When a payment routes to a payment service provider (PSP) that runs native fraud detection, the PSP expects a device session or fingerprint ID collected by its fraud SDK on the checkout page. Pass this data in the
device_sessions
array so Solidgate can forward it to the matching connector during authorization.
Load the PSP fraud SDK on your checkout page, capture the session or fingerprint ID it returns, and include it in the payment request with the
provider
value.
You can pass multiple entries when several PSP SDKs are integrated.
paymentIntent object
Guide
Set up the Solidgate payment form with step-by-step instructions for script loading, container mounting, and payment request configuration.
Payment Form
resignIntent object
Guide
Build a resign payment form that uses stored card tokens to let returning customers complete checkout without re-entering card details.
Resign Form
The
id
value comes from the PSP SDK, not from your application order ID. For example, Checkout Risk.js returns a device fingerprint, and Airwallex device fingerprinting uses the
data-order-session-id
value from its script.
Device sessions containing the unique session ID from a PSP fraud SDK and the associated third-party provider.
Description
Unique session or fingerprint identifier returned by a PSP fraud SDK.
Parameter for tracking customer sessions in payments and for risk analytics. Ensure that you handle this field in compliance with regional data privacy regulations (for example,
GDPR
Reference
in the EU).
Example
dsid_3a20_f9c1_4cd8_89d3_1c5
Description
Specifies the third-party provider associated with the device session.