Authorize.net Payment Profile

Logiforms Support

July 04, 2022 20:57

Authorize.net integration allows for real time credit card processing through the Authorize.net payment gateway. You must have an Authorize.net account before you can configure this profile type. Learn more at http://www.authorize.net.

Authorize.net is one of several payment service integrations available from Logiforms. You might also consider PayPal Payments Standard, PayPal Payments Pro or eSelect Payment Gateway.

Prepare the Form

Your form must have these two fields: Total Dollar Amount and Purchase Description. Total Dollar Amount must be a validated Numeric field, and Purchase Description must be AlphaNumeric.

If Addresss Verification Settings (AVS) is active on your Authorize.net account, then your form must also include these fields:

Address
City
State/Province
Zip
Country

Each of these address fields will correspond to an Authorize.net AVS address field.

Create an Authorize.net Profile

With your form open, from the Post Processing menu choose 3rd Party Integrations; or you can right-click on the form in the Dashboard, and select Form Design Tools > 3rd Party Integrations. The 3rd Party Integration management window appears.
Click Add Profile.
In the Profile Type dropdown list, choose Authorize.net then click Next.
Confirm the that you are in the correct wizard, then click Next again.

Profile Settings

In the Profile Name field, enter a meaningful name for this profile.
If you want this to be the default profile, check the box for Default Profile.
Leave the Manually Triggered Only option unchecked. This is the recommended setting. You should only check it if you are running a payment in respondent update mode or a workflow edit page.
We recommend that you leave Client Side Processing selected. In this mode, transactions are processed before the submission is recorded. When this feature is selected, only successful transactions are recorded in the database.
Enter the Login ID and Transaction Key for your Authorize.net account.
To test your form with this profile, set Test Mode to True.
Before you can submit forms in test mode, you must have an Authorize.net developer account, and the Login ID and Transaction Key you enter in Account Settings must correspond to that developer account. After you have a working form, return to this profile and edit it so that Test Mode is set to False and the Login ID and Transaction Key correspond to your regular Authorize.net account.
In the Auth Type drop-down list, choose the type of authorization. See the summary below in Transaction Types.
Click Next.

Primary Form or FormView Settings

If your form has Form Views defined, you will also see two additional configuration options explained below:

Use on Primary Form: Check this box if you want the payment processing to run on the primary form.

Use on Form Views: Select one or more Form Views that you would also like the payment processing to run.

Field Mappings

The Total Dollar Amount is mandatory. Choose the corresponding field from your form, or choose Enter Static Value and specify the value in the text box that appears.
The Purchase Description is mandatory. Choose the corresponding field from your form, or choose Enter Static Value and specify the value in the text box that appears.
In Credit Card Fields, choose all of the credit card fields that will feed data into the payment gateway.
Click Next to move to the next panel.

Address Verification Settings

If AVS is active on your Authorize.net account, then you need to set the field mappings for:

Address
City
State/Province
Zip
Country

Click Finish to complete and save this profile. When you do so, a series of hidden fields be added to your form, each one having the prefix "Authorize". You can find these fields in the Form Outline Panel of your form.

Visit the Authorize.net Response Code page to learn more about the transaction types for this payment gateway.

Communication with the Customer

You can use the response value returned from Authorize.net to display a "Thank You" page when the payment is successful. You could also display a "Payment Incomplete" page containing both a link to the form and an encouraging message to return and complete the form. This is how to set up two autoresponder profiles.

The first one could have a name like "Authorize Payment Success". In the profile you would configure a Thank You page. Also in this profile, you could create an autoresponder rule having the name "Authorize Payment Failure" that examines the [Authorize.net Response code] wildcard for the value Approved.

The second autoresponder profile could have a name like "Authorize Payment Failure". The autoresponder rule for this profile could examines the [Authorize.net Response code] wildcard for the value Failed. Configure this profile to redirect the user to a web page containing instructions on how to return to their form and try again.

Testing the Integration

After configuring the payment profile, you should test your form. As described in Profile Settings above, you can set Test Mode to True. Later, when you're ready to publish the form, you can set this value to False and change the Login ID and Transaction Key to your regular Authorize.net account credentials.

Transaction Types

The following transaction types are supported. One must be selected in the Auth Type field of Profile Settings.

Type	Details
AUTH_CAPTURE	Authorize and Capture This is the most common type of credit card transaction. The amount is sent for authorization against the user's credit card account and, if approved, is automatically approved for settlement.
AUTH_ONLY	Authorization Only This transaction type is sent for authorization only, to verify the availability of funds on a credit card account. The transaction will not be sent for settlement until a subsequent Prior Authorization Capture type transaction is submitted, or the transaction is submitted for capture manually.
PRIOR_AUTH_ CAPTURE	Prior Authorization Capture Use this transaction type to complete an Authorization Only transaction that was previously authorized through the payment gateway. An Authorization Only and a Prior Authorization Capture together are considered one complete transaction. The payment gateway accepts this transaction type and initiates settlement if the following conditions are met: The original Authorization Only transaction took place no more than 30 days prior. Both transactions are sent with the same valid Transaction Key. The original transaction has not already settled, expired, or failed. The amount purchase amount in the capture transaction must be less than or equal to the Authorization Only amount.
CAPTURE	Capture Only This transaction type completes a previous authorization transaction not originally submitted through the payment gateway, or one where the initial transaction required voice authorization. The payment gateway accepts Capture Only transactions if the following conditions are met: The transaction includes a valid authorization code issued to the merchant to complete the transaction. The transaction includes the customer's entire credit card number and expiration date.

See the Authorize.net Transaction Types page to learn more about all of the response codes and response descriptions.

Address Verification

You can configure the gateway to reject or accept transactions based on the value of the AVS code returned. To configure rejection or acceptance of a transaction based on the AVS return code, you need to ensure that you have the correct settings in your Authorize.net account:

Log into the Merchant Interface.
Select Settings from the Main Menu.
Click on the Address Verification System (AVS) link from the Security section.
Check the boxes next to the AVS codes that the system should reject.
Click Submit to save changes.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.

On This Page