What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
Transactions are not shown in Authorize.net after a submission is madeAsked by JeffreySmith on March 16, 2016 at 02:17 PM
I have an Authorize.net payment form. I have created an Authorize.net sandbox account. I have configured the form with the API and transaction key. Everything seems in order. I have test credit card numbers from Authorize.net that I have used on the form. This seems to be in order. The form is live, not in sandbox mode from Jotform. The account is also live.
The one thing I am not seeing is the transaction appear on Authorize.net. Is there anything else I need to look into, so I can have a complete test of credit card processing?
I took a look at the page you have mentioned and I see that you have a js embed form on the same: https://form.jotform.com/60624029106144
Now looking at it I see that the payment is not made as required. As such, it is possible to submit the form without actually being charged for the same - which could happen if the fields are not completed properly.
If it is important that the payment is made on each submission, I would suggest that you set the field as required.
Just to mention and give you an answer to your question - the integration should work by simply adding your API details and setting the products / subscriptions / donations. All the rest works out of the box (we do however always see it as good practice to do some testing and sandboxing to make sure).
Do let us know how it goes after making the field as required.
Thanks Ben, I changed the payment form to required and tested again - still no luck, the transaction did not appear on Authorize.net Any other thoughts?
On the Authorize.net side, there is a Virtual Tool that you can simulate a credit card transaction. Here's the test I tried: I entered the same info in the Virtual Tool as the info I entered into the form. The Virtual Tool test transaction works and shows up in the transaction detail report on A.net
I just want to make sure the form is integrated correctly on the Jotform side.
Thank you for the additional details. Looking at the form and the Authorize.net wizard, I see that the integration is successful (by pressing Test integration button).
However I do not see the transaction ID shown in the submissions panel.
As such I will raise this to our developers for closer inspection of what might be happening.
The domain where the form resides does not have SSL certification yet. I plan to activate SSL soon. Perhaps this is preventing test transactions.
If you would like to test if that is the case, you can submit the form directly: https://form.jotform.com/60624029106144
This way the form would be opened using the secure method - although all of our forms are using secure embed codes so this should not be the issue.
I have already raised this to our developers, but do feel free to test it out and let us know how it goes for you.
I tested from your link - still no luck.
Are you saying a pay tool jotform is secure and does not require a domain (with embedded code) to be SSL certified?
Yes, the code is loaded over secure protocol and all of its resources were loaded in the same manner. Now truth is that it would be much safer if your website was using HTTPS as well since as soon as you have one non safe part of the website it might allow someone to spy in, but in general the best option while you do not have the https on your website and you wish to have the form embedded would be to use the iframe embed code (How to get the jotform iFrame Code ).
to summarize, it is always best to have all run from/over https, but the form itself uses secure protocol so all data submitted through it is more secure than a form/website loaded over http protocol.
Hope this gives you a bit more details on the same and thank you for updating us.
While I can not give you an exact timeframe, our developers will update you about the issue through this thread as soon as there are any news in regards to the same.
Ben had already submitted a bug ticket report to our higher team support regarding the issue.
Our developer assigned on the ticket will provide updates here when available.
On your other question about the Error 13, I have created a separate thread for it here https://www.jotform.com/answers/796406
We will attend to it shortly.