I'm setting up a Drupal 6 / EC 4 store to sell memberships using ec_recurring and ec_roles (thanks Sammy!) I found that to use A.net for my products, I had to set "allow_recurring" to TRUE in ec_authorize_net_receipt_info().

As I understand the current state of things, ec_recurring is more like "automatically expire" than "automatically renew". That is, there's no way to actually do a recurring payment. In fact, without true recurring payments, I'm not sure at all why "allow_recurring" even exists. Which makes me wonder if I'm understanding properly.

Is that flag for future expansion when true automatic payments are implemented? If so, I can imagine that some store owners would want to give their members the option of automatically renewing or not. In that case, they'll still want to use the A.net gateway for an automatically-expiring ("recurring") product that doesn't actually renew automatically. So the flag as currently implemented would seem to get in the way.

Anyway, my suggestion is to either set allow_recurring to TRUE in the A.net module, or change code elsewhere to allow recognition of the distinction between a one-time purchase of an automatically-expiring product and a true automatic renewal.

Thanks!

CommentFileSizeAuthor
patch.txt380 bytesbpirkle

Comments

gordon’s picture

Status: Active » Needs work

The allow recurring needs to be backed up with all the code to be able to support recurring payments.

bpirkle’s picture

Thanks Gordon. I'll leave my hack in place for now, so that I can use A.net to sell manually-renewed memberships. And I'll look forward to true recurring payments when that's available.

davea’s picture

Please try the latest dev version for your recurring needs. It has support now for recurriing transactions. Please test!!

davea’s picture

Status: Needs work » Reviewed & tested by the community

I have been testing this for 8 months now.

DaveA

davea’s picture

Status: Reviewed & tested by the community » Closed (fixed)

This is now closed

DaveA