Sorry to ask such a dumb question but I've been looking at all the discussions on this module and my understanding is that it now uses (with authorize.net) CIM and may use ARB.

So my questions are:
Do you need ARB enabled?
And if not, do you lose any functionality or stability by disabling ARB?

I believe that the goal is to move away from ARB so I assume that at some point it will be phased out - is this correct?

And on a very different note (perhaps a question for a different thread), is there any thoughts of handling the cc data so that you do not need the functionality of the gateways for anything but processing a transaction? I realize the real problem here is security of data but I don't see any reason in theory why we couldn't encrypt and secure data just as well as they can eventually.

Comments

univate’s picture

univate commented

I believe that the goal is to move away from ARB so I assume that at some point it will be phased out - is this correct?

I'm not aware Authorize.net is phasing out ARB? We have had issue getting support in uc_recurring-2.x due to legacy code in ubercart conflicting, but this is fixed in the latest ubercart-2.x-dev.

Anyone can build the integration with any payment gateway, so it should continue to exist as an option as long as people want to use ARB and are willing to support it.

The problem is ARB is less flexible then CIM, so I wouldn't use it if you can afford the small extra cost you are going to be better off in the long term with CIM.

As for your other question, I have created a blog post to try and address some of the intro stuff to uc_recurring and payment gateways and why we are not storing credit cards:
http://univate.com.au/content/ubercart-recurring-payments-and-subscriptions

reg’s picture

reg commented

Thanks and sorry for the ambiguity, I meant that uc_recurring was moving away from ARB - not authorize.net - but you answered that at the same time so thanks.

The reason I asked these questions was I turned on CIM and ARB in authorize.net and ubercart and thought that was a bit much.

I'll install the dev version then since it's ahead of alpha3 and currently considered better.

univate’s picture

univate commented
Status: Active » Fixed

uc_recurring goal is to support any payment method or gateway and has no preference for any gateway.

If you turn on CIM in ubercart then the authorize.net recurring functionality will use CIM as that provides more features for handling recurring payments. Having them both enabled will not cause any errors though.

Status: Fixed » Closed (fixed)

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