SecureFieldsThreeDSConfig

Turns the built-in 3DS sequence on.

With enabled: true, SecureFieldsClient.submit chains the 3DS steps after tokenization — the versioning call, then the 3DS Method (device fingerprint) in a hidden iframe when the card range has one — and resolves with three_ds_server_trans_id on top of the usual tokenization result.

The chain cannot run at init: it needs the form token, which only exists once the card form has been tokenized. This flag only arms it.

Properties

enabled

enabled: boolean;

Off by default, so an existing integration is unaffected.