The Problem
CIM profiles in uc_authorizenet arent being used in the way truly takes advantage of the CIM API for customers. CIM profiles are created on an order by order basis and customers cant reuse/modify previously entered credit cards.

The Solution
Integrate the functionality of the contrib uc_cim module http://www.ubercart.org/contrib/2537 into uc_authorizenet and ubercart 2.x.

I tried to start on this myself but i quickly ran into the issue that in 2.x CIM profiles are stored in the order. It would seem that we need a new database table to store information per user? I wanted to get other peoples opinion on this so i can implement a logical and drupal like implementation.

BTW my end goal is to get proper customer facing CIM integration working with uc_recurring.

Comments

rszrama’s picture

Title: Customer facing Authorize.Net CIM in 2.x » Customer facing "Card on file" / reference transacts

I'm going to refine your goals a little bit. This should be instead some way to have any reference transactions supported in core, whether it's through Authorize.Net's CIM, CyberSource's Subscriptions, or any other gateway under the sun. Also, we're way past time for this to be a core 2.x feature. Definitely forge ahead, but plan on a patch for 3.x ultimately.

TR’s picture

Version: 6.x-2.x-dev » 7.x-3.x-dev

New features should go into 7.x-3.x first at this point.

bancarddata’s picture

The discussions revolving around Authorize.net's CIM functionality in Ubercart are all over the place: uc_recurring, uc_cim, uc_authorizenet, uc_authnet, etc. The uc_recurring module, as the author has repeatedly stated, has nothing to do with any specific gateway and is intent on keeping it that way (see #901940: Anonymous user checkout setting CIM profile merchantCustomerId = 0 patch, comment #10). The author, as well as others, have also gone so far as to break out the auth.net payment module into a new project and advising users to consider using that project instead of the one that comes with ubercart. Personally, it doesn't matter to me how it all goes down, I just want to have the functionality in D7/UC3. Namely, I wish to be able to use Auth.net's CIM as a data store for my CC info, so both customers (from the checkout page) and employees (from the admin offline order edit page) can reuse CC info with only the need to enter in the CVV number. I would like to use the CIM service because I don't want to have to deal with the PCI issues involved with storing that info myself, and I want to make it as easy as possible for my returning customers to place new orders.

Some topics indicate problems with uc_recurring preventing this functionality. Since recurring payments are ARB and what I am looking for is CIM, I do not see why the functionality should reside in that module. I am not looking to do any kind of recurring billing for a subscription or monthly service charge. I just want to let Authorize.net do the storage of payment info so users can reuse their card info.

There is also the uc_authnet and uc_authorizenet_simdpm projects that are potentially where to put this.

So I just want to know if we can all get to a consensus on where this functionality should reside to start. Then we can merge all of the issues together into one issue in the correct queue and collectively work from there to see who all is willing to chip in on getting this functionality implemented for D7/UC3. I, for one, am willing to contribute time and money for this functionality.

Thanks everyone!

longwave’s picture

m.stenta’s picture

Greetings! You may want to look into the new 7.x-2.x branch of the Ubercart Authorize.net Payment Gateway module. It is a complete rewrite, leveraging the Authorize.net API project.

interestingaftermath’s picture

m.stenta, does your module work with uc_recurring yet for 7.x? I saw #1712344: Integrate with uc_recurring referencing 6.x not yet supporting it but wasn't sure if that was also the case for 7.x. Thanks!

m.stenta’s picture

It does not yet, but there is some initial work by @webmasterkai that needs to be reviewed. In addition to that, @amorsent (other maintainer) needs recurring support for a project he's working on, so I think it's only a matter of time before it comes together. Any help you can provide is greatly appreciated! We can continue discussion in that issue: #1712344: Integrate with uc_recurring

interestingaftermath’s picture

I need this functionality on another site and willing to fund it's completion. Let me know if anyone is interested.