Configuring Authorize.net

The A2Z Events Financial platform can interface with Authorize.net's API, which allows collecting credit card payments through the A2Z Global Admin and Public Site. 

The following information is required from Authorize.net in order for you to collect credit card payments in A2Z. 

Authorize.net configurations

In order to be able to reuse or refund an existing credit card, Customer Information Manager (CIM) service will need to be activated in the Authorize.Net portal.  Please see the following help article, and/or contact your Authorize.net representative for additional information: https://www.gatewaysetup.com/customer-information-manager

Please ensure that once you activate the portal you have reviewed its settings.

Additionally, please determine whether you are using  Advanced Fraud Detection Suite and ensure that no transactions that may go through the portal are placed in either the Authorized/Pending Review or Pending Review states.

Authorize.net Requirements:

1. API Login*: Combination of letters and numbers (CAPS specific)
2. Transaction Key*: Combination of letters and numbers (CAPS specific)
3. MerchID (Merchant Number): Numerical Value

*If you are using an existing Authorize.net account, the Transaction Key will need to be reset. To obtain the API Login ID and Transaction Key, please follow these steps (NOTE: you will have to answer a secret question stored in the Authorize.net account):

1. Log into the Merchant Interface at https://account.authorize.net.
2. Click Settings in the main left side menu.
3. Click API Login ID and Transaction Key.
4. Under Create New Transaction Key, enter the Secret Answer.
   Note: When obtaining a new Transaction Key, the client must choose to disable the old Transaction Key by clicking on the box titled, Disable Old Transaction Key(s). If the client does not check this box, it will take 24 hours for the old transaction key to become inactive and will prevent transactions through our system.
5. Click Submit

Configuring Authorize.net in a2z Event Configuration:

Enter the following into Event Configuration (Events > Event Settings > Event Configuration).

Paypal User Name: API Login Paypal Password: Transaction Key Paypal Merchant: MerchID Paypal Partner: <Blank> Paypal HostAddress: secure2.authorize.net (secure.authorize.net for events deployed before Apr 11, 2019)

NOTE: The HostAddress must be secure2.authorize.net in order for clients to be able to process a Payment Mode = Online Credit Card payment from a card on file (i.e., the "Select Card" drop-down). It is OK to change the HostAddress mid-show cycle. The "Select Card" drop-down will display previously used credit cards on file once you update the HostAddress. 

Testing:

Enter a small payment to ensure transactions are being processed.
NOTE: Please see below for Test mode notes, or use a live card

1. In Global Admin, go to a test Company record > Payments page > enter a $1.00 Online Credit Card payment.
2. If you get a successful message in Global Admin, confirm that it went through to Authorize.net by logging into the Authorize.net Merchant Interface. 
3. Refund the payment in Global Admin using the 'Online Credit Card Refund' Payment Mode.

Authorize.net support (How to obtain the API Login and Transaction Key) : Click Here

Test Mode

Only available for events configured after April 11, 2019

To test, the Authorize.net account must be placed in Test mode by the client using the Authorize.net Merchant Interface.

Navigate to the Event Configuration screen and change the 'Payment Gateway HostAddress' to:

secure2.authorize.net – for live mode
test2.authorize.net  – for Test mode

Common Errors in the Credit Card Log:

• This transaction cannot be accepted. -  The error indicates they have not selected the check box to Disable Old Transaction Key(s).  The client can either wait 24 hours for the old transaction key to become inactive or they can rest the API Login and check the box.
• This account has not been given the permissions required for this request. - This error most likely means the credentials were not put in the correct place in Event Configuration.
• User authentication failed due to invalid authentication values. - verify the credentials entered into Event Configuration.
• The merchant login ID or password is invalid or the account is inactive. - This error most likely means Transaction Key has been changed in Authorize.net, and must be updated in a2z.  Or, Authorize.net representative should be contacted for further questions.
• The referenced transaction does not meet the criteria for issuing a credit. - ensure that  Customer Information Manager (CIM) service is configured and there are no rules in place to prevent reusing the token from previous transactions.