To configure the Payment Gateway for Authorize.Net:
Right-click the Location used for OnlineBill on the Location Configuration window and select Register Policy from the shortcut menu.
Click the Tender tab.
Right-click a Tender Type to be configured and select Payment Gateway > Configure to display the Payment Gateway Configuration window.
Select Authorize.Net from the Payment Gateway list.
Notes:
A warning message displays when the IDI platform detects that there has been a change in payment credentials associated with the E-Check tender types and the system is configured to use Authorize.Net's hosted payment form.
Authorize.Net has indicated this payment gateway will no longer be supported as of march 2018.
Click a row to enter the appropriate information.
Target URL
Target URL endpoint for the payment gateway as provided by Authorize.Net.
Merchant Login ID
Login ID as provided by Authorize.Net. Used with Transaction Key for authentication.
Transaction Key
Transaction key as provided by Authorize.Net. Used with Login ID for authentication.
Transaction Description
Optional transaction description sent with every transaction.
Test Mode
Note
If True, Authorize.Net is configured to send test transactions for the selected Location and Tender Type. You can also toggle the Test/Live mode via the Authorize.Net portal as described in Configuring Transaction Processing Mode. Either method works.
When in test mode at either Authorize.Net or in POS Backoffice Register Policy, primary transactions (e.g. Charge and Credit) will:
Have 000000 returned as their Approval Codes
Have transaction ID’s = 0
Not be visible in the Authorize.Net portal
Follow-up transactions (e.g. Capture and Void) against any transactions completed as described above will return simulated approval and transaction information. These transactions bypass gateway communication entirely when in test mode
Note
Be sure to review any transactions completed while in test mode to ensure live cards are not being impacted.
Transaction Details API URL
Target URL endpoint for Transaction Details calls as provided by Authorized.Net.
OnlineBill Transparent Redirect URL
Target URL redirect for the payment gateway as provided by Authorize.Net. Used by OnlineBill. This setting is ignored for E-Pay accounts.
OnlineBill Landing Page URL
Landing page URL as provided by IDI. Used to process the response from Authorize.Net. Used by OnlineBill. This setting is ignored for E-Pay accounts.
CIM Payment Account Hosted URL
URL to Authorize.Net's Customer Information Manager API.
Test - https://test.authorize.net/profile/
Production - https://secure.authroize.net/profile/
Response File Field Separator & Response File Encapsulation Character
For POS transactions that involve charges (AIM), the IDI platform uses these settings to match the delimiter and encapsulation settings at Authorize.Net. If the settings are undefined (blank), The IDI platform uses comma delimiter and no encapsulation.
Response File Field Separator - Text box allows entry of a single character. All alphanumeric and symbol characters are allowed for example, A-Z, a-z, 0-9, (Comma), | (Pipe), “ (Double Quotes) and so on. The default value = blank (when blank The IDI platform assumes comma).
Response File Encapsulation Character - Text box allows entry of a single character (same set as the Field Separator text box). Default = blank (no value specified).
POS transactions that do not involve charges (CIM) continue to work whether or not these settings match the Authorize.Net settings.
More
Authorize.Net supports configuring field separator (delimiter) and encapsulation characters for responses.
Show Picture
CostGuard uses two methods for processing responses from Authorize.Net.
AIM is used to process charge-related responses
CIM is used to process non-charge related (payment account setup) responses
AIM processing in CostGuard is set up by default to treat responses as comma-delimited with no encapsulation. If the setup on the Authorize.Net gateway does not match the CostGuard setup, AIM processing will fail in CostGuard. For example, if Authorize.Net configuration was set up to send responses as pipe-delimited and double-quote encapsulation, those responses would fail.
Note:
The Authorize.Net gateway settings do not impact CIM processing in CostGuard, nor do they impact requests sent from CostGuard to Authorize.Net.
To ensure responses processed via AIM in CostGuard do not fail due to mis-matched delimiters or encapsulation, the Authorize.Net payment gateway setup in CostGuard must support the selection of delimiter and encapsulation characters to match the setup at Authorize.Net. There are two locations in CostGuard that must support this - Register Policy setup for POS transactions, and Admin Console setup for E-Pay.
So as not to not break existing functionality for users that already have Authorize.Net gateway integration set up CostGuard, ff both settings are left undefined (blank) in CostGuard, it will continue to process responses through AIM as comma-delimited with no encapsulation.
Click OK to save the configuration settings.
Additional Settings for Authorize.Net with PCI 3.0
To prepare the system to use Authorize.Net with PCI 3.0, see:
Configuring Authorize.Net Response URLs
Customizing Authorize.Net's One-Time Payment iframe
Note
Since Drivers License fields are not available on Authorize.Net's hosted payment page, the OnlineBill Payments Configuration Setting, Require E-Check Verification Fields, is ignored.
See also:
Configuring Transaction Processing Mode
Additional Authorize.Net Information