Having to enter CC# every time with Authorize.net CIM

uc_recurring uses the cim features built into the uc_authorize module thats part of ubercart.

Are you saying that what Andrey is asking for does, in fact, work correctly? Please explain.

No, I'm saying asking about features in Authorize.net CIM belongs in the ubercart issue queue where the uc_authorisenet module is maintained not the uc_recurring project.

There are two options here:

1) Port the uc_cim features into uc_authorizenet module (which is what you asked about and why I move the issue here to ubercart)

2) Extend the uc_recurring module to support saved credit card across all gateways that support this feature. I have actually done some work in uc_recurring to already support this functionality on the backend as there is now the following function:

uc_recurring_charge_profile(&$fee, &$order = NULL);

This means you can pass a existing recurring fee record and a new order and have the gateway (if it supports the feature) charge some an amount to that random order. Whats required is frontend to expose that feature to users, ie: when a users is checking out select a saved recurring fee and charge the order to that profile.

What I mean is that if a user has a recurring fee saved it is possible in code to reuse that recurring fee information that would normally be used to process renews to charge another payment on an unrelated order - so could be an order the user creates through the site. This will obviously need a payment gateway like Auth.net CIM which allows you to charge any amount at anytime.

But what we need is to create a new module (that depends on uc_recurring) to provides the front end to these features, so replaces the checkout options with another option to "charge" the order to the account on file.

Its not a major feature to implement, a few form_alters and then changing what happened on checkout so instead of the checkout attempting to charge a credit card it would call that function I referred to above.

univate, is the module you referred to in your last comment in the works?

you do realize that, with "Always create a CIM profile for securely storing CC info for later use." checked, the customer will be limited to only 10 transactions via CIM since it's creating a new profile for each transaction (Authorize.net limits CIM profiles to 10 per UID)? ...without this checked, no CIM profile is created.

edit: the payment profile # per customer profile limit has changed... even still a new CIM profile with the same customer and payment data shouldn't be duplicated.

@univate: uc_recurring_charge_profile() needs to check any permissions, roles, and so forth granted to the user whenever it's invoked.

I don't really know much amount Auth.net CIM as I don't use it in any projects, but I use another gateway with similar features. uc_recurring/CIM integration makes use of the function already in uc_authorizenet module. The functionality I am referring to in uc_recurring should take care of the 10 CIM profiles, as the idea is you can have one profile in uc_recurring that can be re-used. I think the Auth CIM implementation is slightly flawed in that the profile details are being stored against an order, when it would make more sense to have them stored against a recurring fee or even just the user account.

The module to create a UI for these functions that exists in uc_recurring is on my radar, but I don't have a need for it yet so its not a high priority.

univate, it would make sense to store payment profiles against the user account. then you can store the profile unique keys for each order or recurring fee or whatever record has a payment associated with it. http://drupal.org/project/uc_cim separates the payment profiles from the order payments and is reflected in the way the profiles are stored in the db, in the uc_cim_payment_profiles and uc_payment_cim tables.

the auth cim implementation at present is very flawed... there is no cim release for ubercart that is production ready. the irony is that cim is exactly the service you would want to use if you're using an ubercart+authorizenet solution, for recurring payments but also for customers who you expect repeat business from. what merchant doesn't want repeat biz?

Subscribing.

subscribe

@mattwad: You don't have to post a comment to "subscribe". Just press that big green "Follow" button at the top of the page.

Thanks! I've been following that issue and hoped that was going to be my last 'subscribe' comment. I'm so glad it's here :)

Pretty sure this is a duplicate of #527850: Customer facing "Card on file" / reference transacts