juspay/hyperswitch · error · ApiErrorResponse::InternalServerError
Mollie requires HeaderKey or BodyKey auth type
Error message
Mollie requires HeaderKey or BodyKey auth type
What it means
Error "Mollie requires HeaderKey or BodyKey auth type" thrown in juspay/hyperswitch.
Solutions
- Configure the merchant connector account for Mollie with the HeaderKey or BodyKey connector_auth_type
- Recreate/update the connector account credentials to match the HeaderKey or BodyKey schema
When it happens
Trigger: Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1111 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of juspay/hyperswitch@afd9284352 (2026-08-19).
Data as JSON: /api/errors/d15895652a7337cd.
Report an issue: GitHub.
Appendix: source
Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1201
api_key: api_key.clone(),
api_secret: None,
}),
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Razorpay {
api_key: api_key.clone(),
api_secret: Some(key1.clone()),
}),
_ => Err(err("Razorpay requires HeaderKey or BodyKey auth type")),
},
Connector::Mollie => match auth {
ConnectorAuthType::HeaderKey { api_key } => Ok(Self::Mollie {
api_key: api_key.clone(),
profile_token: None,
}),
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Mollie {
api_key: api_key.clone(),
profile_token: Some(key1.clone()),
}),
_ => Err(err("Mollie requires HeaderKey or BodyKey auth type")),
},
Connector::Nmi => match auth {
ConnectorAuthType::HeaderKey { api_key } => Ok(Self::Nmi {
api_key: api_key.clone(),
public_key: None,
}),
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Nmi {
api_key: api_key.clone(),
public_key: Some(key1.clone()),
}),
_ => Err(err("Nmi requires HeaderKey or BodyKey auth type")),
},
Connector::Authipay => match auth {
ConnectorAuthType::SignatureKey {
api_key,
key1: _,
api_secret,
} => Ok(Self::Authipay {View on GitHub (pinned to afd9284352)