Make the module independent from method of payment

The main reason for depending on PayPal WPS is recurring subscriptions - PayPal drives it and sends commerce_subscription the notification that subscriptions have recurred, ended, etc.

That said, it would be nice to support other payment providers - I'm not sure right now if it's easier to split this module into one that does generic subscriptions and one that does the PayPal specific stuff, so we can integrate with other payment providers, or have a subscriptions module per provider. I'll take a look when we get round to integrating our next payment provider, but in the meantime if you (or someone else) would like to give some input, I'm certainly open to suggestions.

Im all in for a second module for the payment method. As mentioned, having two different modules would really make this work even better.

Another +1 for having two separate modules, one that provides the "recurring" part of it and then individual ones that provide the "collecting payment" logic. One thing that you're going to run in to pretty quick is that different gateways, PayPal, Authorize.net, etc, have very different things that they do and do not allow when it comes to processing recurring payments. This is the approach that the uc_recurring module for Ubercart used and it works pretty well.

Hi!
Are you considering Skrill (moneybookers) payment gateway?
Thanx in advanced for the time and answer !

Might be worth looking at the Commerce subscription products module.

The paypal module doesn't yet support recurring payments but there's this threads about it #1126836: Add support for PayPal's Subscriptions and Recurring Billing features