Does this module support recurring payments? E.g. for a monthly subscription for an online service?
TIA

Comments

xibun’s picture

xibun commented

Adyen does support recurring payments - but this module doesn't support that functionality. But I'm happy to review and commit a patch adding the functionality.

prodosh’s picture

prodosh commented

That would be fantastic - I will be happy to test and help with specs etc. if that helps. And if you are in the Zürich area, we could get together and discuss.

xibun’s picture

xibun commented

let's start with the specs in this thread.. I'm happy to review those as well.

prodosh’s picture

prodosh commented
Issue tags: +subscriptions

Specifications to handle subsriptions

Here is a preliminary list of the functions that I can think of:

  1. Buyer subscribes to a package: The PSP (Adyen in this case) will have to be told to bill CHF/EUR/USD X every day/month/week/N Days for the subscription being ordered. The buyer's subscription information will need to be stored in Ubercart too.
  2. The buyer should be able to manage their subscription in Ubercart/Drupal: this includes Cancel, Account Summary / View payments made, maybe changes like Upgrades
  3. When the amount is charged every month (or other period) handle the payment notifications from Adyen and store it in Ubercart
  4. We need to send the buyer a monthly invoice. This could be triggered e.g. as soon as the payment notification comes in from Adyen.

uc_recurring module

The uc_recurring module may be useful because it already provides a generic interface with hooks to Ubercart. It for example adds a tab in the buyer's account profile that has a list of all the payments made. One advantage of this module is that one could work with a number of different payment providers and the buyer and Ubercart would have one common interface to all their activity. The invoice feature could e.g. be implemented using a uc_recurring hook.

My colleague Amin worked on this and will add some more details. He can help you with the pros and cons of using uc_recurring and other problems he faced.

Open Questions:

  1. How to handle changes in product prices, upgrades etc?
  2. While I am happy to be able to charge a fixed price per month, other people may have subscriptions, where depending on usage a different amount is billed each month.

TIA

xibun’s picture

xibun commented

I agree it would be nice when it can do both:
- handle periodic payments
- handle usage triggered payments

for the implementation:
- customers need to be tokenized so they only have to agree to the payments at the beginning
- when you can use uc_recurring that would be preferred by me too
- I know of one other Drupal user that requested this feature, I will see what was done there and if we can get some code contributed back here

bufa06’s picture

bufa06 commented

I would really be interested to be able to use this module with recurring payment, did you guys made any progress on this ?

janton’s picture

janton commented

nOooo.. i was so hoping you guys added a patch or something on the end of this topic :(
It seems you have been both very bussy and did not have time to start working on it.
Working with together with the uc_recurring module would be te way to go.. I think.
Perhaps i can help.. but i'm just starting to learn drupal..