juspay/hyperswitch · error · ApiErrorResponse::InternalServerError
Paytm requires SignatureKey or MultiAuthKey auth type
Error message
Paytm requires SignatureKey or MultiAuthKey auth type
What it means
Error "Paytm requires SignatureKey or MultiAuthKey auth type" thrown in juspay/hyperswitch.
Source
Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1651
api_secret,
} => Ok(Self::Paytm {
merchant_id: api_key.clone(),
merchant_key: key1.clone(),
website: api_secret.clone(),
client_id: None,
}),
ConnectorAuthType::MultiAuthKey {
api_key,
key1,
api_secret,
key2,
} => Ok(Self::Paytm {
merchant_id: api_key.clone(),
merchant_key: key1.clone(),
website: api_secret.clone(),
client_id: Some(key2.clone()),
}),
_ => Err(err("Paytm requires SignatureKey or MultiAuthKey auth type")),
},
Connector::Volt => match auth {
ConnectorAuthType::MultiAuthKey {
api_key,
key1,
api_secret,
key2,
} => Ok(Self::Volt {
username: api_key.clone(),
password: api_secret.clone(),
client_id: key1.clone(),
client_secret: key2.clone(),
}),
_ => Err(err("Volt requires MultiAuthKey auth type")),
},
Connector::Finix => match auth {
ConnectorAuthType::MultiAuthKey {
api_key,View on GitHub (pinned to 3093f22cc4)
Solutions
- Configure the merchant connector account for Paytm with the SignatureKey or MultiAuthKey connector_auth_type
- Recreate/update the connector account credentials to match the SignatureKey or MultiAuthKey schema
When it happens
Trigger: Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1558 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/051c768e0db432c7.
Report an issue: GitHub.