Prerequisites

Before you set up and configure an Authorize.net payment gateway instance on your tenant, enable the Authorize.net payment gateway integration for your tenant. See Enable payment gateway integrations for your tenant for instructions.

Configuration fields

Common configuration fields

There are some common fields you must complete for every gateway configuration. We recommend reviewing our Setup Payment Gateway documentation for information on these common fields:

• Name

• Use Gateway Test Environment

  Note: If you enable Use Gateway Test Environment, you must use developer account credentials, and not the merchant credentials. If you are using the production gateway (test or non-test environment), you must use the merchant credentials.

• Cards Accepted

• Default Authorization Amount

• Verify new payment method (optional)

• Verify updated payment method (optional)

Specific configuration fields

In addition to the common fields, every gateway has unique requirements and information (such as credentials and certain rules) that you must provide to configure the gateway in Zuora.

Authorize.net Credentials

Your credentials will be obtained from Authorize.net and configured in Zuora.

To configure the Authorize.net payment gateway in Zuora, you must enter your API Login ID and Transaction Key in the Setup Payment Gateway page. See Authorize.net's Access Settings document for help determining your API Login ID and Transaction Key, or if you need to obtain a new Transaction Key.

Test the configuration

For basic guidance on how to test payment gateway integrations within a sandbox environment, see Test payment gateway integration .

Accessing Your Gateway's Test Environment

Some payment gateways provide separate credentials for merchants to access their testing (or certification) environment, some gateways use the same credentials for testing as for the production (live) environment but direct test transactions to a different URL, and other gateways do a little of both. Authorize.net provides you the ability to both test your transactions using a developer's test account as well as testing your transactions in your live account in test mode. Testing in both your developer's account and live account in test mode are recommended by Authorize.net. We recommend reviewing this article before you begin testing.

How to Request an Authorize.net Developer Account for Testing

You can sign up for a test account on the Authorize.net Developer website . Once you have signed up, you will receive an email with your account information as well as a list of frequently asked questions and answers .

Accessing the Authorize.net Test (Certification) or Production Environment from Zuora

When configuring the Authorize.net payment gateway in Zuora, you can indicate whether you would like to use the Authorize.net test environment or the Authorize.net production environment.

• If you select Use Gateway Test Environment , Zuora will direct payment transactions to the Authorize.net certification environment at https://test.authorize.net/gateway/transact.dll

• If you do not select Use Gateway Test Environment , Zuora will direct payment transactions to your Authorize.net production environment at https://secure2.authorize.net/gateway/transact.dll

We recommend you to contact Authorize.net to request a set of test credit cards and testing scenarios. When you establish an Authorize.net Developer Test Account, you will receive an email containing your test credentials and some test credit card numbers.

Authorize.net has online documentation on testing, test credit cards, and testing scenarios. Here are some documents to review before you begin testing:

• Merchant Integration Guide

• Authorize.net Developer Website - Community Forum Discussion on Test Credit Card Numbers

Related information

• Overview of Authorize.net gateway integration

• Troubleshoot Authorize.net gateway errors