Customization of Payment Form Field Settings

The Payment Form Field Settings in your Authorize.net account enable customization of fields on Authorize.net SIM, DPM, and Simple Checkout fields. If any of these fields are set to 'required', it will affect the methods you use to submit transactions into your account. These settings can influence features and services like Accept Hosted, Accept Customer, and Invoicing.

If you use these features and have set any of your Payment Form Fields to 'required', you may encounter errors. Please note that these are only examples and not exact representations. The required field names depend entirely on what your Payment Form Field Settings are set to.

Example Errors

Here's a screenshot from Accept Hosted showing a missing, but required, description:

Screenshot from Accept Hosted with missing, but required, phone number:

Screenshot of an Invoicing error with missing, but required, phone number:

If you are using a legacy API, such as SIM or DPM, you may encounter a response similar to the following delimited response:

3|2|33|Phone is required.||P|0||Java Transaction|1.00|CC|auth_capture||||||||||||||||||||||||||731947C0BA155DAD9ED49351193403C0|||||||||||||XXXX1111|Visa|||||||||||||||||

To provide a visual context, here is a screenshot of the 'Settings > Payment Form > Form Field' settings from the account that was used to generate the above responses:

While the above settings will not alter the field values displayed on Accept Hosted, Accept Customer, or the Invoice payment form, any required fields will validate against any transaction processed through your Authorize.net account. You must include the required values if you wish to specify required fields within the Payment Form Field Settings.

Accept Hosted:

For instance, if you have multiple connections to your Authorize.net account and your transaction requirements necessitate these settings, but you also wish to use Accept Hosted where these fields may not be supported on the payment form, you can include them when generating the token to call the Accept Hosted payment form. A working example using XML is attached to this article.

Accept Customer:

If you are using Accept Customer, you will need to create the profile before performing any transactions, including validation transactions. Alternatively, you can include the required fields in the transaction request.

Invoicing:

If you are using Invoicing as well as the SIM or DPM hosted payment form, you cannot specify any required fields in the Payment Form Field Settings. Instead, you will need to collect the fields prior to calling the hosted payment form. You can include them as hidden or non-editable fields in the POST to the SIM/DPM hosted payment form.