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