Authorize.Net: Allow us to capture customers credit card even with no amount to charge through Customer Information Manager (CIM) API

Hi, I hope you can get this figured out for me and surely many other users.

I just got off the phone with Authorize.Net regarding your integration which we found out does not work properly.

Currently you only allow for the sale of products, recurring billing via subscription, a user define amount, or donations.

The main one missing is Customer Information Manager (CIM) which would allow us to capture customer credit card information via JotForm integration with Authorize.Net.

Currently JotForm does not pass through the information to Authorize.Net at a total of $0.00 but does work as a subscription for $1.00. Currently this is the only work around to obtaining client credit card information and storing it on Authorize.

This is a feature that works with other providers but isn't included with JotForm. This is a baseline feature and we've determined that the information does carry over as an unsettled charge if sold as a product. As a recurring subscription, the client information can be retained. No other forms work.

The reason this does not work for us is because we do not have any initial charges for our services and would hate to tell this to people and then have to explain the reasoning behind a $1.00 charge.

Please advise,

Vitaliy

As far as I know, that's how the payment API works. When the amount is zero, there's none to be processed in the payment gateway. 

However, I think what you are looking for is the Payment Authorization. You can enable it in the payment settings. So your customers will not be charged immediately for the amount selected in the form. This only captures your customer's payment details so you can perform the charges manually in your Authorize.net dashboard at a later date.

Guide: https://www.jotform.com/help/292-How-to-Enable-Payment-Authorization

Thanks for the quick reply Elton, I appreciate it.

This is unfortunately not how it works. We've had several extensive phone conversations on this topic and it turns out that an authorization is not what is needed here. Furthermore, this basic feature is available on other platforms their agent mentioned.

We're here to capture the customer's credit card information and store it on Authorize.Net servers for later charges for the services we provide. There is no initial amount to be charged. The charges happen days, if not weeks later, this is why Authorize.Net and others have a customer information manager type of support, to allow this. Not everyone on the internet sells good that get shipped for an x-amount of money.

An authorization would require an actual dollar amount but we don't know what that is. Whole reason we went we Authorize.Net is because of JotForm integration.

If you aren't one of the, could we have one of the engineers have a look here, maybe a call can me made between the two entities as we've tried every variation and have created multiple charges in the process but what's needed while a core item, is not available.

Please advise.

Vitaliy

Thanks. I'll escalate that as a feature request. Once this is implemented in the future, you will be informed here.

Right now, I could not guarantee you of anything or provide an ETA since our developers will process requests based on the number of the users requesting the same feature. The higher the number, the higher priority they will put to it.

Glad to hear back. Is there anyway to not turn this into a bureaucratic process? I've spent literally hours on the phone as well as written correspondence and it's been made very clear that this is basically a "Core" item on which everything is built. Like a base feature. Maybe in the process your software engineers missed this. Is there anyway to have someone look into this as again, it's a basic feature and there's a reason why we sign multi-year agreements with JotForm and renew.

Thanks

We thank you for your cooperation but unfortunately, all feature requests undergo this process. Right now, it is assigned with low priority since as far as I know, there is no similar request about this. Rest assured, once this is added in the future, you will be informed here.