juspay/hyperswitch · error · ApiErrorResponse
Fiservcommercehub requires MultiAuthKey auth type
Error message
Fiservcommercehub requires MultiAuthKey auth type
What it means
Error "Fiservcommercehub requires MultiAuthKey auth type" thrown in juspay/hyperswitch.
Source
Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:925
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
.map(|m| {
serde_json::from_value::<CalidaMetadata>(m.clone())
.map_err(|_| err("Invalid Calida metadata format"))
})
.transpose()?;
Ok(Self::Calida {
api_key: api_key.clone(),
shop_name: calida_meta.as_ref().map(|m| m.shop_name.clone()),
})
}
_ => Err(err("Calida requires HeaderKey auth type")),
},
Connector::Celero => match auth {View on GitHub (pinned to 3093f22cc4)
Solutions
- Configure the merchant connector account for Fiservcommercehub with the MultiAuthKey connector_auth_type
- Recreate/update the connector account credentials to match the MultiAuthKey schema
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:880 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of juspay/hyperswitch@3093f22cc4 (2026-08-23).
Data as JSON: /api/errors/ffe14aed10339cd7.
Report an issue: GitHub.