Hey guys, just wondering if you guys needed a hand moving this project forward. We're doing an implementation right now to try and integrate our site with other payment providers while having a subscription functionality. Let me know if there's anything I can do to lend a hand, I'd love to be able to get some documentation and be able to dig into the code.

Cheers,

Tahiti Petey

Comments

cpelham’s picture

I don't understand why this module has anything to do with (or has to provide its own support for) payment providers/gateways. Doesn't this module simply change the role of a user when he purchases a product of type "subsription" and then keep track of if/when that role should be changed again if/when the subscription expires? I thought the whole point of Commerce was that it was modular and that gateways are each provided by modules of their own which are all plug and play so to speak with all of the other modules. That is to say, shouldn't this module be completely gateway agnostic?

rupertj’s picture

TahitiPetey - Help is always welcome :) Which other payment providers are you interested in integrating with?

cpelham - There's other modules available for what you're thinking of. https://drupal.org/project/commerce_sp is probably a better choice for you. The reason this module is integrated with PayPal (and we hope to integrate with other payment providers in the future) is to support their recurring billing mechanism. While you can use this module to buy a role forever, its main reason for being is to do recurring payment for sites that require a regular payment to a role.

blasthaus’s picture

As cpelham points out, it would be great to have it simply do its "buying a role" bit without any gateway needed. I'm interested to help out if its possible to separate the payment/recurring bit into separate sub-modules that can deal with the payment/recurring bits, paypal being one of them. This way, Commerce Subscription is not reliant on one specific gateway, but open to many. Is that a possible roadmap here?

There is a lot of customization when it comes to recurring payments that are never going to be dealt with in a stand alone commerce gateway module, so I understand the need to include that functionality and control it. Specifically I have to do a subscription, management and recurring payment using First Data. I dread having to do this as a custom module. First Data already exists and does its job for one-off payments, so a lot of the work is done there already.

damiandab’s picture

subscribing

would be nice to include skrill (moneybookers) payment gateway, they support local payments.

instanceofjamie’s picture

Status: Active » Postponed

There's a plan afoot now! We've got stories on the wall for the current sprint (3 week iteration) to add Sagepay and Authorize.net support, while also making Commerce Subscription pluggable, so other recurring payment providers could also be written.

If anyone has anything to suggest, patches are always welcome. As soon as work's begun I'll start putting updates out here. Maybe even make a 2.x branch ;-)

-- Jamie