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 Form logic

    Asked by Matt Gross on June 16, 2011 at 02:33 PM

    Greetings, I absolutely love JotForm and wanted to first give a huge thanks for an awesome platform. I have a customer who needs to collect payments via Authorize.net and I've built then an example form using the donation option (/form/11665702338). However, they need to collect payments to four different Authorize accounts based upon the first digit of the number typed into the 'account number' field. My thought was to create the form four times, each version tied to the correct Authorize.net key pair, but I would need to redirect the user to the correct form based on their initial account number entry. Is there any way to do a first-digit validation and redirect or first-digit validation and key pair swap within JotForm? I appreciate your help!



    Page URL:

  • Profile Image
    JotForm Support

    Answered by NeilVicente on June 17, 2011 at 06:02 AM

    Hi Matt,

    First off, I'd like to thank you for the kind words you have for Jotform.

    Moving on to your question, I'm afraid that what you want to do is currently impossible to achieve. A payment tool such as the Authorize.net integration is treated as a field separate from the other fields in a form, and rightfully so, since the "sub-fields" inside the payment tool are handled by special API codes that transmit the data entered to the respective payment gateway.

    As such, allowing these "sub-fields", such as credit card number, to get involved in conditions could prove to be problematic both to people who submit on the form and the form owners themselves.

    Anyway, are you referring to card type (i.e., mastercard, visa, amex, etc.) when you talked about basing upon the first digit of the card number?

    If yes, a workaround I suggest is to create four payment forms and a short form that asks the user what his/her credit card type is. Then, the user gets redirected to the corresponding payment form depending on the option selected in the short form.

    To achieve this, you must add rules using conditions to dynamically change the Thank You URL.


    Hope this post sheds some light into your question. Feel free to correct me if I'm wrong about the 'first digit' and 'card type' issue.