Not that I know of. Even by today's standards and the latest encryption and SSH/HTTPS connections for ecommerce payment processing, the tools still communicate over plain old cURL.
For example, there has been big fuss about TLS 1.1 being deprecated in favor of TLS 1.2 and some processors like Authorize.net won't accept older TLS. This means every ecommerce store that uses some auth.net plugin of some sort, will need to support TLS 1.2. An example I came across recently was with WooCommerce on a Wordpress store, they used an auth.net plugin. The server required TLS 1.2 and cURL 7.34 to use it.
In any case, just saying there is nothing wrong or old school about cURL. If you're going over secure connections though, make sure the version of cURL on the server is up to par with needed TLS versions. And TLS 1.2 is going to need OpenSSL 1.0.1 at the least, though 1.0.2 or higher is better (if your server uses OpenSSL).