juspay/hyperswitch · error · ApiErrorResponse::InternalServerError
Nexinets requires BodyKey auth type
Error message
Nexinets requires BodyKey auth type
What it means
Error "Nexinets requires BodyKey auth type" thrown in juspay/hyperswitch.
Source
Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1144
Ok(Self::Peachpayments {
api_key: api_key.clone(),
tenant_id: key1.clone(),
client_merchant_reference_id: peach_meta
.as_ref()
.map(|metadata| metadata.client_merchant_reference_id.clone()),
merchant_payment_method_route_id: peach_meta
.as_ref()
.map(|metadata| metadata.merchant_payment_method_route_id.clone()),
})
}
_ => Err(err("Peachpayments requires BodyKey auth type")),
},
Connector::Nexinets => match auth {
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Nexinets {
merchant_id: key1.clone(),
api_key: api_key.clone(),
}),
_ => Err(err("Nexinets requires BodyKey auth type")),
},
Connector::Razorpay => match auth {
ConnectorAuthType::HeaderKey { api_key } => Ok(Self::Razorpay {
api_key: api_key.clone(),
api_secret: None,
}),
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Razorpay {
api_key: api_key.clone(),
api_secret: Some(key1.clone()),
}),
_ => Err(err("Razorpay requires HeaderKey or BodyKey auth type")),
},
Connector::Mollie => match auth {
ConnectorAuthType::HeaderKey { api_key } => Ok(Self::Mollie {
api_key: api_key.clone(),
profile_token: None,
}),
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Mollie {View on GitHub (pinned to 3093f22cc4)
Solutions
- Configure the merchant connector account for Nexinets 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:1089 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/42e8c82585059a00.
Report an issue: GitHub.