juspay/hyperswitch · error · ApiErrorResponse::InternalServerError
Itaubank requires BodyKey auth type
Error message
Itaubank requires BodyKey auth type
What it means
Error "Itaubank requires BodyKey auth type" thrown in juspay/hyperswitch.
Source
Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1762
Connector::Itaubank => match auth {
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Itaubank {
client_secret: api_key.clone(),
client_id: key1.clone(),
certificates: None,
private_key: None,
}),
ConnectorAuthType::MultiAuthKey {
api_key,
key1,
api_secret,
key2,
} => Ok(Self::Itaubank {
client_secret: api_key.clone(),
client_id: key1.clone(),
certificates: Some(api_secret.clone()),
private_key: Some(key2.clone()),
}),
_ => Err(err("Itaubank requires BodyKey auth type")),
},
Connector::Deutschebank => match auth {
ConnectorAuthType::MultiAuthKey {
api_key,
key1,
api_secret,
key2,
} => Ok(Self::Deutschebank {
customer_identifier: api_key.clone(),
key_id: key1.clone(),
signing_private_key: api_secret.clone(),
client_certificate_bundle: key2.clone(),
}),
_ => Err(err(
"Deutsche Bank requires MultiAuthKey auth type \
(customer_identifier / key_id / signing_private_key / client_certificate_bundle)",
)),
},View on GitHub (pinned to 3093f22cc4)
Solutions
- Configure the merchant connector account for Itaubank with the BodyKey connector_auth_type
- Recreate/update the connector account credentials to match the BodyKey schema
When it happens
Trigger: Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1669 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/301bfdfb6ca67d42.
Report an issue: GitHub.