Command: grep -r "requirescustomeraction" . --include="*.rs" Output:…
- User
Command: grep -r "requires_customer_action" . --include="*.rs" Output: ./crates/hyperswitch_connectors/src/connectors/airwallex/transformers.rs: #[serde(rename = "payment_intent.requires_customer_action")] ./crates/test_utils/tests/connectors/worldline_ui.rs: vec!["status=requires_customer_action", "status=succeeded"], ./crates/test_utils/tests/connectors/worldline_ui.rs: vec!["status=requires_customer_action", "status=succeeded"], ./crates/openapi/src/routes/payments.rs:/// 2. transition to a
requires_customer_actionstatus with anext_actionblock or ./crates/openapi/src/routes/payments.rs:/// A Payment could can be cancelled when it is in one of these statuses:requires_payment_method,requires_capture,requires_confirmation,requires_customer_action. ./crates/router/src/connector/stripe/transformers.rs: // We get pending as the status from stripe, but hyperswitch should give it as requires_customer_action as ./crates/router/src/core/utils.rs: // if intent_status is requires_customer_action then set poll_id, fetch poll config and do a poll_status post message, else do open_url post message to redirect to return_url ./crates/router/src/core/payments.rs: states: ["requires_customer_action".to_string()].join(", "), ./crates/router/src/core/payments.rs: states: ["requires_customer_action".to_string()].join(", "), ./crates/router/tests/connectors/iatapay.rs:// Creates a payment checking if its status is "requires_customer_action" for redirectinal flow Assistant
<is_displaying_contents> true </is_displaying_contents>