Configuring Authorize.NET

Testing Your Setup

Authorize.NET has a live server and a testing server. Both servers behave in exactly the same way with the exception that the testing server does not perform any real financial transactions. Hence, the testing server should be used to do development work and to trial run Opentaps features such as order fulfillment to see how they behave.

The testing server requires a testing account, which is distinct from a real account. A testing account can be obtained from,

http://developer.authorize.net/testaccount/

Next, you will need to configure payment.properties for testing. The following setup is recommended,

payment.authorizedotnet.url=https://test.authorize.net/gateway/transact.dll
payment.authorizedotnet.trankey=   Transaction key of the testing account
payment.authorizedotnet.test=FALSE
payment.authorizedotnet.logging=TRUE
payment.authorizedotnet.login=     API Login key of the testing account

The test parameter should always be set to FALSE except for testing special things that will be described below.

Testing Specific Gateway Failures

Suppose you wish to see what happens when there is an AVS address verification failure (code 27) that results in an authorization being declined. We can trigger the test server to return this by using a special VISA credit card number 4222222222222 and an authorization amount equal to the error code ($27.00). Because of the validation code, you'll have to create this CreditCard record by hand and a PaymentMethod for it.

Additionally, you will have to set the test parameter to TRUE in payment.properties and restart opentaps for this to work. When you attempt to authorize $27.00 using this CC, you should get the following gateway response,

    (TESTMODE) The transaction resulted in an AVS mismatch. The address provided does not match billing address of cardholder.