juspay/hyperswitch · error · error_stack::Report<ApiErrorResponse>

Revolv3 requires HeaderKey auth type

Error message

Revolv3 requires HeaderKey auth type

What it means

Error "Revolv3 requires HeaderKey auth type" thrown in juspay/hyperswitch.

Source

Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:911

                    client_secret: api_key.clone(),
                    payer_id: None,
                }),
                ConnectorAuthType::SignatureKey {
                    api_key,
                    key1,
                    api_secret,
                } => Ok(Self::Paypal {
                    client_id: key1.clone(),
                    client_secret: api_key.clone(),
                    payer_id: Some(api_secret.clone()),
                }),
                _ => Err(err("Paypal requires BodyKey or SignatureKey auth type")),
            },
            Connector::Revolv3 => match auth {
                ConnectorAuthType::HeaderKey { api_key } => Ok(Self::Revolv3 {
                    api_key: api_key.clone(),
                }),
                _ => Err(err("Revolv3 requires HeaderKey auth type")),
            },
            Connector::Fiservcommercehub => match auth {
                ConnectorAuthType::MultiAuthKey {
                    api_key,
                    key1,
                    api_secret,
                    key2,
                } => Ok(Self::Fiservcommercehub {
                    api_key: api_key.clone(),
                    secret: api_secret.clone(),
                    merchant_id: key1.clone(),
                    terminal_id: key2.clone(),
                }),
                _ => Err(err("Fiservcommercehub requires MultiAuthKey auth type")),
            },
            Connector::Calida => match auth {
                ConnectorAuthType::HeaderKey { api_key } => {
                    let calida_meta = metadata

View on GitHub (pinned to 3093f22cc4)

Solutions

1. Configure the merchant connector account for Revolv3 with the HeaderKey connector_auth_type
2. Recreate/update the connector account credentials to match the HeaderKey schema

When it happens

Trigger: Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:866 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of juspay/hyperswitch@3093f22cc4 (2026-08-19). Data as JSON: /api/errors/9e275649e3a21a10. Report an issue: GitHub.