I'm maintaining a usage-independent Payment API at http://drupal.org/project/pay . It features Views support, transaction and activity histories for split payments, authorize/capture transactions, etc. The module is pretty robust and gaining traction, and we'd like to implement some more "pay form" modules to show what it can do.

A "pay form" module's job is to either create an interface to collect payments (as in the Donate module, seen Here), or it provides some glue code to collect payment information from existing forms (as in the Webform Pay module). The latter implementation, as a glue module, would be a very useful role for Signup Pay to fill.

The Payment API supports pluggable payment method backends. Available backends currently include PayPal, a robust implementation of Authorize.Net, and a handful of other gateway providers. I believe that writing signup_pay as a Payment API module will allow us to satisfy issues like #231279: Authorize.net Integration , #239597: Non PayPal Processing, and possibly even #253540: node owner's paypal account. And of course, the improvements made to backends and/or the Payment API at large will benefit signup_pay.

Khalid, if you are open to this idea, please let me know and I can contribute code to this effort. I don't want to do that without your blessing, since it's quite a diversion. Please feel free to ping me on IRC.

Comments

Renee S’s picture

Renee S CreditAttribution: Renee S commented

+1 for this!

stenjo’s picture

stenjo CreditAttribution: stenjo commented

I think this is a great idea, and would like to offer my services in modifying signup_pay if the module owner would let me :-)
Working on http://drupal.org/project/tripletex to talk with signup_pay and thinking it would be better to go through the Pay module.

stenjo’s picture

stenjo CreditAttribution: stenjo commented

I am now a maintainer for this module, so we can get some work done if this is still of interest.