If you would like to collect payments using Authorize.net, you can do so using our Payments modal!

Before you get started you will want to have the following information available:

-Your Authorize.net API Log-in ID
-Your Authorize.net Transaction Key

If you are planning on using the integration to collect ACH payments you will be required to fill out a form for Authorize.net that can be found here:

eCheck.net Application

*Note: The eCheck (ACH) setup process may take 2-3 weeks, please take this into account when planning your setup.

NOTE: We do not allow authentication with a demo/test account. These must be credentials from a live account. When authenticating we will make small charge and then refund it, and you will need to adjust your Fraud Prevention/Address Verification Settings (AVS) to allow the test authentication. To do this: Log into the Merchant Interface.

  1. Click Account from the main toolbar.

  2. Select Settings.

  3. Click Address Verification Service in the Security Settings section.

  4. Disable AVS on your Authorize.net account

    Then you will want to make sure that your Authorize.net Form Settings are also set up to not require Address, and Zip Code:

    Authorize.net Payment Form Settings

    To do this you will also follow similar steps as before:

    Click Account from the main toolbar.

  1. Select Settings.

  2. Click Payment Form.

  3. You will see a series of fields and next to each one whether it's required or not. You will want to make sure Address and Zip Code are set to not required.

Then you can go into any of your forms and click on Add-ons --> Process Payments and you will be taken to this window:

After you've typed in this information and clicked on Connect Account you will be taken to the page where you can customize the settings to get started.

Click here to learn the next steps for customizing and updating the settings to begin collecting payments.

NOTE: If you are planning on testing in a sandbox environment you will need to post to the sandbox URL (https://test.authorize.net/gateway/transact.dll) vs. the production URL (https://secure.authorize.net/gateway/transact.dll).

Did this answer your question?