- wiltshsAsked on January 08, 2017 at 03:59 PM
Myself and others have been asking for this feature for 2+ years with no progress anywhere on the horizon. Unfortunately.
- JotForm SupportJim_RAnswered on January 08, 2017 at 04:04 PM
Looking at the link you mentioned https://www.jotform.com/answers/712122 that thread appears to be escalated but we have no news yet. Please keep in mind that feature requests highly depend upon the viability of the feature, the amount of similar requests, and the workload of our developers.
Yes, this feature is something our Developers are considering but it may take time and that's precisely why we can't promise any sort of timeframe for feature requests. Since that original thread was already elevated, as my colleagues promised, you will be updated on that same thread if/when there's something new.
- wiltshsAnswered on January 08, 2017 at 04:28 PM
Understood - just trying to keep it top of mind after 2+ years. I have built a work-around using CreateProfileFromTxn with authorize.net but a much more elegant solution would be one where Jotform calls the CIM APIs directly, creates the Customer Profile and Customer Payment Profile synchronously, and returns both IDs as fields in the email response, the same way the current authorize.net component returns the transaction ID and the authorization code. So it's very similar in terms of workflow, just calling CIM APIs instead of AIM APIs. Then customers would be able to use your https forms and be able to confidently say that they NEVER collect customer credit card information on their website, and that is a big deal for PCI, especially small businesses that lack the ability or resources to do their own coding.
- JotForm SupportJim_RAnswered on January 08, 2017 at 04:35 PM
Indeed, couldn't agree more. It will surely be a better approach if WE build the integration instead (and that's the goal). So, thank you for sharing the workaround you came up with, I have kept this thread Public so other users who are potentially aiming to do the same can look at it as a reference.
- wiltshsAnswered on January 08, 2017 at 05:20 PM
For the sake of sharing, my workaround (still in progress) is to use an Auth Only transaction (which Jotform supports). Within my back end code, I can use the Create Profile from Txn API that Authorize.net provides. When you've created a CIM profile, you can then use various other APIs to retrieve the data associated with that profile to, for example, create a customer record in your CRM system (APIs such as Get Customer Payment Profile, which pulls back the name and address information associated with the card used for the transaction). Obviously you can only do this if you are able to code in your CRM or customer system, which is why it would be much simpler if Jotform can do this pretty small enhancement. But it is do-able with the APIs provided by Authorize.net, but not simple.