Installation and Configuration of the Authorize.Net Integration

Overview

SugarCRM enables businesses to create extraordinary customer relationships with the most empowering, adaptable, and affordable customer relationship management (CRM) solution on the market. Authorize.Net enables merchants to authorize, settle and manage credit card and electronic check transactions via Web sites, retail stores, mail order/telephone order (MOTO) call centers, and mobile devices.

 

The Faye Sugar – Authorize.Net Integration Application allows you to securely enter credit card billing information on Authorize.Net from within SugarCRM. Authorized.Net users are able to charge and authorize credit cards for specific amounts. When using this enhancement, your client profiles and billing information will be organized and safely stored for easy access. 

 

Key Benefits

• Safe and simple credit card transactions that are in compliance with
  all credit card laws.
• Protection of all your client profiles and billing information
• Create quick and easy profiles with credit card data for all your
  customer quotes.
• Avoid re-entering billing information for returning clients.
• Fast and secure client billing and reprocessing of payments
• Easy updating of all customers' billing information.

 

Table of Contents

1. System requirements
2. Installation
3. Configuration

1. System requirements

• cURL enabled on web server
• Sugar v12.0.0 or above Professional, Enterprise or Ultimate Edition
• Active Authorize.Net account
• Active Subscription to Authorize.Net Customer Information Manager

 

2. Installation

Before installing Jira to your SugarCRM instance please make sure you have the following items at hand:

• FayeBSG_Sugar_-_Authorize.Net_Integration-v2.2.1.zip

Please follow the steps in this guide to install the package.

 

 

3. Configuration

Note: You may have to log out and log back in in order for the Authorize.Net Configuration section to appear on the Admin screen.

1. Navigate to the Admin screen, scroll to the bottom, and click on Authorize.NetSettings link.

Note: If you see a blank page or an error instead of Authorize.Net Settings just click on the back button in your browser and the Authorize.Net Settings will load.

2. Enter your Authorize.Net API Login Key, Authorize.Net API Transaction Key, the FBSG License Key, and turn on or off the Allow Customer Profiles to be made from Orphaned Transactions? (see the Create Customer Profiles from Orphaned Transactions section), and select the Test Account checkbox ONLY if you are using an Authorize.Net test account, then click the Save button.

 

Note: You will need to click on the Edit button in order to insert the API Transaction Key.

 

3. By default no users are able to edit billing profiles or change or authorize cards. Use the permissions section to set the permissions for each user and then click the Save button.

 

4. If you DO have your API Login ID or Transaction Key then go to the Using the Authorize.Net Integration guide. Otherwise, continue to the next step.

 

 

API Login ID and Transaction Key

5. Authorize.Net billing profiles in Sugar are linked through the Authorize.Net API Login Key.

Note: If the API Login Key is changed, those billing profiles will NO longer be available for charging or authorizing. If the API Login Key is changed back to its original value, those profiles will once again be available.

 

6. First, Log in to your Authorize.Net account.

https://account.authorize.net/ regular account
https://logintest.authorize.net/ test account

 

7. Click on Account.

 

8. Click on the API Credentials & Keys link under the Security Settings section.

 

9. Your API Login ID will be available directly on this page.

 

10. To get a new valid transaction key you will need to Verify your Identity in the popup window that you will see once you click on Submit. An email with a Pin will be sent to your account email address.

Note: You can choose to disable old transaction keys immediately by checking the Disable Old Transaction Key(s) checkbox. However, ALL old transaction keys will expire 24 hours after the creation of a new Transaction Key regardless if you do not check the box.

 

11. Once you have received your pin, you will be prompted to introduce it in the same popup window, on the next page, then click on Verify Pin.

 

12. On the next page of the popup window you will be informed that your identity was verified. Click on Continue.

 

13. Your new Key will appear on the main screen. You can Copy to Clipboard in order to use it in step 2 above.

 

Your Authorize.Net integration with Sugar is now configured. Please refer to the other guides in this section for more aspects of the integration.