UC Recurring Payments

Is anyone still supporting this? I'd love to see a solution to the beanstream/recurring payments problem.

Same. Although, I am not sure if it's the gateway module that needs to support the recurring payments module, or the other way around...

Either way, I'm hoping to find out from Beanstream if their API supports recurring payments to begin with. I'm pretty sure you can do it via their interface, but not sure if it can be setup or updated across the internet.

I did talk to support@beanstream.com, I had asked them if they knew of any drupal modules other than uc_beanstream to handle this (which, BTW, I think is defunct, with its last commit date in Jan 2009, before uc_beanstream even started). Here is what they said:

The only other module I’m aware of is for UC specifically, http://drupal.org/project/simple_beanstream. That being said, our system is not difficult to integrate with, so a custom setup would likely take only a couple of hours, depending on what you needed it to do (recurring is a bit more complicated).

(Then I asked what they meant by "a bit more complicated"...)

Recurring billing can be as simple as a few extra fields passed in a transaction request, but if you need more control over the setup/operation of the accounts, then you’re looking at an integration with two API’s (one for processing, one for managing the accounts). Also, the flexibility of the system allows for pro-rated amounts, delayed start dates, etc., which can sometimes get into a bit more complicated coding (dealing with dates is sometimes a pain).

All documentation is available in the accounts themselves, if your client has talked to sales they should have a test account setup already. If not then we can get them in touch with a sales person who can get that started.

I just had a look in the code for uc_beanstream, and it *clearly* doesn't even attempt recurring payments. What it does is really very simple, and at the moment, it's only to support normal one-time payments.

Recurring payments are being handled in the new 6.x-2.x branch. Please test and report your results.

Known bugs as of 2011-09-07:

• Recurring payments are always set to the amount of the initial payment, regardless of the setting.
• There is no end-date set to the recurring payments, regardless of the setting.
• Recurring payments are not reported in the customer order.

I've fixed the above bugs, still need to work on the reporting and conditional actions before putting out a beta release.

Hey, thanks for looking at that. It turned out that my own client is cool NOT having recurring payments for now... but it is a D7 site, so I'm going to be attempting to use the D7 version of the module. (I'll start another thread about this...)

date problem with recurring payment.

recurring payment went through Beanstream no problem and I checked TD account, proper recurring account is set up, and showing the charging intervals correctly. and actually recurring charge the next payment. however on drupal/ubercart the recurring payment order status expires after the initial charge and reset next charge date to 1969/12/31.

here's what I found not sure if its related to the problem above.

in drupal, if I create a recurring account at 2013,02-06,11:33am
and my next billing cycle date is 2013,02-07,11:33am, (1 day interval)

BUT, beanstream's next billing cycle date is 2013,02-07,2:00am (not same as drupal one)

I guess this messes up recurring orders of drupal/ubercart.

anyone has any thought on this?

thanks