Payment gateways take an excessive amount of time to develop and require constant maintenance to ensure compatibility with any changes the gateway may make to its API. In short it's a significant amount of work. If we can't guarantee a steady amount of sales from that payment gateway it's not beneficial for us to exhaust a massive amount of time on it. There's hundreds of payment gateways available and if we try to support them all that's essentially all we'll ever be doing due to the time involved.
Implementation of recurring payments is especially time consuming; especially when most gateways have minimum time frames of several days so it takes days between tests, which causes recurring implementations to easily take a month or more just for initial implementation. All of which takes easily a dozen or more CBSubs sales to recoup those costs all the while nothing else is receiving development time.
Reviewing QuickPay Subscription API they don't appear to even handle the recurring aspect of it. This means the built in scheduler in CBSubs would have to be used to trigger a recurring payment, which would rely on your to do manually or using CRON to ensure the scheduler runs regularly. This makes it even more difficult to develop and test as typically CBSubs would just wait for a notification from the gateway to say a renewal was done, process that notification, and done.
My recommended payment gateway is Stripe. We support all of their payment methods. We also support single and recurring (for all payment methods that accept recurring) as well.