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.

  • Profile Image

    Authorize.net: Problem with subscription, error on transaction upon submission

    Asked by reach09 on July 23, 2016 at 12:47 AM

    In the last week or so my integration with Authorize.net has been given me the following error message:

    "The element 'subscription' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd' has invalid child element 'payment' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'. List of possible elements expected: 'shipTo, profile' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'."

    It was working fine and then all of a sudden it stopped working and started giving this message in the past week. I noticed the authorize.net wizard changed but not sure what else changed which is causing this issue.  

    Please help ASAP!



    Page URL:

  • Profile Image
    JotForm Support

    Answered by EltonCris on July 23, 2016 at 05:07 AM

    Hello Nicole,

    Thanks for reporting. We will investigate this issue and get back to you with updates.

    Stay tuned!

  • Profile Image
    JotForm Support

    Answered by EltonCris on July 23, 2016 at 05:15 AM

    I was able to reproduce this problem on a cloned of your form.

    I have now raised this to our developers so they can further investigate and resolve this issue. We'll let you know here once this is resolved.

  • Profile Image
    JotForm Support

    Answered by NeilVicente on July 23, 2016 at 07:25 AM


    This is now fixed. Sorry for the inconveniences caused.