juspay/hyperswitch · error · ApiErrorResponse::InternalServerError
Volt requires MultiAuthKey auth type
Error message
Volt requires MultiAuthKey auth type
What it means
Error "Volt requires MultiAuthKey auth type" thrown in juspay/hyperswitch.
Source
Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1665
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,
key1,
api_secret,
key2,
} => Ok(Self::Finix {
finix_user_name: api_key.clone(),
finix_password: api_secret.clone(),
merchant_identity_id: key2.clone(),
merchant_id: key1.clone(),
}),
_ => Err(err("Finix requires MultiAuthKey auth type")),
},
Connector::Cashtocode => match auth {
ConnectorAuthType::CurrencyAuthKey { auth_key_map } => Ok(Self::Cashtocode {
auth_key_map: auth_key_map.clone(),View on GitHub (pinned to 3093f22cc4)
Solutions
- Configure the merchant connector account for Volt with the MultiAuthKey connector_auth_type
- Recreate/update the connector account credentials to match the MultiAuthKey schema
When it happens
Trigger: Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1572 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/778dcec1412b2a82.
Report an issue: GitHub.