Middle name transfers to Last name field in Authorize.net integration

  • Profile Image
    Asked on January 21, 2016 at 11:44 AM

    In my form, we are using Authorize.net integration, and I am also asking for middle names in the Name field.

    When the Authorize.net confirmation comes through, it has mapped the shipper's actual middle name to Authorize's last name field. It should be mapping the shippers actual last name to Authorize's last name field. I'm imagining this is a bug. Can this be fixed? 

    I'm including a screen shot so you can see the data as it came through from Authorize.net. The name should be "Constance Davis" in both the BILLING and SHIPPING information. You can see that it is "Constance G" under shipping; this is incorrect.

    Thank you!

  • Profile Image
    Answered on January 21, 2016 at 03:12 PM

    I think that is because Authorize.net doesn't support the middle name in the Name field of your form. The name field is mapped under the Auth.net properties as the Shipping Name Field. You may consider removing the middle name to fix this.

    I will also forward this thread to our developers to see if they can do something about this. If there are updates, you should know it in this thread.


  • Profile Image
    Answered on January 21, 2016 at 03:37 PM

    If this was because of Authorize.net not supporting the middle name, wouldn't the Billing name have the middle name instead of last name, just like the Shipping name? Currently the billing name is right and the shipping name is wrong, both while referencing the same field (at least in my form, in this particular case).

    For our purposes, I cannot delete the middle name because the State Board of Education requires us to collect it for identification purposes, and often billing and shipping names are different, so this is quite a problem when the last name comes through as a middle name.

    This may seem like a tiny problem, but for us it may cause major errors, or at least a lot of confusion and extra work. Can you please ask the developers to see if there's something that can be done? I really don't mind work-arounds, but in this case I can't think of anything else that will solve the problem and still meet our requirements.

    Thank you so much!

  • Profile Image
    Answered on January 21, 2016 at 08:30 PM

    This has been already reported, you should be notified via this thread about any updates on this request.

  • Profile Image
    Answered on January 22, 2016 at 04:19 AM


    JotForm's Authorize.Net integration can distinguish between middle name and last name. My tests can confirm this:


    It is most likely that your customer entered "Constance G" as their billing name.

    Hope this clears this issue.


  • Profile Image
    Answered on January 22, 2016 at 01:13 PM

    Thank you for looking into this. Indeed I checked, and wouldn't you know it, our first user put a "G" for her last name on the form, and she uses her middle name as her last name (how bizarre). Thank you for your trouble.