INTERNAL_COMGATE_PRODUCTION_NOT_ENABLED

Comgate merchant is configured for production but only test mode is enabled on the gateway side.

BizKitHub holds the Comgate gateway instance with environment="p" (production), but a pre-flight probe against the Comgate API returned error code 1308 ("Production environment is not enabled for you, it is enabled testing environment only"). Forwarding a customer to the gateway in this state would produce a broken payment page for every order. The platform refuses to create the payment until the misconfiguration is fixed.

Example Error Response

JSON format

{
  "error": {
    "code": "INTERNAL_COMGATE_PRODUCTION_NOT_ENABLED",
    "message": "Comgate merchant is configured for production but only test mode is enabled on the gateway side.",
    "description": "BizKitHub holds the Comgate gateway instance with environment=\"p\" (production), but a pre-flight probe against the Comgate API returned error code 1308 (\"Production environment is not enabled for you, it is enabled testing environment only\"). Forwarding a customer to the gateway in this state would produce a broken payment page for every order. The platform refuses to create the payment until the misconfiguration is fixed."
  }
}

Troubleshooting Steps

Follow these steps to resolve this error

Open the Comgate client portal and activate production mode for the affected merchant id.

Or, until production is activated, change the gateway environment in BizKitHub admin (Payment gateways) from "p" to "t" so the customer is routed to the Comgate test environment.

Verify that the BizKitHub merchant id and secret in the gateway instance match the Comgate portal exactly — a stale or swapped credential triggers the same code.

System Logs

For detailed system information about this error, check the system logs in your BizKitHub Admin dashboard. We provide transparent access to all system logs including detailed error information, request traces, and debugging data.

Need Help?

If you're still experiencing issues after following the troubleshooting steps, our support team is here to help.

Contact Support

Related Resources

Last updated: July 3, 2026

Back to Error Codes