Now that the patch in #835514: Add support for uc_recurring using token payments. has been committed we have two methods of doing recurring payments.
1. eWAY's recurring payments: http://www.eway.com.au/Developer/eway-api/recurring-payments.aspx
2. eWAY's token payments: http://www.eway.com.au/Developer/eway-api/token-payments.as

I really don't see any value of having both recurring setups and it will be confusing for users to know which option to use.

The token payment approach has clear benefits, allowing users to update their data and letting uc_recurring handle the recurring functionality as it should.

So unless someone can give a good reason not to, I am planning to remove this recurring payment functionality and just have token payments as the only recurring functionality.

I plan to do this soon so please speak up if you think this is a bad idea.

Also, seeing as recurring payments have only ever been in the dev version we don't really have any obligation in regards to supporting sites using that method.

Discuss...

Comments

agileware’s picture

agileware commented

I notice that the eWAY recurring payments (rebill) api does allow for updating of the customers credit card details. It is outlined at:
http://www.eway.com.au/Developer/eway-api/recurring-payments.aspx
and
http://www.eway.com.au/_files/documentation/Rebill%20Web%20Service.pdf
under 'Update rebill Customer'.

I was under the impression that the lack of this functionality was the reason for the token payment patch.

agileware’s picture

agileware commented
Status: Active » Fixed

I have now removed the old recurring payments functionality.

Reasons being:
* It is confusing to users to have to choose a method.
* The token payment method integrates better with uc_recurring in that it allows uc_recurring to handle the rebilling, instead of eWAY handling it.
* The token payment functionality can be reused for other thing within the module. For example #1144330: Add option in checkout to "pay using my stored credit card" which then uses the eWay Token Payment API
* Having to support and maintain code for two methods is a waste of resources.
* It was only ever in dev and not 100% complete so there is no obligation to support it (there will be if we leave it in now).

http://drupalcode.org/project/uc_eway.git/commit/7df3ed8

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.