- wiltshsAsked on November 25, 2015 at 08:22 PMI would LOVE to have this feature too. I am currently dependent on a custom PHP form to do this, but the possibility of having a Jotform that takes customer information and creates a CIM profile and payment profile at Authorize.net and returns the CIM profile id and payment profile id (the customer and card tokens) to us would be fantastic. That way merchants can use a secure Jotform with its elegant and flexible styling, and use the tokenization capability that CIM provides so that we don't have to ever touch a credit card number directly, and then use just the token to do billing from our billing systems. It's a fast path to PCI compliance. I'm not a developer, but the methods are well described in the documentation and someone that knows what they're doing could probably create this integration in a matter of a few days, so please let us know if this is a possibility and when we might see it.
- JotForm SupportKevin_GAnswered on November 25, 2015 at 08:29 PM
Thank you for the suggestion.
I've escalated it to our developers, they will take a look into this, but I can not give you a time frame to develop it nor the release date, but we will let you know if we get news about it.
- ypollack16Answered on November 25, 2015 at 08:49 PM
thank you. this would be tremendously helpful as costs are customized for each project we do depending on how long it takes and what's involved. So we don't charge upfront, but we require a credit card on file to charge when we complete a project.
- wiltshsAnswered on November 25, 2015 at 08:55 PM
Yes - it would be fantastic. My sense is that - for your developers who've already worked with Authorize.net ARB and AIM integration methods, this would be fairly simple (even I managed to code something with it in Visual Basic) but I lack the web coding skills to do this. So hopefully someone can take a look at it soon - it brings PCI compliance to a whole new level for small businesses.
- SammyAnswered on November 26, 2015 at 01:22 AM
The feature request has been forwarded to our development team, any updates will be communicated via this thread.
- laundrycareAnswered on January 26, 2016 at 11:23 AM
Sammy - any updates? I think A LOT of jotform users would love this feature. Our company has been anxioiusly awaiting this since August 2015.
- JotForm SupportKevin_GAnswered on January 26, 2016 at 12:28 PM
We have not received news from our second level about the progress on this feature, I will ask for any updates, we will let you know here if we get some.
- wiltshsAnswered on September 06, 2016 at 07:30 PM
This would be HUGE. With all of the emphasis on PCI lately, being able to use the clean look and flexibility of JotForm with the tokenization and security of authorize.net would be a big deal. I see it's been asked for by multiple users on this forum. I have to believe it would be worth it to someone and since you've already done the AIM integration, CIM is not a complex additional step.
- JotForm SupportKevin_GAnswered on September 06, 2016 at 09:38 PM
Unfortunately this has not been implemented yet, but as far as I know this is being considered.
However, we cannot ensure if this will be available nor provide an ETA about when this might be implemented.
In case that we receive news regarding this, we will ensure to let you know as soon as possible.
- wiltshsAnswered on September 25, 2016 at 04:17 PM
Is there any progress on this? Can anyone tell me if (a) Jotform is considering it, with an ETA, or (b) it would be something a partner might do? Given the cost and risk of PCI for many small businesses, integrating with Authorize.net's PCI-compliant tokenization APIs would be incredibly value. The APIs are very simple to use but, since we users cannot code workflow that involves external API calls into JotForm, we're reliant on you to do this. The workflow should allow a form to be published as usual, with a section for card info. After validation the name, address and card info is sent to Authorize.net using the CreateCustomerProfileRequest and createCustomerPaymentProfileRequest. The documentation is all here: http://developer.authorize.net/api/reference/index.html Those APIs respond with either an error code or with the tokenized keys for the profiles (customer or payment type). Then you could plug those into the email that gets sent back to the form owner (vs the customer). This would be SO valuable - and you'd be making a synchronous call with a timeout, so you'd be able to hold up the response email until you have a return from Authorize.net. Seriously, guys, I really don't think this is difficult but would be a huge benefit to small businesses. Candidly I am actually looking for an alternative forms provider because this issue/request has been hanging out there for years. Please look into it seriously and give us something better than you have so far. Thank you.
- JotForm SupportWelvinAnswered on September 25, 2016 at 05:25 PM
Thank you for providing us the additional information about the integration. But our apologies as we cannot give you a timeframe for this request. Everything is on our developer's side and they hold the information if there are updates on this. I'll ask the assigned developer and will let you know.
- wiltshsAnswered on October 30, 2016 at 08:47 PM
This request has been out there for 2+ years now. Come on, it really is time for something more substantial than "I'll ask the assigned developer and will let you know. ". I've never known a SaaS compahy that can see a common request, made multiple times, like this, and yet completely fail to provide any credible response. You keep saying "Everything is on our developer's side" but what does that mean? Do they work for you? Is there a Product Manager? Is there any kind of roadmap or way to see future features? Or is it just what the developer feels like doing? This is really lame guys.
- JotForm SupportowenAnswered on October 31, 2016 at 04:04 AM
I know it might be a bit annoying to receive the same response every time you ask for an update about this feature. However, the developer team are considering about implementing it and as soon as they start working on it you should be notified.
I am sorry that I am not able to provide any further information because what's on board is just this as of now. There should be other bugs or features to be fixed or implemented with higher priority. That should be why our developers are not able to give a specific timetable for this.
We really appreciate your patience on this. Please accept our apology that it has taken this long. Thank you for bringing it up again and we hope to have an update soon.