Variable ChallengeContactPointStepSchemaConst
ChallengeContactPointStepSchema: Struct<
{
changeContactPointParams: Struct<
{
challenge_root_id: optionalKey<String>;
INTERNAL__latency_qpl_instance_id: optionalKey<String>;
INTERNAL__latency_qpl_marker_id: Number;
persisted_data: optionalKey<String>;
},
>;
contactPointPreview: String;
flow: Struct<
{
authenticity_product: optionalKey<Number>;
challenge_root_id: optionalKey<String>;
enrollment_id: optionalKey<Number>;
external_flow_id: optionalKey<Number>;
hashed_ui_state: optionalKey<String>;
ig_container_module: optionalKey<String>;
is_blocking: optionalKey<Number>;
ixt_initial_screen_id: optionalKey<String>;
location: optionalKey<String>;
trigger_event_type: optionalKey<String>;
trigger_session_id: optionalKey<String>;
v2_polling: optionalKey<Number>;
},
>;
resendCodeParams: Struct<
{
challenge_root_id: optionalKey<String>;
INTERNAL__latency_qpl_instance_id: optionalKey<String>;
INTERNAL__latency_qpl_marker_id: Number;
persisted_data: optionalKey<String>;
},
>;
submitCodeParams: Struct<
{
challenge_root_id: optionalKey<String>;
INTERNAL__latency_qpl_instance_id: optionalKey<String>;
INTERNAL__latency_qpl_marker_id: Number;
persisted_data: optionalKey<String>;
},
>;
},
> = ...
The contact-point code step: one params set per action, because the three actions name three different UFAC methods, plus the accumulated state.