Authorize.net Integration: No back link when error message is shown

  • dcboswell
    Asked on April 27, 2015 at 3:22 AM
    One last thing is if bad CC data goes in, it does throw an error but there is no way for the user to return to fix the information. So that
  • Charlie
    Replied on April 27, 2015 at 4:02 AM

    Hi,

    I see what you mean, I've made a test submission in your form, you'll see two of it, one about random text and the other is a dummy test data named "Beverly Hills".

    One sample error message is this:

    Authorize Screenshot 20

     

    It doesn't give a link to go back and fix the error, although, I believe the users can click the back button of the browser to get back on the form. But I'll forward this to our developers and see if they can make adjustment on the payment integration. We'll update you on this thread when we hear any news.

    Thanks

  • dcboswell
    Replied on June 3, 2015 at 4:57 PM

    Charlie,

    Has there been any movement on this? We had a customer receive this error and they left the site instead of going back to the form to complete the transaction. Its one thing to test and have this happen, its another thing to start losing business because of no back button.

    Please let me know something soon.

    Thanks,

    Daniel Boswell

  • jonathan
    Replied on June 3, 2015 at 5:49 PM

    Hi Daniel,

    There is no recent update yet from our developer assigned to the requested feature submitted by Charlie. But I can see that the request ticket is still open and even set as an important feature. 

    We will notify you here as soon as we have news/updates available on the status of this feature.

    Thanks.

  • dcboswell
    Replied on June 3, 2015 at 8:09 PM

    Jonathan,

    Is there somewhere that lists the errors returned by Authorize.net? Or are these error messages created by JotForm itself?

    It would be great to also add a custom message for these errors so that we could provide more instruction to the user such as a contact email if they continue to have issues.

    Thanks,

    Daniel Boswell

  • jonathan
    Replied on June 3, 2015 at 9:20 PM

    Daniel,

    Though I am not that knowledgeable on this since its a programmer thing, I believe thought that the error codes/message returned were from Authorize.Net. This is because the integration was simply using the Authorize.Net API.

    You can check for more details at the Authorize.Net error codes on the page here.

     

    It would be great to also add a custom message for these errors so that we could provide more instruction to the user such as a contact email if they continue to have issues.

    I think this was already applied. Most of the error messages were descriptive enough that it will be easier to understand what they were about.

    Hope this answers your question. Let us know if we can assist you further.

    Thanks.

  • legacymarketingsystem
    Replied on July 22, 2015 at 5:20 PM

    im getting error 133 account inactive.. 

    when i know for sure i have an active auth acct and the login id and transaction key are 100% correct..

    aso gettig error 33 email required when i have the email set to required in jot.. 

     

    very frustrating.. 

  • jonathan
    Replied on July 22, 2015 at 5:26 PM

    @ legacymarketingsystem

    Hi,

    We will resolve your issue separately here http://www.jotform.com/answers/617072

    Thanks.

  • NeilVicente
    Replied on September 14, 2015 at 2:15 PM

    @dcboswell

    We have just added the message "Please go back and fix this" including a link to go back to the form to the error page that displays when something went wrong with the transaction.

    We hope you like it. Do let us know if you have any other questions or concerns.

    Best

  • dcboswell
    Replied on September 14, 2015 at 2:46 PM

    you guys are on the ball today! Thats 2 fixes in 1 day! 

    Thanks I'll be testing this out!

  • Charlie
    Replied on September 14, 2015 at 3:53 PM

    In behalf of my colleagues, you are welcome.

    Please do feel free to test it out and let us know if you encounter any problems.

    Thank you.