receiving, at an application server via an application programming interface (API), data information from each of a plurality of authorization gateways, wherein each of the plurality of authorization gateways maintain, even in an inactive state, an exposed TCP socket for receiving authorization requests, a sign-on endpoint, and a health endpoint that is separate from the sign-on endpoint, wherein the data information comprises a value of service level indicating health for each of a plurality of backend servers communicated by each of the plurality of backend servers to the health endpoint of a corresponding authorization gateway;

determining, by the application server, an overall health of each authorization gateway of the plurality of authorization gateways based on the value of service level and a predetermined value of a weight assigned to each backend server of the plurality of backend servers communicatively coupled to the health endpoint of a corresponding authorization gateway;

placing, by the application server, a set of authorization gateways from the plurality of authorization gateways into an active pool of authorization gateways based on the determined overall health for each authorization gateway in the set of authorization gateways being above a predetermined threshold value by communicating a Sign-On message via the sign-on endpoint of each authorization gateway in the set of authorization gateways, wherein each authorization gateway in the active pool of authorization gateways is configured to service a transaction via the exposed TCP socket; and

routing, by the application server, at least one client request message to an authorization gateway in the active pool of authorization gateways configured to service the transaction.