Add-ons and ModulesAuthorize.Net PSP Module

Authorize.Net PSP Module

Sana Commerce 8.2
Your provider

Back Next

Authorize.Net Specific Configuration Values

The table below provides the description of the Authorize.Net payment module configuration values:

Name	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
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
x_delim_data	In order to implement a relay response, this field must be submitted with a value of FALSE or the merchant has to configure a relay response through the Merchant Interface. The default value should be used only. Default value: FALSE
x_show_form	The show form field indicates that the merchant wishes to use the payment gateway hosted payment form to collect payment data. Default value: PAYMENT_FORM
x_MD5_HashKey	This value is used to authenticate the transaction response. It should be installed in the Merchant Interface and specified in the 'web.config' file. Default value: empty string
x_version	The transaction version represents the set of fields that is included with the transaction response. 3.0 is the default version. 3.1 allows the merchant to utilize the Card Code feature, and is the current standard version. The default value should be used only. Default value: 3.1
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
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
x_relay_url	If this field is submitted, the payment gateway will validate the URL value against the Relay Response URL configured in the Merchant Interface. If the URL submitted does not match the URL configured in the Merchant Interface, the transaction will be rejected. If no value is submitted in the HTML Form POST, the payment gateway will post the transaction results to the URL configured in the Merchant Interface. This must be a relative URL. Default value: RelayResponse.aspx
return_url_success	The URL within the Sana webshop to which the user will be redirected when a payment is successfully ended within PSP. This must be a relative URL. Default value: checkout/ordersubmit.aspx?id=
return_url_error	The URL within the Sana webshop to which the user will be redirected if an unexpected error occurs while trying to pay at the PSP website. This must be a relative URL. Default value: checkout/orderfailed.aspx?id=

More detailed information about general configuration values of the external payment method can be found here.

If you want to post some optional parameters open the 'web.config' file of the Sana Commerce frontend. Locate the <payment-configuration> node in the <sanaCommerce> configuration section, where several modules are defined, which implement different payment methods. The 'Authorize.Net' module is only needed. Here you can add the new configuration entry in the following format:

<add name="[parameter name]" value="[parameter value]" isRequestParameter="true" />

Back Next

Add-ons and ModulesAuthorize.Net PSP Module

Sitemap

Installation

Product Versions

Links

Sana Commerce does not accept any liability for the content of this website, or for the consequences of any actions taken on the basis of the information provided. The information below should be interpreted as an example. No rights can be derived from this information.

Sana Commerce – the integrated e-Commerce solution for Microsoft Dynamics NAV & AX

Updated: January 2013