juspay/hyperswitch · error · ApiErrorResponse::InternalServerError
Authipay requires SignatureKey or BodyKey auth type
Error message
Authipay requires SignatureKey or BodyKey auth type
What it means
Error "Authipay requires SignatureKey or BodyKey auth type" thrown in juspay/hyperswitch.
Source
Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1192
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 {
api_key: api_key.clone(),
api_secret: api_secret.clone(),
}),
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Authipay {
api_key: api_key.clone(),
api_secret: key1.clone(),
}),
_ => Err(err("Authipay requires SignatureKey or BodyKey auth type")),
},
Connector::Bankofamerica => match auth {
ConnectorAuthType::SignatureKey {
api_key,
key1,
api_secret,
} => Ok(Self::BankOfAmerica {
api_key: api_key.clone(),
merchant_account: key1.clone(),
api_secret: api_secret.clone(),
}),
_ => Err(err("Bankofamerica requires SignatureKey auth type")),
},
Connector::Bamboraapac => match auth {
ConnectorAuthType::SignatureKey {
api_key,
key1,
api_secret,View on GitHub (pinned to 3093f22cc4)
Solutions
- Configure the merchant connector account for Authipay with the SignatureKey or BodyKey connector_auth_type
- Recreate/update the connector account credentials to match the SignatureKey or BodyKey schema
When it happens
Trigger: Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1137 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/61af309a2ef507a2.
Report an issue: GitHub.