Payment ServicesAuthorize.Net


Sana Commerce 9.1
Your connector

Configure Authorize.Net

To configure the Authorize.Net payment provider and payment methods you should have the Authoize.Net test/ live account with all the necessary data.

To configure Authorize.Net:

Step 1: In Sana Admin click: Setup > Ordering & checkout > Payment methods > Configuration > Authorize.Net.

Step 2: Choose the appropriate payment integration mode.

There are two modes: test and live. Test mode allows to simulate the payment process as if it is a real payment and helps to make sure that everything will behave the same way when you go live. Live mode implies that a customer makes a real purchase using already configured payment provider and methods.

Step 3: Configure the payment provider by entering the payment provider specific settings of the test/ live account.

The table below provides the description of the Authorize.Net payment provider fields:

Field Description
x_login The merchant API Login ID is provided in the Merchant Interface and must be stored securely.
Default value: depends on the PSP account (test/ live)
x_transaction_key The key which is provided by Authorize.Net.
This key and the API Login ID are the fingerprints, which provide the merchant authentication required for the access to the payment gateway.
For more information, see 'Merchant Integration Guide'.
Default value: depends on the PSP account (test/ live)
x_MD5_HashKey This value is used to authenticate the transaction response. It should be installed in the Merchant Interface.
Default value: empty string
x_relay_response This field instructs the payment gateway to return transaction results to the merchant using the HTML form POST to the merchant's webserver for a relay response.
The default values should be used only.
Default value: TRUE

Make sure that URL which you use as a Relay Response URL (x_relay_url parameter) is on port 80 (or port 443 if you have an SSL certificate installed) and is publically accessible and exists within a firewall that does not prevent Authorize.Net from connecting with it.
For testing Authorize.Net payment module the web page address which is posted to Authorize.Net as a value of x_relay_url parameter must be available from outside because it will be called by Authorize.Net.

x_test_request Indicates if a transaction should be processed as a test transaction.
The live account does not post x_test_request parameter to Authorize.Net. This parameter is needed for testing purposes.
Default value: TRUE
IpRange It is used as a security measure to prevent fraud. Some payment providers pass the payment status of an order by calling the confirm page. In this case it is possible for a malicious user to simulate this call and change the status of the order. To prevent this, a check on the IP of the call can be made by specifying the allowed IP (ranges) in this field.

Multiple values can be separated by the '|' character.

      Starting from June 30, 2016 Authorize.Net will launch a distributed network of servers over dynamics IP addresses. Thus, when it is in place, all connections to Authorize.Net will go through this new network. To be able to process transactions through a new Authorize.Net network and to avoid any problems, you should leave the 'IpRange' field empty. The IpRange field is not available in Sana starting from version 9.1.2. For more information, see 'Akamai SureRoute FAQs'.

Payment ServicesAuthorize.Net