Authorize.net is available only in the UK, North America, and Australia. For an overview of payment providers available in your country, click here.

Authorize.net is a useful payment provider because it can act as a gateway to other merchant accounts from merchant service providers like Heartland. Authorize.net can also provide both in their all-in-one option.

• A gateway is a service that authorizes payments.
• A merchant account is a bank account that assures you'll get paid when a customer purchases from you.

Setup instructions

1. Obtain your Transaction Key and API Login ID from Authorize.net.
   
   1. Register for an account with Authorize.net.
   2. Once you register, Authorize.net will display your Transaction Key and API Login ID. Copy both.
   3. In eCom on the left menu of the Back Office, click Settings and from Payment Settings click Payment Providers.
   4. At the top-right corner of the screen, click Add a payment provider and add Authorize.net.
   5. Paste the Transaction Key and API Login ID into the relevant fields.

      

   6. Ensure no extra spaces are pasted along with the credentials by checking for spaces before and after the Transaction Key and API Login ID.
   7. Click Save.
2. Obtain your Signature Key.
   1. Log into the Merchant Interface at https://account.authorize.net.
   2. Click Account from the main toolbar.

      

   3. Click API Credentials & Keys.

      

   4. Select New Signature Key.
   5. Enable the checkbox labeled Disable Old Signature Key Immediately.
   6. Click Submit.
   7. Request and enter PIN for verification.
   8. Your new Signature Key is displayed. Click Copy to clipboard.
   9. Paste this signature inside Lightspeed eCom.
   10. In your eCom Back Office, click Settings from the main menu on the left-hand side of the screen.
   11. Click Payment Providers from inside the column titled Payment settings.
   12. Click Authorize.net.
   13. Paste the key in the field labeled Signature key.
   14. Ensure no extra spaces are pasted along with the credentials by checking for spaces before and after the Signature key.
   15. Delete any content in the field labeled MD5 Hash, if this field is visible.
   16. Click Save.
3. Add a Relay Response URL.
   1. Log in to your Authorize.net account and click Account.
   2. Click Relay Response.
      
   3. In the URL field enter your web address starting with https://.
      For example, if your web address is www.example.com, enter:
      https://www.example.com.
   4. Click Submit.
      
4. Manually configure card code verification (CCV).
   1. Log in to your Authorize.net account and go to Account > Settings > Payment Form > Form Fields.
   2. Enable both the View and Edit options next to Card Code.
   3. Then, go to Account > Settings > Card Code Verification.
   4. This page allows you to specify how invalid responses are handled during card code validation. You can keep the default settings or modify them to your preferences.

      

5. Test the Authorize.net integration without processing payments.

   1. Log into your Authorize.net account and go to Account > Test Mode.
   2. Toggle the switch labeled Transaction Processing to Test.

      

   3. In the eCom Back Office > Settings > Payment providers > Authorize.net,  switch the dropdown box labeled Mode to Test.
   4. Select which card types you'll accept, and configure the other payment information.
   5. Toggle Activate this payment provider to on.

      

   6. Click Save.

   7. Create a test transaction in your eCom store by buying something from as if you were a customer. Complete the checkout process by entering your address information, selecting any shipping method, choosing Authorize.net as the payment method, confirming your order, and clicking Buy.

   8. Your test is successful if you are redirected to an Authorize.net form asking you to enter your credit card details. It means that the Transaction Key, API Login ID, and the Signature key are correct. Your test is unsuccessful if you see an error screen. See the troubleshooting section here for more information.

6. Ensure the Authorize.net integration and transaction processing settings are set to live.
   1. Log into your Authorize.net account and go to Account > Test Mode.
   2. Toggle the switch labeled Transaction Processing to Live.
   3. In the eCom Back Office > Settings > Payment providers > Authorize.net,  switch the dropdown box labeled Mode to Live.
   4. Click Save.
7. Your setup is complete. Authorize.net is now ready to process live transactions.

Troubleshooting

Orders marked as paid without a captured payment

Using the fraud filter action Do not authorize and hold for review in Authorize.net can cause your orders in eCom to be marked as Paid, even through they are not authorized in your merchant interface. This can be prevented by selecting an alternative filter action or disabling the specific fraud filter.

1. Open the Authorize.net merchant interface.
2. Under Tools, select Fraud Detection Suite.
3. Open the first fraud setting that has Review in the Configuration column.
4. Under Filter Actions, select any other action. Or disable the filter at the top of the screen by deselecting Enable Filter.
5. Select Save.
6. Repeat for any other fraud settings marked with Review in the Configuration column.

Error after completing checkout

Receiving an error after completing checkout is usually caused by an issue with your credentials in the eCom admin or fraud filters in Authorize.net.

Blank spaces in copied credentials

Almost always, the cause of errors is blank spaces before or after the API Login ID, Transaction key, or Signature key.

1. In the eCom Back Office, click Settings > Payment providers > Authorize.net.
2. Check for blank spaces in the Authorize.net credentials. They are very easy to miss, so it is recommended you deliberately check each field by adding your cursor before and after the API Login ID, Transaction key, and the Signature key.
3. If a space is found, delete it and test Authorize.net again using the instructions in Step 4 above.

Incorrect credentials

It is also possible that the API Login ID, Transaction Key, or Signature Key is entered incorrectly. You can verify your API Login ID and request the new Transaction Key and Signature key by following the setup steps above for obtaining a Signature Key.

1. To obtain a new Signature Key, follow the steps located here.
2. While following the process you can verify your API Login ID on the API Credentials & Keys screen.
   
3. During the process, in order to obtain the Transaction Key, select New Transaction Key instead. Remember to enable the checkbox to Disable old Transaction key/Signature key immediately.
4. Once you've added your new credentials, check for spaces, then test Authorize.net again using step 4 in the above setup instructions.

Incompatible Fraud Filters

The eCommerce fraud settings in Authorize.net related to IP filtering should be disabled to prevent the payment from being declined. Authorize.net does not support the kind of IP addresses used by Lightspeed. Lightspeed is using IPV6 whereas Authorize.net uses IPV4.

1. Open the Authorize.net merchant interface.
2. Under Tools, select Fraud Detection Suite.
3. Under E-Commerce Settings, open IP-Shipping Address Mismatch Filter.
4. Disable it by deselecting the Enable filter checkbox. Select Save.
5. Repeat for the Regional IP Address Filter.